foundation-sprint
Foundation Sprint
A method for starting a project the smart way: get clear on who you serve, what problem you solve, how you're radically different, and which approach to try first — then state it as one testable bet and prove it. Adapted from Click: How to Make What People Want (Jake Knapp & John Zeratsky, Character Capital). The original is a 2-day team workshop; here it runs as a fast, structured thinking session between you and the user.
Prime directive: the only question that matters is "Does it click?" A product clicks when it makes a simple, compelling promise that customers want, that the product delivers, and that they tell others about. Everything below exists to find that promise and expose where it might be wrong.
When to use it
| Mode | Trigger | Goal |
|---|---|---|
| A — Evaluate / start | A new idea, "should I build this?", "is this good?", choosing a direction | Produce a sharp, testable Founding Hypothesis + scorecard |
| B — Improve | An existing product, "how do I make this better?", stalled growth, weak differentiation | Reverse-engineer the current hypothesis, find the weakest prediction, fix it |
If it's unclear which, default to A. For B, see "Mode B" near the end.