Sprint (Jake Knapp et al.)
Problem
Small problems do not justify a focused sprint.
Action
Select one important challenge with meaningful value before the sprint begins.
Outcome
The team focuses its efforts on work that matters.
Chapter: Set the Stage - Challenge: Start with a big problem
Problem
Unclear roles and missing perspectives weaken decision-making.
Action
Include a Decider, a Facilitator, and people with different expertise.
Outcome
The team makes better decisions more quickly.
Chapter: Set the Stage - Team: Get a Decider, a Facilitator, and a diverse team
Problem
Interruptions reduce focus and slow progress.
Action
Reserve five full days in a room prepared for sprint work.
Outcome
The team stays focused throughout the sprint.
Chapter: Set the Stage - Time and Space: Schedule five days and find the right room
Problem
Teams lose direction without a shared destination.
Action
Agree on the long-term goal before discussing solutions.
Outcome
Every decision supports the same objective.
Chapter: Monday - Start at the End: Agree to a long-term goal
Problem
Complex problems are hard to solve without a shared view.
Action
Draw a simple map showing the main customer steps.
Outcome
The team identifies where to focus.
Chapter: Monday - Map: Diagram the problem
Problem
Weak assumptions lead to poor solutions.
Action
Interview teammates and other experts to gather key insights.
Outcome
The team creates ideas based on real insights.
Chapter: Monday - Ask the Experts: Interview your teammates and other experts
Problem
Trying to solve everything slows progress.
Action
Choose one important point on the map as the sprint target.
Outcome
The team concentrates its effort where it has the most impact.
Chapter: Monday - Target: Choose a focus for your sprint
Problem
Starting from nothing wastes valuable time.
Action
Study existing solutions and adapt the best ideas.
Outcome
The team develops stronger concepts faster.
Chapter: Tuesday - Remix and Improve: Look for old ideas and inspiration
Problem
Incomplete ideas are difficult to evaluate.
Action
Create a detailed sketch that explains one complete solution.
Outcome
The team compares ideas more fairly.
Chapter: Tuesday - Sketch: Put detailed solutions on paper
Problem
Open discussion can favor opinions over evidence.
Action
Review ideas independently before making the final selection.
Outcome
The strongest solutions are more likely to be chosen.
Chapter: Wednesday - Decide: Choose the best solutions without groupthink
Problem
Choosing one idea too early can hide a better option.
Action
Keep strong alternative solutions available for testing.
Outcome
The team learns which approach works best.
Chapter: Wednesday - Rumble: Keep competing ideas alive
Problem
Building without a clear plan causes confusion.
Action
Lay out the complete customer experience in a storyboard.
Outcome
The prototype follows a consistent flow.
Chapter: Wednesday - Storyboard: Make a plan for the prototype
Problem
Building a complete product takes too much time.
Action
Create a realistic prototype that appears finished without full functionality.
Outcome
The team validates ideas more quickly.
Chapter: Thursday - Fake it: Build a façade instead of a product
Problem
Poor coordination delays prototype development.
Action
Assign clear parts of the prototype to team members using suitable tools.
Outcome
The prototype is completed efficiently.
Chapter: Thursday - Prototype: Find the right tools, then divide and conquer
Problem
Waiting for large studies delays useful learning.
Action
Observe five target customers as they use the prototype.
Outcome
The team uncovers the most important issues quickly.
Chapter: Friday - Small Data: Get big insights from just five customers
Problem
Leading customers produces unreliable feedback.
Action
Let customers interact naturally while asking neutral questions.
Outcome
The team learns how customers really think and behave.
Chapter: Friday - Interview: Ask the right questions
Problem
Individual reactions can be misleading.
Action
Review all interview results and identify repeated findings.
Outcome
The next decision is supported by clear evidence.
Chapter: Friday - Learn: Find patterns and plan the next step
Problem
Sprint momentum fades without a clear follow-up.
Action
Decide the next concrete step before the sprint ends.
Outcome
The work continues without delay.
Chapter: Liftoff: One last nudge to help you start