Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days: Summary & Key Insights

A sprint is designed around a deceptively simple idea: small teams can accomplish in five focused days what might otherwise take months. The week follows a very intentional arc — Monday through Friday — where each day serves a distinct purpose. The flow moves from mapping and understanding to deciding, building, and testing. The rhythm of the week becomes both discipline and catalyst, forcing clear priorities while maintaining creative energy.

On Monday, the team begins by understanding the problem and setting a long-term goal. By Tuesday, attention shifts toward possible solutions — everyone sketches ideas individually, ensuring diversity of thought. Wednesday is the decisive midpoint, when the group reviews all ideas, critiques them, and commits to one direction. That same day, the team creates a storyboard — a detailed plan for the prototype. Thursday is execution: the goal is not to build a perfect product but to make a realistic artifact that customers can interact with. Friday culminates in testing. Real users engage with the prototype as the team watches silently, learning firsthand which assumptions hold and which crumble.

This flow mirrors the natural cycle of design thinking — empathize, define, ideate, prototype, and test — but condenses it into a single, high-intensity week. The sprint builds in structured collaboration while reducing friction. There’s no waiting for a chain of approvals, no vague meetings with unclear outcomes. Instead, it’s about learning fast, with evidence rather than opinion guiding the next step.

The first day sets the foundation. We begin by mapping the problem space, establishing a clear understanding of the challenge, and deciding what success looks like. Every sprint starts with a long-term goal — a north star that frames our efforts. We then work backward, identifying the obstacles standing in the way of that goal. The outcome of this day isn’t a complete plan, but a shared understanding among the entire team.

The map we create is a simple diagram that shows how customers move through our product or system, where decisions are made, and where pain points appear. This visual frame provides context for the week. But equally important are the expert interviews. On Monday afternoon, we bring in people within or outside the organization who deeply understand the problem. They offer insight into customer behavior, technical constraints, competitive dynamics, and past experiments. Everyone takes notes silently, writing down key ideas and forming rough ‘How Might We’ questions — short prompts that reframe insights into opportunities.

By the end of the day, the team converges on a single, narrow target: one piece of the larger problem that, if solved, will have an outsized impact. This decision focus is liberating. Instead of trying to boil the ocean, everyone commits to exploring one important, testable slice of the challenge.