Many executive teams move quickly to decisions but skip the shared learning needed to solve complex problems for good. This post explores a working hypothesis that real executive problem-solving requires a deliberate learning loop — not just decisive action — to create durable results.
In many organizations, executive meetings end with clear decisions and assigned actions. What's less clear is whether those decisions are grounded in enough shared learning to solve the underlying problem. What I'm questioning is whether executive problem-solving has quietly become synonymous with decision-making, rather than with shared learning. That tension is what I want to explore here: are executive teams doing real problem solving — or primarily implementing decisions and hoping they work?
What follows is a working hypothesis, not a finished model or a branded offering. I'm sharing it to test whether it resonates — and I genuinely welcome reactions, pushback, and examples from your own experience.
The hypothesis is this:
Many executive teams are trying to address real, important business problems — but they do so in ways that skip the learning required for those solutions to actually work.
Or, put in Lean terms… they're not following Plan, Do, Study, Adjust (PDSA) cycles. Just Plan and Do. Or maybe just Do.
What I'm Observing in Senior Leadership Teams
Senior leaders are usually focused on the right things:
- Growth
- Cost pressures
- Quality
- Customer retention
- Managing complexity as organizations scale
The issue doesn't necessarily seem to be problem selection.
It's what happens after the problem is named.
A Common Pattern in Executive Problem Solving
A familiar pattern shows up:
- The issue is discussed (or leaders jump to solutioning)
- Opinions are exchanged
- A decision is made
- Actions are assigned
- Progress is reviewed
This looks like effective leadership.
And yet…
the same problems often return — sometimes under new names, sometimes with new initiatives layered on top.
A quick self-check for leadership teams
As you read this, you might ask yourself:
- Do our executive meetings end with decisions but little new understanding?
- Do we revisit the same issues quarter after quarter?
- Do different leaders leave meetings with different interpretations of “the problem”?
- Do we move to solutions faster than we clarify causes?
If you answered “yes” to more than one of these, this hypothesis may be worth exploring.
My Hypothesis: Decisions in Place of Learning
For example, I often see leadership teams identify a cost problem, agree it's serious, and quickly move to hiring freezes, restructuring, or technology investments. Months later, costs may dip — then rebound. When the issue resurfaces, it's treated as a new problem rather than evidence that the original understanding was incomplete.
I'm wondering if the real gap is this:
Executive teams are relying on decisions to substitute for shared understanding and learning.
In other words:
- Deciding is treated as problem-solving
- Authority substitutes for evidence
- Speed substitutes for clarity
From the outside, this can look decisive.
From a systems perspective, it often produces fragile results.
Why Executive Teams Skip the Learning
A few possible contributing factors (this is where I'd especially welcome your thoughts):
- Executives are rewarded for confidence and answers, not visible learning
- There's little shared problem-solving discipline at the senior level
- Analysis is delegated downward, while decisions stay at the top
- Executive meetings aren't psychologically safe places to say “I don't know”
- Metrics are reviewed without understanding variation or system behavior
None of this is about competence or intent. It's about how executive work is structured.
A Concept I'm Exploring: The Executive Learning Loop
As a way to describe an alternative, I've been experimenting with a concept I'm calling The Executive Learning Loop.
This isn't meant as a program or a prescription — more as a way to describe a missing capability.
At a high level, the idea is simple:
Before making decisions about complex business problems, executive teams need a visible, shared way to learn together.
The “loop” looks something like this:
- Clarify the business problem (why this matters now)
- Understand current reality (what's actually happening)
- Explore what's driving today's results
- Test potential countermeasures on a small scale
- Reflect on what was expected vs. what happened
- Decide — with better understanding
Under the hood, this thinking is strongly influenced by A3 problem solving and the Toyota Business Practice — but I'm intentionally trying to describe the behavior, not the tool.
What Might Change If Executive Teams Learned First
If executive teams had a more explicit learning loop, I suspect we'd see:
- Fewer initiatives, with clearer intent
- Better alignment before execution begins
- Less rework at the strategy level
- Earlier surfacing of assumptions and risks
- Problems that are more likely to stay solved
I also suspect it would shift something cultural at the top:
From “leaders need answers”
to “leaders create the conditions for learning.”
What I'm not saying
I'm not suggesting that executive teams lack intelligence, experience, or commitment.
I'm also not arguing for slower organizations or endless analysis.
The question I'm raising is simpler — and harder:
Are leadership teams creating enough shared learning before committing to solutions that shape the rest of the organization?
Where I Need Your Help
This is where I'd really appreciate reader input.
- Does this hypothesis resonate with your experience?
- Where do you see executive problem-solving break down?
- What am I oversimplifying or missing?
- Have you seen senior teams that do learn well together? What's different?
- Is “learning loop” the right language — or does it miss something important?
I'm not trying to sell anything here. I'm trying to understand whether this pattern is real, useful to name, and worth developing further.
As always, the comments (and emails) tend to be where the real learning happens.
I plan to explore this further — including what this might look like in practice — and I'm especially interested in where this hypothesis breaks down.
Please scroll down (or click) to post a comment. Connect with me on LinkedIn.
If you’re working to build a culture where people feel safe to speak up, solve problems, and improve every day, I’d be glad to help. Let’s talk about how to strengthen Psychological Safety and Continuous Improvement in your organization.
