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."
There’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.
On the surface, the world of agile software development is bright, since it is now mainstream. But the reality is troubling, because much of what is done is faux-agile, disregarding agile's values and principles. The three main challenges we should focus on are: fighting the Agile Industrial Complex and its habit of imposing process upon teams, raising the importance of technical excellence, and organizing our teams around products (rather than projects).
It actually doesn't matter whether you actually have a formal retrospective. It doesn't matter whether you have four or five labels of things on your retro board, or exactly how you do the retro. What does matter is the notion of thinking about what we're doing and how we can do better, and it is the team that's doing the work that does this, that is the central thing.
Interestingly, just as software people were talking about how we need to kind of follow this very Taylorist notion as the future of software development, the manufacturing world was moving away from it. The whole notion of what was going on in a lot in manufacturing places was the people doing the work need to have much more of a say in this because they actually see what's happening.