Things I've Learned From Bad Managers
I've had good managers, difficult managers, and managers who taught me more about what not to do than they probably ever intended. Over the course of my career, I've worke…
At the time, some of those experiences were frustrating, exhausting, and occasionally difficult to understand. Looking back, however, I can see that they taught me a great deal. Good managers taught me what effective leadership looks like, but bad managers taught me to pay attention to the things that can quietly destroy trust, motivation, and performance inside an organization. They made me think more carefully about communication, accountability, authority, recognition, and the kind of working environment I want to create when I'm responsible for other people.
I've also come to realize that being a bad manager doesn't necessarily mean being a bad person. Some people become managers because they were excellent at their jobs, without ever learning how to manage people. Others inherit management styles from the people who managed them. Some are insecure about their position, some are overwhelmed by the responsibility, and some genuinely believe that being a good manager means maintaining strict control. Understanding where bad management comes from doesn't excuse it, but it does make it easier to recognize.
The most useful thing I've taken from those experiences is that management is often defined by the small things. It's how you react when someone disagrees with you. It's whether you give people credit. It's whether you communicate a change in direction or simply expect everyone to somehow know about it. It's whether people feel comfortable telling you that something has gone wrong. It's whether employees become more confident and capable while working with you, or whether they gradually become more cautious and disengaged.
Some of the most important lessons I've learned about leadership came from managers who demonstrated exactly what I didn't want to become.
Authority Doesn't Make You a Leader
One of the first things bad managers taught me is that having authority and being a leader are two very different things. A manager has a title, a reporting structure, and usually some degree of decision-making power. None of those things automatically make someone a leader, and having the ability to tell people what to do doesn't necessarily mean that people respect your judgment or trust your decisions.
I've worked with people who seemed to believe that because they were the manager, their opinion automatically carried more weight. Discussions became declarations, questions became challenges, and disagreement became something that needed to be corrected. Instead of seeing their position as a responsibility, they treated it as proof that they were right. The hierarchy became more important than the issue being discussed.
That approach can produce compliance, but compliance isn't the same as commitment. People can follow instructions because they have to while becoming increasingly disengaged from the person giving them. They can attend meetings, complete tasks, and meet deadlines while quietly deciding that there is no point in contributing ideas or challenging decisions. Eventually, the manager may have a team that appears very easy to manage, but only because everyone has learned that speaking honestly isn't worth the effort.
I've learned that a title gives you authority, but what you do with that authority determines whether you earn respect. A good manager doesn't need to constantly remind people that they're in charge. Their behavior should make their leadership obvious.
Micromanagement Doesn't Make People Better
One of the most frustrating management styles I've encountered is micromanagement. It usually begins with something that sounds reasonable. A manager wants visibility. They want to make sure the quality is good. They want to understand what is happening. None of those things are inherently problematic. The problem begins when visibility turns into control and control starts replacing trust.
I've experienced situations where someone was given responsibility for a project but wasn't actually given the freedom to manage it. Every decision needed approval, every piece of work was reviewed, and every small detail became an opportunity for intervention. Sometimes the manager wasn't even correcting something that was objectively wrong. They simply wanted the work done their way.
The result is predictable. When people realize that their judgment isn't trusted, they eventually stop using it. Why spend time thinking through a solution if you know the manager is going to change it anyway? Why take initiative if every decision requires approval? Why accept responsibility if you don't actually have the authority to make decisions?
I've learned that you cannot give someone responsibility while simultaneously taking away their ability to exercise judgment. If you hire someone because they're experienced and capable, you have to give them enough room to demonstrate that capability. Otherwise, you aren't developing an employee. You're training them to wait for instructions.
Good management requires involvement, but it also requires knowing when to step back. People need clear expectations, context, resources, and support. They don't need someone constantly standing over their shoulder.
If Everything Is Urgent, Nothing Is Important
I've worked with managers who seemed incapable of distinguishing between something that was genuinely important and something that had simply become urgent in their mind. Everything needed to happen immediately. Every email required a response. Every new request became the highest priority, even if another project had been identified as the priority the day before.
This creates a strange kind of workplace where everyone is constantly busy but very few people feel like they're making meaningful progress. Employees spend their time switching between tasks, responding to interruptions, and trying to figure out which of several supposedly critical priorities actually matters most.
I've learned that prioritization is one of the most important responsibilities a manager has. If everything is important, then nothing has been prioritized. A manager's job isn't simply to add more tasks to someone's workload. It is to help the team understand where its limited time and energy will have the greatest impact.
This becomes particularly important when priorities change. Businesses change, circumstances change, and sometimes something genuinely more important comes up. That's normal. The problem is when a manager constantly changes direction without acknowledging what has changed or what should now be deprioritized.
You can't keep adding new priorities without removing something else and expect people to maintain the same quality of work. Eventually, something breaks. Usually, it is the employee who gets blamed for not doing everything that was asked of them.
Poor Communication Creates Problems That Don't Need to Exist
Some of the worst workplace problems I've experienced weren't actually difficult problems. They were communication problems that could have been avoided with a five-minute conversation.
Someone wasn't told about a decision. A deadline changed but the person responsible didn't know. Two people received different instructions. An important piece of context was left out. A manager made an assumption that everyone else was supposed to understand without ever explaining it. Then, when the result wasn't what they expected, the person doing the work was questioned about why they hadn't known.
I've learned that managers often underestimate how much information they have simply because of their position. They are included in conversations that their teams aren't part of. They hear discussions about strategy, organizational changes, financial pressures, and priorities that may never reach the people responsible for executing the work.
If you have information that affects someone's ability to do their job, communicating that information is part of your responsibility. Employees cannot execute information they don't have, and they cannot consistently meet expectations that haven't been clearly explained.
One of the most frustrating things about poor management is being held accountable for information you were never given. It creates an environment where employees stop focusing on the actual work and start trying to anticipate what their manager might have meant. That's not productivity. That's guesswork.
Moving the Goalposts Destroys Trust
Another lesson I've learned from bad managers is how damaging it is when expectations change without acknowledgment. You can complete something according to the brief you were given, meet the deadline you were given, and follow the process you were instructed to follow, only to discover afterward that your manager expected something completely different.
Sometimes priorities genuinely change, and there is nothing wrong with that. The problem is pretending they didn't change. A good manager can say, "The situation has changed, so we need to approach this differently." That gives everyone an opportunity to adjust.
A bad manager can change the expectation and then behave as though that was always the expectation.
Over time, this destroys trust. Employees begin to realize that doing what they were asked doesn't necessarily mean they will be considered successful. They start trying to anticipate what the manager might want rather than simply executing the agreed plan. Every task becomes an exercise in reading between the lines.
That isn't a healthy way to work. People need to know that the rules of the game are reasonably stable. If something changes, tell them. If you change your mind, say so. Changing direction isn't a leadership failure. Failing to communicate the change is.
Don't Make People Afraid to Bring You Bad News
I've learned that you can tell a lot about a manager by what happens when something goes wrong. Does someone feel comfortable walking into their office and saying, "We have a problem," or does everyone immediately start trying to figure out how to hide it?
Bad managers often create environments where people are afraid of bad news. The irony is that this doesn't eliminate problems. It simply delays the moment when the manager finds out about them.
If someone notices that a campaign isn't working but is afraid to raise the issue, the organization may continue wasting money. If an employee realizes that a deadline is unrealistic but doesn't feel safe saying so, the deadline will eventually be missed. If someone makes a mistake and knows they'll be humiliated for admitting it, they may try to fix it quietly or hope nobody notices.
Fear is terrible for information flow.
Managers need accurate information to make good decisions. If employees only tell them what they think the manager wants to hear, then the manager is operating with incomplete information while believing they have a clear picture of what's happening.
I've learned that one of the most valuable things a manager can create is an environment where people can tell the truth, particularly when the truth is inconvenient. You want your employees to tell you about problems while they're still small enough to solve.
Credit Should Follow the Work
Few things are more demoralizing than doing the work and then watching someone else receive the recognition for it. I've seen managers who were very visible when things went well but somehow became difficult to find when things went wrong. They were happy to present their team's achievements to senior leadership, but the people who actually did the work were barely mentioned.
Over time, that changes how people behave. Employees begin to realize that doing excellent work doesn't necessarily mean they'll receive recognition for it. They become less willing to volunteer ideas, take initiative, or go beyond what is required. Eventually, some people decide that the safest approach is to do exactly what they're told and nothing more.
Good managers understand that making their team visible doesn't diminish them. If someone came up with an idea, give them credit. If someone led a project, let them present it. If someone solved a difficult problem, acknowledge their contribution.
I've always thought that one of the clearest signs of a confident manager is their willingness to make other people look good. You don't become less important because someone else gets recognized. In fact, your ability to help other people succeed is one of the most important things that makes you valuable as a manager.
Blame Is Not Accountability
Bad managers often talk about accountability, but what they actually practice is blame. When something goes wrong, their first question is often, "Who is responsible?" rather than, "What happened?"
Accountability is important. People should be responsible for their work and their decisions. But accountability isn't about finding someone to punish. It's about understanding what happened, determining what could have been done differently, and making sure the organization learns from the experience.
A blame-oriented culture creates defensive employees. People start saving emails, documenting conversations, avoiding risks, and worrying more about proving that something wasn't their fault than solving the actual problem. Eventually, everyone becomes more concerned with protecting themselves than improving the work.
Sometimes someone genuinely made a mistake. That's part of working with people. The question is what happens next.
A good manager can hold someone accountable while still asking whether the surrounding process contributed to the mistake. Were the instructions clear? Were the resources available? Was the timeline realistic? Did priorities conflict? Was there information the employee didn't have?
I've learned that the best managers don't avoid accountability. They simply understand that accountability is more useful when it leads to learning rather than fear.
Favoritism Is More Visible Than Managers Think
Managers often believe they are better at hiding favoritism than they actually are. Teams notice who gets the interesting projects, who receives more flexibility, whose mistakes are overlooked, who gets invited into certain conversations, and whose opinions seem to carry more weight.
Even when nobody says anything, people are paying attention.
Favoritism is particularly damaging because it changes people's understanding of how success works within an organization. If employees believe that performance, effort, and good judgment are rewarded, they are likely to invest in those things. If they believe that relationships with management matter more, they'll naturally start investing their energy somewhere else.
Fairness doesn't necessarily mean treating everyone identically. Different people have different responsibilities, strengths, needs, and circumstances. A manager can make different decisions for different employees and still be fair.
The problem is when people can't understand the principles behind those decisions.
Once employees believe that the system is unfair, motivation becomes much harder to maintain. Why work harder if the outcome appears to be determined by who you know rather than what you contribute?
You Don't Need to Win Every Conversation
Some managers treat every disagreement like a competition. They need the final word, they need to prove that they were right, and they need everyone else to accept their reasoning even when the decision itself isn't particularly important.
I've learned how exhausting this can be.
There are certainly times when a manager has to make the final decision. That's part of the role. But not every disagreement needs a winner. Sometimes two people simply see something differently. Sometimes the employee has information the manager doesn't have. Sometimes the manager has context the employee doesn't have. Sometimes the best answer comes from combining both perspectives.
The ability to say, "You may have a point," is an underrated management skill. So is the ability to say, "I was wrong."
I've learned that admitting a mistake doesn't make a manager look weak. In many cases, it makes them more credible. People don't expect their managers to be perfect. They expect them to be honest.
A manager who can change their mind when presented with better information is far more useful than one who protects their ego at the expense of a good decision.
Being Difficult Is Not the Same as Having High Standards
I've encountered managers who seemed to take pride in being difficult. They were demanding, difficult to please, and reluctant to praise anyone. They seemed to believe that pressure produced better work and that being tough was evidence of high standards.
It isn't.
High standards are about the quality of the work. Being difficult is about how you treat people while pursuing those standards.
You can expect excellent work without humiliating someone. You can challenge an employee without insulting them. You can reject an idea without making the person who proposed it feel incompetent. You can tell someone that something isn't good enough while still making it clear that you believe they are capable of doing better.
I've learned that some managers use "high standards" as an excuse for poor behavior because it sounds more professional than admitting that they don't know how to give constructive feedback.
There is nothing wrong with expecting people to do excellent work. In fact, good employees often appreciate high standards because they want to be proud of what they produce. But excellence doesn't require cruelty, and difficult behavior doesn't automatically make someone a demanding or effective leader.
When People Stop Talking, Pay Attention
One of the most interesting things I've noticed about bad management is that the warning signs aren't always obvious. Sometimes the biggest warning sign is silence.
People stop contributing in meetings. They stop suggesting ideas. They stop asking questions. They stop challenging decisions. They stop volunteering for projects. They do exactly what they're told and nothing more.
A manager might interpret this as a sign that the team is easy to manage. It may actually be a sign that the team has given up.
I've learned that engagement isn't simply about whether people show up and complete their tasks. It's also about whether they feel that their judgment matters. When people believe their ideas will be dismissed, they eventually stop offering them. When they believe their concerns won't be taken seriously, they eventually stop raising them. When they believe their effort won't be recognized, they eventually stop giving extra effort.
Silence can be mistaken for agreement, but it isn't always agreement. Sometimes it's resignation.
That's why good managers should pay attention not only to what people are saying, but also to what they have stopped saying.
Don't Confuse Loyalty With Silence
Bad managers sometimes say they want loyal employees, but what they really want is obedient employees. There's an important difference.
Loyalty doesn't mean agreeing with everything your manager says. It doesn't mean staying silent when something is wrong. It doesn't mean protecting a manager from information they don't want to hear.
In a healthy workplace, loyalty can actually include disagreement. You can care deeply about an organization and still believe that a particular decision is wrong. You can respect your manager and still challenge their thinking. You can be committed to the team while telling someone that you think the current approach isn't working.
I've learned that some of the most valuable employees are the ones willing to have uncomfortable conversations because they care enough about the work to do so.
A manager who interprets every disagreement as disloyalty will eventually surround themselves with people who know better than to speak honestly. At that point, the manager may feel very supported, but what they actually have is a team that has learned to keep its opinions to itself.
Your Team Is Watching What You Do
One of the biggest lessons bad managers taught me is that people pay far more attention to a manager's behavior than to their words.
You can tell your team that communication is important, but if you don't communicate, they'll notice. You can tell people that mistakes are acceptable, but if you punish the next person who makes one, they'll notice. You can talk about teamwork while taking credit for everyone's work, and they'll notice. You can talk about work-life balance while sending messages at all hours and expecting immediate responses, and they'll notice.
People believe behavior more than they believe policies.
That's why leadership is so difficult. You can't simply tell people what values matter. You demonstrate those values through your everyday decisions.
A manager who wants their team to communicate openly needs to communicate openly themselves. A manager who wants accountability needs to accept accountability. A manager who wants people to respect boundaries needs to respect them too.
Your team is always watching, even when you don't realize it.
Sometimes the Best Lesson Is Knowing When to Leave
Perhaps the hardest lesson bad managers have taught me is that not every situation can be fixed.
When you're invested in your work, it's easy to believe that if you work harder, communicate better, become more patient, or prove your value, eventually the situation will improve. Sometimes it does. Sometimes relationships change, managers grow, organizations recognize problems, and difficult periods pass.
But sometimes they don't.
There are situations where the culture is deeply embedded, leadership isn't interested in changing, or the relationship has deteriorated to the point where no amount of additional effort will make it healthy. I've learned that there is a point where staying doesn't demonstrate resilience. It simply means you've stopped listening to yourself.
Leaving a difficult environment isn't necessarily failure. Sometimes it's the most rational career decision you can make. You can learn from an experience without remaining in it indefinitely, and you can appreciate what a job gave you while still recognizing that it is no longer the right place for you.
Sometimes the most valuable thing a bad manager teaches you is what you will no longer accept in your next chapter.
The Manager You Don't Want to Become
Perhaps the most useful thing about working with bad managers is that they give you a very clear picture of what not to become. You learn not to micromanage people because you remember what it felt like to have someone constantly looking over your shoulder. You learn to communicate clearly because you remember how frustrating it was to work with incomplete information. You learn to give credit because you remember what it felt like when your work disappeared behind someone else's name. You learn to accept disagreement because you remember what happened when disagreement wasn't welcome.
Most importantly, you learn that management isn't primarily about having power over people. It's about having responsibility for the environment in which those people work.
I've had managers who taught me what leadership looks like, and I've had managers who taught me what it doesn't. I'm grateful for both experiences, although I certainly wouldn't want to repeat all of them. The good managers gave me examples worth following. The bad managers gave me boundaries worth remembering.
Over the years, I've started to think that your management philosophy is built from both experiences. You take the things you admired from the people who managed you well, and you consciously reject the behaviors that made you feel frustrated, undervalued, or powerless. Eventually, those experiences become part of your own understanding of what leadership should be.
You realize that you don't have to manage people the way you've been managed. You don't have to repeat the same patterns simply because they're familiar. You can choose to communicate differently, give people more trust, listen more carefully, recognize contributions, admit when you're wrong, and create an environment where people can disagree with you without worrying about the consequences.
That's perhaps the greatest lesson bad managers have given me. They have shown me that the way you treat people at work matters just as much as the work itself.
People may forget the campaigns, projects, presentations, meetings, targets, and deadlines. They may even forget exactly what you said to them. But they will probably remember whether they felt trusted or constantly monitored, respected or dismissed, supported or undermined.
They will remember whether working with you made them feel more capable or less capable.
And eventually, if you become responsible for managing other people, that becomes your responsibility.
The goal isn't to become a perfect manager. Nobody is. The goal is to be conscious of the effect you have on the people around you, to learn from your own mistakes, and to make sure that the people who work with you are better off for having done so.
I've learned a lot from good managers about the kind of leader I want to be. I've learned just as much from bad managers about the kind of leader I never want to become. And while the lessons from the good ones are easier to remember with gratitude, the lessons from the bad ones have probably stayed with me just as strongly.
Sometimes the best management lesson is not something someone tells you.
Sometimes it's the feeling you leave a workplace with, and the decision you make that you never want to make someone else feel that way.
