
The Hidden Cost of a Bad Manager: 7 Signals That Show Up Before Anyone Complains
Christian Timotti
Led operations teams at Whirlpool, Philips and CEVA · September 30, 2026
No P&L has a line called "poor leadership." The cost shows up wearing other clothes: turnover, rush shipping, a project that slipped twice. Here are seven signals that appear in your operation long before anyone files a complaint.
I've seen this in several companies. The manager whose numbers looked acceptable, whose team quietly emptied out over eighteen months, and whose real cost nobody could put a number on until long after they'd moved on.
That's what makes weak management so expensive. It doesn't announce itself. Nobody walks into a leadership meeting and says the problem is a manager. And no P&L has a line called "poor leadership," so the cost shows up wearing other clothes. It arrives as turnover. As rush shipping. As a project that slipped twice. As a customer who stopped calling and nobody asked why.
After twenty-five years in supply chain and operations, I stopped waiting for someone to complain. The signals are usually sitting in numbers you already collect.
Here are seven.
Problems reach you late, and always from the same place
Issues don't get worse because they're hard. They get worse because they traveled slowly. When people feel uncomfortable raising something, or making a suggestion, it sits at team level until it's too big to hold, and then it lands on your desk as an emergency.
Watch the timing rather than the volume. If problems from one area consistently reach you two days later than problems from everywhere else, that gap has nothing to do with the work itself. It's telling you how safe people feel speaking up.
What to do: Start recording two dates for every significant issue: when it actually happened, and when it reached management. The distance between them is the number you want. Compare it across teams. One manager's figure will stand out, and it'll be the same one next quarter.
Your best person leaves and takes years of experience with them
We usually calculate turnover as recruitment plus training. That badly understates what walks out the door.
When an experienced planner or supervisor leaves, you lose the knowledge of which supplier actually delivers on the date they promise, which customer will accept a partial shipment rather than wait, and which machine needs a different setup when the humidity climbs. None of that lives in a system. It took six years to build. It takes about a week to lose, and the person replacing them has to rebuild all of it from scratch.
What to do: Look at who's leaving, not only how many. Ten people leaving from across the business tells you something about the labor market. Three leaving from the same manager inside a year tells you something else entirely. Read the exit interviews for that team on their own, and pay attention to what people carefully didn't say.
It took six years to build. It takes about a week to lose.
Rush shipping costs climb and nobody can explain why
Premium freight is the most honest metric in any operation. It's what you pay to recover from a decision that came too late, or never came at all. Air freight instead of ocean. A dedicated truck instead of a shared load. Somebody's weekend.
A weak manager generates this cost structurally, not occasionally. Decisions wait for them. Priorities stay vague, so the team ends up serving whoever shouted most recently. The cost line climbs, and every month it gets explained away as supplier problems or demand swings. That's how it survives for years without anyone naming it.
What to do: Code every rush shipment for four weeks by root cause, and make sure one of your categories is "decision made late." Most operations don't have that category, which is exactly why the pattern stays invisible. Four weeks of honest coding usually makes the argument for you.
The same problem gets solved every month
Sit through a management review for a quarter. If the same issue shows up three months running, described as resolved each time, you're not looking at a hard problem. You're looking at someone treating symptoms.
There's usually a reason. The real cause sits in another department, or in a process the manager helped design, and both of those require an awkward conversation. Symptoms are easier. They also generate visible activity, which looks like progress.
What to do: Keep a recurrence log. Anything appearing in three consecutive reviews gets escalated automatically, and the question changes from "what happened?" to "why is this still here?"
People stop bringing you bad news early
This one does the most damage, and it's the hardest to spot, because the symptom is silence.
Nobody decides to hide problems. They learn it, one reaction at a time. Someone brings something forward, the response costs them more than staying quiet would have, and they adjust. The manager usually has no idea it's happening, because from where they sit the team looks calm.
What to do: Pay attention to how you find things out. If you're consistently hearing about problems from other departments, from customers, or from your own walk through the floor rather than from the team who owns them, the information path is broken somewhere. That's a leadership issue wearing a communication costume.
The manager's own numbers look fine
Here's the part that keeps weak managers in place for years. They often hit their targets.
They hit them by spending things that never appear on their scorecard. The goodwill of the teams around them. Their people's evenings. The inventory buffer somebody else is carrying to cover their variability. The capability of a team nobody is developing. The performance is genuine. So is the cost, but it lands two departments over and two quarters later, and by then nobody connects it back.
I've watched this one play out more than any other on this list, and it's the reason good operations tolerate bad management far longer than they should.
What to do: When a team posts a strong result, ask what it consumed. If they hit the number while turnover rose, overtime climbed, and the teams around them absorbed more rework, you didn't get a gain. You moved a cost somewhere less visible.
You didn't get a gain. You moved a cost somewhere less visible.
Nobody argues in the meeting
Silence in a team meeting reads as alignment. Usually it's just silence.
Real alignment is noisy on the way to a decision and united afterwards. When you see the reverse, quiet in the room and disagreement in the corridor, the actual decision-making has moved somewhere you can't observe it. The manager is collecting consent rather than commitment, and those behave very differently when something goes wrong.
What to do: Sit in on a team meeting you weren't scheduled to attend and count how often someone contradicts the manager. Zero should worry you. Afterwards, ask the manager what they heard. The gap between what got said and what they registered will tell you more than the meeting did.
What This Actually Costs
The countable costs are the smaller half. Recruitment, onboarding, the productivity gap while somebody new gets up to speed. Those land in a spreadsheet and someone owns them.
The bigger costs never get attributed to anyone. The supplier who quietly stopped offering you flexibility. The improvement project that died because the team had no appetite for another initiative. The capable person who stayed but stopped bringing ideas. Nobody traces those back to a manager, which is precisely why the problem lasts.
If You Recognize One Of Your Managers Here
Most weak managers aren't bad people. They got promoted for being excellent at the job below the one they hold now, and then nobody taught them the new one. That's an organizational failure before it's an individual one, which also means it's usually fixable, and fixing it costs less than the turnover it prevents.
Four things that work:
- Name the behavior, not the character. — "Your team escalates late" is something a person can act on. "You're not a people person" isn't.
- Give them routines before theory. — Most struggling managers have never actually been shown what a good one-to-one looks like, or been told that delegation has levels and you're supposed to say which one you mean.
- Set a review date and keep it. — Without a date, support drifts into an open-ended hope.
- Decide upfront what happens if nothing changes. — Honestly, the organizational damage comes less from the weak manager than from everyone watching nothing happen about it for two years.
Reflection
Think about the strongest operational result your business delivered last quarter.
Now ask what it consumed, and whether anyone counted that.
Before you close this
Who came to mind while you were reading?
If someone you work with would recognize themselves in one of these signals — or would sleep better knowing what to look for — send it to them. It is a shorter conversation than the one that happens two years from now.
About the Author
Christian Timotti
Founder of Carpe Omnia. 28+ years of executive experience in supply chain, operations, and leadership development.
