breadcrumb line

Building the Management Muscle

One of the most revealing things we do in an operational analysis is to shadow a manager for a day. Ask that manager at 8:00 a.m. how they expect to spend their time and you will usually hear some combination of managing the team, solving problems, coaching people, and improving the operation.

Then the day starts. Someone calls in sick. A customer issue gets escalated. Material is late. A report needs to be fixed. An employee has a question. The schedule changes. Something that should have happened yesterday didn’t. Before long, the manager is answering questions, expediting work, moving people around, and occasionally stepping in to do the work themselves.

At the end of the day, they have solved a lot of problems. But how many of those problems will be waiting for them again tomorrow?

When we conduct day-in-the-life studies, we analyze where managers actually spend their time. The pattern is remarkably consistent. Somewhere between 40% and 60% of a manager’s day may be spent reacting to problems or fighting fires, while often only 1% to 3% is spent identifying and solving the root causes of those problems.

Most CEOs recognize the pattern immediately because they experience some version of it themselves. It isn’t that managers don’t want to solve root causes. Most aren’t aware of how much of their day has become reactive. And they can’t simply ignore the customer escalation, the employee problem, the missing information, or the inbox filling up in front of them. So, the cycle perpetuates itself. They get very good at fighting fires, but they never get enough distance from the fire to figure out why it keeps starting.

This Is Where Plans Start to Fail

Most annual plans ask an organization to do something it is not doing today: grow faster, improve margins, increase throughput, integrate an acquisition, reduce waste, improve service, or introduce a new management process. Every one of those goals introduces new demands on the people responsible for running the business.

That is where capability starts to matter. Leaders often build the plan around what needs to change without spending enough time considering two important questions: Do our managers have the time to manage differently? And, if they do, have we taught them how?

You can’t simply ask a manager who already spends half the day fighting fires to spend more time solving root causes. To them, that sounds like one more responsibility being added to a day that is already full. Before capability can grow, some of the whirlwind has to come out.

That starts with understanding what’s creating it. When we map reactive time, we can usually begin to see patterns. Maybe managers are sitting in ineffective meetings. Maybe they aren’t receiving the right information from the department before them. Maybe decisions keep escalating because roles are unclear. Maybe the same staffing or scheduling issue appears every week. Once those patterns are visible, leadership can begin removing the conditions that create unnecessary firefighting.

When those management skills and routines are underdeveloped, the annual plan doesn’t necessarily collapse, but it does get absorbed into the existing whirlwind, and the new initiative becomes one more thing on the list.

Managers continue solving today’s problems rather than preventing tomorrow’s. Meetings become status updates. Training happens, but old habits return. Changes get launched but never fully settle into the operation. The plan may be perfectly sound. The organization simply hasn’t built enough management muscle to carry it.

What Leaders Commonly Get Wrong

The first mistake is confusing responsiveness with capability. Firefighting is highly visible. The manager who jumps into a crisis, fixes the customer problem, fills the staffing gap, and gets production moving again looks valuable. They are valuable.

The danger comes when this becomes the primary definition of good management. A manager can be exceptionally skilled at putting out fires without ever reducing the number of fires the organization creates. In fact, some of the managers an organization considers indispensable are indispensable precisely because so much knowledge and problem-solving ability remains concentrated in them. Every unusual situation comes back to the same person. They are constantly needed. That may feel like evidence of capability, but it is usually evidence that capability hasn’t spread across the department or organization.

The second mistake is assuming that training creates capability. Training creates knowledge. That’s important, but it is only the beginning.

A manager can spend a day learning how to run a better meeting, coach an employee, build a useful dashboard, communicate with different personalities, or work through the root cause of a problem. Then they return to an environment that is moving quickly, full of competing priorities and people who do not behave like the examples in the training deck.

The Learning Guild (1), drawing on research around the forgetting curve, summarizes the challenge this way: people may forget roughly 50% of newly presented information within an hour, 70% within 24 hours, and 90% within a week when that learning is not reinforced. The exact rate will vary by person and circumstance, but the implication for management development is clear: exposure to an idea is not the same as being able to apply it.

What Builds Capability

In our own management training, the classroom portion is intentionally only one part of the process. Managers learn the concepts first. Then comes the part where the learning starts to become useful: they try it, someone watches, they debrief what happened, and then they try it again.

