What does success look like — in terms anyone can explain without reading the spec?
OUTCOME MAP: PROMPT DECK
════════════════════════════════════════════════════════════
DESIRED OUTCOME
A person compresses their world into five priorities
on one page — the empty cells become their strategy —
and they return weekly to update it.
│
├── Contributing Factors
│ ├── CDD prototype explored 5 interaction patterns (Mission Control, Stack, Morning Pages, Compass, Conversation)
│ ├── Figma template validates visual design for 5x5 grid
│ ├── 1,200+ pages of 5P-structured content prove the pattern works at scale
│ ├── The mental model site IS a filled Prompt Deck at portfolio scale
│ ├── Stackmates provides auth and session management
│ └── Convex provides real-time collaborative data layer
│
├── Obstacles
│ ├── Zero external users → need 10 fills to validate thesis
│ ├── "What if I pick the wrong five?" → grid self-corrects (wrong picks won't fill)
│ ├── People fill once, never return → snapshot comparison + weekly review ritual
│ ├── Investors expect slides, not grids → export to presentation + share link
│ ├── Blocked by Agent Platform + Identity → persistence requires auth
│ └── "Self-reflection tools feel cringe" → frame as strategy instrument, not journal
│
├── Investigations (answer before committing)
│ ├── Do external users fill ≥15 of 25 cells in first session? [Owner: Wik, user testing]
│ ├── Do they return within 7 days? [Owner: Wik, D7 tracking]
│ ├── Which pattern (Mission Control vs Stack) has higher completion? [Owner: Eng, A/B]
│ └── Does Pep Talk or Pitch mode drive more return visits? [Owner: Wik, tracking]
│
├── Success Measures (binary)
│ ├── ≥10 external users fill a grid → YES / NO
│ ├── D7 return rate > 35% → YES / NO
│ ├── Grid completion rate > 60% of cells → YES / NO
│ └── ≥3 grids shared externally → YES / NO
│
├── Roles (RACI)
│ ├── Accountable: Wik (product decisions, kill date, user testing)
│ ├── Responsible: Engineering team (build), Wik (pilot recruitment)
│ ├── Consulted: 5 test users (founders from existing network)
│ └── Informed: Engineering repo via commissioning table
│
└── Next Actions (momentum within 48 hours)
├── Wire Convex persistence to CDD prototype (Sprint 0, day 1)
├── Recruit 5 pilot users from founder network (parallel with build)
└── Define 3 starter templates: Personal, Venture, Industry (Sprint 2)
════════════════════════════════ ════════════════════════════
Gate
Before moving to Value Stream Map:
- Desired outcome is crisp: "compress into five priorities, empty cells become strategy, return weekly" — YES
- Contributing factors have evidence: prototype exists, visual design done, 1,200+ pages prove pattern
- Obstacles have mitigations assigned: each has a counter-strategy
- Investigation questions have owners: Wik (user testing, tracking), Eng (A/B)
- Success measures are binary: all four are YES/NO with thresholds
- RACI is complete: one Accountable, clear ownership chain
- Next actions are assigned: three tasks with owners and timing
Context
- Value Stream Map — Next: where does time die?
- Outcome Map Template — The empty pattern
- Spec — Full depth