The most expensive thing you can build is the wrong product. Two weeks of structured discovery is cheaper than six months of wrong engineering. Here’s the exact framework we use at Key Brains.
Week 1: Understand
Days 1-2 are stakeholder interviews. We talk to everyone who has an opinion about what should be built — founders, customers, customer success, sales, support. We’re not collecting requirements; we’re mapping mental models and identifying contradictions.
Days 3-4 are customer interviews. We target 8-10 users who represent the ideal customer profile. We ask about their current workflow, not about the product. What do they do today? Where does it break? What do they use instead?
Day 5 is synthesis. We run an affinity mapping session with the full team to identify patterns, surface assumptions, and prioritize the highest-value problem to solve.
Week 2: Define
Days 6-7 we map the solution space. We run a design sprint — diverge with lots of sketches, converge on a testable concept, build a medium-fidelity prototype.
Days 8-9 we test the prototype with 5 users. We’re not asking “do you like it?” We’re watching them use it and noting where they get confused, skip steps, or say something revealing.
Day 10 is the readout. We deliver a product brief: validated problem statement, solution concept, key risks, go/no-go recommendation, and a phased roadmap for the MVP.
The Outcome
After 2 weeks you know whether you’re solving the right problem, what the MVP should actually be (usually much smaller than the original idea), and what the biggest unknowns are going into development. That clarity is worth more than any methodology certification.
