Summary
Highlights
John Zeratsky explains that after leaving Google Ventures to start their own VC firm, Character Capital, they noticed a gap in the very early stages of company building for pre-seed startups. Design Sprints were helpful but often lacked foundational clarity on who the customer was, the problem being solved, and market differentiation. This led to the creation of the Foundation Sprint in 2021-2022, specifically designed for these initial, critical decisions.
The Foundation Sprint involves the core team clearing their calendars for roughly 10 hours (over two days) to go through a highly scripted sequence of activities. The process aims to define the project's basics, differentiate from competitors, and outline the implementation approach. This results in a "founding hypothesis." After the Foundation Sprint, teams proceed to Design Sprints for 3-4 weeks to run experiments, build prototypes, and test them with customers, validating the hypothesis. This structured approach, though initially counterintuitive, is presented as having a high ROI.
The first phase of the Foundation Sprint focuses on defining the basics: the target customer, the problem being solved, key competitors, and their current solutions or workarounds. This phase uses a "work alone together" tactic, where team members individually brainstorm answers before voting and having a designated decider (usually the CEO) make the final choice. This rapid decision-making process helps align the team and create a clear, specific understanding of the project's core elements.
The speakers emphasize that while the questions in the "Basics" phase seem simple, teams often discover surprising differences in perspectives among co-founders. This process provides clarity and transparency, revealing that even seemingly obvious elements are often less clear than assumed. Identifying competitors beyond direct rivals, including workarounds, is highlighted as a common "aha moment." The advantage section sets the stage for differentiation, enabling teams to identify what unique capabilities they possess that nobody else can replicate effectively.
The second phase focuses on differentiation, which is considered the heart of the Foundation Sprint. The goal is to craft a clear, radically differentiated promise to customers that stands out from alternatives. The process starts with scoring the product against classic differentiators (e.g., fast/slow, easy/hard to use) and then moves to creating custom differentiators. This culminates in a 2x2 diagram, similar to Steve Jobs' iPhone introduction, where the product ideally lands in the "top right" quadrant, distinct from competitors in "loserville."
Beyond classic differentiators, teams are encouraged to create custom, precise differentiators that represent a "new version of reality" for customers. For example, the startup Melo chose to differentiate on being "mobile-first" and "works out of the box," while Latchet focused on "helps you grow" and being "cooperative." This phase concludes with creating a "mini-manifesto" containing project principles derived from these differentiators (e.g., "help sellers help each other"). These principles serve as decision-making guides throughout product development.
The final phase of the Foundation Sprint, "The Approach," involves identifying and evaluating different implementation paths for the product. Using an activity called "Magic Lenses," teams plot their potential approaches on various axes representing critical viewpoints: customer experience, practicality, growth potential, financial health, and differentiation. This structured evaluation helps the team decide on an initial primary approach and a backup plan. The "Lenny Lens" of founder excitement is also humorously noted as a valuable consideration.
The output of the Foundation Sprint is the "founding hypothesis," a concise statement articulating the customer, problem, differentiated solution, and competitive advantage. This explicit hypothesis eliminates ambiguity and provides a clear target for testing. The next step is a sequence of Design Sprints, where the team iteratively tests aspects of the hypothesis using prototypes and customer feedback, tracked through a detailed "scorecard." Early scorecards often show areas of failure (red), which leads to refinement and eventual success (green), accelerating the path to product-market fit.
The speakers discuss how AI is impacting sprints, primarily by enabling faster and more realistic prototype creation through "vibe coding." However, they caution against outsourcing the critical thinking phase to AI. While AI can quickly generate a generic-looking product, the Foundation Sprint's emphasis on deep, intentional thought about differentiation and problem-solving remains crucial. Detailing sketches and a clear plan before using AI tools ensures the final product is opinionated and aligned with customer needs, rather than just a generic output.
Jake and John offer a Miro template of their Foundation Sprint process at character.vc, allowing anyone to apply the framework. They emphasize that while clearing calendars for these sprints might feel unnatural, the high ROI and clarity gained are invaluable. The process not only helps in building successful products but also fosters a deeper connection with customers and strengthens team alignment by focusing on core problems and delivering on unique promises.
The speakers, Jake Knapp and John Zeratsky, introduce the concept of the Foundation Sprint. This process addresses common founder failures, such as unclear target customers or untested ideas. The Foundation Sprint aims to clarify core decisions collectively within a short timeframe, usually about 10 hours, emphasizing deep thinking over rapid, generic AI-assisted building. It's presented as a "missing manual" for refining and testing startup ideas, building on their experiences with hundreds of teams and their famous Design Sprint methodology.
Jake Knapp recounts the origin of the Design Sprint. While working at Google, he experienced a pivotal week in Stockholm where his team, facing potential closure, cleared their calendars to rapidly prototype what would become Google Meet. This experience highlighted the power of focused, collective effort to create a testable prototype, leading him to develop the structured one-week Design Sprint (Map, Sketch, Decide, Prototype, Test) that he and John Zeratsky later refined at Google Ventures with over 200 teams.