How Managers Can Use Structured Problem Solving

In this guest article, Flavio Soriano — founder of High Bridge Academy and a former McKinsey and Arthur D. Little consultant who has trained more than 10,000 professionals — shares a practical six-step framework for structured problem solving that any manager can apply, from a whiteboard discussion to a complex business challenge.

When a project misses its deadline, the first instinct is usually to fix the visible problem. Add another person, reduce the scope, move the date or push the team harder.

I learned in consulting that this is often where teams lose time. Before deciding what to change, you need to understand what is actually causing the delay. The issue could be scope changes, one late dependency, unclear ownership or an unrealistic estimate. Each points to a different response.

That is where problem definition matters.

A manager who takes a little time to clarify what is happening gives the team a much better starting point for analysis and decision-making. In practice, a few disciplined questions at the beginning often save far more time later. Organisations with structured problem-solving processes achieve 67% better decision outcomes compared to those with informal approaches, according to Lean Wisdom’s 2025 management research — a figure that reflects exactly this discipline applied consistently.

Why Unstructured Problem Solving Leads to Poor Decisions

Most management problems first show up through visible symptoms — falling sales, rising customer complaints, missed deadlines or lower productivity. The pressure to act makes it easy to treat the symptom as the problem itself. That usually creates a few familiar patterns:

• The team starts discussing solutions before agreeing on what is wrong.
• The loudest or most senior voice determines how the issue is framed.
• People gather large amounts of information without deciding what they need to learn.
• Different functions discuss different versions of the same problem.
• A reasonable solution gets applied to the wrong cause.

The cost shows up in longer meetings, duplicated work and decisions that have to be revisited.

How managers frame a problem can influence the decisions that follow. In one study of engineers, scientists and managers, subtle changes in how the problem was presented affected both the decisions participants made and how they perceived risk.

For managers, following a structured decision-making process creates a useful pause between spotting a symptom and choosing a response. Getting root causes and symptoms mixed together makes everything that follows harder.

A Structured Problem-Solving Approach for Managers

Structured problem solving gives a team a common route from an unclear situation to a defensible decision. The six moves below are simple enough for an ordinary team discussion and disciplined enough for a complex business problem.

1. Define: State What Is Actually Happening

Start with the observable situation.

• What changed?
• Where is it happening?
• Who is affected?
• Why does it matter?

“Customer satisfaction is getting worse” is too broad to guide useful analysis. “Repeat complaints from UK enterprise customers increased after the new onboarding process launched” gives the team somewhere specific to investigate.

A strong definition creates boundaries. It tells people what belongs in the analysis and what can wait.

2. Separate: Sort Symptoms, Causes, Constraints and Assumptions

Teams often mix four different things together.

• A missed deadline is a symptom.
• A slow approval process could be a cause.
• Limited engineering capacity is a constraint.
• “The team needs another developer” is an assumption about the cause and solution.

Keeping those categories separate stops an early theory from quietly becoming accepted fact. This is also where managers should listen carefully to the language in the room. Phrases such as “we already know why” or “the obvious fix is” deserve a closer look.

3. Structure: Break the Problem Into Logical Parts

Once the problem is defined, divide it into components the team can investigate without major overlap or gaps. For a customer-retention problem, a manager might look at customer segment, product, channel, stage of the customer journey and time period. The right structure depends on the issue, because the categories need to help the team locate where the change is actually happening.

The MECE framework is one useful discipline here. It helps managers separate a problem into distinct components while still covering the important parts of the issue — Mutually Exclusive (no overlap between categories) and Collectively Exhaustive (no significant gaps).

4. Prioritise: Decide What Deserves Attention First

A structured problem can still produce a long list of things to investigate. Managers need to decide which questions are most likely to affect the final decision. Prioritise the issues that could explain the largest share of the problem, the assumptions carrying the most weight and the questions the team can test quickly.

This keeps the team focused on the questions most likely to change the decision. The team needs enough evidence to make a sound decision without analysing every possible angle equally.

5. Test: Challenge the Working Explanation

Now bring in data, observations and stakeholder input. If the team believes customer complaints are rising because service quality has fallen, compare complaint types, teams, channels and time periods. Speak to the people closest to the process.

Look for evidence that weakens the current explanation as well as evidence that supports it. This also helps reduce decision-making bias when a team has already become attached to one explanation.

6. Decide and Communicate: Make the Reasoning Easy to Follow

By this point, the decision should connect clearly to the analysis. Explain what the team found, which cause matters most, what response has been chosen and why. Then make ownership and the next action explicit.

Clear stakeholder communication matters because people need to understand the reasoning behind the action they are being asked to take. It also makes the decision easier to revisit when new information appears.

What Structured Thinking Looks Like in Practice

