#160 — The Foundation Sprint workshop

A Foundation Sprint is a focused 2-day workshop that helps a small team define exactly who their product is for, what problem they solve, how they are different, and which strategic bet to make first. On day one, the team clarifies the basics (customer, problem, advantage, competitors); on day two, they explore multiple approaches and converge on a single Founding Hypothesis—a clear, testable promise that future Design Sprints, prototypes, and GTM experiments are designed to validate.

A Foundation Sprint happens earlier than a Design Sprint: it’s about deciding what you should be building and why, not how to design and test a specific solution. A Design Sprint is typically a five-day process to prototype and user-test one solution, while a Foundation Sprint is a two-day strategy process to align the team on customer, problem, differentiation, and a Founding Hypothesis that later Design Sprints will attempt to prove or disprove.

The Foundation Sprint was created by Jake Knapp and John Zeratsky, the creators of the original Design Sprint and partners at venture fund Character Capital. They distilled it from decades of work on products like Gmail, Google Meet, Google Ads, YouTube, and from advising more than 300 companies including Flatiron Health, Gusto, One Medical, Blue Bottle Coffee, and Slack, all of which benefited from a clear, simple founding promise.

A Founding Hypothesis is a concise, Mad Libs–style statement that combines your target customer, their core problem, your approach, and your differentiation into one simple, testable promise. For example, Gmail’s implicit hypothesis was that people overwhelmed by email would switch from Outlook, Hotmail, or Yahoo to a product offering dramatically more storage and great search, while Slack’s promise centered on teams wanting communication that is faster and more organized than email.

Founders should run a Foundation Sprint at the beginning of a big bet: starting a company, launching a new 0→1 product, entering a new market, or significantly repositioning an existing product. It is especially valuable when co-founders give different answers to basic questions like 'Who is our customer?' or 'What makes us different?', or when pitch decks and roadmaps feel polished but the underlying strategy is still fuzzy or disputed.

Preparation involves forming a tiny team (usually three to five people including a true Decider), blocking two full days with at least six hours of focused time each, and setting up a physical or virtual workspace with a whiteboard, sticky notes, paper, and dot stickers for voting. Before the sprint, the Decider can draft rough answers about the target customer, key problem, advantage, and competitors to provide context, knowing that the sprint will surface, challenge, and refine these assumptions.

The sprint should include a small cross-functional group: the Decider (often the CEO, founder, or product lead) plus leaders from product, design, engineering, and possibly GTM or customer-facing roles who will actually execute. Limiting the group to about five people prevents slow, consensus-driven decision-making and ensures the Founding Hypothesis reflects both strategic intent and real-world constraints in building and selling the product.

Before Google Meet, the team spent 18 months refining a complex pitch for a 3D virtual conference room, loaded with interactive tools that colleagues never fully understood or wanted. Under pressure during a week in Stockholm, they threw away the complexity and focused on a simple hypothesis—'fastest and easiest video calls in the browser'—and built a working prototype in days that spread virally inside Google, illustrating how clarity and focus beat feature-rich but fuzzy visions.

Gmail centered on users overwhelmed by email, promising to solve overflowing inboxes better than Outlook, Hotmail, and Yahoo through more storage and powerful search. Blue Bottle Coffee focused on coffee enthusiasts willing to pay more and go out of their way for freshly roasted, carefully prepared coffee that far exceeded mainstream chains, while Flatiron Health targeted oncology practices needing better data and software than traditional medical record systems.

A Foundation Sprint helps avoid building on vague visions, misaligned co-founder assumptions, and endless debates about differentiation that never resolve into real decisions. It also surfaces dangerous hidden hypotheses—like targeting '3D aficionados' with an overcomplicated product—so founders can replace them with simpler, higher-leverage promises that customers actually understand and care about.

Note-and-Vote improves decisions by separating idea generation from discussion: everyone writes ideas silently, the group reviews and votes, and then the Decider makes the final call after a brief debate. This pattern reduces groupthink and HiPPO dynamics, speeds up decision-making, and ensures a Foundation Sprint produces a clear, actionable strategy instead of being derailed by the loudest voice in the room.

The Foundation Sprint sharpens your path to product-market fit by forcing you to choose a specific customer, a painful problem, and a differentiated approach, then turning that into a testable Founding Hypothesis. Instead of running random experiments, you design prototypes, Design Sprints, and GTM tests that directly confirm or falsify your core promise, just as teams behind Gmail, Slack, and other breakout products did with their early, simple promises.

Yes, because the Foundation Sprint focuses on universal strategic elements—customer, problem, approach, and differentiation—rather than any particular technology stack. Case studies like Blue Bottle Coffee show how consumer brands can use a clear Founding Hypothesis to guide everything from product design to store experience and marketing, while Flatiron Health demonstrates its relevance in regulated, non-consumer domains like healthcare.

A strong Founding Hypothesis is simple enough to say in one breath but specific enough to be falsifiable, naming a clear customer, a concrete problem, and a believable advantage over real alternatives. If it sounds like it could apply to dozens of products or 'everyone,' it is too vague; if it hinges on a tiny, contrived niche like '3D aficionados' without a clear switching reason, it is likely too narrow or misguided.

Your main competitor is 'do nothing' if customers can continue with their current workaround or status quo without significant immediate pain, risk, or cost, even if your solution seems objectively better. In the Foundation Sprint, explicitly listing competitors—including 'do nothing'—often reveals that the real challenge is making the problem urgent and painful enough that teams will endure switching costs, not just out-feature existing tools.

Once you have a Founding Hypothesis, translate it into a small set of validation experiments such as Design Sprints, clickable prototypes, early-access programs, or targeted customer interviews with your exact ICP. For example, a 'fastest, easiest video calls' hypothesis might be tested by a bare-bones browser prototype used internally or by a handful of design partners, with success measured by adoption, repeat usage, and qualitative feedback on speed and simplicity.

You should revisit your Founding Hypothesis at major milestones like launching, raising a new round, entering a new segment, or when data consistently contradicts your assumptions. Many teams run a lightweight version of the Foundation Sprint during these inflection points to re-confirm who their best customers are, which problems are most acute, and whether their differentiation still matters in a shifting competitive landscape.

If your hypothesis is wrong, that’s a success of the process: you have quickly falsified a clear bet instead of slowly discovering that a vague vision doesn’t resonate. The Foundation Sprint’s goal is to make assumptions explicit so that you can pivot, refine your customer or problem, and craft a new hypothesis grounded in what you learned, much like the Google Meet team adjusted their strategy away from 3D rooms toward simple, fast calls.

The Founding Hypothesis and the artifacts from a Foundation Sprint can anchor your fundraising narrative by clearly articulating the customer, problem, and unfair advantage behind your company. Investors who liked products like Gmail, Slack, and Blue Bottle responded to their simple, memorable promises; framing your pitch around a similarly sharp hypothesis makes your story easier to understand, remember, and underwrite.

For early-stage teams, two days may feel like a big investment, but it is small compared to months of building the wrong thing or misaligned co-founder expectations. The article is grounded in teams who wasted long cycles before finding clarity—as with the pre-Meet 3D concept at Google—and argues that a short, intense Foundation Sprint is one of the highest-leverage uses of founder time at the beginning of a big project.