System

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

1. MonWorkshop — We confirm the scope, check the foundation, and agree what we're testing and how.
2. TueExplore — Research, and two or three directions for flow, prototype, interface and system.
3. WedExplore — The directions, taken far enough to compare honestly.
4. ThuShape — The strongest direction, sharpened for the lock.
5. FriDirection lock — We review the directions together and commit to one.

Week 2 · Get something real

1. MonMake — The chosen direction, built out.
2. TueMake — The core of it, made real.
3. WedRefine — A review together, then the fixes it turns up.
4. ThuTest — Checked against what we set out to learn, and finished.
5. FriDelivery — A walkthrough, and everything lands in your Hub.