Discovery comes first (build second)

Dear friend,

I know the feeling. You can picture the finished thing, you're keen to get moving, and any time spent "just talking" feels like time wasted. I've been there too.

But building the wrong thing beautifully is still building the wrong thing. Discovery is the bit that stops that happening.

What discovery actually is

Discovery is simply the work of understanding the problem before you commit to a solution. It's questions, not code. And the questions are the point.

• What are we really trying to fix, in the customer's words?
• What have you already tried, and why didn't it stick?
• What can't we change — budget, platform, the busy season?
• How will we know it worked?

That last one catches people out. If you can't say how you'll measure success, you're not ready to build yet.

Why it saves you money

Every assumption you leave unspoken is a small bet. Discovery brings those bets out into the open while they're still cheap to lose.

The most expensive thing you can build is a confident answer to the wrong question.

Here's the order I trust:

1. Understand the problem and the people it affects
2. Agree what success looks like, in numbers if you can
3. Only then decide what to build

Done well, discovery isn't a delay. It's the thing that lets the build run in a straight line instead of doubling back every fortnight.

Give it an afternoon. Ask the awkward questions early, when the only cost is a slightly longer meeting.

If you want someone to run those questions with you and pressure-test the answers, start with a FREE call.