Sprint
1. The question this book addresses
Can important ideas be validated in a short amount of time?
- Process
- Monday: define the problem, Tuesday: sketch solutions, Wednesday: decide
- Thursday: prototype, Friday: test with customers
- Core goal
- Learn something important instead of shipping a finished product
- Quickly verify the riskiest assumptions instead of debating for too long
2. What designers can take away
Connect planning, design, and research into one learning loop
- Team work
- Compare each person’s sketches structurally rather than deferring to the loudest voice
- Move to the next step with accountable decisions instead of forcing consensus
- Prototype
- Make it concrete enough that customers feel it is real, even if it is not an actual product
- Focus on the key flow where you can observe reactions rather than polish
3. How to apply it right away
Start by organizing the most important questions you can learn within one week
- Sprint questions
- Write down what you need to know by the end of this week for it to be a success
- Decide first which customers to test and which behaviors to observe
- Storyboard
- Draw only the 6–8 steps of encountering the problem and experiencing the solution, not every screen
- Instead of asking whether it is good, have people actually use it and record where they get stuck
