library / lib83ce021c288e7718
Sprint_ How to Solve Big Problems and Test New Ideas in Just Five Days
In a sentence
A step-by-step playbook for running a five-day 'sprint' that lets teams answer their most important questions by prototyping and testing ideas with real customers before committing significant time and money.
Sprint distills the methods Jake Knapp, John Zeratsky, and Braden Kowitz developed and refined across 100+ engagements at Google Ventures into a practical, day-by-day guide for solving big problems fast. Instead of endless meetings, churning email, and months-long projects built on untested assumptions, a sprint compresses the work into a single focused week: Monday you map the problem and pick a target, Tuesday you sketch competing solutions, Wednesday you decide which to test, Thursday you build a realistic façade-style prototype, and Friday you put it in front of five target customers and learn. Rich with stories—a hotel-delivery robot, a coffee company's online store, a cancer-trial matching tool, fitness software, and workplace messaging—the book shows that any challenge, no matter how large, can benefit because you solve the surface first and learn the hard way without the hard way. It's a book for experts and beginners alike who have a big opportunity or problem and need to start with confidence.
The four lenses
- Science
- Statistics
- Systems
- Strategy
Tags
The model
A causal framework in which structured design levers and team conditions produce focused team states (shared understanding, concrete solutions, honest customer reactions) that drive validated learning and confident decisions, ultimately reducing risk and accelerating progress toward business goals.
Big Challenge Selectiondesign lever
The deliberate choice to focus the sprint on a high-stakes, time-pressured, or stuck problem that is important enough to justify the team's full energy and attention for a week.
Decider Engagementdesign lever
The active, authoritative participation of an empowered decision-maker (or delegate) who provides vision, criteria, and makes binding choices throughout the sprint rather than ceding authority to consensus.
Team Diversity and Expertisedesign lever
The composition of a small (seven or fewer) cross-functional team that includes the people who build the product plus extra experts and troublemakers, ensuring distributed knowledge is available in the room.
Focused Time and Spacecontextual condition
The structural conditions of a cleared five-day calendar, six-hour timeboxed days, a no-devices rule, and a whiteboard-rich room that eliminate fragmentation and concentrate attention on a single challenge.
Problem Framing and Targetbehavioral pattern
The Monday output of a long-term goal, sprint questions, a customer-centric map, and a single chosen target customer and moment that aligns the team and directs all subsequent effort.
Shared Understandingpsychological state
The team psychological state of common, aligned comprehension of the problem, customer, opportunity, and risk built through expert interviews, How Might We notes, mapping, and the visible 'shared brain' of the whiteboards.
Concrete Solution Generationbehavioral pattern
The Tuesday activity of individuals working alone together to transform abstract ideas into detailed, self-explanatory solution sketches that can be fairly evaluated without sales pitches.
Structured Decision Makingbehavioral pattern
The Wednesday sticky-decision process (art museum, heat map, speed critique, straw poll, supervote) plus Rumble logic that produces crisp, low-debate choices reflecting team priorities while avoiding groupthink.
Realistic Prototype (Façade)behavioral pattern
The Thursday output of a Goldilocks-quality, disposable façade built in one day that appears real enough to evoke honest reactions while requiring minimal investment.
Customer Testing with Five Usersdesign lever
The Friday practice of conducting Five-Act Interviews with five target customers, watched together by the team, to elicit honest reactions and the 'why' behind them.
Validated Learningpsychological state
The team state of insight gained from observing genuine customer reactions—identifying patterns of success and failure—that answers sprint questions and reveals the 'why' before expensive commitment.
Confident Next-Step Decisionoutcome metric
The outcome of the team and Decider knowing, with evidence, whether and how to proceed—classified as efficient failure or flawed success—and what to build or fix next.
Risk Reduction and Progress Toward Goaloutcome metric
The ultimate business outcome of saving time and money by avoiding wrong paths and accelerating real-world success toward the long-term goal, measured by downstream results like adoption or sales growth.
How they connect
- big challenge selection → influences problem framing and target
- team diversity and expertise → predicts shared understanding
- focused time and space → influences concrete solution generation
- problem framing and target → predicts shared understanding
- shared understanding → predicts concrete solution generation
- concrete solution generation → predicts structured decision making
- decider engagement → moderates structured decision making
- structured decision making → predicts realistic prototype
- realistic prototype → mediates validated learning
- customer testing → predicts validated learning
- validated learning → predicts confident next step
- confident next step → predicts risk reduction and progress
A candidate measure
Sprint_ How to Solve Big Problems and Test New Ideas in Just Five Days — derived measurement candidates
Big Challenge Selection
perceived stakes/urgency rating; strategic importance judgment
self-report suitability: high
Decider Engagement
presence at key sessions; reversal rate of decisions
self-report suitability: high
Team Diversity and Expertise
role coverage count; team size
self-report suitability: medium
Focused Time and Space
days blocked; observed distraction incidents
self-report suitability: high
Problem Framing and Target
artifact completeness; alignment of target with sprint questions
self-report suitability: high
Shared Understanding
convergence of member responses; perceived clarity
self-report suitability: high
Concrete Solution Generation
number of sketches; comprehension rate during critique
self-report suitability: medium
Structured Decision Making
time-to-decision; number of debate detours
self-report suitability: medium
Realistic Prototype (Façade)
trial-run defect count; perceived realism rating
self-report suitability: low
Customer Testing with Five Users
screening match rate; interviews completed
self-report suitability: medium
Validated Learning
count of patterns seen by 3+ customers; question-resolution count
self-report suitability: high
Confident Next-Step Decision
decision clarity rating; follow-up action taken
self-report suitability: high
Risk Reduction and Progress Toward Goal
sales growth rate; adoption counts; estimated cost/time saved
self-report suitability: low
The story
The reader An entrepreneur, team leader, or maker with a bold vision who wants to deliver an idea, product, or service to the world and make their time at work count.
External problem
They face a big, high-stakes problem and don't know where to focus effort, how to start, or whether their idea will actually work.
Internal problem
They feel stuck, overwhelmed by churn—endless email, slipping deadlines, meetings—and anxious that their effort isn't going toward what matters most.
Philosophical problem
Work shouldn't be wasted on questionable assumptions and unproductive debate; people's limited time should count and make a real difference in customers' lives.
The plan
- Set the stage: pick a challenge, get a Decider, recruit a diverse seven-person team, and clear five days.
- Monday: start at the end, map the problem, ask experts, and pick a target.
- Tuesday: find inspiration and sketch competing solutions individually.
- Wednesday: decide on the best solutions and build a storyboard.
- Thursday: build a realistic façade prototype.
- Friday: interview five target customers and learn from their reactions.
Success
- You make rapid, focused progress and know within a week whether you're on the right track.
- You get clear customer data and confidence before committing months and money.
- Your team becomes a problem-solving machine with shared understanding and better, faster decisions.
- Work becomes meaningful—building things that matter to real people.
At stake
- You stay stuck in churn, burning months and money on untested assumptions.
- Risky ideas fail expensively in the real world after you're too committed to change.
- Endless debate and groupthink lead to mediocre or no decisions.
- Your bold vision never reaches the world.
Chapter by chapter
ch03Set the Stage
This chapter argues that effective problem-solving begins with a clear understanding of the challenge and assembling the right team in an optimal environment.
ch04Monday
This chapter concentrates on establishing a concrete framework for kick-starting a productive workweek by emphasizing the importance of setting long-term goals and targeted actions.
- Starting with a clear long-term goal is crucial for guiding effective week-to-week operations.
- Mapping challenges visually can reveal solutions that may not be immediately apparent, fostering collaborative problem-solving.
- Engaging with experts within your team is essential to harness a range of insights and abilities that contribute to identifying obstacles.
- A targeted sprint focus can dramatically enhance productivity by minimizing distractions and realigning efforts with significant objectives.
ch05Tuesday
This chapter focuses on the importance of remixing and improving upon existing ideas rather than relying solely on original concepts, urging professionals to sketch detailed solutions to foster innovation.
ch06Wednesday
In the quest for innovation, Wednesday's process emphasizes structured decision-making, the vitality of competing ideas, and a clear storyboard to ensure that prototypes effectively address user needs while avoiding the pitfalls of groupthink.
- Structured decision-making can unlock hidden potential in a wealth of ideas, preventing groupthink.
- Keeping competing ideas alive is essential; they may yield innovative solutions that refine or even revolutionize initial concepts.
- Visual storyboarding provides clarity, ensuring that every concept aligns with user needs and scenarios.
- Embracing diverse opinions fosters a culture of creativity, leading to more robust solutions.
ch07Challenge
This chapter explores how the Blue Bottle Coffee team leveraged a design sprint to navigate the complexities of launching an online store, transforming a significant business challenge into an opportunity for innovation.
ch08Team
A successful sprint requires the right mix of team members, led by a decisive leader, to navigate complex challenges efficiently.
ch09Time and Space
In a world of constant interruptions and fragmented attention, this chapter argues for the structured approach of design sprints to reclaim productivity and foster meaningful work.
- Fragmented attention due to constant interruptions is a significant barrier to workplace productivity.
- A well-structured design sprint provides a critical framework for professionals to reclaim focus and facilitate meaningful work outcomes.
- The no-device rule in a sprint environment enhances collective focus and prioritizes engagement among team members.
- Ample writing space, such as large whiteboards, is essential for visualizing ideas and fostering creative collaboration.
ch10Start at the End
This chapter emphasizes the importance of establishing a clear long-term goal and addressing potential pitfalls before diving into problem-solving, drawing inspiration from the Apollo 13 mission's structured approach in crisis.
- Clear, aligned goals are central to a successful project; take the time on day one to define what you want to achieve.
- Embracing potential failure scenarios helps teams address assumptions upfront, reducing the risks of misalignment later.
- Transforming fears into questions fosters a mindset shift from anxiety to curiosity, paving the way for innovative solutions.
- Achieving clarity about long-term goals can yield greater satisfaction and productivity during the sprint.
ch11Map
Creating a simple map to visualize complex business challenges can significantly improve understanding and streamline processes, much like how a physical map guides readers through the intricate world of "The Lord of the Rings."
ch12Ask the Experts
This chapter argues that assembling a diverse pool of expert insights is essential for tackling complex challenges, emphasizing that distributed knowledge across a team can significantly enhance understanding and solution-generation.
ch13Target
This chapter discusses the process of identifying a critical focus for a design sprint, emphasizing the importance of selecting a specific customer and key moment around which all subsequent project work revolves.
ch14Remix and Improve
This chapter argues that true innovation often arises from remixing and improving existing ideas rather than attempting to create something entirely new, emphasizing a structured approach to gather inspirations through techniques like Lightning Demos.
- True innovation often stems from remixing existing ideas and perspectives rather than beginning with a blank slate.
- Lightning Demos enable teams to gather inspiration and insights efficiently while encouraging cross-domain thinking.
- There is immense value in exploring abandoned ideas within companies, as they may hold the key to breakthroughs in current challenges.
- Creative collaboration thrives on collecting diverse influences, expanding the potential for unique solutions.
ch15Sketch
In this chapter, the focus on sketching as a collaborative and individual tool challenges traditional brainstorming methods, advocating for a structured approach to generating concrete solutions from abstract ideas.
- Sketching is an essential practice that democratizes idea generation by requiring only basic drawing skills to express complex ideas.
- Working alone but in parallel leads to more diverse and innovative solutions than traditional group brainstorming.
- The iterative nature of sketching facilitates the transformation of abstract ideas into well-defined proposals that can be rigorously evaluated.
- Clear visual communication significantly reduces misunderstandings and misinterpretations among team members, increasing overall productivity.
ch16Decide
In an era where endless discussions often lead to indecision or dissatisfaction, this chapter presents a structured decision-making process designed to foster efficiency and clarity in team settings.
- Prolonged discussions often lead to fatigue and indecision, emphasizing the need for structured decision-making in team environments.
- The Sticky Decision process divides decision-making into five clear steps to enhance efficiency and clarity.
- Using visual tools such as dot stickers and sticky notes prevents biases and captures team insights meaningfully.
- It is essential for the Decider to maintain decision-making authority to prevent outcomes dictated solely by group consensus.
ch17Rumble
This chapter introduces the concept of the "Rumble," a testing method that allows teams to explore multiple conflicting ideas simultaneously through prototyping, enabling data-driven decision-making without premature compromises.
ch18Storyboard
The process of crafting a detailed storyboard is crucial in ensuring that prototypes not only function well but also resonate with user expectations before the testing phase.
- A well-crafted storyboard is an essential roadmap for any prototype, preventing overlapping confusion and ensuring clarity in customer interaction.
- Emulating stories from creative powerhouses like Pixar reveals the significant advantage of early visual planning within any fast-paced development environment.
- Active collaboration and the efficient appointment of roles—like a designated Decider—propel teams toward more effective outcomes without the drain of collective decision-making fatigue.
- Templates and existing ideas should be utilized rather than reinventing the wheel in the storyboarding phase, which streamlines the execution of the overall sprint process.
ch19Fake It
This chapter argues for the pragmatic value of creating a realistic façade or prototype to test ideas quickly, emphasizing the benefits of early feedback over attachment to a long development process.
- Prototyping doesn’t require perfection; it requires practicality.
- Early feedback is invaluable; the sooner you get it, the better.
- A façade can be just as effective as a fully developed product in eliciting user reactions.
- Teams that practice the “prototype mindset” can outmaneuver those committed to extensive, rigid development processes.
ch20Prototype
In this chapter, the authors present a structured approach to prototyping that emphasizes the importance of selecting the right tools and effectively collaborating within a diverse team to create a realistic, functional representation of an idea.
ch21Small Data
This chapter argues for the power of small data, advocating that even a handful of user interviews can reveal critical insights into customer behavior and preferences, as demonstrated through a compelling anecdote about the publishing of Harry Potter.
- Simple data from just five interviews can reveal 85 percent of user issues, challenging the belief that more extensive research is always necessary.
- Engaging users directly can provide insights that statistics often mask, revealing the deeper reasons behind user frustrations or successes.
- The emotional reactions observed during interviews can guide substantive product improvements that are missed in larger, impersonal studies.
- An incremental approach to user testing allows for faster pivots and more effective designs.
ch22Interview
This chapter demystifies the art of conducting effective customer interviews, centered around Michael Margolis's structured approach that illuminates user experiences and uncovers critical feedback.
ch23Learn
The culmination of a design sprint involves gathering insights from real customers, allowing teams to learn rapidly whether their prototypes meet user needs or require swift iteration.
Related in the library