Skip to content

✦ Why We Build

On the fragility of understanding, the cost of losing it, and what it means to build software that actually changes someone's situation.

This is the shortest of the five volumes. It contains no method, no template, no checklist. It is the worldview that every later practice serves — that something is always lost when understanding crosses a hand, and that the discipline of how we work is, at root, the discipline of losing less.

The five essays

  1. OpeningSomething is always lost when understanding crosses a hand. The compression of meaning across every boundary in the chain.
  2. What Gets LostObservation reveals what accommodation has made invisible. The receptionist who said her morning was "busy."
  3. The Cost of Losing ItTrust is not built by delivering features. It is built by delivering features that change what was promised they would change. The invisible erosion of the condition under which good work is possible.
  4. The Second QuestionDid shipping it change what we said it would change? The question most teams skip. The discipline of confidence.
  5. The Invisible GroundThe discipline is not about process. What kind of work becomes possible when meaning survives the crossings.

Begin the opening →


Supplementary — Direction (transitional)

The pages below are operational content (Vision, Mission, Goals, OKRs, Initiative Identification, Value Declaration, Financial Translation, Client Relationship Strategy, Portfolio Direction). In the PDFs, this material lives in Volume II's "Direction" section, not in Volume I. They sit here as a transition while Volume II's restructure is in progress. Treat them as supplementary; they will move to /cycle/before-we-build/ when Phase 2 executes.

200apps · How We Work · NWIRE