Field note5 min read
A spike with explicit exit criteria
We front-load alignment: one page on the job-to-be-done, constraints, and definition of success. Every artifact maps back to that page.
10-day rhythm
- Day 1: problem framing + risks with sponsor and tech lead
- Day 3: prototype flows + feasibility notes; book user co-design
- Day 8: decision memo with options, cost, appetite, and recommendation
Tip
Ship the decision memo even if you defer the build—it becomes the north star for future teams.
Decision memos force clarity. Keep options, constraints, appetite, and risks on one page so execs can trade scope without meetings.
Stakeholder map
- Sponsor: approves appetite and success criteria
- Tech lead: owns feasibility notes and risks
- Design: validates desirability with 3 user touchpoints
Key takeaways
- 10-day spikes
- Decision memos
- Joint squads
DiscoveryWorkshopsDecision Making