At McKinsey, I learned not to treat the first visible problem as the full problem. Before recommending an action, we would break the issue down and look for where the change was actually coming from.

A manager can apply the same approach when customer complaints rise. Instead of immediately adding staff or retraining the whole service team, first separate the complaints by product, customer segment, channel, type and timing.

If the data shows that most complaints come from new customers using one product during their first two weeks, the investigation becomes much more focused. The manager can look closely at onboarding and early support before committing resources elsewhere.

Why Structured Thinking Improves More Than Problem Solving

The benefits also show up in team performance, because a shared structure changes how people discuss, divide and resolve problems:

• Meetings become clearer because everyone is discussing the same problem.
• Delegation improves because work can be assigned to specific parts of the analysis.
• Data gathering becomes more focused because teams know which questions they need to answer.
• Stakeholder communication improves because the reasoning behind a decision is easier to explain.
• Alignment happens faster because assumptions and priorities are visible.
• Rework falls because fewer people spend time solving a poorly framed problem.

Research on group decision-making shows that good decisions depend on relevant information being shared and evaluated. Group dynamics can also distort which information receives attention. A clear structure gives managers a practical way to organise that discussion around the evidence and the problem being solved.

It also improves management decision-making because responsibilities become clearer. One person can investigate customer behaviour while another looks at process performance, and both pieces still connect to the same question.

Better Decisions Start With a Clearer Problem

For many problems, the process can happen on a whiteboard during one focused discussion:

Define → Separate → Structure → Prioritise → Test → Decide and Communicate

The value comes from giving the team a shared way to think before everyone starts pursuing solutions.

When managers define the problem clearly, they can gather better evidence, focus their teams and explain decisions with greater confidence. That brief investment at the beginning usually makes the work that follows much easier to manage.

Disclosure and Disclaimer

This is a paid guest article, see our disclosure policy for details. The content in this article reflects the views and experience of the named author. It is provided for general information and educational purposes only and is not intended as professional management consultancy advice. The Happy Manager and Apex Leadership Ltd accept no liability for actions taken in reliance on the content of this article.

Further Reading

• High Bridge Academy: What Is MECE and Why It Matters in Business — Flavio Soriano’s own guide to the MECE framework, covering how to structure a problem into mutually exclusive and collectively exhaustive components — the discipline that underpins Step 3 of the framework in this article. Read the guide
• MIT Sloan Executive Education: Problem-Solving Methods — A Leader’s Guide — A comprehensive overview of the most effective problem-solving frameworks for leaders, covering divergent and convergent thinking, root cause analysis, and how structured approaches strengthen decision-making systems across organisations. Read the article
• The Happy Manager: Decision-Making Bias — What Managers Can Learn From Traders — How cognitive biases affect management decisions and what practical steps managers can take to reduce their influence — directly relevant to Step 5 of the structured problem-solving framework. Read the article

References

1. Lean Wisdom (2025). Complete Guide to Effective Decision Making Strategies for Managers 2025. (Organisations with structured implementation processes achieve 67% better decision outcomes than those with informal approaches.) https://www.leanwisdom.com/blog/effective-decision-making-strategies-for-managers-in-management/
2. Burning Glass Institute / PM Study Circle (2026). Decision-Making and Problem-Solving: Skills for Better Results. (41% of 6.8 million US job postings from 2022–2024 specifically mentioned decision-making abilities.) https://pmstudycircle.com/decision-making-and-problem-solving/
3. Stivers, J.B. and Covin, T.J. (1995). Problem Framing Effects on Decisions and Risk Perceptions of Engineers, Scientists and Managers. University of Nebraska Digital Commons. https://digitalcommons.unl.edu/managementfacpub/89/
4. Stasser, G. and Titus, W. (1985/2017). Pooling of Unshared Information in Group Decision Making. PubMed Central. (Group decision-making and information sharing dynamics.) https://pmc.ncbi.nlm.nih.gov/articles/PMC5579088/

Our problem solving resources

You’ll find more practical problem solving ideas in our great-value e-guide: What’s the Problem?! A comprehensive guide to problem solving, complete with these 9 essential tools:

• Tool 1: When you don’t know what to do
• Tool 2: Defining questions for problem solving
• Tool 3: Finding the right problems to solve
• Tool 4: Problem solving check-list
• Tool 4a: Using the question check-list with your team
• Tool 5: Problem analysis in 4 steps
• Tool 5a: Using 4 Step problem analysis with your team
• Tool 6: Questions that create possibilities
• Tool 6a: Using the 5 questions with your team
• Tool 6b: Putting creativity to work – 5 alternate questions
• Tool 6c: Workshop outline
• Tool 7: Evaluating alternatives
• Tool 8: Creative thinking techniques A-Z
• Tool 9: The 5 Whys technique

Further Reading

>> Return to Problem Solving Hub