Expanded Detail:

1. What Problem Are We Actually Trying to Solve?

A good problem statement describes a gap:

What is happening now compared with what should be happening?

“We have an inventory problem” is not a useful problem statement. It is too broad.

A clearer statement might be: Finished-goods inventory has increased from 42 to 61 days of supply during the past three months, while customer service has remained unchanged.

That statement tells us:

• What changed
• How much it changed
• When it changed
• Why it deserves attention

A useful problem statement does not blame someone or quietly prescribe a solution.

“We need another warehouse” is not a problem statement. It is a proposed solution.

The actual problem might be poor inventory accuracy, obsolete products, inefficient slotting, unnecessary safety stock, or slow-moving inventory that nobody wants to address.

What should you do next?

Complete this sentence: Currently, ______ is happening. We expected ______. This is causing ______.

Keep refining it until someone unfamiliar with the situation can understand the gap.

---

2. How Do We Know This Is the Real Problem?

What first catches your attention is often a symptom.

Late customer orders may be caused by warehouse performance, but they could also result from inaccurate inventory, delayed production, late supplier deliveries, unrealistic promises, transportation constraints, or poor order data.

Adding warehouse labor might make everyone feel productive. It will not help much if the orders are late because the products have not been manufactured.

This is why experienced problem-solvers stay curious longer than everyone else.

They do not ask only: What went wrong?

They also ask: What caused this condition to exist?

The 5 Whys can help you explore causes, but five is not a magic number. Some problems require three questions. Others branch into several contributing causes. The purpose is to move beyond the visible symptom without turning the exercise into a search for someone to blame.

What should you do next?

Ask:

• Is this the problem or a symptom?
• Where does the problem first appear?
• When does it happen?
• When does it not happen?
• What changed before it started?
• What conditions are consistently present?

Do not settle for the first explanation simply because it sounds reasonable.

---

3. What Evidence Supports That?

Opinions can point you toward a problem. Evidence helps you understand it.

Evidence may include:

• Process data
• Customer complaints
• Quality records
• Supplier performance
• Inventory history
• Observations from the workplace
• Interviews with the people doing the work
• Comparisons across products, shifts, facilities, or time periods

The key is to separate what you know from what you think you know.

Consider these two statements:

The night shift is causing the shipping delays.

During the past four weeks, 72% of orders missing the shipment cutoff were released to picking after 3:00 p.m., across both shifts.

The first statement points toward blame. The second gives the team something it can investigate.

Data alone is not enough, either. A spreadsheet may show where the problem occurs without explaining why. That is why good problem-solvers examine the numbers and go see the work.

What should you do next?

Create two short lists:

What we know

Facts that can be observed, counted, verified, or demonstrated.

What we believe

Explanations, opinions, expectations, and conclusions that have not yet been verified.

The second list is not necessarily wrong. It simply needs to be tested.

---

4. What Assumptions Are We Making?

Every solution rests on assumptions.

We assume the forecast will be accurate. We assume the supplier can increase capacity. We assume customers will accept a longer lead time. We assume employees will follow the new process. We assume the system data is correct.

The most dangerous assumptions are usually the ones nobody realizes they are making.

Suppose a company responds to stockouts by increasing safety stock. That decision may assume:

• Demand variability is causing the shortage.
• Lead times are accurate.
• Inventory records are reliable.
• The supplier is consistently delivering the requested quantity.
• The stocking policy is the same for every item.
• More inventory will improve service.

Any of those assumptions could be wrong.

What should you do next?

Ask everyone involved to finish this sentence: For this solution to work, we are assuming that ______.

Then identify which assumptions would cause the most damage if they proved false.

Test those first.

---

5. What Are the Trade-Offs?

A solution can improve one part of the business while making another part worse.

More inventory may improve availability but consume cash and warehouse space.

Larger production batches may increase equipment efficiency but create excess inventory and longer response times.

Using the lowest-price supplier may reduce purchase price while increasing quality failures, lead-time risk, or administrative effort.

Expediting an order may protect one customer while delaying several others.

There is rarely a perfect business decision. There are usually choices with different costs, benefits, risks, and consequences.

This is why problem-solving must consider the entire system—not just the department where the problem became visible.

What should you do next?

