The questions this sprint answers
- ·What's the path from first touch to done?
- ·What's the riskiest assumption we need to test?
- ·What's the most important thing on each screen, and does it read that way?
- ·What are our tokens — color, type, spacing, radius?
Decisions we'll make together
- ·The path from first touch to done
- ·Where people drop off, and the fix
- ·The riskiest assumption to test
- ·What counts as a pass
Week 1 · Get unstuck
- MonWorkshop — We confirm the scope, check the foundation, and agree what we're testing and how.
- TueExplore — Research, and two or three directions for flow, prototype, interface and system.
- WedExplore — The directions, taken far enough to compare honestly.
- ThuShape — The strongest direction, sharpened for the lock.
- FriDirection lock — We review the directions together and commit to one.
Week 2 · Get something real
- MonMake — The chosen direction, built out.
- TueMake — The core of it, made real.
- WedRefine — A review together, then the fixes it turns up.
- ThuTest — Checked against what we set out to learn, and finished.
- FriDelivery — A walkthrough, and everything lands in your Hub.
You leave with: A user journey · A screen map · A clickable prototype · A test plan you can run · Key screens, designed · Specs a developer can build from · Design tokens · A component library