the translation — resolution increases by phase
Resolution increases by phase
None of these failures look like failures while they're happening. The Epic that was named after a system area looks productive — it has stories underneath, those stories sit in columns on a kanban board, the board moves left to right, the roadmap looks healthy. The team is moving fast. The substitution is invisible because each artifact is internally consistent. Every link in the chain is honest. The chain just isn't connected to the problem at the other end.
The discipline that prevents this is not more documentation. It is asking, at every gate, whether the resolution of understanding is enough for what comes next. Not maximum understanding — that is over-shaping, expensive and wasteful. Not minimum understanding — that is under-shaping, the work that ships the wrong thing. Enough. The phases of this volume each name a resolution: just enough to do the thing the next phase requires, and no more.
Backbones are enough to map. Wireframes are enough to amigos. Scenarios are enough to pull. Each phase produces only the resolution the next phase needs.
Each part closes with a resolution gate — what counts as enough understanding before the next phase begins. The gate is what the team checks. Failing it means staying in the current phase a little longer. Passing it without checking is the substitution failure with another name.