For each serious option, ask:

• What improves?
• What becomes worse?
• Who benefits?
• Who carries the cost or risk?
• What could happen somewhere else in the supply chain?
• Is the trade-off temporary or permanent?
• Can we reverse the decision if it does not work?

A solution is stronger when the trade-offs are understood before implementation rather than discovered afterward.

---

6. What Does Success Look Like?

“Fix the problem” is not a measurable target.

Success needs a clear condition.

Instead of: Improve supplier performance.

Try: Increase the supplier’s on-time delivery from 84% to at least 96% within 90 days without increasing total landed cost or quality defects.

A clear target aligns the team and prevents the definition of success from changing after the work begins.

It also forces an important conversation: Are we trying to eliminate the problem completely, reduce it to an acceptable level, prevent recurrence, or contain the damage while developing a longer-term solution?

Those are different goals.

What should you do next?

Define:

• The result you want
• The measurement you will use
• The current performance
• The target performance
• The timeframe
• Any conditions that must not become worse

Success should be understandable before the solution is selected.

---

7. How Will We Know We Succeeded?

Some solutions create a temporary improvement. The numbers look better for a week, attention moves elsewhere, and the old problem slowly returns. That is not a solved problem. It is a problem taking a short break.

A complete problem-solving process includes follow-up. ASQ’s problem-solving guidance includes sustaining the gains, while the Plan-Do-Check-Act cycle emphasizes testing a change, reviewing the result, and acting on what was learned.

Track both the final outcome and the conditions that produce it.

For example:

Outcome measure

• Customer orders shipped on time

Process measures

• Orders released before cutoff
• Picking completion time
• Replenishment shortages
• Inventory accuracy
• Carrier departure performance

The outcome tells you whether you won. Process measures help explain why.

What should you do next?

Decide:

• What will be measured
• Who will review it
• How often it will be reviewed
• How long the result must hold
• What action will be taken if performance slips
• What new process should become standard

Do not declare victory when the solution is launched. Declare victory when the result has been demonstrated and sustained.

---

A Simple Problem-Solving Path

The seven questions can be organized into five practical stages:

1. Define

Describe the gap between the current condition and the desired condition.

2. Understand

Gather evidence, examine the work, and separate symptoms from contributing causes.

3. Decide

Compare options, assumptions, risks, and trade-offs.

4. Test

Try the most promising change on an appropriate scale before making a larger commitment.

5. Learn

Measure the result, adjust the approach, standardize what worked, and capture what the team learned.

This follows the same practical logic found in A3 thinking and PDCA: understand the problem, develop a response, test it, evaluate the evidence, and continue improving. A3 is especially valuable because it makes the reasoning visible and creates a basis for discussion rather than hiding the thinking inside a long report.

---

Example: Late Customer Orders

Imagine a distribution center where customer complaints about late orders are increasing.

The first proposed solution is to add more people to the warehouse.

Before approving that expense, the team works through the Decision Guide.

What problem are we actually trying to solve?

During the past four weeks, 16% of orders missed the same-day shipment target, compared with the company goal of 5%.

How do we know this is the real problem?

The late orders are real, but warehouse labor has not yet been established as the cause.

What evidence supports that?

Most late orders were released to the warehouse after the normal picking cutoff. Picking productivity remained close to target.

What assumptions are we making?

The original solution assumes that more labor will make late-released orders ship on time.

What are the trade-offs?

Additional labor increases cost and may provide little benefit if orders continue entering the warehouse too late.

What does success look like?

Reduce missed same-day shipments from 16% to below 5% within six weeks without increasing labor cost per order.

How will we know we succeeded?

Track order-release time, picking completion, carrier departure, and overall on-time shipment performance each week. The team may still decide that staffing needs to change. But now that decision will be based on the actual constraint rather than the first visible symptom. That is the difference between reacting to a problem and solving one.

---

Common Problem-Solving Traps

Starting with the solution

“We need new software” may be an idea. It is not a definition of the problem.

Solving the symptom

Repeated expediting may protect today’s shipment while leaving the broken planning process untouched.

Using averages that hide the problem

Average performance may look acceptable even when one product family, supplier, customer, shift, or facility is consistently failing.

Confusing correlation with cause

