Take the learnings from your worst manager
Nobody forgets their worst manager. You can probably name yours right now. You can probably still recite, with unsettling precision, the exact thing they did that made you close your laptop and stare at the wall.
That level of detail is the point.
Good management is mostly invisible. Things work. Blockers quietly disappear. You go home on time without ever really noticing why. Bad management is different. It's vivid. It leaves marks. You remember the meeting, the comment, the decision – and exactly how it made you feel.
The mistake most people make is treating a terrible manager as something to survive and then forget, like food poisoning. Survive, yes. Forget, no.
Your worst manager is one of the most detailed case studies in failure you'll ever get for free. Unlike a book on leadership, you were there for every incident. You had the full context. You experienced the consequences firsthand.
So instead of just asking, "How did they get this so wrong?", ask a more useful question: "What can I learn from it?"
Good examples are vague, bad examples are specific
Ask someone what made their best manager great and you get abstractions: "she trusted me", "he had my back", "they gave me room to grow". True, useless. You cannot operationalise "had my back". It compresses a hundred small, situational decisions into a warm feeling.
Now ask what made their worst manager awful and the answers arrive with timestamps.
"She rewrote my status report at 11pm, changed important details and then shared with leadership without telling me."
"He agreed to the scope change in the meeting, then blamed me for the scope change in the retro."
"She asked for detailed daily updates on a task we'd estimated at three weeks, then acted surprised it slipped."
Specificity is what makes something learnable. The bad manager hands you concrete, replayable scenarios where you know the inputs, the decision made, and the damage caused. You can analysis them: what should have happened in that meeting? What would the competent version of that email have said? That is deliberate practice material, and it costs you nothing except the therapy you were going to need anyway.
Turn the grievance into a spec
Venting has a shelf life. At some point the story about the manager who scheduled a "quick sync" for 5:55pm on a Friday stops being cathartic and starts being a rut. You can get relief from converting each grievance into an inverted requirement, the way you'd turn a bug report into an acceptance criteria.
Take each memorable incident and write down three things:
- What they did
- What it cost
- What the inverse behaviour looks like in practice
Not the inverse sentiment, the inverse behaviour. "He never gave context" does not invert to "I will give context", which is just another warm abstraction. It inverts to something testable: when I delegate a task, I state why it matters, who consumes the output, and what "done" looks like, before the person asks.
A working PM will quickly recognise how directly this maps:
- The manager who escalated without warning teaches you a rule: nobody named in an escalation hears about it first from the escalation.
- The manager who hoarded information as leverage teaches you that context asymmetry inside a team is a project risk, not a management style.
- The manager who treated every status meeting as a cross-examination teaches you that if people only ever report good news to you, you have built a reporting system that manufactures surprises.
Three or four of these rules, written down and actually checked against your own behaviour, will do more for how you run projects than most formal training. Formal training tells you what good looks like. Your worst manager showed you, in high definition, what the failure state looks like from underneath, which is where your team currently sits relative to you.
The uncomfortable part: you have their failure modes
Here is the section people skip. The reason your worst manager's behaviour is so legible to you is that the underlying pressures are universal, and you are subject to all of them. They micromanaged because they were scared and visibility felt like control. They took credit because they were insecure about their own standing. They changed priorities weekly because saying no to their own boss was harder than disrupting their team.
You will feel every one of those pressures. Under a slipping deadline, "just checking in" messages start feeling reasonable. When your project succeeds, the summary email that slightly overstates your role practically writes itself. The value of having watched someone fail at this is that you know what the early symptoms look like, because you documented them from the other side.
So make the check explicit. When you notice yourself asking for an update you don't actually need, or softening a commitment you made to your team because a stakeholder frowned, name the pattern.
"This is the thing Ryan used to do."
It is a crude technique and it works, because you have already attached a strong negative memory to the behaviour. Your worst manager pre-loaded the deterrent for you.
Steal the one thing they were good at
Almost no bad manager is uniformly bad. Most were promoted for a genuine strength, and the organisation then discovered the rest. The bully often had real commercial instincts. The micromanager frequently had the sharpest eye for detail on the floor. The credit-taker was, annoyingly, excellent at making work visible upward, a skill their team badly needed and never learned because it was being used against them.
Separating the skill from the person is the mature move, and it is worth doing precisely because it is unpleasant. If you refuse to learn anything from someone you disliked, you have made your professional development hostage to your feelings about individuals, which is its own management failure mode. Take the upward-visibility skill and use it for your team instead of on them. Take the detail obsession and apply it to risks instead of to people's calendars.
Gratitude not required
None of this means the experience was worth it, and you are under no obligation to arrive at some redemptive conclusion where you're grateful for the suffering. That's the self-help version, and it's dishonest. A bad manager cost you sleep, confidence, and probably a year of career momentum. The learning does not retroactively justify the cost.
But the cost is sunk. The only live question is whether you extract anything from it. You already paid the tuition for the most detailed, personalised course on management failure you will ever take. Most people walk out without the notes.
Write yours down, invert them, and check yourself against them when the pressure arrives, because it will, and on that day you will either be the rule you wrote or the story someone else tells.
