How did we arrive at this proposal — and how do we track that value is delivered?
| Map | Question | Key Finding |
|---|---|---|
| Outcome Map | What does success look like? | 10 users fill a grid, D7 return > 35%, 4 binary measures. |
| Value Stream Map | Where does time die? | 2% flow efficiency — 5 hours work in 16 days. Step 5 (Update) never happens. |
| Dependency Map | What must happen first? | 2 hard deps (Identity, Convex). 22 engineering days + Identity fix wait. |
| Capability Map | What can we actually do? | 7 of 17 at maturity 3+, 10 to build. 60% composition, 40% new. |
| A&ID | How do agents orchestrate? | 3 agents, 5 instruments, 4 loops. Instrument adds capability in 5 phases. |
Templates: docs/pictures/templates/
The Bridge
Pictures sit between sales and engineering. The prompt deck sells the vision in five cards. The spec builds the machine. These five maps prove the thinking is sound.
| Prompt Deck (sales) | Pictures (bridge) | Spec (engineering) |
|---|---|---|
| "Five things, one page, gaps visible" | Outcome: 10 users fill, D7 > 35%, 4 binary measures | Sprint 0: auth scaffold, data model, grid component |
| "One return visit proves everything" | Value Stream: 2% flow efficiency, UPDATE never happens | Commissioning: 10 components, % complete |
| "Five patterns explored, zero persistent" | Capability: 7/17 at maturity 3+, 10 to build | Build sequence: 3 sprints, acceptance tests |
| "Fill, find gaps, return, compound" | A&ID: 3 agents, 5 instruments, 4 feedback loops | Feature map: 10 features with state |
| "Founders first, teams second, everyone" | Dependency: 2 hard deps, 22-day path + Identity wait | Players: 3 JTBD, ICP psycho-logic |
Context
- Prompt Deck PRD — Decision surface
- Prompt Deck — Sales: five cards, scannable
- Spec — Engineering: full depth
- Pictures Templates — Empty patterns to fill