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+ scored prospects/week → 5 calls/month. 4 binary measures. |
| Value Stream Map | Where does time die? | 0.7% flow efficiency — 80min work in 13 days. Follow-up is #1 bottleneck. |
| Dependency Map | What must happen first? | 3 hard deps, but P1 gaps have only soft deps — start immediately. |
| Capability Map | What can we actually do? | 10 of 16 at maturity 3+, 6 at zero. 80% composition, 20% new. |
| A&ID | How do agents orchestrate? | 3 agents, 6 instruments, 4 loops. Agent activates 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) |
|---|---|---|
| "Qualify before contact" | Outcome: 5 calls/month, binary success measures | Sprint -1: Resend env vars, LinkedIn OAuth |
| "Five calls, fifteen percent" | Value Stream: 0.7% → 7% flow efficiency target | Commissioning table: 13 components, % complete |
| "80% composed, 20% new" | Capability: 10/16 at maturity 3+, 6 to build | Feature/Function/Outcome: 13 rows with states |
| "Research, score, compose" | A&ID: 3 agents, 5 instruments, 4 loops | WorkChart: 5-stage routing with adaptive logic |
| "Two ICPs, two paths" | Dependency: 3 hard, 7 soft, 17 days critical | Players: 5 JTBD, ICP psycho-logic, revenue model |
Context
- Sales Dev Agent PRD — Decision surface
- Prompt Deck — Sales: five cards, scannable
- Spec — Engineering: full depth
- Pictures Templates — Empty patterns to fill