The Diagnosis Before the Prescription

There is a reliable pattern in consulting engagements that go sideways: the team arrives with a hypothesis, spends the discovery phase looking for evidence to support it, and presents a recommendation that confirms what they suspected on day one. The client paid for insight; they got validation.

The antidote is a genuine commitment to diagnosis before prescription.

Separating Symptoms from Causes

Clients almost always describe their problem in terms of symptoms. "Our projects are always late." "Our engineers are not productive." "We keep losing customers after the first year."

Each of these is an observation, not a cause. The consulting work is to move from the observation to a falsifiable theory about why the pattern exists.

• Projects are late: is it scope changes, estimation failures, dependency management, resource availability, or decision-making latency?
• Engineers are not productive: is it tooling, context-switching, unclear requirements, technical debt, or hiring?

Generating multiple competing hypotheses—and then designing lightweight tests to discriminate between them—is more rigorous than picking the most plausible explanation and running with it.

The Cost of Premature Diagnosis

Recommendations built on incomplete diagnosis have a characteristic failure mode: they address a real problem, just not the one causing the most pain. The client implements the recommendations, sees partial improvement, and correctly concludes that something is still wrong.

This is expensive in time and credibility.

What Good Diagnosis Looks Like

• Interviews that surface contradictions, not consensus
• Data analysis that challenges the stated narrative
• Explicit documentation of what would change your mind
• Time-boxing diagnosis so it doesn't become an indefinite research project

The goal is not certainty—it is good enough confidence to make a recommendation that can be adapted as the situation evolves. Diagnosis is an investment in the quality of what comes after.