Sprint

It was the most expensive chair in the history of office furniture. A team of designers, engineers, and researchers had spent years perfecting it. They conducted ethnographic studies, built hundreds of prototypes, and consulted with ergonomic experts. On paper, it was flawless—a marvel of responsive lumbar support and breathable mesh, designed to solve the problem of sitting. But when it launched, a critical flaw emerged. People hated it. They couldn't figure out the dozen-plus adjustment levers. It was a perfect solution to a problem nobody quite had, born from a long, meandering, and costly process. This story plays out every day inside big companies and small startups alike. A promising idea gets trapped in a cycle of endless meetings, conflicting opinions, and slow-moving development, only to arrive, too late and too complicated, in a world that has already moved on.

At Google, Jake Knapp saw this pattern constantly. As a designer, he’d been part of projects that succeeded spectacularly and others that burned millions before quietly disappearing. He became obsessed with a single question: how do you get to the important part—the moment of truth when you see your idea interact with a real customer—without wasting months or years? He started experimenting, borrowing ideas from design thinking, business strategy, and even his own team meetings. He was creating a focused, five-day process to cut through the noise. When he moved to Google Ventures, he partnered with John Zeratsky and Braden Kowitz to refine this method with over a hundred startups. They were running these intense, week-long 'sprints' on everything from coffee robots to cancer research, compressing months of work into a single, high-stakes week. "Sprint" is the result of that relentless experimentation, a guide to solving big problems and testing new ideas in just five days.

Module 1: Setting the Stage for Speed

The first day of a sprint is all about alignment and focus. It’s where you stop the endless churn of daily work. You dedicate one week to one massive problem. The entire process hinges on getting this foundation right. It starts with a simple but powerful idea. Begin with the end in mind by setting a long-term goal. Where do you want to be in six months or a year? This is a concrete, optimistic target that everyone on the team agrees on. For Blue Bottle Coffee, their goal was to bring their unique café experience to new customers online. This North Star guides every decision for the rest of the week.

So, with that goal set, you have to confront reality. What could stop you from getting there? This brings us to the next step. Translate your assumptions and risks into a few key Sprint Questions. These questions turn fear and uncertainty into focused curiosity. Savioke, the robotics company, assumed their delivery robot would create a great hotel guest experience. They turned this into a question: "Will guests find the robot awkward?" This is a question they could answer by Friday. It's testable. It's specific.

Now, let's turn to the map. To solve a complex problem, you need to simplify it. Create a simple, visual map of the customer's journey. This is a short story with a customer as the main character. It has a beginning, a middle, and an end. Think five to fifteen steps, max. For Flatiron Health, a company tackling cancer research, the map showed a patient moving from diagnosis to clinical trial enrollment. This simple visual organizes the chaos. It gives the team a shared understanding of the problem space.

And here's the thing. No one person knows everything. The CEO doesn't have all the answers. Neither does the lead engineer. Leverage your team's collective knowledge by interviewing experts. On Monday afternoon, you bring in people from across the company. You talk to the finance expert. The marketing expert. The customer support lead who talks to users every single day. These short, structured interviews fill in crucial gaps in the map. They reveal hidden complexities and opportunities.

Finally, Monday ends with a critical decision. You can't solve the entire problem at once. You must choose one target customer and one target event on your map. This is where the Decider, a person with final say, makes a call. Savioke chose to target the hotel guest at the moment of delivery. It was the riskiest, most important interaction. By focusing the entire week on this single moment, they could get a clear result. This ruthless focus is the secret to moving fast.

Module 2: Sketching Solutions, Not Just Ideas

Tuesday is about generating solutions. It’s a structured process, not a free-for-all brainstorm. Traditional brainstorming often favors the loudest voices, not the best ideas. The Sprint process flips this on its head. It starts with a simple principle. Find inspiration by remixing and improving existing ideas. Great innovation is rarely a lightning bolt of pure genius. It’s usually a clever combination of things that already exist. Melitta Bentz didn't invent the idea of a filter. She just repurposed blotting paper from her son's notebook to make a better coffee filter.

To make this systematic, the sprint uses a structured exercise. It's called Lightning Demos. Each person spends a few minutes presenting great solutions from other products or industries. The Blue Bottle Coffee team looked at how a chocolate company described flavors. This gave them a new way to talk about their coffee beans. The goal is to collect a library of interesting concepts you can adapt.

Building on that idea, the sprint process recognizes a fundamental truth about creativity. The best ideas come from individuals working with deep focus. Groupthink kills innovation. So on Tuesday, the team works "alone together." Everyone is in the same room, but they are working individually. This prevents the loudest person from dominating the conversation. It allows for deep, uninterrupted thought.

So what does this individual work look like? It’s about making ideas concrete. Use sketching to turn abstract thoughts into testable solutions. You don't have to be an artist. Stick figures and boxes are fine. The goal is to articulate a complete idea on paper. A sketch is a hypothesis. It forces you to think through the details. How does the user get to this screen? What does this button say? What happens next? An abstract idea in a meeting can sound great, but a sketch reveals its flaws and strengths.

And it doesn't stop there. To push your thinking, you use a rapid-fire exercise. Force creative variations with a technique called Crazy 8s. You take a sheet of paper. You fold it into eight sections. Then, you give yourself eight minutes to sketch eight different variations of your core idea. One minute per sketch. This pressure forces you past your first, most obvious solution. It pushes you to explore alternatives you wouldn't have considered otherwise. It's a workout for your creative muscles. By the end of Tuesday, every team member has produced a detailed, well-thought-out solution sketch. Anonymously. Ready for critique.

Module 3: Deciding Without Debate

Wednesday is decision day. In a normal project, this is where things grind to a halt. Endless debates. Competing egos. Decision fatigue. The sprint uses a structured, almost silent process to make choices quickly and effectively. It feels unnatural at first. But it works. The core idea is to evaluate all solutions silently and simultaneously to reduce bias. The team hangs all the anonymous sketches on the wall, like an art museum. Everyone walks around and reviews them in silence.

Here's where it gets interesting. Instead of talking, the team uses stickers. Use dot voting to create a "heat map" of interesting ideas. Each person gets a sheet of small dot stickers. As they review the sketches, they place dots next to specific parts they like. A great headline. A clever diagram. An insightful flow. This creates a visual heat map of the group's collective opinion. It happens without a single word of debate. It highlights the good ideas, no matter who created them.

From this foundation, the critique begins. It's a highly structured conversation. Conduct a structured "Speed Critique" for each concept. The facilitator walks through a sketch. A designated scribe captures the big ideas on a whiteboard. The team discusses the concept for exactly three minutes. The creator of the sketch remains silent until the very end. This prevents them from being defensive. It allows the idea to stand on its own.

But flip the coin. A purely democratic vote can lead to weak, compromised solutions. The sprint needs a real decision. This leads to the most important part of the day. The Decider makes the final call with a "Supervote." After a quick, non-binding straw poll, the Decider gets three special stickers. They place these on the sketches or specific features they want to prototype. This decision is final. It ensures the team moves forward with conviction. It also ensures the person with authority is fully bought-in, preventing them from second-guessing the outcome later.

So here's what that means. By the end of the day, you have winning concepts. To prepare for prototyping, the team creates a storyboard that plans every step of the prototype. This is a comic book-style plan, about 10 to 15 panels long. It shows exactly what the customer will see and do. It starts with how they discover the product, like a Google search or a news article. It walks through every click and interaction. This storyboard is the blueprint for Thursday. It eliminates guesswork and ensures the prototype tells a cohesive story.