That shoulder-to-shoulder piece matters because managers are often being asked to use muscles they haven’t used before. Running a structured one-on-one may sound simple until the employee gives an unexpected answer. Root-cause problem-solving may make perfect sense on a whiteboard until five different causes appear plausible. Coaching rather than directing sounds straightforward until you are under pressure and already know the answer yourself.

Having someone there in those early repetitions to observe, question, and course correct helps turn an idea from the classroom into a management habit. Over time, the questions start to change. Instead of immediately asking, “How do we fix this?” a manager might ask: What happened? What should have happened? Why is there a gap? Have we seen this before? What is actually causing it? And what would prevent it from happening again?

We saw the impact of that shift at a major pharmaceutical manufacturer. Frontline employees became better at surfacing operating problems while managers developed a more consistent way of working through root causes. The important part wasn’t creating a longer list of issues. Most organizations already have plenty of those. It was developing the ability to do something useful with them.

Instead of repeatedly working around the same sources of loss, teams became better at identifying, escalating, investigating, and eliminating them. Unit production costs ultimately fell from approximately 25 cents to below 23 cents—an small unit-level change that translated into millions of dollars in savings at scale.

The result wasn’t achieved because of one breakthrough idea. It came from dozens of better management decisions accumulating over time.

When Problems Start Arriving Differently

There is a maxim Carpedia has used for years: Bring solutions, not problems. That doesn’t mean employees should hide a problem until they have figured everything out themselves. There are plenty of situations where a manager needs to know about an issue immediately. The distinction is whether the problem arrives with any thinking attached.

Compare, “We’ve got a problem. What should I do?” with, “Here’s what happened. I think this is what’s causing it. I’ve looked at two ways we could handle it, and here’s the one I’d recommend.”

The manager may still need to help. The proposed solution may even be wrong. But the second conversation is building autonomy while the first one isn’t. Eventually, managers spend less time answering questions their teams are capable of answering themselves, employees become more comfortable thinking through options, and problems are solved closer to where they occur. That’s how capability spreads beyond the person who originally had it.

The Last Degree

Sam Parker and Mac Anderson popularized a simple analogy in 212° The Extra Degree (2). At 211 degrees Fahrenheit, water is hot. At 212, it boils. The point of the analogy is that the final degree can be the difference between effort and a fundamentally different result.

We see a version of that constantly in execution. The problem was identified. The root cause was found. A solution was designed. The process changed. Everyone was informed. The action item was checked off. Taken together, that can feel like 100%. More often, it’s 95%.

The difficult final piece (that last degree needed to reach boiling point) is going back to see what actually happened. Did people adopt the new behavior? Is it happening consistently? Did it solve the problem we thought it would solve? Did the expected operational or financial result show up? Or did everyone quietly find a workaround three weeks later?

This final degree is particularly vulnerable because, by the time a solution has been implemented, the next problem is already competing for attention. Capable managers resist the urge to equate action completed with outcome achieved. They stay with the issue long enough to know the difference.

Building the Management Muscle

A CEO cannot personally coach every supervisor, solve every root cause, or keep every improvement in place. Nor should they. The leverage comes from creating an organization in which managers have enough space to manage and enough capability to make good use of that space.

You begin to see the effect in small ways. The same fires stop appearing quite as often. Managers ask more questions before giving answers. Employees bring problems with thinking attached. Coaching happens closer to the work. Issues get solved at lower levels of the organization rather than automatically escalating. And improvements continue producing results after the people who originally introduced them have moved on.

That is management muscle. Not a manager who can carry more and more of the organization on their back, but an organization that becomes progressively better at carrying itself.

  1. Source: Art Kohn, “Brain Science: The Forgetting Curve—The Dirty Secret of Corporate Training,” The Learning Guild, March 13, 2014.
  2. Parker, Sam, and Mac Anderson. 212° The Extra Degree: Extraordinary Results Begin with One Small Change.Sourcebooks, 2018

Award-winning consulting firm

  • Canada's Most Admired Corporate Cultures 2025
  • Top Consulting Firm 2025, Consulting.ca
  • Top Management Consulting Firm 2025
  • Great Place to Work Certified
  • Business Insider America's Top Management Consulting Firms 2026
  • Global 100 2026 Winner