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? | Win rate >30%. 49% live but inaccessible — 2 blockers gate everything. |
| Value Stream Map | Where does time die? | 7% flow efficiency — 40h work in 35 days. Bid prep is #1 bottleneck. |
| Dependency Map | What must happen first? | 3 hard deps (auth, permissions, ventures query). Fix 2 things → unlock 20 features. |
| Capability Map | What can we actually do? | 31 capabilities: 20 live, 3 dormant, 5 partial, 2 broken, 1 gap. |
| A&ID | How do agents orchestrate? | 4 agents, 6 instruments, 4 loops. The answer library IS the moat. |
Templates: docs/pictures/patterns/
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) |
|---|---|---|
| "Built for how they sell" | Outcome: win rate >30%, 4 binary success measures | Sprint 0: wire 3 dormant algorithms |
| "70% auto-fill, empty library" | Value Stream: 7% flow efficiency, bid prep is #1 waste | Sprint 1: seed library with 1 real RFP |
| "App complete, auth broken" | Dependency: 3 hard deps, 14-day critical path | Commissioning: 32 components, % complete |
| "Six days wire three algorithms" | Capability: 31 capabilities, 20 live, 3 dormant | Feature/Function/Outcome: 41 rows with states |
| "Lost the bid nobody tracked" | A&ID: 4 agents, 6 instruments, compound flywheel | Sprints 2-4: company entity, activity logging, data quality |
Context
- PRD Index — Sales CRM & RFP
- Prompt Deck — 5-card pitch
- Spec — Engineering depth
Questions
What is the most important visual missing from the sales crm rfp picture set — and why does it matter?
- Which relationship between elements in this diagram is most underspecified — and what would happen if it were wrong?
- If this picture were shown to a new engineer on day one, what would they misunderstand — and how should the picture be changed?
- What assumption does this visual make that should be made explicit in the spec?