Pipeline Nowcast Pictures
Five pre-flight maps for the composite variance algorithm.
| Map | Question | Key Finding |
|---|---|---|
| Outcome Map | What does success look like? | Single composite score replaces five dashboards |
| Value Stream Map | Where does time die? | Manual status meetings are the bottleneck |
| Dependency Map | What must happen first? | CRM + agent comms already flow; forecast baselines are the gap |
| Capability Map | What can we actually do? | Algorithm patterns proven; signal normalization is new |
| A&ID | How do agents orchestrate? | Nowcast Engine reads 5 instruments, one feedback loop |
Bridge
| Picture | Driving Word | Feeds |
|---|---|---|
| Outcome Map | Variance — actual vs forecast | Spec: success criteria |
| Value Stream Map | Latency — signal to decision | Spec: performance targets |
| Dependency Map | Coverage — minimum signals | Spec: confidence calculation |
| Capability Map | Composition — 80% reuse | Spec: build ratio, platform |
| A&ID | Feedback — drift triggers action | Spec: recommendations engine |
Context
- PRD Index — Pipeline Nowcast
- Prompt Deck — 5-card pitch
- Spec — Engineering depth
Questions
What is the most important visual missing from the pipeline nowcast 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?