Introduction:  

Like the authors—Knapp, Zeratsky, and Kowitz—you have a desire to improve productivity. While we can all track activities, find optimal work times, and create endless to-do lists, the real challenge is working better together.

At Google Ventures (GV), Knapp and his team focused on improving team processes while searching for the “next best thing.” This led to the concept of Sprints—a structured, five-day process for solving big problems and testing ideas rapidly.

A Sprint helps teams answer critical business questions through rapid prototyping and user feedback, rather than waiting months to launch a full product. Here’s how it works:

• Monday: Define the problem and set a goal.
• Tuesday: Brainstorm and sketch solutions.
• Wednesday: Choose the best solution and create a storyboard.
• Thursday: Build a prototype.
• Friday: Test with real customers and gather feedback.

Addressing the Challenge

No problem is too big for a Sprint. Instead of developing a full product, a Sprint focuses on the surface—where customers interact with your solution. The goal is to learn quickly how users react, which helps avoid overconfidence in untested ideas.

Building the Team
A Sprint team should have seven or fewer members. The ideal roster includes:

• A Decider (the decision-maker, often an executive or product owner)
• A Finance Expert
• A Marketing Expert
• A Customer Expert
• A Tech/Logistics Expert
• A Design Expert
• A Troublemaker (a contrarian who pushes boundaries)

The Decider plays a crucial role—if they don’t buy into the Sprint, reconsider your project focus.

The Five-Day Sprint Process

Monday – Define the Problem
The first day is about setting a clear goal:

• What’s the long-term objective?
• What key questions must be answered?
• Where does the biggest opportunity for improvement lie?

A Customer Journey Map is created to visualise the user experience. Interviews with experts help refine the challenge. By day’s end, the team selects a specific target on the map—the biggest challenge that, if solved, will have the most significant impact.

Tuesday – Sketch Solutions
The second day starts with Lightning Demos—each team member presents relevant ideas from other industries, products, or previous projects.

In the afternoon, team members sketch their own solutions. Instead of brainstorming aloud, each person quietly draws their best idea in detail. These sketches are reviewed on Wednesday.

Wednesday – Decide on the Best Idea
On Wednesday, the team picks the best idea(s) to prototype.

• Silent Review: Everyone examines the sketches independently.
• Dot Voting: Team members vote on their favorite elements.
• Final Decision: The Decider makes the call on what gets prototyped.

The chosen solution is then turned into a Storyboard, a step-by-step visualization of how the prototype will work.

Thursday – Build a Prototype
Instead of creating a full-fledged product, Thursday is about faking it just enough to test with users on Friday.

• Use tools like Keynote, PowerPoint, or basic scripts to simulate a working product.
• The team is divided into roles:
• - Makers (create the prototype)
• - Stitchers (ensure consistency)
• - Writers (craft the script and messaging)
• - Asset Collectors (gather images, icons, or data)
• - Interviewers (prepare for Friday’s user tests)

A trial run ensures everything flows smoothly before testing.

Friday – Test with Users
The final day is when the team gets real user feedback.

• The Interviewer conducts five 1-on-1 user tests, asking participants to interact with the prototype while sharing their thoughts.
• The rest of the team watches remotely, taking notes.
• Five tests are usually enough to spot patterns and determine whether the idea is viable.

By the end of Friday, the team will reach one of three conclusions:

1. It works! Move forward with development.
2. It needs tweaks. Refine and test again.
3. It fails. Scrap it and start fresh—without wasting months on the wrong idea.

Conclusion

A Sprint condenses months of work into five intense days. By focusing on rapid iteration, real user feedback, and a structured approach, teams can make informed decisions without over-investing in unproven ideas.

Rather than endlessly debating or launching half-baked products, a Sprint provides clarity, confidence, and speed—ensuring that the best ideas rise to the top.