What are we building for?
Most organizations that build technology have become better at looking effective than at being effective. The plans run on time. The dashboards stay green. And brilliant work goes, at enormous scale, into things no one needed, while the best people slowly stop bringing their ideas to the room.
It is a particular ache: being skilled at something you have quietly stopped believing in.
The work rarely fails where people look. An excellent team still loses to a strategy that never says no, to a portfolio that grades every new idea on the old business's numbers, to a structure where honesty costs too much. The weakest part sets the ceiling for all the rest. Fixing your favorite part changes nothing.
What We Build For is a book about that whole chain: six parts, from strategy to the human conditions, with purpose running through them all. It is written for the tech lead, the architect, the product manager, the engineer, and the leaders above them.
The book is finished and with early readers. It will be here, in print and for Kindle, when it is out.
If you would rather feel it than read the argument, the short version is free.