Two things happening at the same time does not prove that one caused the other.

Blaming people too quickly

People work within systems, processes, incentives, training, tools, and constraints. Look for the conditions that made the error likely.

Choosing the most comfortable explanation

The familiar answer is not always the correct answer.

Implementing without testing

A small, controlled test can reveal problems before the company commits significant time, money, or credibility.

Failing to follow up

Without measurement and ownership, even a good solution can quietly disappear.

---

Five-Minute Problem-Solving Worksheet

Use this whenever you feel pressure to jump immediately into action.

The problem we are trying to solve is:

We believe this is the real problem because:

The evidence shows:

The most important assumptions are:

The major trade-offs are:

Success would look like:

We will know we succeeded when:

You do not need a complicated form to improve your thinking. You need the discipline to answer the right questions before committing to the answer.

Frequently Asked Questions

What is the first step in solving a problem?

Define the gap between the current condition and the desired condition. Avoid beginning with a solution, blame, or a broad statement such as “performance is bad.”

How do I know whether I found the root cause?

A likely cause should be supported by evidence, explain how the problem was created, and give you a reasonable way to test whether changing that condition improves the result. Complex problems may have several contributing causes rather than one root cause.

Is asking “why” five times always enough?

No. Five Whys is a prompt to continue investigating, not a requirement to stop after exactly five questions. Some problems need fewer questions; others require several branches of analysis.

Should every problem use a formal problem-solving method?

No. Match the effort to the size, risk, and complexity of the problem. A small reversible issue may need only the seven Decision Guide questions. A recurring, expensive, cross-functional, or safety-related problem may require a more rigorous method such as A3, PDCA, DMAIC, or 8D.

When should we implement a solution?

Implement when you can clearly explain the problem, support the likely causes with evidence, understand the important assumptions and trade-offs, define success, and establish how the result will be measured. Whenever practical, test the change on a smaller scale first.

---

The Most Important Question

Solving problems is not about having an impressive toolkit. It is about thinking clearly when everyone feels pressure to move quickly. The next time a problem appears, resist the urge to begin with: What should we do?

Start with: What problem are we actually trying to solve?

That one question may prevent weeks of work aimed at the wrong target.

---

Connected Knowledge

Continue exploring:

• Decision Making Models Cheat Sheet.
• First Principles: Elon Musk Method of Thinking
• How to Find the Root Cause of Any Problem: Stop Fixing the Wrong Things.
• PDCA Continuous Improvement – Deming Cycle 
• Problem Solving Quotes by Top Minds.
• The Confidence Curve: Why Confidence Often Increases as Visibility Decreases.
• The First Principles Supply Chain Series.
• Work Smarter, Not Harder: The Productivity Collection You Need.

---

Want to stay ahead in the supply chain game? Subscribe to our newsletter for the latest trends, insights, and strategies to optimize your supply chain operations.

• “Every problem is a gift. Without them we wouldn’t grow” ~Tony Robbins
• “Your ability to solve problems and make good decisions is the true measure of your skill as a leader.” ~Brian Tracy
• “It takes a lot of hard work to make something simple.” ~Steve Jobs
• “I suppose it is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail.” ~Abraham Maslow
• “The supreme art of war is to subdue the enemy without fighting.” ~Sun Tzu, The Art of War.
• “We can not solve our problems with the same level of thinking that created them” ~Albert Einstein
• “We are continually faced by great opportunities brilliantly disguised as insoluble problems.” ~Lee Iacocca
• “The most serious mistakes are not being made as a result of wrong answers. The truly dangerous thing is asking the wrong questions.” ~Peter Drucker, Father of Modern Management.
• “Inside of every problem lies an opportunity.” ~Robert Kiyosaki
• “It’s so much easier to suggest solutions when you don’t know too much about the problem.” ~Malcolm Forbes
• “One hour of true focus delivers more than ten hours of distracted effort ever could.” ~Dave Waters
• “One thing is sure. We have to do something. We have to do the best we know how at the moment . . . ; If it doesn’t turn out right, we can modify it as we go along.” ~Franklin D.Roosevelt
• “If I had an hour to solve a problem I’d spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.” ~Albert Einstein

Continuous Improvement Resources