How to handle a client who wants to skip discovery

A client eager to skip straight to execution is usually trying to save time and money, and discovery is exactly the phase that prevents the far more expensive rework that happens when nobody actually confirmed what "done" means before starting. The instinct to accommodate is understandable and often costs everyone more in the end.

Holding the line on discovery isn't about protecting your process. It's about protecting the client from a much more expensive version of the same delay, later.

Skipping discovery usually costs more time later than it saves now

Discovery feels like overhead in the moment and its absence tends to surface later as rework, misaligned expectations, or a deliverable that technically matches the brief but misses what the client actually needed. The time saved upfront is rarely the time actually lost downstream.

Explain what discovery actually prevents, not just what it produces

Explaining discovery as a deliverable, "you'll get a brief," undersells it. Explain what it actually prevents, misaligned expectations, wasted execution time, a result that doesn't match what they actually needed, so the client understands its real function.

Offer a compressed version instead of skipping it outright

A full discovery phase and no discovery at all aren't the only options. Offer a genuinely compressed version, a shorter but still real discovery step, that respects the client's urgency while still confirming the fundamentals before execution begins.

Name the real risk of starting execution without it, plainly

State plainly what happens if the engagement proceeds without discovery, work built on unconfirmed assumptions, a higher chance of a costly revision later, rather than quietly absorbing the risk without the client understanding it was ever a risk.

Hold the line when the project genuinely can't work without it

For some projects, skipping discovery genuinely undermines the ability to deliver something the client will actually be happy with. In those cases, hold the line clearly, with the reasoning explained, rather than caving to avoid a difficult conversation.

A simple checklist

If you do nothing else, do these five things:

• Explain what discovery actually prevents, not just what it produces.
• Offer a genuinely compressed version instead of skipping it entirely.
• State plainly the real risk of proceeding without it.
• Hold the line when the project genuinely depends on it.
• Don't quietly absorb a risk the client doesn't know they're taking.

Do that, and discovery stays a step that protects both sides, not overhead a client talks you out of at the first sign of urgency.