Part one established that meetings are a symptom. This post is about the disease — the management behaviours that produce not just bad meetings, but disengaged teams, talent departure, and the specific organisational sadness of watching smart people slow themselves down to match the pace of a badly run room.
None of what follows requires a villain. Every habit on this list is exhibited, somewhere, by someone who genuinely wants their team to do well. That is precisely what makes them worth naming.
The manager who equates presence with productivity — who notices who arrives first and leaves last, who replies fastest, who speaks most in meetings. The result is a team that optimises for being seen rather than for doing good work. The best performers, who tend to be efficient rather than performative, quietly start job hunting.
Tell: your team knows who's "always on" but couldn't rank them by actual output.
Someone brings you a problem. You solve it. This feels productive — you have moved something forward. What you have actually done is removed a learning opportunity, confirmed that escalation works, and ensured the next time this happens they will bring it to you again. The manager who solves everything becomes the bottleneck for everything.
Tell: your team's first move when stuck is to find you, not to try something.
The underperformer everyone knows about but nobody has spoken to directly. The team dynamic that's been quietly toxic for eight months. The behaviour that should have been addressed after the first incident, not the fifth. Each delay costs more than the conversation would have — in morale, in trust, and eventually in the dramatic exit that nobody saw coming, even though everyone did.
Tell: you have rehearsed a difficult conversation more than three times and still haven't had it.
Checking in on work that doesn't need checking. Requesting updates on things that are clearly fine. Reopening decisions that were made well and made clearly. The manager who does this usually has genuine anxiety about outcomes — but the message received by the team is simply: "I don't trust you." That message, received consistently, turns confident professionals into cautious ones.
Tell: your team asks for approval before taking actions they are clearly qualified to take alone.
Priorities shift — that is reality. The damaging version is when they shift without naming what got deprioritised. The work that just became irrelevant, and without any apparent recognition that the team has now spent three weeks on something that is being quietly shelved. People can handle change. They cannot handle feeling like their effort was invisible.
Tell: your team has learned not to get too attached to any project because something will probably supersede it.
The manager who avoids friction at all costs — who hedges feedback to soften it into meaninglessness, who agrees in the room and equivocates after it, who would rather be comfortable than clear. These managers tend to have good relationships and low-performing teams. Being liked and being trusted are not the same thing. Trust requires honesty. Honesty sometimes costs comfort.
Tell: your team describes you as "really nice" but struggles to tell you what you actually think about their work.
The antidote to each of these is not its opposite taken to an extreme. You do not fix micromanagement with complete abdication. You do not fix conflict avoidance by becoming combative. The correction in each case is something more precise — a recalibration rather than a reversal.
The single most reliable indicator of a good manager is not how they behave when things are going well. It is how quickly and clearly they communicate when things are not. That quality — the willingness to be honest in proportion to its importance — is rarer than any technical skill and harder to teach.
Reading a list like this, most managers will nod along at the habits they see in other people and feel a mild twinge at one or two of their own. That twinge is the useful bit. The question worth sitting with is not "do any of these apply to me?" — almost certainly some do — but "which one is my team most currently paying the price for?"
That answer, honestly held, is the only one worth acting on. Because fixing a management habit requires more than knowing it exists. It requires noticing, in real time, the specific moment when the old pattern is about to run — and choosing something different instead. Which is, as it happens, the subject of part three: how to actually build a team culture where that kind of quality shows up consistently, without you having to hold it all together personally.
