Most leadership teams are incredibly good at one thing: experiencing their problems. The hard part is not naming what is wrong. The hard part is operational problem solving, the discipline of actually moving a stuck issue to resolved.
They can describe them in detail. They’ve been living with them for months, sometimes years. The meeting about the problem is on the recurring calendar. Everyone in the room knows exactly what’s wrong.
And nothing changes.
This isn’t a failure of intelligence. It’s a failure of operating environment. And it’s one of the most expensive habits a leadership team can develop.
Fluent in the Problem, Illiterate in the Solution
Most teams, when they encounter a persistent operational problem, do roughly the same thing: they convene, discuss, diagnose, and then schedule a follow-up meeting. The problem gets documented. It gets tracked. It gets its own recurring agenda item.
What it doesn’t get is solved.
Part of this is structural. Organizations that haven’t built a decision-making culture default to discussion. Discussion feels like progress. It produces artifacts (meeting notes, action items, slide decks) that look like forward motion. But artifacts aren’t outcomes. A well-documented problem that keeps repeating is still a problem.
Part of it is psychological. Sitting in the problem is low-risk. As long as you’re still analyzing, you haven’t committed to a solution that might not work. The moment you act, you’re accountable for the result. So the analysis phase extends, because it’s safe there.
The cost compounds quietly. Every week the problem continues, it costs money, capacity, morale, or customer trust, usually all four. And over time, the problem starts to feel like weather. Uncomfortable, but just how things are.
That’s when it becomes truly expensive. Not because the problem is unsolvable. Because the organization has stopped believing it is.
The Shift That Turns Discussion Into Operational Problem Solving
The teams that break out of this pattern share one trait: someone in the room forces a different question.
The typical question is some version of “What’s the problem?” The teams that move ask: “What would have to be true for this to be solved? What’s the smallest thing we could do this week to test whether that’s right?”
The first question keeps the team oriented toward the past, toward what went wrong and who owns the pain. The second orients them toward the future and, critically, toward action.
At Amazon, waiting for perfect information wasn’t an option. You made a call on the best data you had, watched what happened, and adjusted. That discipline is a big part of why a billion-unit fulfillment network could scale the way it did. The answer to an incomplete information environment is never more analysis. It’s a hypothesis, a test, and a result you can actually learn from. That same instinct is what separates a real operating cadence from review theater, where the deck looks clean and nobody actually decides.
Stop Letting the Problem Run You
Priorities shift constantly because whoever is in most pain gets the most attention. The same issues surface in every weekly meeting. The founder is the default owner of anything that isn’t clearly someone else’s job, which means the founder is the default owner of most things. The team has stopped bringing up certain problems because bringing them up doesn’t lead anywhere.
Getting control means breaking that cycle deliberately. Not by having all the answers, but by refusing to let the organization stay comfortable with problems that are costing real money.
The founders who made this shift didn’t do it by working harder or getting smarter. They did it by changing the operating environment: the questions their teams were allowed to stay stuck on, the way decisions got made and owned, the standard for what counted as resolution versus what counted as ongoing management.
That operating environment is something you build. It doesn’t happen on its own.
Find a Solution, Act, and Iterate
Most teams never get to resolution not because they can’t solve the problem, but because they’re waiting for the solution that’s guaranteed to work before they commit to any solution at all. That solution doesn’t exist. Waiting for it is how you stay stuck.
A few disciplines that change this consistently:
Separate diagnosis from decision. Most meetings try to do both at once and do neither well. Diagnosis produces a clear problem statement and the information needed to act. Decision starts from that statement and answers three questions: what are we going to do, who owns it, and by when. Keep these separate. Force the team to complete the diagnostic before reaching for solutions, and to reach for solutions before the meeting ends.
Kill the parking lot. Every leadership team has a list of things to revisit later. Items go in and rarely come back out. When a problem gets parked, it’s usually because no one wants to own it. Before anything gets parked, ask: is this a real priority or are we avoiding a hard decision? If it’s real, it gets an owner and a date. If it isn’t, drop it.
Make iteration the expectation, not the failure mode. Most teams treat a solution that doesn’t fully work as a failure. This makes people risk-averse and slow. The teams that move fastest treat every action as a test: we tried this, we learned that, we adjusted. The goal isn’t to be right on the first attempt. The goal is to generate learning fast enough to get to right before the problem costs more than the iteration.
Hold the line on single ownership. Decisions made by committees rarely get executed. When a problem has multiple owners, it has no owner. One person, accountable for an actual outcome, not a deliverable or a process, but a result. That single change is one of the highest-leverage moves a leadership team can make.
Why This Is Hard to Do From Inside
The challenge with changing how a team thinks is that you’re working against habits that feel like strengths. A team that’s good at analysis thinks that rigor is why it’s good. A founder who has managed every hard call personally thinks that control is what makes the business work.
Breaking those patterns from the inside is genuinely difficult. You’re too close to see the habit clearly, too embedded in the culture to challenge it without political cost, and you have existing credibility invested in the way things currently work.
This is a significant part of what a fractional operating partner does, not just fixing the operational infrastructure, but changing how the leadership team uses it. Building the habits and the environment where operational problem solving is the default, not a special effort. If you want to see what that looks like day to day, here is a week in the life of a fractional operating partner.
The strategic advisory work I do often involves exactly this: sitting with a founder or executive team and doing the slow work of replacing problem-experiencing with problem-solving. Not a new methodology or a reorg, but changing the questions the team asks in every meeting, until asking better questions becomes automatic.
The Starting Point
If your leadership team is smart, well-intentioned, and still stuck on the same problems it was stuck on a year ago, the issue probably isn’t the problems. It’s the pattern.
The Forge Assessment is the diagnostic that shows you where your highest-cost operational and organizational problems actually live, what they’re costing you, and what needs to change first. It’s also the beginning of a different kind of conversation, one oriented toward moving, not analyzing.
The problems aren’t going anywhere on their own. The question is whether your team is set up to solve them.
Learn more about The Forge Assessment →
Jason Bonito is the founder of Crucible76, a fractional operating partner practice helping growing businesses fix operational chaos, scale their teams, and drive real growth. DATA · DECISIONS · GROWTH.
