before we build — opening
Opening
Previously, we described what happens to understanding when it crosses a boundary. Each crossing compresses it. Language approximates experience. Briefs approximate conversations. Code approximates specifications. By the time software runs, the original problem may be unrecognisable — not because anyone was careless, but because the chain had no mechanism to preserve what mattered.
This volume is about the work that happens before the first boundary is crossed. While the understanding still lives in its original form — in the person who has the problem, in the system that is failing — there is still a chance to capture it with enough fidelity that it survives what comes next.
That work has three phases. Each holds a different question and catches a failure mode no other phase catches. The structure is not overhead — collapse any of the three and the failure mode it held becomes invisible. It still happens. It just happens without a name.
| Phase | The question it holds | The failure mode when absent |
|---|---|---|
| Direction | Why do we exist and for whom? | Every scope conversation restarts from scratch. Features survive on confidence, not on fit with anything named. |
| Intent | What specific gap are we betting on? | Features succeed individually while the situation never changes — and no level of the chain holds that observation. |
| Discovery | Did we witness it or just describe it? | The solution is built for the problem as assumed, not as it exists. The assumption surfaces in production. |
Two stories run through all of it. Gal is a science teacher whose exam grading costs 47 minutes every cycle in a way she has stopped noticing. Uri runs billing operations whose monthly subscription cycle drops charges silently in a way the team has normalised. Same three phases. Two different kinds of problem.