DIAGNOSE FIRST

Finding the Real Problem Before Choosing the Solution

You cannot solve a problem well if you have not understood it.

A delivery is late. Sales are falling. Customers are complaining. Work is missing deadlines. The same failure returns even after people have tried to fix it.

The first response often seems obvious. Hire more people. Buy a new system. Add another check. Set a tighter deadline.

But what if the proposed solution addresses only the visible symptom?

A problem can have several possible causes. A solution that works in one situation may fail in another. A quick fix may improve one measure while creating a new problem somewhere else.

The cost is not limited to money. It includes wasted time, repeated work, lost opportunities, and decisions made on weak evidence.

DIAGNOSE FIRST: Finding the Real Problem Before Choosing the Solution gives you a practical method for examining a problem before committing to a response.

A clear method for better diagnosis

The book develops an eight-stage process:

FRAME → OBSERVE → SEPARATE → TRACE → TEST → TARGET → INTERVENE → VERIFY

Each stage has a specific purpose.

• FRAME: Describe the problem without building a solution into the statement.
• OBSERVE: Establish what is happening, how much it has changed, and when the pattern began.
• SEPARATE: Distinguish facts, perceptions, symptoms, causes, effects, and assumptions.
• TRACE: Build causal chains and compare competing explanations.
• TEST: Examine evidence that supports or weakens each explanation.
• TARGET: Identify the mechanism or leverage point worth addressing.
• INTERVENE: Choose a response that fits the diagnosis and the limits of the situation.
• VERIFY: Check whether the cause, the original problem, and the wider system have changed.

The sequence is a guide, not a rigid formula. New evidence may require you to revisit an earlier stage.

The aim is not to investigate everything. It is to understand enough to make a sound decision.

What you will learn

Define the problem clearly. Learn to describe a condition without assuming its cause or prescribing a remedy before the investigation begins.

Use evidence before explanation. Establish a baseline, examine changes over time, and recognise when a measure or observation is not strong enough to support a conclusion.

Compare possible causes. Build causal chains, identify missing information, and keep alternative explanations open until the evidence helps distinguish them.

Test your own explanation. Ask what you would expect to observe if your explanation were correct, and what evidence would make you reconsider it.

Find the point worth changing. Look beyond the most visible symptom to the mechanism, constraint, or process step that may have greater influence.

Choose a proportionate response. Match the intervention to the diagnosis, the available evidence, the cost of action, and the possible side effects.

Check whether the problem is solved. Define the measures and review conditions before acting. Look for lasting change, not just a short-term improvement in one number.

Reduce the chance of recurrence. Consider prevention, feedback, early warning signals, and controls that address the diagnosed mechanism without adding unnecessary work.

A practical book, not just an explanation of ideas

DIAGNOSE FIRST contains 20 chapters organised into five parts. The book moves from understanding the problem to examining causes, selecting an intervention, and preventing the problem from returning.

It includes practical diagnostic exercises, ten persistent problem cases, reusable worksheets, registers, a master diagnostic record, and audits.

The examples cover familiar situations such as falling sales, customer complaints, missed deadlines, low productivity, quality failures, communication problems, repeated operational mistakes, and growth bottlenecks.

These cases help you practise the method. They are not fixed answers to be copied into every situation. Each problem requires evidence of its own.

Who should read this book?

This book is for people who need to understand a problem before deciding what to do about it.

It will be useful to managers, team leaders, consultants, researchers, analysts, business owners, and professionals who investigate recurring failures or support decisions.

You do not need to be a specialist in formal causal analysis to begin. The book uses a practical sequence and familiar language to help you organise your observations, question assumptions, and choose what to investigate next.

The method can be applied to operational problems, service failures, performance gaps, customer issues, and other situations where the visible condition may not reveal its cause.

What makes the approach useful?

The method does not promise that every cause can be found or that every intervention will succeed.

Instead, it gives you a disciplined way to make your reasoning visible, identify what remains unknown, compare explanations, and decide what evidence you need.

It also helps you recognise when more investigation is justified. A small, reversible decision may need only a short diagnosis. An expensive or difficult-to-reverse decision calls for stronger evidence.

That distinction helps you avoid both rushed decisions and unnecessary analysis.

Start with the problem, not the solution

The next time a problem appears, resist the pressure to select the first plausible remedy.

Describe what is happening. Establish what you know. Compare explanations. Test the one you are considering. Then choose a response and check the result.

DIAGNOSE FIRST: Finding the Real Problem Before Choosing the Solution gives you a repeatable method for doing this with greater care.

If you are tired of seeing the same problems return after another round of fixes, this book will help you approach them differently.

Understand the problem before you commit to the solution.