Discovery is the most misunderstood phase in product development. Most teams treat it as a formality — a brief kickoff call, a few stakeholder interviews, a mood board. Then they're off, designing and building before they've truly understood the problem.
We've built over 50 products. The ones that failed — or had to be completely rethought six months in — almost always had the same root cause: the team started building before they understood what they were building, and why.
“The week of doing nothing isn't nothing. It's the week you find out the feature everyone is excited about is the one nobody actually needs.”
What a discovery week looks like
When we work with clients, we protect this time fiercely. We've walked away from projects where the client wouldn't allow it. Not because we're precious about process, but because we've seen what happens when you skip it: six months of beautiful, expensive work solving the wrong problem.
The best founders we've worked with are the ones who push back on their own assumptions hardest in week one. That intellectual honesty, applied early, is worth more than any design tool or engineering framework. It's the difference between building a product and building the right product.