Leadership
June 11, 2025
6
Min
The 7-Step Problem-Solving Process Leaders Actually Use
Problem Solving
|
That was the moment a regional COO, looked across the boardroom and admitted what everyone else in the room felt but hadn’t yet said aloud. The division’s customer churn hadn’t improved after three different interventions. Each time, the team had reacted fast - but also too shallow. No one had paused long enough to trace root causes or pressure-test assumptions.
So, we stepped in and introduced a rhythm. Not a magic formula, but a disciplined way to move from chaos to clarity. The results? Within a quarter, they halved churn and regained confidence across functions.
This blog is about that rhythm.
Executives face a volume of problems that aren’t just technical or logistical - they’re entangled, political, and emotionally loaded. Left unchecked, the tendency is to either act too fast or spiral into endless diagnosis.
According to McKinsey, fewer than 30% of transformation efforts succeed largely due to poor problem framing and inconsistent solution design.
We’ve seen it first-hand: seasoned leaders getting caught in the loop of "solution-first thinking." The real differentiator? A repeatable, cognitive process for solving high-stakes problems.
We call this framework “The Resolution Spiral”. Why a spiral? Because each step is meant to build on the last without becoming rigid - looping back when needed, evolving as the situation demands.
“What exactly are we trying to solve?”
Sounds basic, but most teams jump straight to solving a symptom.
We encourage framing problems in terms of outcomes and impact. Use techniques like the 5 Whys, or ask: If we fix this, what actually changes?
Reflection Prompt:
If your team had to write down the problem in one sentence, would everyone write the same thing?
Micro-action:
Run a 20-minute alignment session where each stakeholder defines the problem in writing. Compare. Discuss.
Break the beast into parts.
Think like a consultant: segment the problem using MECE (Mutually Exclusive, Collectively Exhaustive) logic.
For example, “customer churn” might split into onboarding, customer support responsiveness, and product-market fit.
Micro-action:
Create a simple tree diagram or whiteboard cascade breaking the big issue into bite-sized buckets.
Not all branches deserve your time.
Use data to identify which sub-problem has the highest leverage. Don’t confuse urgency with importance.
Ask: Which of these, if solved, creates the most value?
Pro Tip:
Use an impact vs. feasibility matrix to focus efforts.
Micro-action:
Rank each sub-issue by estimated impact and speed to resolution. Circle your top two.
Swap opinions for structured guesses.
At this point, we switch from “what’s wrong” to “why it’s wrong.”
Build hypotheses like: “We believe churn is high because the onboarding sequence overwhelms users.”
This narrows your investigation and makes data collection purposeful.
Reflection Prompt:
Are your team’s hypotheses falsifiable, or just vague assertions?
Micro-action:
Write 2-3 clear hypotheses. Plan how you’d prove or disprove each.
Don’t boil the ocean.
Now test your hypotheses with just enough data. This might mean user interviews, metrics deep dives, or quick experiments.
Pro Tip:
Use “decision-back” thinking: What data would change your mind?
Micro-action:
Set a 10-day window for lightweight data collection tied directly to your hypotheses.
Move from options to decisions.
Now generate a set of solutions. Then stress test them. What are the second-order consequences? What will this break? Who will resist?
Use a pre-mortem session: assume the solution failed - why?
Micro-action:
Shortlist two solutions. Run them through a decision quality checklist: desirability, feasibility, sustainability.
Resolve and reflect - or repeat the loop.
Choose a solution. Assign ownership. Track implementation rigorously - but don’t declare victory prematurely.
Build in learning loops. If it works, why did it work? If not, re-enter the spiral from Step 3 or 4.
Reflection Prompt:
What have we learned that applies to other teams, products, or regions?
Micro-action:
Schedule a 30-minute retrospective three weeks after launch. Make it sacred.
Want to operationalise this in your leadership context?
Build shared language.
Train your top 50 leaders on the spiral. Make it your organisation’s problem-solving OS.
Codify in templates.
Integrate this framework into decision memos, war rooms, and quarterly planning cycles.
Coach in real time.
Don’t make it academic. Use active problems to practice. Rotate facilitators. Build fluency.
Pro Tip:
Create a “Problem-Solving Guild” that meets monthly to workshop live challenges and cross-pollinate lessons.
Even experienced executives fall into traps:
Defaulting to solutions before diagnosis.
Confusing consensus with clarity.
Running analysis loops with no decision deadlines.
Over-engineering fixes for people problems.
What helps? Having one leader act as the “spiral steward” - someone who holds the team accountable to the rhythm.
Prompt 1:
When was the last time a well-intentioned solution of yours made things worse? What part of the spiral did you skip?
Prompt 2:
What’s one systemic issue in your organisation that’s being treated as a one-off fire?
It’s not about being methodical for the sake of it. It’s about creating a culture that gets better every time it solves something hard.
Pick one problem currently swirling in your leadership orbit. Gather your team. Walk through the first three steps. That’s it. Don’t overthink it.
And if you want a workbook version of the Resolution Spiral to try in your next offsite, just drop us a line.
Team SHIFT
"We’ve already thrown resources at it. We’ve restructured twice. And it’s still not working."
That was the moment a regional COO, looked across the boardroom and admitted what everyone else in the room felt but hadn’t yet said aloud. The division’s customer churn hadn’t improved after three different interventions. Each time, the team had reacted fast - but also too shallow. No one had paused long enough to trace root causes or pressure-test assumptions.
So, we stepped in and introduced a rhythm. Not a magic formula, but a disciplined way to move from chaos to clarity. The results? Within a quarter, they halved churn and regained confidence across functions.
This blog is about that rhythm.
Executives face a volume of problems that aren’t just technical or logistical - they’re entangled, political, and emotionally loaded. Left unchecked, the tendency is to either act too fast or spiral into endless diagnosis.
According to McKinsey, fewer than 30% of transformation efforts succeed largely due to poor problem framing and inconsistent solution design.
We’ve seen it first-hand: seasoned leaders getting caught in the loop of "solution-first thinking." The real differentiator? A repeatable, cognitive process for solving high-stakes problems.
We call this framework “The Resolution Spiral”. Why a spiral? Because each step is meant to build on the last without becoming rigid - looping back when needed, evolving as the situation demands.
“What exactly are we trying to solve?”
Sounds basic, but most teams jump straight to solving a symptom.
We encourage framing problems in terms of outcomes and impact. Use techniques like the 5 Whys, or ask: If we fix this, what actually changes?
Reflection Prompt:
If your team had to write down the problem in one sentence, would everyone write the same thing?
Micro-action:
Run a 20-minute alignment session where each stakeholder defines the problem in writing. Compare. Discuss.
Break the beast into parts.
Think like a consultant: segment the problem using MECE (Mutually Exclusive, Collectively Exhaustive) logic.
For example, “customer churn” might split into onboarding, customer support responsiveness, and product-market fit.
Micro-action:
Create a simple tree diagram or whiteboard cascade breaking the big issue into bite-sized buckets.
Not all branches deserve your time.
Use data to identify which sub-problem has the highest leverage. Don’t confuse urgency with importance.
Ask: Which of these, if solved, creates the most value?
Pro Tip:
Use an impact vs. feasibility matrix to focus efforts.
Micro-action:
Rank each sub-issue by estimated impact and speed to resolution. Circle your top two.
Swap opinions for structured guesses.
At this point, we switch from “what’s wrong” to “why it’s wrong.”
Build hypotheses like: “We believe churn is high because the onboarding sequence overwhelms users.”
This narrows your investigation and makes data collection purposeful.
Reflection Prompt:
Are your team’s hypotheses falsifiable, or just vague assertions?
Micro-action:
Write 2-3 clear hypotheses. Plan how you’d prove or disprove each.
Don’t boil the ocean.
Now test your hypotheses with just enough data. This might mean user interviews, metrics deep dives, or quick experiments.
Pro Tip:
Use “decision-back” thinking: What data would change your mind?
Micro-action:
Set a 10-day window for lightweight data collection tied directly to your hypotheses.
Move from options to decisions.
Now generate a set of solutions. Then stress test them. What are the second-order consequences? What will this break? Who will resist?
Use a pre-mortem session: assume the solution failed - why?
Micro-action:
Shortlist two solutions. Run them through a decision quality checklist: desirability, feasibility, sustainability.
Resolve and reflect - or repeat the loop.
Choose a solution. Assign ownership. Track implementation rigorously - but don’t declare victory prematurely.
Build in learning loops. If it works, why did it work? If not, re-enter the spiral from Step 3 or 4.
Reflection Prompt:
What have we learned that applies to other teams, products, or regions?
Micro-action:
Schedule a 30-minute retrospective three weeks after launch. Make it sacred.
Want to operationalise this in your leadership context?
Build shared language.
Train your top 50 leaders on the spiral. Make it your organisation’s problem-solving OS.
Codify in templates.
Integrate this framework into decision memos, war rooms, and quarterly planning cycles.
Coach in real time.
Don’t make it academic. Use active problems to practice. Rotate facilitators. Build fluency.
Pro Tip:
Create a “Problem-Solving Guild” that meets monthly to workshop live challenges and cross-pollinate lessons.
Even experienced executives fall into traps:
Defaulting to solutions before diagnosis.
Confusing consensus with clarity.
Running analysis loops with no decision deadlines.
Over-engineering fixes for people problems.
What helps? Having one leader act as the “spiral steward” - someone who holds the team accountable to the rhythm.
Prompt 1:
When was the last time a well-intentioned solution of yours made things worse? What part of the spiral did you skip?
Prompt 2:
What’s one systemic issue in your organisation that’s being treated as a one-off fire?
It’s not about being methodical for the sake of it. It’s about creating a culture that gets better every time it solves something hard.
Pick one problem currently swirling in your leadership orbit. Gather your team. Walk through the first three steps. That’s it. Don’t overthink it.
And if you want a workbook version of the Resolution Spiral to try in your next offsite, just drop us a line.
Team SHIFT
"We’ve already thrown resources at it. We’ve restructured twice. And it’s still not working."
That was the moment a regional COO, looked across the boardroom and admitted what everyone else in the room felt but hadn’t yet said aloud. The division’s customer churn hadn’t improved after three different interventions. Each time, the team had reacted fast - but also too shallow. No one had paused long enough to trace root causes or pressure-test assumptions.
So, we stepped in and introduced a rhythm. Not a magic formula, but a disciplined way to move from chaos to clarity. The results? Within a quarter, they halved churn and regained confidence across functions.
This blog is about that rhythm.
Executives face a volume of problems that aren’t just technical or logistical - they’re entangled, political, and emotionally loaded. Left unchecked, the tendency is to either act too fast or spiral into endless diagnosis.
According to McKinsey, fewer than 30% of transformation efforts succeed largely due to poor problem framing and inconsistent solution design.
We’ve seen it first-hand: seasoned leaders getting caught in the loop of "solution-first thinking." The real differentiator? A repeatable, cognitive process for solving high-stakes problems.
We call this framework “The Resolution Spiral”. Why a spiral? Because each step is meant to build on the last without becoming rigid - looping back when needed, evolving as the situation demands.
“What exactly are we trying to solve?”
Sounds basic, but most teams jump straight to solving a symptom.
We encourage framing problems in terms of outcomes and impact. Use techniques like the 5 Whys, or ask: If we fix this, what actually changes?
Reflection Prompt:
If your team had to write down the problem in one sentence, would everyone write the same thing?
Micro-action:
Run a 20-minute alignment session where each stakeholder defines the problem in writing. Compare. Discuss.
Break the beast into parts.
Think like a consultant: segment the problem using MECE (Mutually Exclusive, Collectively Exhaustive) logic.
For example, “customer churn” might split into onboarding, customer support responsiveness, and product-market fit.
Micro-action:
Create a simple tree diagram or whiteboard cascade breaking the big issue into bite-sized buckets.
Not all branches deserve your time.
Use data to identify which sub-problem has the highest leverage. Don’t confuse urgency with importance.
Ask: Which of these, if solved, creates the most value?
Pro Tip:
Use an impact vs. feasibility matrix to focus efforts.
Micro-action:
Rank each sub-issue by estimated impact and speed to resolution. Circle your top two.
Swap opinions for structured guesses.
At this point, we switch from “what’s wrong” to “why it’s wrong.”
Build hypotheses like: “We believe churn is high because the onboarding sequence overwhelms users.”
This narrows your investigation and makes data collection purposeful.
Reflection Prompt:
Are your team’s hypotheses falsifiable, or just vague assertions?
Micro-action:
Write 2-3 clear hypotheses. Plan how you’d prove or disprove each.
Don’t boil the ocean.
Now test your hypotheses with just enough data. This might mean user interviews, metrics deep dives, or quick experiments.
Pro Tip:
Use “decision-back” thinking: What data would change your mind?
Micro-action:
Set a 10-day window for lightweight data collection tied directly to your hypotheses.
Move from options to decisions.
Now generate a set of solutions. Then stress test them. What are the second-order consequences? What will this break? Who will resist?
Use a pre-mortem session: assume the solution failed - why?
Micro-action:
Shortlist two solutions. Run them through a decision quality checklist: desirability, feasibility, sustainability.
Resolve and reflect - or repeat the loop.
Choose a solution. Assign ownership. Track implementation rigorously - but don’t declare victory prematurely.
Build in learning loops. If it works, why did it work? If not, re-enter the spiral from Step 3 or 4.
Reflection Prompt:
What have we learned that applies to other teams, products, or regions?
Micro-action:
Schedule a 30-minute retrospective three weeks after launch. Make it sacred.
Want to operationalise this in your leadership context?
Build shared language.
Train your top 50 leaders on the spiral. Make it your organisation’s problem-solving OS.
Codify in templates.
Integrate this framework into decision memos, war rooms, and quarterly planning cycles.
Coach in real time.
Don’t make it academic. Use active problems to practice. Rotate facilitators. Build fluency.
Pro Tip:
Create a “Problem-Solving Guild” that meets monthly to workshop live challenges and cross-pollinate lessons.
Even experienced executives fall into traps:
Defaulting to solutions before diagnosis.
Confusing consensus with clarity.
Running analysis loops with no decision deadlines.
Over-engineering fixes for people problems.
What helps? Having one leader act as the “spiral steward” - someone who holds the team accountable to the rhythm.
Prompt 1:
When was the last time a well-intentioned solution of yours made things worse? What part of the spiral did you skip?
Prompt 2:
What’s one systemic issue in your organisation that’s being treated as a one-off fire?
It’s not about being methodical for the sake of it. It’s about creating a culture that gets better every time it solves something hard.
Pick one problem currently swirling in your leadership orbit. Gather your team. Walk through the first three steps. That’s it. Don’t overthink it.
And if you want a workbook version of the Resolution Spiral to try in your next offsite, just drop us a line.
Team SHIFT