Design a Foundation Sprint for pre-product clarity

The Foundation Sprint: Clarity Before Prototype

Design Sprints are for testing solutions against users — but teams at the very beginning of a project don't have a solution worth testing yet. What they have is a vague idea, an exciting possibility, and no agreement on who it's for or why it wins. The Foundation Sprint is a 2-day process specifically for that pre-solution stage: forcing hard choices on customer, problem, competition, and differentiation so the next sprint isn't relitigating first principles.

How the Design a Foundation Sprint Prompt Works

The prompt structures Day 1 around four short sessions that answer the foundational questions most teams skip: who is the customer specifically, what is the problem urgently, who else is competing, and what is our single 10x differentiation axis. The 2x2 at the end of Day 1 plots competitors on two axes so the open quadrant — where no one lives — becomes visible.

Day 2 turns the Day 1 output into a Founding Hypothesis: a single sentence combining customer + product + differentiation with an explicit falsification signal. The hypothesis includes a target number that would invalidate it, which converts the usual "we believe..." statement from vague optimism into a testable claim. The original Design Sprint method from Google Ventures proved that time-boxed decision-forcing beats open-ended exploration — the Foundation Sprint applies the same discipline one level earlier in the product lifecycle.

When to Use It

• You have an idea and a team but no agreement on who it serves specifically.
• A previous project died because the team was still debating fundamentals in week six.
• A founding team is pre-MVP and needs to align on direction in 2 days.
• A new product area is being explored and leadership wants a gating decision.
• A prior Design Sprint felt productive but didn't stick because the foundation was fuzzy.

Common Pitfalls

• Writing the hypothesis without a falsification signal. If you can't name the number that would kill the idea, the hypothesis is marketing, not science.
• Skipping the 2x2 and going straight to the hypothesis. The plot reveals which axes are already crowded — without it, teams pick differentiation axes that competitors are already strong on.
• Treating Day 2 as optional. The Founding Hypothesis is the artifact that travels; Day 1 without Day 2 decays within weeks.

Sources

• The Design Sprint — Google Ventures
• Good Product Team / Bad Product Team — Silicon Valley Product Group
• How to Get Startup Ideas — Paul Graham
• Y Combinator Library