Executive Problem Solving: Are You Learning, or Just Deciding?

TL;DR: Deciding feels like progress, and learning is what makes a solution hold. This is a working hypothesis about why executive problem solving so often skips the second part, and where I suspect it falls apart.

The meeting goes well. The problem gets named, the discussion is sharp, and by the end there's a decision everyone can live with. Owners get assigned, calendars updated. People walk out feeling like they accomplished something, because they did do something. A choice got made.

Then a quarter goes by. Sometimes two. And the same problem is back on the agenda, wearing a slightly different outfit. Costs crept back up. The retention fix didn't hold. The reorg that was supposed to settle things created three new questions instead. So the team does what it did last time. It discusses, it decides, it assigns, it moves on.

I've started to wonder whether a lot of executive problem-solving has quietly turned into something else: decision-making that feels like problem-solving but doesn't resolve much. That's the tension I want to put on the table. Are leadership teams actually solving problems, or mostly making decisions and hoping they work?

What follows is a working hypothesis, not a finished model and definitely not a branded offering. I'm putting it out to see whether it survives contact with your experience. I want the pushback as much as the agreement.

Here it is. Most executive teams are working on real, important problems. They just work on them in a way that skips the learning those solutions need in order to hold. In Lean terms, they're not running Plan, Do, Study, Adjust cycles. They're running Plan and Do. Sometimes just Do.

The problem usually isn't the problem they pick

Senior leaders tend to be pointed at the right things. Growth, cost pressure, quality, customer retention, the steady complexity that comes with scale. I rarely look at an executive agenda and think they've chosen the wrong issues.

What happens after the problem gets named is where it gets interesting. A familiar sequence kicks in. The issue gets discussed, or someone jumps straight to a solution. Opinions are exchanged. A decision gets made, actions get assigned, and progress gets reviewed at the next meeting. From the outside, this is exactly what good leadership is supposed to look like.

And yet the same problems keep coming back, sometimes renamed, sometimes with a fresh initiative stacked on top of the last one.

A quick self-check for your leadership team

If you want to test this against your own meetings, a few questions:

• Do our meetings end with decisions but not much new understanding?
• Do we revisit the same issues quarter after quarter?
• Do different leaders walk out with different versions of what “the problem” even is?
• Do we reach for solutions faster than we get clear on causes?

If more than one of those lands, the rest of this is probably worth your time.

Why deciding gets mistaken for solving

Here's the part I keep turning over. Deciding is fast, and it feels like progress. Learning is slower, and it feels like delay. So under pressure, with a room full of capable people who got promoted for being decisive, the team picks the thing that feels like progress.

The catch is that the cost of skipping the learning doesn't go away. It just shows up later, usually as the same problem returning. And the same problem returning is the expensive kind. Solving something once is work. Solving it twice is waste.

I see a version of this with cost problems all the time. A leadership team names the cost issue, agrees it's serious, and moves quickly to a hiring freeze, a restructuring, or a technology investment. Costs dip for a while, then drift back up. When they resurface, they get treated as a brand-new problem rather than as evidence that nobody fully understood the first one.

Put another way, decisions are standing in for shared understanding. Authority ends up doing the work that evidence should do, and speed does the work that belongs to clarity. It looks decisive from across the table. From a systems view, it tends to produce fragile results.

A few guesses at why this happens

This is where I'd most like your help, because I'm speculating. A few things that might explain it. Executives get rewarded for confidence and answers, not for visible learning. There's often no shared problem-solving discipline at the senior level the way there might be in an improvement team or out on a floor. Analysis gets delegated downward while the decisions stay up top, so the people deciding aren't the people who looked closely. And plenty of executive rooms aren't safe places to say “I don't know” out loud, which is its own kind of problem. Reviewing metrics without understanding variation or system behavior doesn't help either.

None of that is about intelligence or intent. It's about how the work at the top is structured.

The Executive Learning Loop

To describe the alternative, I've been playing with a concept I'm calling the Executive Learning Loop. I don't mean it as a program or a prescription. It's just a way to name a capability that often seems to be missing.

The idea is plain. Before deciding on a complex business problem, an executive team needs a visible, shared way to learn together first.

Roughly, the loop looks like this:

• Clarify the business problem, and why it matters now
• Understand current reality, what's actually happening
• Explore what's driving today's results
• Test a possible countermeasure on a small scale
• Reflect on what you expected versus what happened
• Then decide, with better understanding

Underneath, this is heavily shaped by A3 thinking and the Toyota Business Practice. I'm deliberately describing the behavior instead of handing over the tool, because the tool tends to become the point and the thinking gets lost.

What might change if teams learned first

I have suspicions, not proof. If executive teams ran something like this loop, I'd expect fewer initiatives carrying clearer intent, better alignment before execution starts, less rework at the level of strategy itself, and assumptions and risks surfacing earlier instead of after launch. Mostly I'd expect more problems that actually stay solved.

There's a cultural shift hiding in there too, and it's the one I care about most. It moves the job of a leader away from “I need to have the answer” and toward “I create the conditions where we can find one.”

What I'm not claiming

I'm not saying executive teams lack intelligence, experience, or commitment. I'm not arguing for slower organizations or analysis that never ends. The question is narrower than that, and harder. Are leadership teams building enough shared learning before they commit to the solutions that shape everyone below them?

Where I could use your help

This is the part I actually wrote the post for.

• Does this match what you've seen?
• Where does executive problem-solving break down in your world?
• What am I oversimplifying, or missing entirely?
• Have you watched a senior team that does learn well together, and what made it different?
• Is “learning loop” the right language, or does it miss something?

I'm not selling anything. I'm trying to figure out whether this pattern is real, worth naming, and worth building out further. The comments and the emails are usually where the actual learning happens around here. I plan to keep pulling on this thread, especially the places where the hypothesis falls apart, so tell me where you think it does.