The 8-Step Problem-Solving Method: A Practical Framework

By JJ Andrade, author of “The 8-Step Problem-Solving Method”. Updated October 2026.

Every organization faces problems. The difference between companies that thrive and those that stall is not the absence of problems; it is how they solve them. Most businesses solve problems reactively: something breaks, someone patches it. The 8-Step Problem-Solving Method is a structured, repeatable way to solve any business problem, and it is also a good test for any consultant you are thinking of hiring.

What is the 8-Step Problem-Solving Method?

It is a sequence: clarify the problem, break it down, set a target, find root causes, design countermeasures, implement, check results, standardize.

I refined it through years of consulting work across industries and documented it in the book The 8-Step Problem-Solving Method. It combines Lean Six Sigma problem-solving with queuing theory for problems that involve flow, capacity or waiting.

Why does most problem-solving fail?

Teams jump to solutions, solve the wrong problem, skip root cause analysis, decide on opinions instead of data, and have no plan to keep the gains.

Jumping to solutions: most teams skip diagnosis and go straight to fixes.
Solving the wrong problem: without a clear definition, resources go to symptoms.
No root cause analysis: band-aids feel productive but the problem comes back.
Lack of data: decisions based on opinions, not evidence.
No sustainment plan: improvements fade because nothing holds them in place.

What are the 8 steps?

Steps 1 to 3 define the problem and the target. Step 4 finds root causes. Steps 5 and 6 fix them. Steps 7 and 8 prove and keep the result.

Step 1: Clarify the problem

“Sales are down” is not a problem statement. “Q2 enterprise sales in the Northeast fell 18% vs Q1, driven by a 40% drop in new customers” is. Write what, where, when and how much; define the gap to the target; set scope; align stakeholders.

Step 2: Break down the problem

Use Pareto analysis to find the vital few causes, stratify data (by type, time, place), map the process and narrow to the specific point of cause.

Step 3: Set a target

Specific, measurable, time-bound. Example: “Reduce defect rate from 4.2% to 1.5% by Q4.” Challenging but achievable, and approved by leadership.

Step 4: Analyze root causes

Use the 5 Whys and cause-and-effect (fishbone) diagrams, and validate with data. Use queuing theory models when the problem involves flow, capacity or waiting. Common categories: People, Process, Equipment, Materials, Environment, Management.

Step 5: Develop countermeasures

Countermeasures, not “solutions”: targeted actions against specific root causes. Generate options, rate them on impact, cost, feasibility and speed, and plan with owners and deadlines.

Step 6: Implement countermeasures

Execute with clear accountability, track weekly (daily for critical work), remove obstacles fast and document changes.

Step 7: Monitor results and process

Compare results with the Step 3 target, use statistics to confirm the change is real, watch for side effects, and go back to Step 4 if results fall short.

Update SOPs, train the team, add visual tools (dashboards, control charts), share lessons and schedule audits.

What does the 8-Step Method look like in a real case?

A logistics company with 28% late deliveries used the 8 steps to find a loading dock queue, fix it, and get late deliveries down to 9.4%.

Step 1: 28% of shipments late, average delay 2.3 days, costing $180K per month in penalties and credits.
Step 2: Pareto showed 65% of late deliveries came from 2 of 7 distribution centers, and 70% involved one carrier.
Step 3: target: late deliveries from 28% to 10% in 90 days.
Step 4: root causes: loading dock queues averaging 3.5 hours from scheduling conflicts; carrier capacity not matched to peaks; no real-time shipment visibility.
Step 5: dock appointment scheduling, a second carrier for peaks, shipment tracking with alerts.
Step 6: all three implemented over 45 days with a dedicated project lead.
Step 7: after 60 days, late deliveries at 9.4%, dock queues down from 3.5 to 1.2 hours, monthly penalties down $140K.
Step 8: the new dock scheduling became standard in all 7 centers, with a carrier playbook and a monthly review.

The dock problem in Step 4 is a queuing problem: arrival patterns and service capacity at the docks. That is the combination I describe in Combining Lean Six Sigma and queuing theory.

How do you vet a process improvement consultant before hiring?

Ask them to walk through a past project step by step: problem, data, root cause, target, result and how it was kept. Vague answers are a warning.

Use the 8 steps as an interview guide. A good process improvement consultant should answer each of these clearly:

Problem (Step 1): “How would you write the problem statement for my business after the first week?” Listen for numbers, not slogans.
Data (Steps 2 and 4): “What data will you collect, from where, and for how long?”
Target (Step 3): “How will we agree on a measurable target before any change?”
Root cause (Step 4): “Show me a past case where the real root cause was different from what the owner believed.”
Who does the work (Step 6): “Will you work with my team on the floor, or deliver a report?” Ask who exactly will do the work.
Proof (Step 7): “How will we know the change worked and was not random?”
Sustainment (Step 8): “What stays with us after you leave: SOPs, training, dashboards?”
References: ask for one or two past clients you can call, and ask them what was measured before and after.
Credentials: ask where a Lean or Six Sigma belt was earned and what projects were done for it. Published work (books, articles, tools) also helps you judge depth.
Written scope: ask for a written scope that says what each phase (diagnostic, implementation, training) covers, what you receive, and what happens if the target is not reached.

What red flags should I watch for when hiring a consultant?

Promises of results before seeing data, no written scope, no measurement plan, a junior team you never met, and nothing left behind when they leave.

They promise a result (a percentage, a dollar amount) before measuring anything.
They skip straight to a tool or software they sell.
There is no written scope, or it does not say what each phase covers.
They cannot explain how results will be measured.
The person who sold the project is not the person doing the work.
Nothing is planned for training or standardizing at the end.

What mistakes should I avoid when solving problems myself?

Skipping steps (most often root cause), working alone, analyzing for months instead of testing, declaring victory early, and ignoring data.

Skipping steps: skipping Step 4 is the most common and most costly mistake.
Working alone: different views find better root causes.
Analysis paralysis: do not analyze for 6 months when you could test a hypothesis in 2 weeks.
Declaring victory too early: monitor for 60 to 90 days before standardizing.
Ignoring the data: if the data contradicts your hypothesis, change the hypothesis.

How do I get started with the 8-Step Method?

Pick one small, well-defined problem, follow each step in order, write everything down, and review what you learned at the end.

The method is simple to understand and takes discipline to run. For the full method with tools, templates and more case studies, get the book: The 8-Step Problem-Solving Method.

If you want help applying it, see how engagements work or book a free 30-minute operations diagnostic.