Rapidly test and validate any startup idea with the 2-day Foundation Sprint (from the creators of the Design Sprint) | Jake Knapp & John Zeratsky (Character Capital)
Jake Knapp and John Zarotsky introduce the Foundation Sprint, a 10-hour framework for founders and product teams to refine and test ideas. This process helps clarify customer, problem, differentiation, and approach, followed by design sprints to validate the founding hypothesis with customers.
Deep Dive Analysis
16 Topic Outline
Origins and Evolution of the Design Sprint
Introduction to the Foundation Sprint Framework
Phase 1: Defining the Project's Core Basics
The 'Note and Vote' Technique for Decision-Making
Phase 2: Developing a Clear Differentiation Strategy
The Importance of Radical Differentiation for New Products
Evaluating Price as a Product Differentiator
Creating Custom Differentiators and a 'Mini Manifesto'
Phase 3: Choosing the Right Project Approach with 'Magic Lenses'
The Paradox of Speed: Why Slowing Down Helps
The Foundation Sprint's Output: The Founding Hypothesis
Executing the Design Sprint to Test the Hypothesis
Case Study: Latchet's Iterative Sprint Journey
Case Study: Mellow's Learning Through Sprints
Leveraging AI Tools in Prototyping and Product Development
Motivation and Benefits of the Foundation Sprint
8 Key Concepts
Design Sprint
A structured, five-day process developed at Google and Google Ventures, where teams clear their calendars to go from a problem to a tested prototype with customers, following steps like map, sketch, decide, prototype, and test.
Foundation Sprint
A two-day (roughly 10-hour) process for core teams to align on a new project's fundamental strategy, covering customer, problem, competition, differentiation, and approach, culminating in a clear 'Founding Hypothesis'.
Work Alone Together / Note and Vote
A decision-making tactic used in sprints where individuals silently generate ideas or answers, then vote on them, with a designated decider making the final choice to ensure diverse input and efficient progress.
Differentiation
The crucial process of defining a product's clear and unique promise that makes it radically stand out from all existing alternatives, compelling customers to try it and ensuring the product delivers on that promise.
Loserville
A term used in the 2x2 differentiation diagram to describe the three quadrants where competitors typically fall, emphasizing that a new product should aim for the distinct top-right quadrant to succeed.
Magic Lenses
A framework used in the Foundation Sprint's third phase to evaluate different product implementation paths by plotting them against various criteria or 'lenses' like customer experience, pragmatism, growth, financial health, and differentiation.
Founding Hypothesis
The concise, single-sentence output of a Foundation Sprint that explicitly states the product's core strategy: 'If we solve this problem for this customer, with this approach, we think they're going to choose it over the competitors because of differentiator one and differentiator two.'
Click
A strong signal observed during customer interviews when a prototype or product genuinely resonates and excites a customer, indicating a potential for product-market fit.
10 Questions Answered
The Foundation Sprint helps founders and product teams get clarity and alignment on the core strategy of a new product or startup, ensuring they build the right thing before investing significant time and resources.
A Foundation Sprint typically requires clearing the calendar for roughly 10 hours, usually spread over two days in four to six-hour blocks.
Differentiation is crucial because customers are bombarded with choices and tend to ignore new products; a clear, radically differentiated promise is needed to capture their attention and motivate them to try it.
This technique ensures everyone contributes ideas independently, preventing groupthink, and then uses voting and a designated decider to move through decisions quickly and transparently.
Price is rarely the most important differentiator, but it can be a clear advantage for AI companies solving problems previously unsolvable with software, often requiring a 10x cheaper offering than legacy manual approaches.
The main output is a 'Founding Hypothesis,' a single sentence that explicitly defines the customer, problem, approach, and key differentiators, providing a clear strategy to test.
By forcing teams to slow down and deeply think about what makes their product unique and valuable to customers before building, it helps avoid wasting time and resources on generic or undifferentiated solutions.
The Foundation Sprint sets the strategic direction by creating a Founding Hypothesis, which is then rigorously tested and refined through a sequence of Design Sprints where prototypes are built and validated with customers.
AI can significantly speed up the creation of realistic prototypes, acting like an on-demand prototyping team, but it's critical to use it after deep thinking and clear planning to avoid generic outputs.
The 'Mini Manifesto' is a one-page decision-making guide that includes the 2x2 differentiation chart and project principles, helping teams make consistent decisions aligned with their unique promise.
22 Actionable Insights
1. Clear Calendar for Key Decisions
Clear your calendar for about 10 hours (spread over two days) with your core team at the very beginning of a project to make all key decisions together and identify project basics. This ensures alignment and clarity from the start.
2. Prioritize Deep Thinking for Uniqueness
Slow down and engage in deep thinking about what will make your product truly unique, especially when building with AI, as rushing can lead to generic outputs and ultimately slow down long-term progress.
3. Invest Two Days for High ROI
Dedicate two days to the Foundation Sprint process to gain a clear hypothesis and strong sense of your idea’s viability, as this investment can yield the highest return in your product’s history.
4. Follow Three-Phase Foundation Sprint
Structure your initial project planning into three phases: Basics (customer, problem, competition), Differentiation (unique value proposition), and Approach (implementation path), to systematically build your founding hypothesis.
5. Define Core Project Basics
Clearly identify your most important customer, the specific problem you’re solving for them, your direct competition, and all existing alternatives or workarounds for that problem. This provides foundational clarity and alignment.
6. Employ “Note and Vote” for Decisions
When making key decisions, have everyone on the team silently write down their individual answers, then vote on the options, and finally, a designated decider makes the final choice. This ensures diverse input and efficient decision-making.
7. Craft a Radically Differentiated Promise
Focus on creating a clear, customer-centric promise for your product that is radically differentiated from alternatives, strong enough to entice trials, and consistently delivered upon.
8. Visualize Differentiation with 2x2
Create a two-by-two diagram to clearly map your product’s differentiation against competitors, ensuring your product occupies the “top-right” quadrant (not “Loserville”) based on customer-centric values.
9. Start with Classic Differentiators
Begin your differentiation exercise by scoring your product and competitors against standard classic differentiators (e.g., fast/slow, easy/hard, free/expensive) to warm up the team and identify initial areas of distinction.
10. Develop Custom Differentiators
Beyond classic metrics, craft specific custom differentiators that reflect a new reality or unique lens your product offers, then score them against competitors to identify truly unique advantages.
11. Establish Project Principles
After defining differentiation, create 1-2 concise project principles (e.g., “help sellers help each other,” “do the thing that makes sellers more money”) to guide future decisions and ensure alignment with your unique value proposition.
12. Explore Multiple Implementation Paths
When deciding on your product’s approach, identify several distinct implementation paths (e.g., app, platform, plugin, full stack) that solve the same core problem for the same customer, even if you initially favor one.
13. Evaluate Approaches with “Magic Lenses”
Assess each potential product approach by plotting it against various “magic lenses” (e.g., customer experience, pragmatism/speed, growth potential, financial health, differentiation, founder conviction). This provides a multi-faceted view for decision-making.
14. Commit Primary & Backup Approach
After evaluating options, clearly decide on your primary product approach and identify a backup plan. This reduces the fear of failure and enables faster pivoting during experiments.
15. Formulate a Clear Founding Hypothesis
Conclude the Foundation Sprint by articulating a single, explicit founding hypothesis statement (e.g., “If we solve [problem] for [customer] with [approach], we believe they’ll choose it over [competitors] because of [differentiator 1] and [differentiator 2]”). This provides a testable strategy.
16. Follow with Design Sprints for Testing
After establishing your founding hypothesis, clear your calendar for 2-3 weeks to conduct a sequence of design sprints. This allows you to run experiments, test your hypothesis, and gather evidence on whether your product clicks with customers.
17. Utilize a Detailed Design Sprint Scorecard
At the end of each design sprint, use a detailed scorecard to evaluate your founding hypothesis against customer feedback. Track whether the customer is right, the problem is real, the approach works, differentiation is effective, and if the product “clicks.”
18. Outsource Prototyping, Not Thinking
Leverage AI tools to rapidly create realistic prototypes, but critically, do not outsource the deep thinking required for product design, messaging, and differentiation. Focus on a clear plan before generating AI-assisted outputs.
19. Create Detailed Sketches Before AI Prototyping
Before using AI to generate prototypes, create detailed manual sketches or plans outlining exactly what the product needs to look like and how it will solve the customer’s problem. This ensures an opinionated, well-defined product rather than a generic AI-generated one.
20. Leverage AI for Price Differentiation
Consider price as a strong differentiator if AI enables you to solve problems previously unsolvable with software, leading to significantly lower costs (e.g., 10x cheaper) compared to traditional methods.
21. Stay Close to Customers Weekly
Engage with your customers weekly throughout the product development process, from planning to testing, to maintain a deep understanding of their needs and ensure your efforts are aligned with what truly matters to them.
22. Foster Team Alignment with Structured Work
Use structured processes like sprints to bring teammates together, focus on the most important tasks, and minimize social dynamics or context switching. This fosters authentic collaboration and renewed motivation.
7 Key Quotes
Going fast can actually slow you down in the long run.
John Zeratsky
The two days that you invest in a sprint might be the highest ROI days in the history of your product.
Lenny Rachitsky
The more AI generated or assisted they are, the more generic they tend to turn out.
John Zeratsky
We want to have like a way of looking at the world that puts all of the competitors into Loserville.
Jake Knapp
Every project has at its core, every new product has at its core, a hypothesis. There is a founding hypothesis. It's just usually not explicit.
John Zeratsky
While you're outsourcing prototyping, don't outsource the thinking as well.
John Zeratsky
I had 50 conversations over the past month, but I learned so much more from even the first conversation when I had a hypothesis and I had a prototype or a couple of prototypes to show them. It's like night and day.
Maruthi
5 Protocols
The Foundation Sprint Process
Jake Knapp, John Zeratsky- Clear your calendar for roughly 10 hours, spread over two days (e.g., two 4-6 hour blocks).
- Assemble the core team (co-founders, product, engineering, design, marketing leadership).
- Phase 1: Basics - Identify the most important customer, the problem being solved, the competition, and existing alternatives/workarounds using the 'Note and Vote' tactic.
- Phase 2: Differentiation - Define what sets the product apart from alternatives. Start by scoring classic differentiators, then write and vote on custom differentiators, and create a 2x2 diagram to visualize the unique promise.
- Phase 3: Approach to the Project - Identify different implementation paths for the product and evaluate them using 'Magic Lenses' (e.g., customer experience, pragmatism, growth, financial health, differentiation, founder conviction).
- Commit to a first-choice approach and identify a backup plan.
- Formulate the 'Founding Hypothesis' as a single, clear sentence summarizing the strategy.
- Follow this with a sequence of Design Sprints (2-3 weeks) to test and refine the hypothesis with customers.
Note and Vote Technique
Jake Knapp- Everyone on the team works in silence.
- Each person writes down their own answers to a specific question (e.g., 'Who's the most important customer?').
- Once all answers are collected, the team votes on them.
- A designated 'decider' makes the final decision based on the votes and discussion.
Design Sprint Process (Post-Foundation Sprint)
Jake Knapp, John Zeratsky- Start with the 'Founding Hypothesis' from the Foundation Sprint.
- Identify the biggest risks that the hypothesis might not be true.
- Map how customers discover the product and what the core experience looks like.
- Using the map, pinpoint the key moment for assessing the identified risks.
- Sketch solutions: Each person individually sketches their proposal for how that key moment should work.
- Choose the strongest sketches; often, multiple prototypes are built to test head-to-head (e.g., using fake brands).
- Build realistic prototypes (can involve vibe coding, real code, static mock-ups, product videos).
- Test the prototypes with real potential customers.
- Evaluate results using a detailed scorecard, assessing if the customer, problem, approach, and differentiation aspects of the Founding Hypothesis are validated or need revision.
Differentiation Strategy Development
Jake Knapp, John Zeratsky- Review the project's basics (customer, problem, competition, alternatives) to establish context.
- Score the product's potential against classic differentiators (e.g., fast/slow, easy/hard to use, free/expensive) relative to competitors.
- Generate custom differentiators, focusing on unique aspects or a 'new lens' on reality for customers.
- Vote on the most promising custom differentiators.
- The decider selects one or two strong differentiators.
- Plot the chosen differentiators against competitors on a scale, being honest about where the product stacks up.
- Create a 2x2 diagram, positioning the product in the top-right quadrant (avoiding 'Loserville') to clearly define its unique promise.
- Ensure the chosen differentiation is both deliverable by the team and compelling to customers.
Magic Lenses Activity for Approach Selection
Jake Knapp, John Zeratsky- Identify all different implementation paths or approaches the team could take to build the product (e.g., app, plugin, full stack).
- For each approach, plot its position on various 'lenses' (axes), representing different viewpoints or priorities.
- Standard lenses include: Customer Expert (easy to use, perfect solution), Pragmatic (cheap, fast), Growth (easy to adopt), Financial Health (long-term value), and Differentiation (aligns with chosen differentiators).
- Teams can also create custom lenses, such as 'Founder Conviction' (how excited the founders are to build it).
- Analyze the plotted options: If one approach consistently appears in the favorable quadrant across most lenses, it's a clear winner.
- If there's no clear winner, the team decides which lens or viewpoint is most important for their current stage.
- Commit to a primary approach and identify a backup plan in case the first choice needs to pivot.