recycling
Turn them into cycles
A side that goes unrecognized
The mirror-image economy
When we enter the world of refuse and waste, we cross over into a mirror-image economy. In the "normal" world, we pay to acquire things; on the other side of the looking glass, we pay to get rid of them. Junk isn't merely worthless; it has negative value.
A chemical engineer once told me about a recent improvement in a manufacturing process; by fine-tuning a chemical synthesis he had increased the yield of a certain commodity from 98 percent to 99 percent. I congratulated him, but I couldn't help remarking that this seemed like a rather paltry improvement. "Ah, you miss the important point," he said. "The amount of waste goes from 2 percent down to 1 percent. It's cut in half. We save tremendously on disposal costs."
Hints towards a non-extractive economy
An Article by Matt WebbThere’s a movement called the circular economy which is about designing services that don’t include throwing things away. There is no “away.”
A non-extractive economy is going to look very different to today’s economy. These points feel opposed somehow but they are part of the same movement:
- With CupClub, it’s all about infrastructure.
- With the battery-free Game Boy, it’s untethered from infrastructure: once manufactured, no nationwide electricity grid is required to play.
We’ll need better tools to track and measure. There will be new patterns for new types of services. New technologies to build new products. New language. So it’s fascinating seeing the pieces gradually come together.
The Fidelity Curve
How do we choose which level of fidelity is appropriate for a project?
I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing.
I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing.
Four levels of fidelity
Suppose we have four levels of fidelity…
- Rough sketch (on paper or an iPad)
- Static mock-up (eg. Photoshop or Sketch)
- Interactive mock-up (eg. Framer, InVision)
- Working code prototype (HTML/CSS, iOS views)
Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained
Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it.
Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.