Here's a statistic that should stop every leader in their tracks: about 95% of people believe they're self-aware. The actual number who are? Somewhere between 10 and 15%.

Sit with that gap. It means that for roughly four out of five people walking around confident they know how they come across — they don't. And since managers are people, it means the odds are uncomfortably high that your boss, or you, is operating with a serious blind spot while feeling completely clear-eyed.

This is, I'd argue, the root cause underneath almost every bad-boss story I've ever told.

The blind spot is the whole problem

Think about the managers I've written about. The one who couldn't articulate feedback and fired a man over "red flags." The one who held public shaming sessions and called it "re-education." The jealous boss who couldn't see her own scarcity mindset. Not one of them thought they were a bad boss. Every single one of them, I'd bet, would have told you they were fair, reasonable, maybe even good.

That's the terrifying part. Bad management almost never feels like bad management from the inside. The public-shamer thought he was rigorous. The avoidant boss thought he was busy. The credit-stealer thought the idea was basically his anyway. The self-awareness gap is the gap between the manager people actually experience and the manager the boss believes themselves to be — and the wider that gap, the more damage gets done by someone who sincerely believes they're doing fine.

How leaders get this wrong

They mistake their intention for their impact. "I didn't mean it that way" becomes a permanent defense against ever learning how they actually land. Intent is invisible to your team. Impact is all they get.

They surround themselves with people who won't tell them. The higher you rise, the less honest feedback you receive, because telling the boss the truth gets riskier. So the most powerful people often have the worst data about themselves — and the least incentive to fix it.

They treat feedback as an attack instead of information. The defended leader experiences "here's how that landed" as a threat to fight off, which trains everyone around them to stop offering it. And then the blind spot calcifies.

How to avoid it

Assume you're in the 85%, not the 15%. Genuine humility starts with accepting that you probably can't see yourself clearly — and that this is normal, not a personal failing. The leaders who close the gap are the ones who stop assuming they've already closed it.

Go get the data you're not being handed. Real 360 feedback. Anonymous input. Actually asking your team "what's it like to be managed by me?" and bracing yourself to hear it without flinching or retaliating. The feedback you have to chase is the feedback you most need.

Watch for the wince, and walk toward it. The moment a piece of feedback stings is the moment it's probably true. Defended leaders flee that sting. Growing ones get curious about it.

Here's the hopeful part, and I mean it: the gap is closeable. I know because I've closed some of my own — I was a rigid, rule-worshipping rookie manager once who'd have sworn I was just being fair. What moved me from blind to better wasn't talent. It was being willing to find out I was wrong. That willingness is the whole skill. Most people never develop it, which is exactly why the ones who do become the leaders everyone remembers for the right reasons.

We've reached the part of the AI era where a manager can type "write a performance review for an underperforming employee" into a chatbot and have a polished, professional, devastating document in about four seconds. And reader, they are doing it. In droves.

I want to talk about why this is the newest costume for one of the oldest bad-boss failures in the book: the refusal to actually talk to the human being you're responsible for.

The new "red flags"

I once wrote about a manager named Richard who fired a man for having "a lot of red flags" he could never actually articulate. Vagueness was his shield — a feeling can't be cross-examined.

AI-generated feedback is Richard's dream tool. It manufactures specificity-shaped language without requiring the manager to have done any of the specific noticing. It produces sentences like "demonstrates inconsistent alignment with team objectives" that sound like observation but contain none. The boss who couldn't be bothered to watch your work closely can now generate paragraphs about it. The fog gets a vocabulary.

And the employee can feel it. There is a particular chill to receiving feedback that's articulate and hollow at the same time — words about you that clearly weren't written by anyone who watched you work.

How leaders get this wrong

The failure isn't using AI. It's what they use it to avoid.

They use it to skip the noticing. Good feedback comes from a manager actually paying attention over time. AI lets them fake the output without doing the input — generating a review for someone they never really observed.

They use it to skip the discomfort. The whole point of the hard conversation is sitting across from a person and staying in the room for their reaction. Outsourcing the words is a way of not being fully present for the moment that matters most.

They use it to launder the cowardice. A document feels official, neutral, defensible. "It's all written up" becomes a way to deliver a verdict without ever having a dialogue. The paper does the confronting so the manager doesn't have to.

How to avoid it

Use AI for the scaffolding, never the substance. Let it help you organize thoughts you already have from your own observation — never to generate observations you never made.

Do the noticing yourself, all year. If you can't write three specific, real examples of someone's behavior without a chatbot, you haven't been managing them. Fix that before you fix the review.

And never, ever let the document replace the conversation. The review is a record of a dialogue that should have already happened, face to face, more than once. If the first time someone hears the feedback is when they read the AI-polished PDF, you've already failed them.

AI can draft the words. It cannot care about the person. The day we forget the difference is the day management stops being a human job — and the employees on the other end will know long before we admit it.

Let's be honest. Nobody quits a job. People quit bosses. The job is fine. The job is a series of tasks you could do half-asleep, and frequently do. The boss, however, is a fully sentient human being who has chosen — chosen, with intention and forethought — to be like that.

So in the spirit of public service, here is what actually separates a bad boss from a merely mediocre one. Mediocre bosses forget your name. Bad bosses remember it and use it as a weapon.

1. They run their calendar like a hostage situation

You will know this boss because their meetings have no agenda, no end time, and somehow always need "just five more minutes" that mysteriously expand into the heat death of the universe. They schedule things at 4:55 PM on a Friday and call it "quick." They double-book themselves and then act betrayed when one of the meetings turns out to be a real thing with real humans.

The tell: they say "let's take this offline" and then never take it offline. It just dies in a swamp somewhere, along with your will to live.

2. They confuse "availability" with "leadership"

This boss is online. At all times. On every channel. They will Slack you at 11 PM with a question that begins "no rush but" and ends with a deadline of 9 AM. They believe responsiveness is a personality. It is not. It is a symptom.

The deeply funny part is they think this makes them a great manager. In reality, they have become the human equivalent of a smoke alarm with a dying battery — constant noise, no signal, and everyone in the building secretly wants to rip them off the ceiling.

3. They have one (1) feedback mode and it is "vibes"

Good feedback is specific. It sounds like: "In Tuesday's meeting, when you cut off Marcus, it derailed the conversation. Try waiting until people finish next time."

Bad-boss feedback sounds like: "I just feel like… you know? The energy. We need more ownership. More fire. Be more of a driver, less of a passenger. Does that make sense?"

No. It does not make sense. It has never made sense. It is a horoscope.

4. They take credit like it's an Olympic sport

Your idea, presented in a meeting last month, dismissed at the time as "interesting but not for this quarter," now reappears in an all-hands deck under their name, with a slightly worse name and a clip-art rocket ship. They will present it with the unearned confidence of a man explaining his own wedding to his wife.

When you bring it up, they will say "we all worked on that," using the royal "we," which in this context means "I."

5. They mistake panic for urgency

Everything is on fire. Always. The roof is on fire, the basement is on fire, the concept of the building is on fire. Except nothing actually is, because if everything is a P0, nothing is. This boss has confused stress with strategy. They are essentially a golden retriever who has discovered email.

You can spot them by their language. "We need to move fast on this." "This is mission-critical." "I need this yesterday." A normal person would simply say, "Hey, can you get this to me by Thursday?" But that would require knowing what day it is, which they do not.

6. They have feelings, and those are your problem now

Look, everyone has bad days. The difference is that a healthy adult goes home and feels them. A bad boss brings them to a 1:1 and downloads them into you like you're emotional Dropbox. You will leave the conversation knowing about their divorce, their dog's medication, and a vague grievance against someone named "Greg in Finance," but not whether your promotion is happening.

Sympathy fatigue is real. You did not sign an employment contract to be anyone's therapist, and frankly, you're not licensed.

7. They love "transparency" until it points at them

This boss talks about radical candor the way crypto guys talk about freedom. Constantly, loudly, and never in a way that benefits anyone but them. They want you to "bring your full self to work" so they can manage that self into the ground.

Ask them a direct question about strategy, comp, or why the org chart changed overnight, and watch transparency develop a sudden, terrible cough.

8. The cardinal sin: they make you smaller

This is the one that actually matters. The rest is comedy. This one is the thing.

A bad boss leaves you with less than you came in with. Less confidence. Less curiosity. Less of a sense that the work you do matters or that you, the person doing it, are a whole human being. They shrink the room. They shrink you in the room. After enough time around them you start to second-guess things you used to know cold, and you can't quite remember when that started.

A good boss does the opposite. You walk out of the 1:1 feeling like you can do the thing. Not because they pumped you up — that's its own scam — but because they were clear, fair, and actually paid attention. That's it. That's the bar. It is not high. It is on the floor. And yet.

---

The takeaway

If you have a bad boss right now: it's not you. It is genuinely, in a way that can be diagrammed on a whiteboard, them.

If you are a bad boss right now: the first step is admitting it, the second step is asking your team what to fix, and the third step is not retaliating against whoever tells you. That last one trips up a lot of people.

And if you're somewhere in the middle, congratulations — you're a manager. Welcome to the hardest job nobody trained you for. Try not to Slack anyone at 11 PM.

Last time I wrote about Michael Scott — the boss with all the heart and none of the skill, the man we love precisely because he cared too much and bumbled the rest. Today I want to talk about his spiritual opposite. Not a competent jerk. The other thing. The rare thing. The boss who has the heart and figured out how to wield it.

I'm talking about Ted Lasso.

A mustachioed American football coach hired to manage an English Premier League soccer team despite knowing, and I cannot stress this enough, nothing about soccer. On paper, a disaster. In practice, the most quietly radical depiction of leadership television has produced in years — and, weirdly, a better HR training video than most actual HR training videos.

Let me make the case for why Ted is a case study in leadership done right, including — especially — the parts where he gets it wrong.

He leads with curiosity, not authority

The single most-quoted line from the show is Ted chalking two words onto a sign in the locker room: "Be curious, not judgmental."

It sounds like a fridge magnet until you watch him actually live it. Ted walks into a building full of people who think he's a clown — players, press, the fans literally chanting for him to be fired — and instead of armoring up and asserting his authority, he gets curious about them. He learns names. Everyone's names. The limo driver in the first episode, the kit man, the journalists who are openly mocking him. He introduces himself to his driver and uses the man's name twice during a short ride.

This is not a small thing, and it's not just niceness. Knowing someone's name and using it is the most basic act of seeing a person, and most bosses can't be bothered. Ted understood instinctively what took me years of HR work to articulate: people will run through walls for a leader who makes them feel known, and they will quietly disengage from one who treats them as headcount.

He doesn't pretend to know what he doesn't know

Here's the part that should be studied in every leadership program in the country. Ted is the boss, the head coach, the guy with the title — and he openly, cheerfully admits he has no idea what he's doing on the technical side.

He doesn't fake soccer expertise. He surrounds himself with people who have it — quiet, brilliant Coach Beard, and famously, Nate, the kit man, whose ideas Ted actually solicits and uses after overhearing him. Ted promotes the equipment manager because the equipment manager had good ideas, which is a thing almost no insecure leader would ever do, because it would mean admitting the kit guy knew something they didn't.

Think about the bosses I've written about in this series — the ones who couldn't give feedback because being wrong felt like annihilation, the ones whose fragile egos couldn't tolerate anyone else shining. Ted is the photographic negative of all of them. He welcomes feedback, admits when he doesn't know something, and gives credit freely. His ego is so secure that he doesn't need to be the smartest person in the room. He just needs the room to win.

He's vulnerable, and it makes him stronger, not weaker

Ted is going through it. A divorce, an ocean between him and his son, and — in the show's bravest move — debilitating panic attacks.

A lesser show would have made his struggles a secret weakness that nearly destroys him. Ted Lasso does something more honest: Ted faces divorce, distance from his son, anxiety attacks, and loss, and remains open and honest with his team, which earns their respect and loyalty. He goes to therapy. He — a folksy, optimistic, emotionally old-fashioned guy — does the work of confronting his own mental health, on screen, and is shown as more of a leader for it, not less.

This matters enormously, because it dismantles the oldest lie in management: that vulnerability is weakness and the boss must be an impenetrable rock. Ted's willingness to be vulnerable created an environment where his team felt safe raising concerns, asking questions, and expressing their own emotions. That's the whole game. Psychological safety doesn't come from a poster. It comes from a leader who goes first.

And now — the part you've been waiting for — he screws up

Because here's what would make this post dishonest if I left it out: Ted Lasso is not a perfect leader. The show is too smart for that. He fails, repeatedly, in ways that matter.

He's so committed to being liked and keeping the peace that he sometimes avoids hard truths until they fester. His relentless positivity occasionally lands as dismissive — Coach Beard actually yells at Ted for claiming he doesn't measure success by wins, because Beard and the players genuinely do care about winning, and Ted has to learn that his philosophy can't simply override what his people need. And the great tragedy of the series is Nate — the kit man Ted elevated — who curdles into resentment and betrayal, in part because Ted, distracted by his own struggles, stopped giving Nate the attention and mentorship that had made him bloom in the first place.

That's a real leadership failure. Ted neglected someone who needed him, and it cost him.

Why his failures are the actual lesson

But here's the turn, and it's why Ted is a better case study than any flawless fictional leader could ever be.

Ted owns his mistakes. He doesn't deflect, doesn't campaign against the people he's wronged, doesn't reach for vague "red flags" to justify himself. When he's wrong, he says so. When he hurts someone, he tries to repair it. When Rebecca eventually confesses that she hired him specifically to sabotage the team — that his whole job was a trap designed for him to fail — Ted takes a moment, recognizes the courage it took her to admit it, appreciates her honesty, and forgives her so they can move forward together.

Sit with that. His boss admits she set him up to fail, and his response is grace. Not because he's a pushover — because he understands that people are more than their worst decisions, and that a leader's job is to make it safe for people to become better than they were.

That's the thing the whole series is teaching, and it's the thing I've been circling for this entire blog. Ted's values don't spare him from bullying, backstabbing, undermining, and heartbreak — but they guide him through it with humility and grace, without ego. Good leadership isn't the absence of failure. It's what you do with failure — yours and everyone else's.

Be a goldfish

There's a moment early on where Ted tells a player who made a mistake to "be a goldfish," because the goldfish has a ten-second memory and is, therefore, the happiest animal on earth. Let it go. Don't carry the error as a verdict on your worth. Learn the lesson, drop the shame, swim on.

I think about that a lot, honestly, after writing this whole series about bosses who did the opposite — who carried grudges, who made employees carry shame that was never theirs, who turned every mistake into a permanent mark on a permanent record.

Ted Lasso represents the leader on the other side of all that. The one who's curious instead of judgmental. Who builds people up instead of needing them small. Who can be wrong, say so, fix it, and stay warm through the whole thing. Who understands — and this is the line that ties him to everything I believe about this work — that how you lead matters more than what you know, and that the job is creating an environment where people feel safe, seen, and supported enough to find their own answers.

Michael Scott had the heart and not the skill. The real bad bosses had the skill and not the heart. Ted Lasso is the rare, fictional, deeply aspirational both — proof of concept that you can be relentlessly kind and genuinely effective, that the two were never actually in conflict, and that the leaders who tell you otherwise are usually just describing their own limitations.

He's not real. I know he's not real.

But he's a really good blueprint. And the best part of the blueprint is the simplest: care about people, stay curious, own your mistakes, and be brave enough to go first.

Believe.

We've been heavy for a while in this series. Let's lighten up. Here's a collection of boss jokes — the kind you tell at happy hour after the third drink, when everyone finally admits they've worked for the same person. Steal them freely.

The classics

My boss told me to have a good day. So I went home.

I asked my boss, "Can I have a day off next week?" He said, "Sure, which one?" I said, "Thursday." He said, "Absolutely not, that's a workday." Then why did he ask.

My boss said, "You're like a son to me." Critical. Disappointed. And withholding affection. Got it.

I don't have an attitude problem. I have a problem with your leadership and the attitude is just a symptom.

My boss asked why I only get sick on workdays. I said it must be my immune system — it's clearly anti-work.

On "open door" policies

My boss has an open-door policy. The door's open. He's just never behind it.

"My door is always open," she said, scheduling our meeting for the fourth Tuesday she'd cancel.

We have an open-door policy and a closed-mind policy, and only one of them is enforced.

On feedback

My boss said, "Don't think of it as criticism, think of it as feedback." Then the feedback made me cry, so I'm pretty sure it was criticism.

My performance review just said "needs to be more of a team player." There is no team. He fired everyone. I am the team.

My boss gave me feedback so vague I'm now improving in directions that don't exist.

"Can you be more proactive?" Sure. I'm proactively updating my résumé.

On meetings

This meeting could have been an email. The email could have been a sticky note. The sticky note could have been nothing.

My boss scheduled a meeting to discuss why we have too many meetings. It ran long.

"Quick sync?" he asks, at 4:55 on a Friday, like the word "quick" has ever once been honored in the history of this company.

We had a brainstorm. He stormed. We watched.

On the workload

My boss said, "We're like a family here." Then gave me the workload of three people and the pay of half of one. Truly, just like my actual family.

I was told to "wear many hats." Nobody mentioned they'd all be on fire.

My boss believes in work-life balance. My work, his life.

"We're all going to have to do more with less." Great. I'll start by doing less.

On the self-aware ones (rare, endangered)

My boss admitted he was wrong once. We held him. Nobody knew the protocol.

My new boss said, "I don't know everything, so I'll be relying on the team." We didn't recognize the language at first. We had to look it up. Turns out it's called "humility."

My boss asked for honest feedback and then didn't retaliate. I'm shaken. I may need to lie down.

The one that's a little too real

The best boss I ever had didn't do anything flashy. She just told me the truth, gave me credit, had my back, and trusted me to do my job.

I know. Where's the punchline. That's the joke — almost nobody's ever had one.

---

That's the laugh. If a few of these landed a little too hard, well — that's why we tell the jokes. Sometimes it's the only way to say the true thing out loud.

You were hired for your competencies. Remember that interview? They wanted you. Specifically you. Your resume, your portfolio, your way of thinking about the problem. They called you a "great fit." They told you the team needed exactly what you brought.

And then, somewhere between month four and month fourteen, something shifted.

You couldn't quite name it at the time. You can probably name it now.

The bait and switch nobody warns you about

Here's the move, and once you see it you can't unsee it: toxic workplaces hire you for your competencies and then push you out for your character. The same things that got you the job — the directness, the standards, the refusal to just nod along — become the things that get you written up. "Not a culture fit." "Rubs people the wrong way." "Could work on stakeholder management."

Translation: you noticed something was broken and you said so out loud.

And if your character somehow survives the squeeze, they'll come for you on a different front: you're too competent. You're moving too fast. You're making other people look bad. You're "creating friction." You're a "lone wolf." Suddenly being good at your job is itself the problem, and nobody can quite articulate why, but everyone agrees there's a vibe.

The metric was never the metric

You can out-perform every KPI on the board. You can hit numbers nobody on the team has hit in three years. You can be the person leadership points to in the all-hands as an example of what good looks like. And you can still get managed out.

Because the real metric was never performance. The real metric was compliance.

Did you go along. Did you stay quiet in the meeting where the obvious thing went unsaid. Did you laugh at the joke. Did you protect the right people from the right information. Did you make your manager look good even when your manager was the problem.

That's the scorecard. The one on the dashboard is decorative.

Toxic workplaces don't fire you. They set you up to fail.

This is the part that takes the longest to see, because it doesn't look like sabotage. It looks like neglect with a smile.

The brief gets vague. Decisions you used to be in on now happen without you. The meeting moves and nobody tells you. Your scope shrinks in ways that are hard to point at — a project reassigned here, a stakeholder rerouted there, a "let's have so-and-so take the lead on this one." Your manager stops giving you feedback because, you'll later realize, they've already decided. The 1:1s get shorter. The Slack messages get colder. The performance review uses words that weren't in your last three.

You didn't get worse at your job. They stopped setting you up to succeed.

This is not underperformance. This is engineered disengagement. There's a difference, and it matters, because one of them is something you did and the other is something done to you.

It is not always obvious you're being set up

People imagine sabotage as a movie villain — the smirking boss with the manila folder. Real workplace setup is dumber and quieter than that. It's a calendar invite that doesn't include you. It's getting handed a project six weeks late with a one-week deadline. It's "we already decided, but I wanted your input." It's being asked to fix something with none of the authority to actually fix it, and then being held accountable for not fixing it.

By the time you realize the pattern, you've already spent months blaming yourself for the math not adding up.

That's the trick. You're not supposed to see it. You're supposed to internalize it.

What happens to the truth-tellers

Every toxic workplace has a quiet rule: the person who names the problem becomes the problem.

You raised the thing in the meeting that nobody wanted to raise. You said the project was off-track when leadership wanted to hear it was fine. You flagged the bad behavior. You asked the question that made the room go silent.

And from that moment, you were on a clock you couldn't see.

They don't argue with truth-tellers. They exile them. Slowly, politely, with a lot of HR-approved language. Because the alternative is admitting the truth was true, and that would require change, and change is expensive, and you — you are cheaper to lose.

The deepest damage isn't the job

Here's the part that doesn't get talked about enough, because it's the part that doesn't fit on a LinkedIn post.

Toxic workplaces don't just waste your talent. They teach you to doubt it.

You walk in trusting yourself. You walk out flinching at your own instincts. You second-guess emails you'd have sent in thirty seconds a year ago. You over-explain. You preemptively apologize. You read a piece of feedback five times trying to figure out what they "really" meant. You start to wonder if maybe you are difficult. Maybe you are too much. Maybe everyone else can see something about you that you can't see about yourself.

They rewrite your identity in the language of your performance review.

You used to trust yourself. That's the line that should be on a billboard outside every toxic office building. You used to trust yourself. And then a system that benefited from your self-doubt spent a year and a half teaching you not to.

How to know it was them, not you

If you're reading this and trying to figure out which side of the line you're on, here are the questions that tend to clarify it:

When you describe what happened to people outside the company, do they look concerned for you, or do they nod along like, yeah, that's normal? Did your skills atrophy, or did your access shrink? Did your judgment get worse, or did your environment get worse? When you left or were pushed out, did your confidence come back — slowly, awkwardly, but unmistakably — once you were no longer in that room?

If the answer to that last one is yes, you have your answer to all of them.

Coming back to yourself

The recovery from a toxic job is not professional. It's personal. You're not just looking for a new role. You're trying to find the version of you that walked into the old one — the one who trusted her read on the room, who didn't need three colleagues to validate an email before sending it, who knew what she was good at without needing permission to know.

She's still in there. She got buried, not deleted.

The work now is remembering that the problem was never your competence and never your character. The problem was that you walked into a system that needed you to be smaller, and you refused, and the system did what systems do.

You weren't too much. You weren't too difficult. You weren't underperforming.

You were just in a place that couldn't afford to let you be right.

Let me point out a contradiction so common that most companies have stopped even noticing they're living inside it.

The same organization that prints "family first" on its values poster, that puts work-life balance in the recruiting deck, that talks about being a place for "whole humans" — is very often the same organization with a rigid, one-size-fits-all attendance policy that makes it genuinely hard to, say, pick your kid up from school. The poster and the parking-lot reality are pointing in opposite directions, and the people caught in the gap are usually the caregivers.

Who rigid policy actually punishes

When you mandate fixed hours and fixed presence with no real flexibility, you're not applying a neutral rule evenly. You're quietly selecting against the people whose lives don't fit a 9-to-5, on-site mold — and that's disproportionately parents, single parents, people caring for aging relatives, people with their own health needs.

I once wrote about Zach, who asked to shift his hours by thirty minutes for childcare, did everything right to get it approved, and ended up fired over a payroll mistake nobody bothered to check. The deeper sin in that story wasn't the paperwork error. It was a system so rigid that a reasonable human need became a liability. The "family first" companies generate Zachs constantly, because their stated values and their operational reality were never actually reconciled.

How leaders get this wrong

They confuse fairness with rigidity. I've written about this as a mistake I made myself early on — believing "treating everyone the same" meant "no exceptions ever." It doesn't. Identical treatment of different circumstances isn't fairness; it's just inflexibility wearing fairness as a disguise.

They advertise values they won't operationalize. Putting "family first" on the wall and then punishing people for having families isn't just a gap. It's a bait-and-switch, and employees experience it as a specific betrayal.

They treat flexibility as a favor instead of a system. When accommodation depends on whether your particular manager happens to be nice, you get exactly the favoritism and inconsistency that breeds resentment — some people get grace, others get written up, for the same need.

How to avoid it

Build flexibility into the policy, not the manager's mood. Make reasonable schedule adjustments a documented, evenly available option — so it's a system anyone can use, not a gift bestowed on favorites.

Reconcile the poster with the practice. If you claim "family first," audit whether your actual policies make family possible. If they don't, either fix the policies or take down the poster. The hypocrisy costs you more than the honesty would.

Judge the work, not the schedule. Someone who shifts their hours to handle their life and still delivers is not a problem to be managed. They're a responsible adult to be trusted.

The companies that mean "family first" don't have to say it on a poster — you can tell by whether their people can actually leave at 2:30 to get their kid without it becoming a thing. The ones that only say it are usually the ones where saying it is all they ever did.

Let me tell you how a good employee got fired for stealing time he didn't steal, at a company that had "family first" printed on the wall.

We'll call him Zach. Zach was, by every account, doing his job well. The only thing Zach did wrong was have a life — specifically, a childcare situation that required him, temporarily, to shift his hours. Instead of working 7:00 to 3:00, he needed to come in at 6:30 and leave at 2:30. Same number of hours. Just slid earlier on the clock.

He did the responsible thing. The thing you're supposed to do. He went to his supervisor, explained the situation, and got it approved. Cleared it. Handshake, nod, "no problem, Zach." Done.

A few weeks later, the General Manager fired him for wage theft.

Let's walk through how that happened, because every single step is a small, human, deeply ordinary act of self-protection — and stacked together, they cost a good man his job.

The setup

Here's the actual mechanics of the disaster.

Zach's supervisor — the one who approved the schedule change — was also the person responsible for entering his team's time into the payroll system. Zach included. So the supervisor knew about the new hours. He'd approved the new hours. And then, when it came time to log Zach's hours in payroll, he entered the old ones. 6:30-to-2:30 Zach got recorded as 7:00-to-3:00 Zach, week after week.

That was the big, bad, load-bearing mistake. Everything downstream flows from it.

Now — why didn't the supervisor just update the times? This is where it gets human, and a little sad.

The project Zach worked on was set up with man-hours assigned a specific way. There was a plan. A budget of time, allocated against tasks, baked into how the whole thing was tracked. And the supervisor was afraid that if he started entering hours that deviated from the plan — even accurate ones, even ones he'd personally approved — it would draw attention. Raise a question. Make him look like he'd gone off-script. So he kept entering the numbers that matched the plan, because the numbers that matched the plan kept the supervisor safe.

Read that again. The supervisor falsified Zach's time records — recording him as present when he wasn't — to protect himself from a conversation about a schedule he had already okayed. He chose his own comfort over accuracy, and in doing so, he built the exact trap Zach would fall into.

The trap springs

Enter the General Manager.

The GM is looking at the operation, watching people come and go, and he notices something. Zach is leaving at 2:30. Every day. Out the door at 2:30 on the dot.

But the payroll records — the ones the supervisor entered — say Zach is being paid until 3:00.

To the GM, the math is simple and damning: this guy is getting paid for a half hour he's not working, every single day. That's wage theft. That's stealing. And so the GM, armed with what looks like an open-and-shut case, fires Zach on the spot.

Except the GM had it exactly backwards. Zach wasn't leaving thirty minutes early. Zach was arriving thirty minutes early. He was in at 6:30 — before the GM ever clocked the parking lot — putting in his full, honest, approved shift and then some. The "stolen" half hour at the end of the day was matched by a half hour at the start that the GM never saw and never bothered to look for.

Zach wasn't stealing time. Zach was working it. He got fired for the crime of being the only person in the chain who'd actually done the right thing.

So many people failed, in so many small ways

What I love about this story — in the bleak way you can love a thing that perfectly illustrates a point — is that nobody here is a cartoon villain. There's no Richard twirling a mustache. There's just a series of normal people each making the small, self-protective choice, and the small choices compounding into a catastrophe that landed entirely on the one person with the least power.

The supervisor failed Zach by not entering his real hours — and worse, by not telling anyone up the chain that Zach's schedule had changed. One email. "Hey, Zach's on adjusted hours for a few weeks, 6:30 to 2:30, all approved." That email would have prevented everything. He didn't send it because sending it meant explaining the deviation, and explaining the deviation felt risky to him.

The GM failed Zach by skipping his due diligence entirely. He saw a 2:30 departure, assumed the worst, and reached for termination without asking a single question. He never pulled the badge-in records. Never asked what time Zach arrived. Never asked the supervisor "wait, is there something I should know about this guy's schedule." Never gave Zach the thirty seconds of "hey, walk me through your hours" that would have unraveled the whole thing. He had a story that made sense to him, and he acted on it, and a story that makes sense is not the same as a story that's true.

And the system failed Zach by being built so that an honest deviation felt more dangerous to log than a quiet falsification. When the safest thing for everyone is to keep the numbers matching the plan, you've designed an organization that punishes honesty. That's not a Zach problem. That's an architecture problem.

The uncomfortable truth underneath all of it

Here's the thing this story makes me say out loud, even though it isn't a nice thing to say:

When the moment comes, most people will protect themselves first.

Not because they're evil. Because they're human, and self-preservation is wired deep, and an organization under pressure quietly teaches everyone that the cost of protecting yourself is always paid by someone else, later, somewhere you won't have to watch.

The supervisor liked Zach. I'd bet money on it. The supervisor approved the schedule change with a smile and meant it. And then, when the choice was between accurately representing Zach's hours and protecting his own standing on the project, the supervisor chose himself — probably without even fully admitting to himself that's what he was doing. That's the part that should scare you. It rarely feels like betrayal from the inside. It feels like "I'll just keep things consistent for now" and "I'm sure it'll be fine" and "I don't want to make waves." It feels reasonable. It always feels reasonable, right up until someone gets fired for wage theft they didn't commit.

This is the hard, honest thing I want anyone reading this to absorb: even your manager — the person whose literal job is to have your back, the one who smiled and approved your request — will let you fall if catching you means putting their own neck on the line. Not every manager. Not every time. But often enough that you cannot afford to assume otherwise. Their self-interest and your wellbeing are aligned right up until the second they aren't, and you usually don't get to know in advance when that second will arrive.

What Zach should have done — and what we can all learn

I hate "what the victim should have done" framing, because it can slide into blaming the person who got hurt. So let me be clear: none of this was Zach's fault. He did the right thing. He asked. He got approval. The failure was entirely in the people and systems above him.

And — both things can be true — there are protective habits this story should burn into all of us.

Get it in writing. That verbal handshake approval? Worthless when it mattered. If Zach had a single email — "Confirming my temporary schedule of 6:30 to 2:30, approved by you on [date]" — the wage theft accusation dies on contact. A paper trail isn't paranoia. It's the seatbelt you're glad you wore. Any change to your schedule, your scope, your comp, your responsibilities: confirm it in writing, every time, even when you trust the person. Especially when you trust the person, because trust is exactly what makes you skip the email.

Start the approval at the top, or make sure the top knows. A change approved only by your direct supervisor lives or dies on that one person relaying it accurately. Zach's whole catastrophe hinged on information that existed in exactly one head and never made it up the chain. When something deviates from the norm, make sure the deviation is visible to the people who'll be making decisions based on it — don't let your reality live in a single fragile link.

And if you're a leader: do the due diligence before you reach for the worst-case story. The GM had a hammer and saw a nail. Thirty seconds of curiosity — one question about when Zach arrived — would have saved a man's livelihood. Before you act on a story that makes someone the villain, ask whether you've actually checked, or whether you've just found a story that's convenient to believe.

Would it have changed anything?

Honestly? It's hard to say. Maybe Zach fights it and wins his job back, vindicated by the badge records. Maybe the company, embarrassed, quietly makes it go away and Zach never trusts them again anyway. Maybe the supervisor finally fesses up; maybe he lets Zach take the fall to keep his own record clean. People who protect themselves once tend to keep doing it. The same instinct that mis-entered the hours doesn't usually grow a conscience under pressure.

We don't get a clean ending here, because real ones rarely come clean.

One more thing, just for fun

Oh — and I should mention. This was one of those companies.

You know the kind. "Family first." "We value work-life balance." "Our people are our greatest asset." Probably had it on a poster in the break room, in a nice sans-serif font, next to a stock photo of a diverse team laughing at a salad.

A man asked to adjust his hours by thirty minutes to take care of his kid, did everything right to make it happen, and got fired for it — at the family-first company. The very thing they put on the wall was the thing they punished him for needing.

They never really mean it, do they? The companies that have to tell you they value work-life balance are, with remarkable consistency, the ones who'll fire you for using it. The values on the wall aren't a description. They're an advertisement. And the gap between the poster and the parking-lot reality is exactly the size of one good employee, packing his desk at 2:30, on his way to pick up his kid.

I've spent a lot of these posts writing about bad bosses I've had. So it's only fair that I write about the time the bad boss was me.

Because she was. Early on, freshly handed a team and a title, I was exactly the kind of manager I'd now gently pull aside. I wasn't cruel. I wasn't a screamer. I didn't play favorites or take credit or do any of the cinematic villain stuff. My failure was quieter and, honestly, more common: I led with the rulebook and forgot there were people on the other side of it.

I was black and white about policy. Bright, hard lines. And I want to be careful here, because that instinct wasn't all wrong — and I'll defend the part of it that was right before I tell you how it failed me.

In defense of the rookie I was

Here's the thing about applying policy evenly: it actually matters. It matters a lot.

When you apply the rules consistently across every person and every team, you are doing something genuinely important. You're protecting people from favoritism. You're making sure the loud, well-liked, politically savvy employee doesn't get a pass that the quiet, heads-down one would never get. You're creating a workplace where the standard is the standard, regardless of who you are, who you know, or how much the manager happens to like you. Even-handed policy is one of the few real defenses employees have against the arbitrary use of power. It's how you keep "manager's discretion" from quietly becoming "manager's bias."

Fairness is not a small thing. Inconsistency is how discrimination hides. When two people do the same thing and get different outcomes based on nothing but the manager's mood or preference, that's not flexibility — that's the beginning of a lawsuit and the end of trust. So the part of me that wanted everyone held to the same line? That part had good instincts. That part was protecting something worth protecting.

The problem wasn't that I cared about fairness. The problem was that I thought fairness and sameness were the same word.

Where it went wrong

I was hell-bent on no. No was my default setting. No was safe. No mitigated risk. Someone would come to me with a request — a schedule adjustment, an exception, a "my situation is a little different" — and before they'd even finished the sentence, I had already started building the case for why I couldn't possibly, because if I said yes to them I'd have to say yes to everyone, and then where would we be.

I patrolled risk night and day. I treated every exception as a precedent and every precedent as a threat. I was so focused on protecting the organization that I forgot the organization is made of people, and that protecting it sometimes means protecting them.

And here's what I genuinely could not see at the time: I thought I was being a strong manager. Firm. Consistent. Fair. I thought the discomfort I was creating was just the natural cost of holding a line, and that good leaders held lines, so the discomfort meant I was doing it right.

What I was actually doing was teaching a group of talented people that their humanity stopped at the door.

What it cost

The results showed up exactly where they always show up.

Morale slid. Not dramatically — quietly, the way it actually goes. The energy in meetings flattened. People stopped bringing me things. Why would they? They'd learned that bringing me a problem got them a policy, not a person. The little discretionary effort that makes a team great — the staying-late-because-they-care, the catching-the-thing-before-it-breaks, the going-the-extra-foot — it evaporated, because discretionary effort is a gift people give to managers who treat them like humans, and I wasn't.

And then people left. Retention is the most honest scoreboard in management, and mine was telling me the truth even when I wasn't ready to hear it. Good people, people I'd have fought to keep if I'd understood what I was losing, started finding other places to be. They didn't leave because the policies were too strict. They left because they didn't feel seen. Those are different things, and it took me an embarrassingly long time to learn the difference.

I had optimized for risk and lost the thing that actually creates value: people who want to be there.

The lesson that took me years to learn

Here's the insight that eventually cracked it open for me, and it's the thing I'd put on the wall of every new-manager training if I could:

Fair doesn't mean identical. Fair means consistent in your principles, not robotic in your application.

A black-and-white manager treats fairness as: everyone gets the exact same answer. A mature manager treats fairness as: everyone gets the same consideration, the same care, the same honest weighing of their actual situation against the actual purpose of the rule.

Because here's what I didn't understand as a rookie: the rule is not the point. The rule is a tool that exists to serve a purpose. When you apply a rule in a way that defeats its own purpose — when you say no to a grieving employee's schedule request in the name of "consistency," when you deny a reasonable accommodation because you're afraid of precedent — you're not actually upholding the policy. You're worshipping it. You've confused the map for the territory.

The skill — and it is a skill, one nobody is born with — is learning to ask a different question. Not "what does the policy say?" but "what is this policy for, and does saying yes here violate that purpose or serve it?" Sometimes the answer really is no, and you hold the line, and you hold it kindly and clearly. But sometimes the answer is "this situation is exactly the kind of thing flexibility exists for," and the consistent, fair, principled thing to do is to bend.

And — this is crucial — you can do that equitably. The test isn't "did I give this one person a break." The test is "would I extend this same consideration to anyone in this same situation, regardless of whether I like them?" That's the line that separates compassionate management from favoritism. Favoritism bends the rules for people you prefer. Compassionate management bends them for circumstances that warrant it, and would do the same for anyone in those circumstances. One is bias. The other is wisdom. They look similar from the outside, which is exactly why rookies like me retreat to rigidity — because rigidity feels safer than the hard work of being trusted to judge.

Why bad bosses can't do this

This is the part where I'll connect it back to everyone I've written about.

The genuinely bad bosses I've had could not navigate this nuance — but for the opposite reason from the one that tripped me up. I failed at it out of inexperience and fear. They failed at it out of self-interest.

A bad boss can't apply compassion fairly because they don't actually have a principle underneath their decisions — they have preferences, and moods, and politics. They bend the rules for the people who flatter them and enforce them brutally on the people who threaten them. Their "flexibility" is just favoritism, and their "consistency" is just a weapon they aim selectively. The reason they can't navigate the nuance is that nuance requires a stable internal compass — a real, examined sense of what's fair and why — and they don't have one. They have a sense of what's good for them.

I, at least, was failing in good faith. I had the compass; I just hadn't learned to read it yet. I was over-correcting toward rules because I didn't yet trust my own judgment, and rules don't require judgment, which is exactly why frightened new managers cling to them. The bad bosses weren't clinging to anything. They were freelancing, and calling it leadership.

That distinction — failing because you haven't learned versus failing because you don't care — is the whole difference between a rookie and a problem. Rookies grow. Problems just acquire more power.

Who I am now, because of who I was then

I'm a strong leader today. I'll say it plainly, the way I've been practicing saying true things plainly: I'm good at this. And I'm good at it because of the rookie who got it wrong, not in spite of her.

Every time I sit with a manager who's white-knuckling the rulebook, terrified to use their own judgment, I recognize her instantly, because I was her. I know that the rigidity isn't cruelty — it's fear wearing the mask of principle. I know exactly what she needs to hear, because I needed to hear it once: that her instinct toward fairness is good and worth keeping, and that the next level of the skill is learning fairness is about people, not paperwork.

I learned to ask about the human before I reach for the handbook. I learned that "let me understand your situation" is not a threat to consistency — it's the foundation of it. I learned that the best risk mitigation isn't saying no to everything; it's building a team that trusts you enough to tell you the truth, early, while problems are still small. I learned that the word "human" comes first in "human resources" for a reason that took me years and several lost employees to actually understand.

The rookie who said no all day and patrolled risk all night wasn't a bad person. She was a scared one, doing her best with a toolkit that only had one tool in it. I have a lot of compassion for her now. She's the reason I can do this work.

She just hadn't met the people behind the policies yet.

Now I never forget them. They're the whole job.

The single-career-for-life idea is officially dead, and the people who killed it weren't the job-hopping employees everyone loves to scold. Something like 82% of senior executives now openly acknowledge that the one-company career is gone, that jobs have become transient, that people will keep moving toward situations that work better for them.

And somewhere, a manager is still shaking his head about how "nobody's loyal anymore."

Let's talk about that, because the loyalty conversation is one of the most dishonest in all of work — and the dishonesty runs uphill, not down.

Who actually broke the deal

Here's the part the "kids these days have no loyalty" crowd conveniently forgets: companies broke the loyalty contract first, and they broke it decades ago.

The old deal — give us your career, we'll give you security — died when mass layoffs became a routine quarterly lever instead of a last resort. When "we're a family" started meaning "a family that will restructure you out on a Tuesday to hit a number." When pensions vanished and raises stopped keeping pace and the fastest way to get paid what you're worth became leaving. I've written about people fired for "red flags" no one could name, set up to fail by design, managed out for being too good. That's what taught a generation not to be loyal. Not TikTok. Experience.

So when an employee leaves for a better offer, they're not betraying a contract. They're responding rationally to a contract that was torn up by the other side a long time ago. Job-hopping isn't disloyalty. It's self-protection learned from watching what loyalty got the people who had it.

How leaders get this wrong

They demand a loyalty they don't reciprocate. The manager who expects you to bleed for the company but would cut you in a downturn without losing sleep is running a one-way street and calling it a virtue.

They guilt instead of invest. "After everything we've done for you" is the cry of a company that would rather make leaving feel shameful than make staying feel worthwhile.

They treat retention as an entitlement, not an earning. Bad leaders think people should stay. Good ones know people choose to stay, every day, and that the choice has to be re-earned constantly.

How to avoid it — and what replaces loyalty

Stop chasing loyalty. Start earning retention. The new deal isn't "stay forever out of duty." It's "stay because this is genuinely the best place for you to be right now." That's a higher bar, and it's the only honest one.

Make staying the rational choice. Pay fairly without making people leave to get it. Offer growth so the ambitious don't have to job-hop to advance. Treat people like the free agents they actually are, and a surprising number will choose to re-sign.

Be the kind of place people boomerang back to. Here's the upside of the transient era: when you treat people well, departures become alumni, and alumni come back, refer talent, and speak well of you. The leaders who win in a low-loyalty world are the ones who replaced the demand for loyalty with something better — a track record of treating people so well that they want to stay, and think fondly of you even when they go.

Loyalty as obligation is over, and good riddance — it was always mostly a tool for guilting people into accepting less. What replaces it is cleaner and more honest: be worth staying for. The companies still complaining about disloyalty are usually the ones who never tried.

There's a kind of manager who runs a tight ship and is very proud of it. Deadlines get hit. Nobody's late. The team is "disciplined." From the outside — and from above — it can even look like good leadership.

Get closer and you'll notice the thing holding it all together isn't respect or buy-in or shared purpose. It's fear. The team performs because they're afraid of what happens if they don't. And the manager has made a fatal error in interpretation: he thinks the silence in the room is respect, when it's actually people bracing.

Let's talk about fear-based management — how it works, why it feels effective, why it's quietly destroying everything it touches, and how to lead without it.

How fear-based management actually operates

It's rarely a guy screaming all day. The cartoon tyrant exists, but most fear-based managers are subtler and more effective than that. The control is in the atmosphere, not always the volume.

It's the unpredictability — the boss whose mood you have to read before you know which version of him you're getting today, so everyone stays slightly on edge all the time. It's the implied threat behind pleasant words: "I'd hate for this to reflect badly on you." It's public criticism that makes an example of one person so the other ten fall in line. It's the cultivated sense that your job is never quite safe, that approval is conditional and revocable, that one wrong move could be the move. It's information hoarded so you're always a little dependent. It's the cold shoulder deployed as punishment.

The unifying logic is control through anxiety. A frightened person is a compliant person. A frightened person doesn't push back, doesn't ask hard questions, doesn't challenge the boss, doesn't leave (at first). Fear is, in the short term, an extremely effective control technology. That's exactly why it's so seductive and so common.

Why it feels like it's working (and why that's a trap)

Here's the seduction: fear produces fast, visible compliance. People jump. Things get done. The manager feels powerful and effective, and the metrics might even back him up for a while.

But compliance is not commitment, and that distinction is everything. Fear gets you the minimum — exactly what's required to avoid punishment, and not one ounce more. It cannot get you discretionary effort, the extra creativity, the caught-it-before-it-broke, the genuine care. Those are gifts, and people don't give gifts to someone they're afraid of. They give them to someone they trust.

So the fear-based manager gets a team that looks productive and is actually running on empty — doing the letter of the job while withholding the spirit of it, and counting the days until they can leave.

How leaders get this wrong

They mistake fear for respect. The quiet, deferential, no-pushback team feels respectful from the throne. It isn't. Respect makes people speak up; fear makes them shut up. If nobody ever disagrees with you, that's not a sign you're right. It's a sign you've made it dangerous to tell you you're wrong.

They confuse control with leadership. Controlling people is not the same as leading them. Control is what you reach for when you don't have the harder thing — the ability to make people want to follow. Intimidation is leadership's counterfeit.

They strangle the bad news they most need. This is the killer. In a fear-based culture, problems get hidden, not surfaced — because the messenger gets shot. So the manager is always the last to know, finding out about the disaster when it's far too late to fix cheaply. He's built a machine that systematically blinds him to exactly the information he needs most.

They drive out the best first. Your highest performers have the most options. They're the ones who will least tolerate being managed by fear, and the first to walk. Fear-based management acts as a filter that retains the cornered and the compliant and bleeds out the talented and the mobile.

How to avoid it

Audit the silence. If your team never pushes back, never brings you bad news, never disagrees in a meeting — don't take comfort in it. Get worried. Ask yourself honestly whether you've made candor safe or made it dangerous. The quiet is data, and it's usually bad news about you.

Replace fear with clarity and trust. People don't need to be scared to perform; they need to know what's expected, believe it's fair, and trust that doing good work will be recognized rather than punished. Clear expectations and consistent fairness produce better discipline than fear ever does — and they produce it without the rot.

Make it safe to fail forward. The antidote to fear is psychological safety: the confidence that an honest mistake, surfaced early, gets met with "okay, let's fix it" instead of a public execution. That single shift turns your team from a problem-hiding machine into a problem-solving one.

Notice if you enjoy the fear. This is the hard, honest one. Some managers like being feared — it feels like power, it soothes their own insecurity. If you feel a little hit of satisfaction when people scramble at your displeasure, that's worth sitting with. The need to be feared almost always comes from a fear of your own: that without the leverage of intimidation, you wouldn't be followed at all.

The bottom line

Fear-based management is the lazy counterfeit of real authority. It works just well enough, just long enough, to convince the person doing it that it's working — while it quietly hollows out the team, hides the truth from the boss, and drives away everyone good enough to leave.

The respect a fear-based manager thinks he's earned evaporates the instant his power does. Watch how people talk about that boss the day he no longer controls their paycheck. That's the real performance review.

Lead so that people would still follow you if you lost the ability to punish them. If the answer is yes, you never needed the fear. If the answer is no, the fear was the only thing you ever had — and it was never going to be enough.

This one's sensitive, so let me be careful and fair from the start, because it's a topic where it's easy to be neither.

Let me tell you about Lucy.

Lucy worked for a privately owned, mid-size company in Texas — about 200 people. It was, openly and proudly, a "Christian company." This wasn't subtle or implied. They talked about God and Christianity in the open. Meetings opened with prayer. There were team Bible studies. Faith was woven into the daily fabric of the place, worn right there on the company's sleeve for everyone to see.

For a lot of the people who worked there, this was wonderful. A workplace aligned with their deepest values, where they didn't have to leave their faith at the door, where the people around them shared their framework for meaning and morality. That's a genuinely good thing for those people, and I don't want to pretend otherwise.

Lucy was not one of those people. Lucy did not share the religion. And her experience is the one I want to sit with — not because the company was evil, but because her discomfort was real, and it's the kind of discomfort that's easy for the majority in a place like that to never notice.

First, the legal reality, because people get this wrong constantly

Let me put my HR hat on and clear up the law, because there's a lot of confusion here. (Quick caveat: I'm an HR professional, not your lawyer, and this is general information, not legal advice for your specific situation.)

Can a private company be openly religious, pray at meetings, and host Bible studies? Generally, yes. A privately owned business expressing a religious identity is, broadly speaking, legal. Companies are allowed to have a culture, and for many, faith is part of it. Nobody was breaking the law by opening a meeting with a prayer.

Is religion a protected class? Yes — and this is the part people forget. Under Title VII of the Civil Rights Act (which covers most private employers with 15 or more employees), religion is a protected characteristic. And critically, that protection runs in every direction. It protects Christians. It protects Jews, Muslims, Hindus, Buddhists. It protects people whose beliefs are uncommon or held by only a few. And — this is the key one for Lucy — it explicitly protects atheists and people with no religious belief at all. "None" is a protected religious status just as much as "Baptist" is.

So here's the balance the law strikes: the company can express its religion, but it cannot discriminate based on religion, and it cannot coerce employees into religious practice. Those are different things, and the line between them is exactly where Lucy lived.

What would cross the legal line? Firing, demoting, denying raises or opportunities, or retaliating against someone because of their religion or lack of it. Harassment based on religion. And notably, religious harassment can include explicitly or implicitly coercing employees to participate in religious practices. Also relevant: an employee can request a reasonable accommodation — like being excused from a mandatory prayer they object to on grounds of conscience — and the employer generally has to grant it unless it poses a genuine hardship.

So Lucy was right about the thing she understood: they couldn't legally fire her or retaliate against her for not being Christian. Her job, in the strict legal sense, was protected.

The problem is that the law protects you from the things that can be proven. It does not protect you from how it feels.

Where Lucy actually lived: the gap between legal and comfortable

Here's the hard truth this whole post is circling. Something can be completely legal and still quietly corrosive for the person on the outside of it.

Lucy couldn't point to a single fireable offense committed against her. Nobody said "convert or you're gone." Nobody docked her pay for skipping Bible study. On paper, nothing was wrong. And yet she came home worn down, week after week, by an experience that doesn't fit neatly into any legal category.

Because here's what it's actually like to be the one person in the room who doesn't bow your head.

When the meeting opens with prayer and everyone else closes their eyes, you're left with a small, constant, impossible decision. Do you close yours too, performing a devotion you don't feel, to blend in? Do you keep them open and sit there visibly apart, the one person clearly not participating, hoping no one glances over? There's no neutral option. Every single meeting, you have to choose how much of yourself to hide.

Lucy didn't want to participate in something she didn't believe — that would have felt false. But she also didn't want to appear different, because appearing different in a place where sameness is the norm carries a cost you can feel even when no one names it. So she existed in a permanent low-grade tension: too honest to fake it, too exposed to be honest. That tension is exhausting in a way that's hard to explain to someone who's never been the only one.

And the judgment she felt? It may never have been spoken aloud. It probably wasn't. But belonging in a tight religious culture is often subtly tied to shared faith, and when you don't share it, you can feel yourself quietly sorted into a different category — not hated, not punished, just... slightly outside. Not quite one of us. And humans are exquisitely sensitive to that sorting, even when it's never put into words. Especially when it's never put into words, because then you can't even address it. You just feel it.

The pros, honestly stated

I promised fairness, so let me give the religious company its real due, because there are genuine upsides.

For employees who share the faith, a values-aligned workplace can be deeply fulfilling. There's a coherence to working somewhere whose stated principles match your own. These companies are often genuinely communal — they tend to take care of their people, show up during personal crises, and operate from an explicit ethic of compassion that a lot of secular companies only gesture at. The owners frequently aren't being cynical; they're running their business according to what they sincerely believe is right, and many of them would be horrified to learn someone like Lucy felt excluded. There's often real warmth in these places. That warmth is not fake. It's just not universal, and that's the rub.

The cons, just as honestly

But wearing religion on the company's sleeve carries real costs, and a good leader has to be willing to see them.

It narrows the circle of belonging along a line that has nothing to do with the work. It creates an in-group and an out-group based on faith, and the out-group — even when treated perfectly legally — pays an emotional tax just for showing up. It can quietly shape who gets hired, who gets mentored, who gets invited to the informal conversations where careers are actually made, all without anyone consciously intending bias. It puts people like Lucy in the position of either masking or marking themselves, every day, forever. And it exposes the company to real legal risk the moment that cultural pressure tips over into anything that looks like coercion or differential treatment — which, in a place where the line is blurry and everyone assumes good intentions, is easier to cross than they think.

There's also a deeper cost the company can't see from the inside: they will never get the full truth from their Lucys. She's not going to raise her hand in the all-hands and say the prayers make her uncomfortable. She's going to smile, keep her head down, and eventually leave — and the company will record it as "not a culture fit," never understanding that the culture was the thing that fit her out.

What I'd tell the company, and what I'd tell Lucy

To a leader running a faith-forward company: You're allowed to have your values. But the most Christian thing you could do — and I say that sincerely, on its own terms — is to make genuinely sure the person who doesn't share your faith feels as safe, as valued, and as full a member of the team as everyone else. That means making religious activities truly optional with zero visible cost to opting out. It means watching whether your Lucys get the same mentorship, the same opportunities, the same inclusion in the informal stuff. It means creating a way for someone to say "this makes me uncomfortable" without it being a career-limiting move. If participation is truly free — no penalty, no subtle sorting, no raised eyebrow — then you've earned the right to your culture. If it isn't, you've built an in-group with a legal disclaimer.

To Lucy, and everyone like her: Your discomfort is legitimate. You're not being oversensitive, and you're not obligated to perform a faith you don't hold to keep the peace. The law is genuinely on your side more than you might think — your beliefs (or absence of them) are protected, you can't lawfully be retaliated against for not participating, and you can even request to be excused from things like mandatory prayer as a reasonable accommodation. But also be honest with yourself about the daily emotional cost, because that part the law can't fix. Sometimes the healthiest read on a place that requires you to hide a fundamental part of yourself to belong is simply: this may not be the place for me. Not because you're wrong. Because fit goes both ways, and you deserve to work somewhere you don't have to decide, every Tuesday morning, whether or not to close your eyes.

The honest bottom line

A company can be openly religious and entirely legal and still be a hard place to be the odd one out. All three of those things are true at once, and pretending any one of them away does a disservice to somebody.

The faithful employees deserve their values-aligned workplace. Lucy deserves to not feel like a stranger at her own job. And the law sits in the middle, drawing a line — you can express, you can't coerce — that's clear in a textbook and blurry as anything in a conference room where everyone's bowed their head but one.

The companies that handle this well aren't the ones that hide their faith. They're the ones secure enough in it to make absolutely certain that the person who doesn't share it never pays a price for that. That's a high bar. Most don't clear it. The ones that do are genuinely special — and Lucy's company, for all its warmth, probably never even knew the bar was there.

Every workplace is a poker game, and most people never realize they've been dealt in.

Not the cartoon version of office politics — the backstabbing and the obvious schemers. I mean the quieter game, the one happening underneath every meeting, every hallway exchange, every "quick sync." And the most dangerous players at the table are the ego-driven, power-hungry managers who've gotten very, very good at not showing their hand.

Here's the thing about a skilled poker player: the tells are there. They're always there. But the obvious ones — the temper, the credit-stealing, the open hostility — those are the equivalent of a beginner slamming the table. Easy to spot. The genuinely dangerous players gave those up years ago. What's left are the micro-tells, the involuntary leaks, the little physical and verbal giveaways most people at the table never learn to read.

Let me teach you to read them. Once you see them, you can't unsee them.

Tell #1: The body that's always claiming territory

Watch how an ego-driven manager occupies space, because the body leaks what the mouth controls.

They spread. The expansive posture — leaning back with hands behind the head, an arm slung over the neighboring chair, papers and phone and coffee fanned out to colonize the table — is a primate dominance display dressed up in business casual. It says this space is mine, and so, by extension, are you. Watch them in a conference room: the secure leader takes up a normal amount of room. The power-hungry one annexes the territory around them.

Watch the walk, too — the unhurried stroll into a meeting that's already started, the way they make a room wait. Punctuality is deference, and deference is for other people. Making you wait is one of the cheapest, most deniable power moves there is, and the people who do it habitually are telling you exactly how they rank you.

And watch the handshake, the touch. The hand that lands on your shoulder a beat too long. The palm that turns yours downward in a shake. The guiding hand on your back steering you through a doorway you were perfectly capable of walking through. These read as warmth or courtesy on the surface. Underneath, they're small assertions of physical control, and the tell is that they only ever flow downward — they touch subordinates this way, never their own superiors.

Tell #2: Eye contact as a weapon, not a connection

Most people think strong eye contact signals confidence and honesty. With this type, it's more complicated, and the tell is in the pattern.

The ego-driven manager often gives too much eye contact — the unblinking, slightly-too-long lock that isn't connection but pressure. It's the stare that's measuring you, waiting for you to look away first, turning a conversation into a small dominance contest you didn't know you'd entered. Notice how you feel after: vaguely unsettled, subtly diminished, not sure why.

But here's the more revealing version: watch their eyes when someone else is talking — especially someone they don't consider important. The gaze drifts. They check their phone. They look over the speaker's shoulder for someone better to talk to. Attention is a currency, and they spend it strictly according to your perceived value to them. The person who locks eyes with the VP and goes glassy when the junior analyst speaks has just shown you their entire value system in the span of one meeting.

Tell #3: The praise that's actually a cage

This is the subtle one, and it's the tell most people completely miss because it's disguised as something nice.

Listen to how they compliment. The ego-driven manager rarely gives clean praise. It comes with a hook. "You're so much better at this than the others" — praise that isolates you from your peers and binds you to them. "I knew you had it in you" — praise that quietly claims credit for your achievement. "You're the only one I can trust with this" — praise that's actually a leash. The healthy leader's praise leaves you feeling capable and free. This kind leaves you feeling chosen, which is a much stickier and more dangerous feeling, because chosen people work to stay chosen.

The flip side is the compliment-with-a-blade, the negging that keeps you slightly off balance. "That's a great idea — surprising, coming from you." "You clean up well today." "I love how you don't even care what people think." Each one lands a tiny cut wrapped in a tiny gift, and you walk away vaguely deflated without being able to point to anything you could fairly object to. That's not clumsiness. That's the technique. Keeping you a half-step unsteady keeps you easier to lead.

Tell #4: Speech patterns that police the hierarchy

The way they talk — not what they say, but the architecture of it — is full of tells.

They interrupt downward and defer upward. Track who gets cut off and who gets heard out. The ego-driven manager talks over subordinates with ease and would never dream of doing it to their own boss. The direction of the interruptions is a perfect map of how they rank everyone in the room.

They ask questions that aren't questions. "Don't you think it would be better if...?" "Wouldn't you agree that...?" These are commands disguised as collaboration, and the tell is that there's no version of the situation where "no, actually" is a welcome answer. They want the appearance of buy-in without the reality of it.

They use "we" for blame and "I" for credit. Listen closely over time. When something goes well, watch the language drift toward "what I built," "my call," "my vision." When something goes wrong, it becomes "we dropped the ball," "the team missed this," "mistakes were made." The pronouns are doing quiet accounting, and the books are always balanced in their favor.

They go warm in public and cold in private, or vice versa. The mismatch between someone's onstage and offstage self is one of the loudest tells there is. The manager who is charming in the all-hands and curt in the one-on-one is showing you which audience they're performing for — and it isn't you.

Tell #5: How they treat the people who can't help them

This is the single most reliable read at the entire table, and it's the one I'd tell you to watch above all others.

Watch how they treat the people with no power over their career. The receptionist. The cleaning staff. The new temp. The waiter, if you ever catch them at a work dinner. People manage up instinctively — anyone can be charming to someone who controls their bonus. The mask only comes off with people who can't do anything for them, and that's exactly where the real personality lives.

The manager who is gracious to the executive and dismissive to the assistant has told you everything. The warmth they show you is conditional and strategic; it will last exactly as long as you're useful, and it will vanish the moment you're not. The person who's kind only when kindness pays is not kind. They're just calculating, and you're currently on the profitable side of the math. Don't mistake your current position for safety.

Tell #6: The micro-expression when you succeed

The hardest tell to fake, and the most telling, is the involuntary flash that crosses an insecure, power-hungry person's face when someone else wins.

Watch them — really watch — at the moment a colleague gets praised, lands the big client, gets the promotion. For a fraction of a second, before the trained smile arrives, there's something else. A tightening around the eyes. A flicker of something cold. The scarcity-minded see others' success as their own loss, and the body knows it before the face can cover it. A secure person feels genuine warmth at someone else's win, and it shows. The ego-driven person has to manufacture the warmth, and there's always a beat of lag while the manufacturing happens. Learn to see that beat. It's the truest card they'll ever accidentally show you.

How to play your own hand

So you've learned to read the table. Now what?

First: don't tip that you can see. The whole advantage of reading tells is that the other player doesn't know you're reading them. Stay gracious, stay professional, and simply update your internal model of who you're dealing with. Knowledge you keep to yourself is leverage; knowledge you announce is just a fight you've started early.

Second: protect your hole cards. Around a manager who collects information to use later, share less than feels natural. Keep your ambitions, your vulnerabilities, your personal struggles closer to the vest than you would with someone who's earned your trust. Document things. Confirm agreements in writing. Not because you're paranoid — because you've read the table accurately and you're playing accordingly.

Third: know when to leave the game. Here's the thing poker teaches that the office tries to make you forget — you are allowed to stand up from a bad table. If you've read the tells, watched them confirm over months, and concluded you're sitting across from someone whose entire game is power and ego, no amount of skilled play makes that a winning seat. The best players don't grind out hands at a table where the deck is rigged. They cash out and find a better game.

The final read

Here's what all these tells have in common, the thing underneath the body language and the speech patterns and the conditional warmth: insecurity. Genuinely powerful, genuinely secure people don't need to claim the territory, win the staring contest, cage you with praise, or perform warmth they don't feel. They have nothing to prove, so they don't perform.

The tells are the insecurity leaking out. The bigger the display, the smaller the person running it. Every dominance move is a confession that they're not as solid as they're pretending to be — that underneath the expansive posture and the strategic charm is someone terrified of being seen as ordinary.

Once you understand that, the whole table changes. You stop being intimidated and start being informed. You're not a chip in their game anymore.

You're just a very good player who finally learned to read the room.

There's a quiet revolution happening in how teams communicate, and it's being sold to us as pure progress. The AI notetaker joins the call. The recap lands in your inbox. The action items auto-populate. Nobody has to take notes, nobody has to remember, nobody has to even really be there. Efficient!

And something is dying in the gap, and I want to name it before we optimize it out of existence entirely.

The thing the summary leaves out

I once wrote about a manager, Ben, who scheduled a standing weekly meeting with an employee and then bolted five minutes before it every single time. The meeting existed on the calendar; the connection never happened. The empty chair was the message.

The over-summarized workplace is Ben's failure at scale — except now it's dressed as innovation. When the meeting becomes a transcript, you capture the information and lose the relationship. You get what was decided and lose the thing that actually binds a team: the side comment, the read on someone's tone, the "hey, are you okay, you seem off today," the trust that gets built in the unstructured minutes around the agenda.

A summary tells you what happened. It cannot tell you that someone went quiet when their project came up, or that two people are quietly at war, or that your best performer is one bad week from quitting. That information only lives in the room — and increasingly, no one's in the room.

How leaders get this wrong

They mistake information transfer for management. Forwarding a recap is not leading. The job was never just moving facts from one place to another; it was the human attention that travels alongside the facts.

They use efficiency to avoid presence. The same instinct that made Ben skip the one-on-one now hides behind "I'll just catch the summary." It feels productive. It's actually abandonment with better branding.

They let people become un-seen. A team member who only ever appears to you as a line in an auto-generated recap is a team member you've stopped actually knowing. And people who feel unseen disengage — quietly, and then permanently.

How to avoid it

Protect the live conversation like it's the asset it is. Use AI to capture logistics so you can spend the actual meeting being present — not so you can skip the meeting.

Keep the one-on-one sacred and human. No notetaker as a substitute for your attention. The whole value is that a real person is listening to a real person.

Ask the questions a transcript can't answer. "How are you, really?" "What's not in the recap that I should know?" The unstructured human stuff is not the inefficiency to be trimmed. It's the job.

Efficiency is a wonderful servant and a terrible master. The leaders who win the next decade won't be the ones with the cleanest summaries. They'll be the ones who still bothered to be in the room.

Return-to-office is still one of the most fought-over topics in the working world, and the numbers tell you why: somewhere around 70% of remote-capable employees want hybrid or fully remote arrangements, while only about a third want to be mostly on-site. The smart organizations have started replacing blanket mandates with flexible, role-based models.

The not-smart ones are issuing decrees. And I want to talk about what an RTO mandate actually says — because employees hear the subtext loud and clear, even when leadership thinks it's being subtle.

What "come back to the office" often really means

Here's the translation a lot of workers are doing in their heads when the all-staff email lands: We don't trust you to work unless we can see you.

Because for most knowledge roles, the on-site mandate isn't about collaboration — if it were, it would be designed around when collaboration actually happens, not five fixed days of everyone sitting in the same building doing solo work next to each other. It's about visibility. It's about a leadership instinct that confuses "I can see you at your desk" with "you are being productive," which are completely different things and always have been.

I once wrote about a man fired for "wage theft" because his boss saw him leave at 2:30 and assumed the worst — never checking that he'd arrived at 6:30. That's the surveillance instinct in miniature: judging the work by the optics of presence instead of the reality of output. A blanket RTO mandate is that same instinct, scaled to the whole company.

How leaders get this wrong

They mandate presence instead of designing for it. "Everyone, five days, because I said so" is not a strategy. It's a failure to do the harder work of figuring out what actually needs to happen in person and building around that.

They measure the wrong thing. A butt in a seat is not output. The leader who feels reassured by a full parking lot is reassuring themselves, not improving anything.

They spend trust they can't get back. Forcing people back without a real rationale tells your best, most mobile employees exactly how much you trust them — and those are precisely the people with the options to leave. They will.

They pretend it's about culture when it's about control. Employees can tell the difference between "we genuinely do better work together on these days" and "we don't believe you're working." Dressing the second one up as the first just adds insult.

How to avoid it

Start from the work, not the wish. Ask what genuinely benefits from being in person — hard collaboration, onboarding, certain creative sessions — and design around those, not around a number of mandated days.

Measure outcomes, not optics. If someone delivers, where they sat while delivering is not your business. If they don't, that's a performance conversation, not a real-estate policy.

Be honest about your reasons. If you want people in for a real reason, say the real reason and let it stand on its merits. If your only reason is that you feel uneasy not seeing them, that's your discomfort to manage, not a policy to impose.

The RTO debate is, underneath, a trust debate. The companies that handle it well treat their people like capable adults and get loyalty in return. The ones that fail treat presence as proof and wonder why everyone good keeps leaving. Where someone sits has never been the same as whether they're worth trusting. The bosses who can't tell those apart are telling on themselves.

There's a sentence I expect to hear a lot more of in the coming years, and it makes my skin crawl every time: "The system flagged you."

Your productivity score dipped. The engagement model surfaced your name. The performance algorithm identified you as low-percentile. The AI recommended the restructure, and unfortunately your role didn't make it. No human decided this, you understand. The machine did. Nobody's fault. Nothing to discuss.

I want to talk about how AI is becoming the most powerful accountability-laundering device ever invented, and how it's letting cowardly leadership do an old thing in a new, untouchable way.

Engineered disengagement, now with a robot to blame

I once wrote about how toxic workplaces don't fire you — they set you up to fail, then point at the failure as if it were yours. The cruelty was always in the deniability: every individual step looked reasonable, so you couldn't prove the pattern.

AI is rocket fuel for that deniability. Now the setup and the verdict can be attributed to a system that "just analyzes the data" — data the company chose, weighted, and aimed. When a leader says "the algorithm flagged you," what's really happening is a human being is hiding their judgment, their bias, or their predetermined decision behind a wall of math that feels objective and is anything but.

The algorithm didn't decide to weight "hours visibly online" over actual output. A person did. The algorithm didn't choose which roles to feed into the restructure model. A person did. The machine is not the decision-maker. It's the alibi.

How leaders get this wrong

They use "objective" data to dodge ownership. The whole appeal of the algorithmic verdict is that no one has to stand behind it. That's not a feature. That's a manager refusing to do their job.

They let the metric become the manager. When a number on a dashboard replaces actual judgment about a human's contribution, you get people optimizing for the metric instead of the work — and good people punished by a model that can't see what they actually do.

They hide bias inside the black box. An algorithm trained on a biased history launders that bias into "data." The leader gets to enact the same old favoritism and exclusion while claiming pure objectivity. It's the cleanest discrimination ever devised, because it doesn't feel like a choice.

How to avoid it

Own every decision a tool informs. If you act on what the system surfaced, you decided. Say so. "I'm making this call, and here's my reasoning" — never "the system made me."

Interrogate what you're measuring. Before you trust a flag, ask what the model rewards and whether it actually correlates with the work that matters. Most "productivity" metrics measure visibility, not value.

Keep a human in every consequential loop, with a name attached. Anyone affected by an algorithmic decision deserves a person who will look them in the eye, explain it, and answer for it.

The technology is not the villain here. The villain is the same as it ever was: a leader who wants the authority to end someone's livelihood without the courage to own the choice. "The algorithm flagged you" is just "I had no clue what to do" wearing a lab coat. Don't let anyone hand you a verdict that nobody will sign their name to.

Look, I've been writing some heavy stuff lately. So today I want to tell you about a guy I'll call my "bad boss who wasn't really bad," because compared to what came later in my career, he was practically a saint. A weird, mildly inappropriate, deeply 1972-coded saint.

He was in his sixties. I was twenty-two. Fresh out of school. The ink on my diploma was so wet I could still smudge it. And he was the kind of man who said things like "Hello, kitties!" when he walked into a room of women.

Reader. Kitties.

The vocabulary of a man who learned management before women had checking accounts

He didn't mean anything bad by it. That's the thing. That's always the thing, isn't it? He genuinely thought "Hello, kitties!" was a charming greeting. The way someone might say "hey, team!" or "morning, everyone!" Except instead he picked a word that, in 2025, would get you walked to HR by an escort of three lawyers and a tactical mediator.

His whole vocabulary was like this. We were "sweetheart" and "honey" and "dear" — never our actual names, which I think was less misogyny and more that he genuinely could not remember them. He'd call across the office, "Sweetheart, can you grab that file?" and four of us would turn around, because we had collectively become The Sweethearts, an unwilling girl group that never released an album.

He'd compliment your outfit in a way that made you suddenly aware of your outfit. He'd notice a haircut. He'd notice if you skipped lunch. He noticed everything about us in a way that was simultaneously creepy and, weirdly, more attentive than any boss I've had since. I'm not defending it. I'm just saying the bar fell into hell at some point and we should probably talk about that too.

The sexy librarian incident

So one day I wore my glasses to work.

I don't normally wear them. I wear contacts. But my eyes were tired, I was twenty-two and broke and probably hungover, and I figured nobody would notice.

He noticed.

He walked past my desk, did a full double-take, and said — and I want you to know I am quoting verbatim, because this sentence has lived rent-free in my head for over a decade — "Well well, look at you. You look like a sexy librarian."

I just sat there. I didn't know what to do with my face. My face had not been trained for this. My face was twenty-two years old and had a communications degree, not a "respond to your sixty-something boss commenting on your sex appeal" degree.

So I did what every woman my age did in that moment, in that decade, in that situation: I laughed. A small, polite, please-go-away laugh. The laugh that says "I am acknowledging that a thing has been said, and I would like very much for the thing to now be over." And he chuckled and walked off, pleased with himself, and I sat at my desk and wondered if I should take the glasses off.

I took the glasses off.

I want to be clear: nothing else happened. He didn't follow it up. He didn't try anything. He wasn't that kind of guy. He was just a guy from a time when commenting on a young woman's appearance was something you did before your morning coffee, like reading the sports page. He genuinely thought he was being nice.

And that, I think, is the whole tangled knot of it.

The thing that makes this complicated

Because here's where it gets uncomfortable, and where I want to be honest.

He was, in many ways, a really good boss. He defended his team. He went to bat for our raises. He took the heat when something went wrong and gave us the credit when something went right. He noticed when I was struggling and pulled me into his office for a pep talk that I, embarrassingly, still remember the substance of.

He also called me "kitten" once and I'm still processing it.

These two things existed in the same man. And I think a lot of women my age and older have a version of this guy in their career story — the boss who was, on the books, a good boss, but who came with a side dish of casual creep that you just kind of had to eat around. The boss whose competence and decency you remember warmly, and whose comments about your sweater you remember less warmly, and you're not sure what to do with the fact that both memories belong to the same person.

The temptation is to pick one. He was good, therefore the comments were no big deal. Or, he made the comments, therefore nothing he did counts. Both of those are easier than the truth, which is that a man can be a real mentor to you and also a low-key liability, and the way our culture handled that for decades was to tell women to just be cool about it.

We were so cool about it. We were the coolest. We were ice.

The carryover, which is the actual point

Here's why I wanted to write about him, even though he was, in the grand scheme of bosses I've had, basically fine.

Because the "Hello, kitties!" guy is retiring. He's mostly retired, actually. The men who learned to manage in the seventies and eighties — the ones for whom "honey" was a normal way to address a junior colleague, for whom commenting on your appearance was just being friendly — they're moving out of the workforce. Good. Godspeed. Enjoy your boats.

But here's the thing nobody talks about: they trained the next generation. The men currently in their forties and fifties, who are running things now — they learned how to be bosses from those guys. They learned what was normal from those guys. They watched those guys get away with things and they absorbed the lesson, even when they didn't mean to.

So we still get the carryover. Softer now, sure. More plausibly deniable. Nobody's calling you "kitten" anymore — but they're still commenting on your outfit in a way that makes you not want to wear it again. They're still "joking" in the meeting in a way that makes you the punchline. They're still doing the thing where they remember your appearance more than your last presentation.

The vocabulary updated. The reflex didn't.

And the women in their twenties right now are doing exactly what I did at twenty-two: laughing politely, going home, telling their friends about it over drinks, and wondering if they're being too sensitive about it. (They are not.) (We were not.) (Nobody is.)

What I'd say to my twenty-two-year-old self in the glasses

I wouldn't tell her to make a big deal of it. The world she was in wasn't going to receive a big deal kindly, and I'm not going to lie to her about that.

But I might tell her this: you don't actually have to laugh. You can just not. You can let the moment land in silence and watch what he does with it. You can say, "Oh, weird thing to say," and go back to your work, and let the awkwardness be his to hold instead of yours. You don't owe a polite laugh to a comment that made you feel like you were suddenly visible in a way you didn't ask to be.

I'd also tell her: keep the glasses on. They look great. The problem was never the glasses.

And to the guy himself, wherever he is

I hope you're well. I hope your boat is nice. I hope your grandkids are teaching you words like "cringe" and "ick" and explaining, gently, why you cannot say certain things at Thanksgiving anymore. I hope you've stopped calling women "kitties," but if you haven't, I hope at least your wife has staged some sort of intervention.

You weren't the worst boss I ever had. Not even close. The worst bosses I had came later, in suits, with the right vocabulary and the wrong intentions, and I almost wish I'd had your honesty — the honesty of a man who at least let you see exactly what he was.

Almost.

I'm still keeping the glasses on, though.

Let me tell you about Richard.

Richard was a boss. Richard was also, by the broad consensus of everyone who ever reported to him, a real Dick — a nickname so apt that I'm not sure anyone remembered it was technically short for his actual name. Some people grow into their names. Richard sprinted.

This isn't my story. It happened to someone I'll call John — a perfectly competent, perfectly normal employee who had the misfortune of being disliked by Richard for reasons Richard was never, not once, in years, able to actually explain.

And that — the never being able to explain it — is the whole psychological heart of this story. So let's talk about it.

A man of strong feelings and no vocabulary

Richard had feelings about John. Big ones. Persistent ones. Richard did not like John, and Richard felt this dislike in his bones, in his gut, in whatever organ generates a vague sense of grievance.

What Richard could not do — what Richard was constitutionally, almost magnificently unable to do — was turn that feeling into a single concrete sentence about a single concrete thing John could change.

You know the manager who can say, "Hey, in Tuesday's client call, you talked over the customer twice and we lost the room — let's work on that"? That's a manager doing his job. That's feedback. It's specific, it's actionable, it points at a behavior instead of a person, and it gives the employee a door they can actually walk through.

Richard was the opposite of that man in every measurable way. Ask Richard what was wrong with John and you'd get a long, frustrated exhale. A shake of the head. A "there's just... something." A gesture, vaguely, at the air around John, as if the problem were atmospheric. Richard had a feeling the size of a weather system and a vocabulary the size of a fortune cookie.

Where Richard's words did work great: behind John's back

Now, I don't want to give the impression that Richard couldn't communicate. Richard was an excellent communicator. A gifted one, even.

He just only did it about John, to everyone except John.

Richard could complain about John with the fluency of a man delivering a TED talk. To peers. To other managers. To anyone in the break room who made the fatal error of asking how things were going. Richard had a rich, detailed, deeply felt catalog of concerns about John — and he was happy to share it with the entire org chart, in confidence, repeatedly, with feeling.

The one person who never got to hear any of it was John.

This is one of the most common and most cowardly patterns in all of management, and it deserves to be named for what it is: it's not feedback, it's campaigning. Richard wasn't trying to help John improve. He was building a case in the court of public opinion, lining up witnesses, making sure that by the time anything official happened, the narrative was already set. He was managing John's reputation instead of managing John.

And here's the tell: a manager who genuinely wants an employee to improve talks to them. A manager who has already decided to be done with someone talks about them. The direction of the conversation tells you everything about the intention behind it.

The psychology, and the ego underneath it

So why couldn't Richard just say the thing? Let's get into it, because this is the actually interesting part.

Giving someone clear, actionable feedback requires a few things Richard didn't have.

It requires emotional regulation — the ability to feel a strong feeling and not be run by it, to cool the reaction down enough to find the information inside it. Richard couldn't do this. Richard's dislike arrived as pure heat, and heat doesn't form sentences. It just radiates.

It requires self-reflection — the ability to ask "what specifically is bothering me, and is it actually about him, or is it about me?" This is the question Richard could not afford to ask, because the honest answer might have implicated Richard. Maybe John was confident in a way that made Richard feel small. Maybe John questioned things and Richard heard questions as challenges to his authority. Maybe John was simply good, and good people are threatening to insecure ones. To articulate the real problem, Richard would have had to look in a mirror, and the mirror was the one room in the building Richard refused to enter.

And it requires ego strength — and here's the irony that makes this whole thing tick. We think of guys like Richard as having big egos. They don't. They have fragile ones. A person with a genuinely secure ego can sit across from an employee, deliver hard feedback, tolerate the discomfort of the other person's reaction, and stay steady. That takes a self that doesn't shatter on contact. Richard didn't have that self. Articulating a specific criticism means standing behind it, defending it, possibly being wrong about it — and a fragile ego cannot risk being wrong, because being wrong feels like being annihilated. So it's safer to stay vague. Vague can't be argued with. "Red flags" can't be disproven. A feeling can't be cross-examined.

Richard hid behind vagueness because vagueness was the only place his ego felt safe. Specificity would have required him to be accountable for his own judgment, and accountability was the one thing Richard's ego could not survive.

"A lot of red flags"

Which brings us to the morning Richard fired John on the spot.

No warning that morning. No formal process worth the name. Just Richard, deciding he was done, and informing John of this fact with the now-legendary explanation that John had "a lot of red flags."

Red flags. That was it. That was the whole performance review, the whole case file, the entire articulated reason for ending a human being's employment: a lot of red flags.

And the cruelest part — the part that reveals exactly how long this had been coming — is that it wasn't the first time Richard had said it. He'd used the phrase before. "Red flags." More than once. Always the same words, always the same fog around them, never once followed by an actual example of an actual flag of an actual color. John had even asked. Which red flags? Can you give me one? And Richard couldn't. Or wouldn't. The flags remained classified, eyes-only, available to every break room in the building but never to the man they belonged to.

You cannot fix a red flag you're never shown. That's not an accident. That's the design. Because if Richard had ever named one specific, addressable thing, John might have fixed it — and then Richard would have been stuck with a John he still didn't like and no longer had a reason to remove. The vagueness wasn't a failure of communication. It was the strategy. It kept the exit door open at all times.

The serious part, because there has to be one

Here's where I stop making fun of Richard, because somewhere out there is a real John, and the John in this story didn't find it funny at all.

Being managed by a Richard does real damage. When you know your boss has a problem with you but he won't tell you what it is, you live in a low-grade panic that never resolves. You can't improve, because you've been given nothing to improve. You can't defend yourself, because there's no specific charge to answer. You start scrutinizing your own every move, trying to guess at the invisible standard, trying to read the mood of a man who has decided your fate and won't tell you the verdict. It is a uniquely crazy-making form of professional limbo, and people carry the self-doubt from it for years.

And the firing, when it finally comes, is almost a relief — except it isn't, because it arrives with no closure, no explanation, nothing John can learn from or grow past. Just "red flags" and a cardboard box. Richard got to keep his story. John got to carry the wound.

The truly insidious thing is that John will spend months, maybe years, asking himself what were the red flags? He'll comb back through everything, looking for the flaw, internalizing a verdict that was never really about his performance at all. He'll do the work of self-criticism that Richard was too cowardly to do honestly out loud. That's the final theft: Richard outsourced his own unexamined feelings, and John pays the interest.

What a real leader does instead

So that the post isn't just a roast, here's the contrast, because it's clarifying.

A real leader who doesn't click with an employee does the uncomfortable thing: they get specific. They separate "I have a personality friction with this person" from "this person is underperforming," because those are completely different problems with completely different solutions. They give feedback to the person's face, early, while it's still small enough to fix. They tolerate the discomfort of the conversation instead of dumping it into the break room. And if it truly isn't working out, they can say why, in plain language, with examples, like an adult who stands behind their own judgment.

That's not just nicer. It's braver. It requires the exact ego strength Richard lacked — the kind that can be accountable, can be specific, can risk being wrong, and can let an employee leave with their dignity and a clear understanding of what happened.

Richard couldn't do any of that. So Richard complained, and stewed, and gestured at the air, and finally reached for the vaguest possible weapon and fired a man with the words "red flags."

The real red flag, of course, was Richard.

It usually is.

Not every bad boss is a villain. Some of them are just a knot you can't quite untangle, even years later. This one is mine.

She wasn't bad. I want to say that up front, because the easy version of this story would make her a monster, and she wasn't one. She was warm and funny and, in a lot of ways, good to me. She was also a woman who crossed about every professional boundary there is to cross, and the strangest part — the part I've spent a long time sitting with — is that for a while, I let her. I more than let her. Some part of me liked it.

So this is a story about boundaries. But it's also a story about why I didn't defend mine, which turns out to be the more interesting question.

The hair, the rides, and the cheek pinch

Let me just list them, because the list is genuinely a little unhinged when you see it all together.

She asked me to do her hair. As in, style it. At work. Me, a director, with my own team and my own deliverables, standing behind my boss with a round brush.

She asked me for rides. Places that were not on my way, at times that were not convenient, for reasons that were not work. And I gave them, cheerfully, like an unpaid concierge with a graduate degree.

And once — this is my favorite, in the way that something can be your favorite and also make you wince — she pinched my cheek. Pinched it. The way your grandmother does to a four-year-old at Thanksgiving. Ohh, look at this one. I was a grown professional woman and my boss pinched my cheek like I was a cherub in a Renaissance painting.

She also insulted me constantly, though I don't think she meant to. They were accidental, these little cuts — a backhanded compliment here, a "well, you wouldn't understand" there, a comment about my outfit or my age or my approach that landed wrong and that she never seemed to notice landing at all. Death by a thousand papercuts, except the person holding the paper had no idea she was cutting.

And here's the part I have to be honest about: I didn't mind. At the time, I genuinely didn't. In fact, some part of me felt that all of it — the hair, the rides, the cheek, even the little insults — brought us closer. Like I was special. Like I was in. Like the boundary-crossing was a kind of intimacy, and the intimacy was a kind of safety.

It took me a long time to understand what that response actually was.

A short, necessary detour into fawning

There's a stress response most people have never heard of, and once you learn about it, you start seeing it everywhere — especially at work, and especially in women, and especially in high achievers.

Most people know fight or flight. Some people know freeze. Fewer people know about fawn.

Fawning is the stress response where, faced with a threat or a power imbalance or an unpredictable authority figure, you don't fight and you don't flee — you please. You appease. You make yourself useful, agreeable, indispensable, easy. You manage the other person's emotions so that they never have a reason to turn on you. You merge your needs into theirs until you can't quite locate your own anymore.

It's a survival strategy, and it's a smart one. It usually develops early, in childhood homes where keeping a volatile adult happy was the safest way to get through the day. And it follows you into the workplace beautifully, because the workplace rewards it. The fawner is the one who stays late, who never says no, who anticipates the boss's needs before the boss does, who is "so easy to work with," who "never complains." The fawner gets called a team player. The fawner gets called a star.

The fawner is also exhausted, resentful in a way she can't admit to herself, and slowly disappearing.

Here's the thing about fawning that makes it so sneaky: it feels like connection. When I did my boss's hair, when I gave her the rides, when I laughed off the cheek pinch — my nervous system read that as I am safe, I am valued, I am close to the powerful person and therefore I am protected. It didn't feel like a stress response. It felt like friendship. That's the trap. The very thing that's costing you your boundaries registers, internally, as warmth.

So when I tell you I didn't mind doing her hair — I believe that I didn't, consciously. But I also think that the part of me doing the not-minding was a much younger part, a part that learned a long time ago that the way you stay safe around an unpredictable powerful person is to make yourself so pleasant and so useful that they could never want to hurt you.

It worked, too. Right up until it didn't.

The day I showed her up

Here's where the warmth turned, and where I learned what was actually underneath it.

I developed a project. Independently, with a contractor, fully within my scope as a director — this was my job, this was exactly the kind of thing I was there to do. And it was good. I knew it was good. I built it, I shaped it, I brought it to life, and then I presented it to her and to our senior leadership.

It landed. It really landed. The room responded the way you dream about a room responding. I could feel it — that rare, clean feeling of doing the thing you're good at, in front of the people who needed to see it, and having it work.

And I looked at my boss, expecting — what? Pride? Shared joy? The warmth she'd shown me a hundred times over the dumbest things?

Her eyes shot fire.

I want to be precise about this because it was so fast and so unmistakable. For one unguarded second, before she rearranged her face, I watched something flash across it that was not pride. It was something closer to fury. And then she caught herself, and she smiled, and she said how proud she was of me, and then she told me to leave.

"Get out!" she said, laughing, performing delight. "Reward yourself! Take a half day! You've earned it!"

It was framed as generosity. Go on, you deserve it, treat yourself. But I knew, even in the moment, that I was not being rewarded. I was being removed. She could not stand to be in the room with my success for one more minute, and the half-day was the most socially acceptable way she could find to make me disappear.

I took the half day. Of course I did. I was a fawner. I thanked her for it.

Scarcity, jealousy, and the math that wasn't real

What I understand now, that I didn't then, is that my boss was operating from a scarcity mindset so deep it shaped everything.

In her math, my success and her success were on a seesaw. If I went up, she went down. There was only so much room at the top, only so much credit to go around, only so much good available, and every bit of it I earned was a bit she lost. My win wasn't a win for her team or her department or her own leadership — it was a threat. A subtraction. A spotlight swinging away from her and onto me.

This is one of the saddest ways a person can move through the world, and it is everywhere in workplaces, and it does enormous damage. Because a leader with a scarcity mindset cannot let the people under them shine, since every bit of their shine reads as your dimming. They hoard credit. They withhold sponsorship. They feel personally diminished by their own team's excellence. They turn the thing that should be their greatest source of pride — the success of the people they developed — into their greatest source of threat.

And here's the bitter irony, the part that still gets me:

My success forced her success. When I got promoted, the structure required her to be promoted too — you can't have a director reporting to someone who isn't senior enough to manage a director. My rise literally lifted her. But she couldn't see it that way. She experienced her own promotion not as something she'd earned, and not even as a happy side effect of having developed a strong person, but as a kind of consolation prize handed to her because of me. A reward based on my merit, not hers. Which, in her scarcity math, wasn't a reward at all. It was another reminder.

She got promoted and felt smaller. I have genuinely never seen anything sadder in a professional setting.

The line that I think explains everything

There's one more piece, and it's the piece where my anger softens into something more complicated.

Our VP told her — to her face — that the best thing she ever did was hire me.

Ouch.

I want you to sit with how that must have felt for her. Imagine being a leader, with all your own ambitions and insecurities and your whole sense of yourself riding on being seen as good at your job, and having your own boss tell you that your single greatest accomplishment was hiring someone else. Not anything you built. Not anything you did. The best thing you ever did was recognize that someone else was good.

That is a devastating thing to hear. And while it confirmed everything I knew about my own value, it also — and I mean this honestly — it also broke my heart for her a little. Because I think that sentence probably landed on a wound that was already there long before I ever showed up. I think she'd spent her whole career afraid of exactly that, and then someone said it out loud.

It doesn't excuse how she treated me. The fire in her eyes was real, and so was the harm, and so was the slow erosion of being managed by someone who needed me small to feel okay. But it does let me hold her with some compassion now, from a safe distance, years later. Hurt people guard their territory like it's the last territory on earth. She was guarding. She'd probably been guarding her whole life.

What I'd tell myself, and maybe you

If I could go back, I wouldn't tell my younger self to confront her. That's not the lesson. The lesson is gentler and harder than that.

I'd tell her: you can be warm without doing her hair. You can be kind without being available at all hours for rides that aren't your job. You can be close to someone without dissolving your own edges into theirs. The closeness you're feeling when you fawn isn't actually closeness — it's a deal you're making with your own nervous system, and the price is yourself, and you don't have to keep paying it.

And I'd tell her this, which took me the longest to learn: her reaction to your success was never information about your success. When her eyes shot fire, that wasn't a sign you'd done something wrong. It was a sign you'd done something right, in front of someone who couldn't bear it. Don't let a jealous person's discomfort become your internal evidence that you should shine less. That's how the small stay small and make sure you join them.

I presented an amazing project that day. It was good. It was mine. I built it.

And the half-day she sent me home with? I think about it differently now. She meant it as a way to get me out of the room.

I think I'll keep it as a victory lap.

Let me tell you about Ben, who had a gift.

Not a good gift. A specific one. Ben had a near-supernatural ability to remember an urgent task at exactly four minutes and thirty seconds before any meeting he didn't want to attend. He would be sitting there, perfectly idle, and then — like a man receiving a message from beyond — he'd suddenly need to go do a thing. A very important thing. Right now. So sorry. We'll catch up soon.

The person on the other end of this weekly disappearing act was Ann. And Ann's slow-motion erosion is one of the most quietly devastating bad-boss patterns there is, precisely because it never looks like anything. No yelling. No write-ups. No villain monologue. Just a chronically empty chair where her manager was supposed to be.

Let's talk about it.

Ben hated one-on-ones (with one telling exception)

Ben did not like meeting with his team one-on-one. As a category, the activity repelled him. He found reasons to skip them, kept them short when he couldn't, and generally treated the foundational ritual of management — actually talking to the people you manage — as an imposition to be managed around.

With one exception. There was one person Ben always seemed to have time for. One person he prioritized, protected, kept close. And everyone noticed, because of course they did. Teams always notice who the boss has time for.

This is worth pausing on, because the favorite-and-the-frozen-out dynamic is its own special poison. When a leader lavishes access on one person and starves everyone else, they're not just neglecting the others — they're broadcasting a hierarchy of worth. The favorite gets information, context, air cover, and a relationship. Everyone else gets to watch. It breeds exactly the resentment and insecurity you'd expect, and it quietly tells your whole team that proximity to power is distributed by favoritism, not earned by contribution. That's a culture killer, and it starts at the top.

Ann never got a fair shot to begin with

Here's the part that makes Ann's story worse: she was set up shaky from day one.

Ann was a member of the senior leadership team — a manager, a real one, with real responsibility. And she was hired without a formal job description. Sit with how strange that is. A senior leader brought on with no written definition of what her job actually was. She understood her role at a high level — she knew she was a manager, knew her general domain — but the specific projects, the concrete goals, the actual expectations? Abstract. Foggy. Defined, if at all, in conversations she increasingly couldn't get.

When you hire someone without clarity about what success looks like, you have handed them an impossible assignment dressed up as a job. They cannot hit a target they can't see. And later — this is the trap — they can be judged for missing it. "Lack of clarity" is one of the most common and most deniable ways organizations set people up to fail, because the failure looks like the employee's fault when it was baked into the role before they ever started.

A quick, necessary word about office politics

Why was Ann kept in the fog? In her case, it likely wasn't personal incompetence on Ben's part — it was probably political. And we should be honest about how that works, because it's everywhere.

Sometimes a person is kept out of the loop on purpose, for reasons that have nothing to do with their performance. Maybe Ann's role overlapped with someone else's territory and keeping her vague kept the peace. Maybe information was currency and Ben was hoarding it. Maybe there was a turf war upstream and Ann's clarity would have forced a decision someone didn't want to make. Maybe she'd been hired to satisfy some org-chart requirement without anyone actually wanting to cede her real scope.

Whatever the specific flavor, the result is the same: a capable person gets deliberately under-informed because her being fully empowered is inconvenient to someone's agenda. Office politics, at its worst, is the practice of sacrificing clarity, fairness, and good people on the altar of someone's positioning. And the person being sacrificed is usually the last to find out it's happening.

So Ann did the right thing

Now, here's what I love about Ann, and why this story is so maddening.

She didn't sulk. She didn't quietly disengage and coast. She did the proactive, mature, take-ownership thing that every management book would applaud: she scheduled a standing weekly meeting with her boss. Every Tuesday. A recurring slot, right there on the calendar, a structural solution to a relationship problem.

And Ben accepted it.

Victory, right? She'd fixed it. She'd advocated for herself, created the container for the clarity she needed, and gotten her boss to agree to it in writing on the shared calendar. This is exactly what you're supposed to do.

And then Ben ran. Every. Single. Week.

Every Tuesday, like clockwork, about five minutes before the meeting, Ben would remember something urgent. Something pressing. Something that simply could not wait and that required him to be anywhere other than in a room with Ann. He'd pop up, deliver his apologetic little "ah, something's come up," and vanish.

The meeting never happened. Not once. Week after week, the standing meeting stood — right there on the calendar, a recurring monument to a conversation that perpetually failed to occur.

And I want to be precise about how cruel this is, even though it never raised its voice. Ann had been told, implicitly, "the way to fix this is to take initiative." So she took initiative. And her initiative was met not with a flat "no" — which she could have pushed back on — but with a "yes" that was secretly a "no," delivered weekly, with a smile, in a way that gave her nothing to fight. You cannot escalate "my boss keeps having emergencies." You cannot file a grievance about a man who technically agreed to meet you and just never quite makes it. The avoidance was perfectly engineered to be undeniable and unaccountable at the same time.

That's the signature of a certain kind of bad boss: they never give you the clean "no" you could act on. They give you the soft, deniable, endlessly renewable "not right now" that slowly drives you insane.

What this actually does — to Ann and to the company

Let's name the damage, because it's real and it compounds.

To Ann: She felt increasingly distanced from the teams, from her purpose, from her objectives and expectations. That's not a vibe — that's a person being structurally severed from the information she needs to do her job and the relationship she needs to feel like she belongs. Over time, that isolation does what isolation always does: it breeds self-doubt. She starts wondering if it's her. If she's doing something wrong. If she's somehow not worth her boss's time, since clearly one person is. A confident senior leader slowly becomes an anxious, second-guessing one — not because she changed, but because she was starved of the basic inputs of belonging and direction.

To the company: This is the part executives don't track and absolutely should. A senior leader operating without clarity is an enormously expensive form of waste. Ann's talent — the talent they hired and are paying for — is being stranded. She can't align her work to priorities she doesn't know. She can't course-correct on feedback she never gets. She can't drive the outcomes they need because nobody will tell her what the outcomes are. Multiply that across the time she stays, and you've got a high-salaried person running at a fraction of her capacity, growing more disengaged by the week, almost certainly updating her résumé. The company is paying full price for a person it has quietly disabled.

And here's the kicker: when Ann eventually leaves, or underdelivers on goals she was never clearly given, the story will get written as Ann wasn't the right fit. Not Ben refused to manage her. The avoidant boss almost always escapes the blame, because his failure is made of absences, and absences don't show up in anyone's file.

The lesson, for bosses and for the Anns of the world

If you're a leader: the one-on-one is not optional, and it is not a favor you grant your favorites. It is the single most important recurring act of management you perform. Skipping it isn't a scheduling quirk — it's a dereliction of the core duty, which is to make sure the people you're responsible for know what they're doing, why, and that they matter. Avoidance is a decision. Standing someone up every Tuesday is a thing you are choosing, and your team experiences it as exactly what it is.

And if you're an Ann: first, you did nothing wrong. You did the right thing, and the right thing was sabotaged by someone above you, and that is genuinely not a failure you can self-improve your way out of. But here's the hard, freeing truth — when a boss makes himself this unavailable, this consistently, after you've done everything right, he is telling you something. Not with words, because words could be held against him, but with the empty chair. The empty chair is the message. Believe it. And start, quietly, making a plan that doesn't depend on him ever showing up — because the data strongly suggests he won't.

Ann deserved a boss who kept the Tuesday meeting.

Most people do. It's such a low bar. And it's astonishing, and a little heartbreaking, how many Bens manage to limbo right under it — five minutes early, every single week, on their way to somewhere that isn't you.

I want to talk about the moment they finally got what they wanted.

The moment your voice goes up. The moment the tears come at the worst possible time, in the worst possible meeting, in front of the worst possible people. The moment you walk out of a room because if you stay one more second you are going to say something you can't take back. The moment you finally — finally — react like a human being who has been treated badly for a very long time.

And then watch what happens next. Watch how fast the conversation shifts from what was done to you, to how you handled it. Watch how the room repositions you, in real time, from the person who was harmed to the person who is "a lot." Watch the emails that get sent after. Watch the "are you okay?" messages that aren't really asking. Watch your reputation get rewritten in a single afternoon.

Because that moment — the one you've been white-knuckling against for months — that moment is the gift you accidentally handed them. And they have been waiting for it.

What it actually took to get there

Nobody who hasn't lived it understands what it took to not break sooner.

You communicated your boundaries. Calmly. Professionally. In writing, even, because you'd already learned that verbal didn't count. You said what you needed. You explained why. You proposed solutions. You used the language from the leadership book everyone pretends to have read. You made it easy for them.

They moved the boundary anyway. Then they moved it again. Then they pretended the boundary had never been there in the first place.

You tried to remain the bigger person. You absorbed things you shouldn't have had to absorb. You let comments slide because making them an issue would have made you the issue. You translated your own real, legitimate feelings into corporate-safe language — "I'm a little frustrated" when you meant "I am furious." "I'd appreciate clarity" when you meant "you are gaslighting me." "I want to make sure we're aligned" when you meant "please stop lying to my face."

Your feelings were dismissed. Not even argued with — dismissed. Waved off. Reframed as you being "sensitive." Or "in your head about it." Or "taking it personally" — as if the thing happening to you personally could be taken any other way.

Your needs were belittled. The accommodation you asked for was treated like an imposition. The support you requested became evidence that you weren't cut out for it. The thing you flagged as not okay was treated as a preference, like you were being picky about the temperature in the room instead of telling them the building was on fire.

And through all of it, you held. You held and you held and you held, because you knew — you knew — that the second you didn't, the entire story would become about your not-holding.

And then it happens

And then one day it happens.

It's almost never the big thing that does it. That's the cruel joke. It's usually something small, something almost laughably minor, layered on top of months of larger things. A passive-aggressive email. A meeting that gets moved without telling you. A coworker repeating your idea back to you like you've never heard it. A "just checking in" Slack that you know is a check-up. A tone. A look. A nothing that would have been a nothing on any other day.

But it's not any other day. It's day six hundred of being treated like this, and your body has been keeping the score, and the score has finally come due.

Your voice goes up. Or it shakes. Or both.

The tears come and you can't stop them and you hate yourself for crying because you know — even in the middle of it, you know — that this is the moment they're going to use. You can already see them filing it away. You can already feel the room recalibrating around you.

Or you stand up. Or you walk out. Or you say the thing you have spent months not saying, and it comes out louder than you meant, or sharper than you meant, or in front of someone who wasn't supposed to hear it.

You leave the room in a visible state of distress.

And in the silence right after, you can hear the story being rewritten in real time.

What that moment actually was

I want to name what was happening in your body in that moment, because nobody at work is going to name it for you. They have a vested interest in not naming it.

That was not you losing it.

That was a nervous system that has been in a state of low-grade emergency for months finally hitting the wall it could not climb anymore. That was your body — which has been clenching its jaw at night, knotting its stomach on Sunday, holding its shoulders up by its ears for so long you forgot they could come down — telling you it could not keep this up. That was a chronic absence of safety producing the response that chronic absence of safety produces, in every mammal on earth, every single time.

That was an appropriate reaction to abuse.

I'm going to say that again because it's the sentence I needed someone to say to me and nobody did.

That was an appropriate reaction to abuse.

You did not overreact. You under-reacted for months and your body finally refused to under-react anymore. There is a difference, and that difference is the whole story.

The trap they set, that you were never going to fully avoid

Here's what I've come to understand about that breaking point, and why it's so devastating.

The system was designed to produce it.

Think about it. Every part of what was done to you — the dismissal, the belittling, the boundary violations, the gaslighting, the isolation, the standard-of-one-applied-only-to-you — every part of that produces stress in the human body. Predictably. Mechanically. Like running an engine without oil. The system that treated you that way knew, on some level, that eventually the engine would seize.

And then, when it seized, they got to point at the seized engine as the problem. "See? She's unstable. See? He can't handle feedback. See? They're not a culture fit. Look at how they reacted."

The reaction was the goal. Not the only goal, but a useful one. Because a reaction is something they can put in a file. A reaction is something they can build a case around. A reaction lets them stop being the people who mistreated you and start being the people who "had concerns" about you. The reaction launders everything that came before it.

That is why it felt like a trap. Because it was one.

I don't say this to make you feel worse about not avoiding it. I say it so you can stop replaying it on a loop and asking yourself why you couldn't have just held on a little longer, said it a little softer, kept it together one more day. Because the answer to that question is: you could have. And then it would have happened the next day, or the day after, or the day after that. The trap was set in a hallway you couldn't see, and you were always going to walk down it eventually, because the only alternative was not being human.

You were going to react. They were going to use it. That was the design.

What this does to the version of you that remembers it

The breaking-point memory is one of the worst ones. I'll be honest about that.

Even now, years can pass, and your brain will hand you a 2 AM gift of that moment — your voice cracking in that meeting, or the look on that coworker's face when you finally said it, or the walk back to your desk afterward, or the bathroom you cried in, or the email you sent later trying to apologize for something that didn't need apologizing for.

Your brain keeps replaying it because some part of you still believes that if you can just figure out the right thing you should have said instead, you can fix what happened next. You can't. There was no right thing to say. There was no version of you, calm enough and articulate enough, that was going to be received as anything other than the problem, because the determination that you were the problem had already been made, and your reaction was just the convenient hook to hang it on.

The replay is not you problem-solving. The replay is you being haunted.

And I'm sorry. I really am. Because I know what it costs to carry that memory. I know how it makes you flinch the next time you feel any strong emotion at work, because your body has learned that feeling things in a professional setting is dangerous. I know how it makes you over-correct in your next job, going so flat and so controlled that you start to feel like you're not even there. I know how it makes you mistrust your own reactions for years afterward — wondering, every time something upsets you, whether you're "overreacting again," whether you're "being too much again," whether the thing you're feeling is real or whether you're broken.

You're not broken. You were broken into. There's a difference, and it matters.

What I want to say to anyone reading this who is still inside it

If you're still in the job and you haven't broken yet: I'm not going to tell you to hold on longer. I'm going to tell you that the breaking point isn't a moral failure. It's a physiological event. If it's coming, it's coming. Try to make sure that when it comes, you are somewhere that you can be received gently — by yourself, if no one else.

If you broke recently and you're spiraling about it: the spiral is not the truth. The spiral is the aftershock. Your nervous system is doing housekeeping on months or years of stored stress, and it's ugly, and it's exhausting, and it ends. Slower than you want it to. But it ends.

If you broke a long time ago and you're still carrying it: I see you. The shame about that moment is the last piece of the original injury that's still doing damage, and it doesn't belong to you. It was never yours. It was theirs, and they handed it to you to carry because they couldn't bear to hold it themselves.

You can put it down. Not all at once. But you can put it down.

The reframe I had to fight for, and am still fighting for

For a long time, I believed the story they wrote about that moment. I believed I had failed. I believed I had proven them right. I believed that if I had just been a little stronger, a little calmer, a little more graceful under pressure, none of what came after would have happened.

It took me longer than I want to admit to understand that I had it exactly backwards.

I didn't fail in that moment. I survived it. My body did what it was supposed to do — it told me, in the loudest language it had available, that the situation was no longer tolerable to a human nervous system. The signal worked. The signal worked perfectly. The problem wasn't the signal. The problem was that I was in a place where the signal was used as ammunition instead of received as information.

In a healthy environment, that moment would have been a flag. Someone would have noticed. Someone would have said, what's going on with you, and how can we help. Someone would have understood that a previously composed, high-performing person doesn't suddenly come apart for no reason, and gone looking for the reason.

In the place I was, the moment was a verdict. And the verdict was decided before I ever raised my voice.

So I want to say this clearly, for me and for anyone else who needs to hear it:

You did not lose it. You located it. You located the exact point at which what was being done to you became more than a person could carry in silence. That point exists in every human being. Finding it does not make you weak. It makes you a mammal with a working nervous system.

The shame doesn't belong to the person who finally cried in the meeting. The shame belongs to the people who built a meeting where crying was the only honest response left.

I heard this one secondhand, from someone who lived through it, and it has stuck with me ever since — partly because it's so theatrical, and partly because underneath the theater is one of the most common and most cowardly moves in all of management.

There was a manager. Healthcare setting. And his signature move went like this: he would summon an entire department into his office. Ten or so people, packed in. And then, in front of all of them, he would point to one — the person who'd made some mistake — and have them sit down in the chair across from his desk. And there, with their peers watching, he would "re-educate" them.

Re-educate. Sit with that word for a second. It's such a tell. It's the word you reach for when you want to dress up a public shaming in the language of development. He wasn't correcting an error. He was holding a trial, and requiring the rest of the department to serve as the gallery.

Let's talk about why this is so much worse than it might first appear.

"But it's healthcare — the stakes are life and death"

Let me address the strongest defense of this manager right up front, because in a healthcare setting it's a real one and it deserves a real answer.

Yes. In healthcare, mistakes can genuinely be life or death. A medication error, a missed step, a lapse in a protocol — these aren't abstractions. They can hurt or kill a patient. So when a leader in that environment feels a fierce urgency about getting things right, that urgency is legitimate. Nobody should pretend the stakes aren't enormous. A manager who is casual about errors in that setting would be the bad guy in a different post.

But here's the thing, and it's the whole hinge of this piece: the urgency of the stakes does not require a public execution. You can convey "this matters, this is serious, this can never happen again" with total force, total gravity, total clarity — in a one-on-one conversation. The seriousness travels just as well, arguably better, when it's delivered directly to the person, eye to eye, without an audience. The high stakes justify the intensity of the correction. They do not justify the venue.

In fact, the public version actively undermines patient safety, and I'll come back to why. But first, let's name what's really going on.

Why managers actually do this (hint: it's not for the team's benefit)

A manager who corrects one person in front of ten is almost never doing it for the educational value. The official story — "everyone can learn from this mistake" — is a fig leaf. If the goal were genuinely to teach the department a lesson, you could do that with an anonymized example, a protocol review, a training, a message that doesn't require a named human being to sit in a chair and absorb humiliation while their colleagues study their shoes.

So why do it the cruel way? Two reasons, and neither is flattering.

First: it's easier. This is the ugly little secret at the center of it. A direct, private, one-on-one conversation about a mistake is hard. It's confrontational in the most personal way. You have to sit across from one human being, look them in the eye, deliver difficult feedback, and then stay in the room for their reaction — the defensiveness, the hurt, the excuses, the tears, whatever comes. That takes skill, and nerve, and emotional steadiness. Doing it publicly is a way of diffusing all that. The presence of an audience changes the dynamic; the person being corrected can't react honestly with ten peers watching, so they just absorb it and stay quiet. The manager gets to deliver the hard message without having to handle a real human response to it. Public correction is what cowardice looks like when it's wearing a manager's badge.

Second: it's a power display. Making someone sit in the chair in front of their peers isn't about the mistake. It's about establishing, for the whole room, who's in charge and what happens to you if you slip. It's governing by fear. The lesson the department actually takes away isn't "don't make that error" — it's "don't get caught, don't stand out, and for God's sake don't end up in the chair." That's a very different lesson, and it's a poisonous one.

Only inexperienced or lazy leaders broadcast a criticism to the group instead of speaking directly to the one person who needs to hear it. The experienced, healthy-minded ones learned a long time ago that the hard private conversation is the actual job — not a thing to be avoided, but the work itself.

What it does to the person in the chair

Let's not lose the human being at the center of this.

Being publicly corrected by your manager in front of your entire team is a profoundly shaming experience, and shame is one of the most corrosive things you can do to a person's relationship with their work. It's not the same as guilt. Guilt says "I made a mistake." Shame says "I am a mistake," and it sears in deep. The person in that chair doesn't walk away thinking clearly about how to improve their technique. They walk away flooded — heart pounding, face hot, replaying it, certain that every colleague who watched now thinks less of them.

And here's the part that matters for the work itself: shamed people don't perform better. They perform worse. They get anxious, they second-guess, they freeze up, they hide errors instead of surfacing them. Which, in healthcare, is the literal opposite of what you want. You want a culture where someone who realizes they made a medication error runs toward the conversation — reports it immediately, openly, so it can be caught and fixed before a patient is harmed. A manager who holds public trials guarantees the reverse. He trains his entire department to conceal mistakes, because everyone has seen what happens when yours becomes known. He thinks he's promoting safety. He's manufacturing exactly the silence that gets patients hurt.

What it does to everyone watching

The damage doesn't stop with the person in the chair. The other nine people in that office are absorbing something too.

They're learning that their workplace is not safe. They're learning that any one of them could be next, that a mistake here doesn't get a private conversation and a path forward — it gets a public reckoning. So they brace. They go quiet. They stop taking the small, smart risks that good work requires. They stop volunteering, stop flagging problems, stop raising their hands. The whole department contracts into a defensive crouch.

And it breeds something even uglier: a low hum of hostility and mistrust. When a manager governs through public humiliation, the team can't fully trust him — and they start to struggle to trust each other, because everyone witnessed everyone else's worst moment, and everyone knows their own is on file in the group memory. It corrodes the collegiality that high-functioning teams run on. People who should be allies become wary co-survivors of the same bad boss. That's the hostility he fostered — not loud, not dramatic, just a permanent background tension that makes the whole place worse to be in.

What a strong manager does instead

None of this is hard to fix in principle. It just requires the one thing the public-shamer is avoiding: the courage to have a direct conversation.

A healthy-minded manager who learns of a mistake — even a serious, scary, patient-safety mistake — pulls that person aside. Privately. Closes the door. And has the real conversation: here's what happened, here's why it's serious, here's the impact it could have had, here's what needs to change, and here's how I'm going to help you make sure it doesn't happen again. They can be every bit as grave, every bit as urgent, every bit as clear about the stakes as the public version — more so, actually, because the person can actually hear them instead of just surviving the humiliation. And then, separately, if there's a genuine lesson the whole team needs, you teach it without a sacrificial human attached: "We had a near-miss this week, here's the protocol reminder for everyone."

Private correction. Public teaching. The person keeps their dignity, the lesson still lands, and the manager has done the harder, braver, more skilled thing. That's not soft. That's strong. The willingness to sit in a closed room and have the uncomfortable conversation directly is precisely what separates a real leader from someone who just enjoys the chair facing his desk.

The bottom line

The manager who held public trials probably thought he was being a tough, no-nonsense leader who took patient safety seriously. In reality he was taking the easy road and calling it rigor.

There is nothing tough about humiliating someone in front of their peers. It's the move you make when you don't have the spine for the harder, quieter, infinitely more effective conversation behind a closed door. It shames the one, frightens the many, buries the very mistakes it claims to prevent, and leaves a residue of hostility over the entire team.

"Re-education," he called it. The only person who needed re-educating was the man behind the desk.

I've written a lot of words across this series trying to diagnose bad bosses — their tells, their psychology, their costumes. But if you made me boil the whole thing down to a single, instant diagnostic, I'd give you this one.

Tell a leader something they did that didn't land well, and watch what happens in the first two seconds.

The good ones wince. The bad ones bristle. That's the whole test.

What the wince actually means

The wince is the physical sign of a person taking in uncomfortable information about themselves without immediately defending against it. It's the micro-expression of someone whose first instinct, when told "that hurt" or "that didn't work" or "that came across badly," is to consider whether it's true before deciding how to feel about it.

The bristle is the opposite. It's the instant armor-up. The "well, actually." The reframe that makes the feedback the problem instead of the behavior. The subtle shift of the conversation from "what I did" to "how unfair it is that you'd say that." Bad leaders bristle because, to a defended ego, feedback isn't information — it's an attack to be repelled.

I've watched both reactions up close many times, and I have never once seen them lie. The wince and the bristle are involuntary. They tell you, faster than any reference check or personality test, whether you're dealing with someone capable of growth.

How leaders get this wrong

They defend first and think never. The bristle isn't just a bad look in the moment — it teaches everyone watching to stop bringing this person the truth. One good bristle can buy a manager years of silence, which feels like peace and is actually rot.

They confuse being challenged with being disrespected. A defended leader experiences "here's how that affected me" as insubordination rather than a gift. So they punish the messenger, and the message — and every future message — disappears.

They think admitting fault is weakness. It's the reverse. The leader who can say "you're right, I got that wrong, thank you for telling me" reads as more secure, not less, because only a stable ego can afford to be wrong out loud.

How to avoid it (and pass the test)

Train the pause. When feedback arrives, the entire game is the half-second between hearing it and reacting. Build a habit: breathe, assume there's something true in it, get curious before you get defensive. The wince can be learned even if it isn't your instinct.

Say the magic sentence. "Tell me more about that." It does two things at once — it buys you a moment to manage your own reaction, and it signals to the other person that the channel is open, that truth is safe here.

Reward the messenger, visibly. The person brave enough to tell you a hard thing should walk away glad they did. Thank them. Act on it where you can. That's how you keep the data flowing instead of strangling it.

If some of the bad-boss stories in this series made you wince — quietly wondering "wait, have I done that?" — I have genuinely good news. That wince is the single most encouraging thing about you as a leader. The bosses in those stories never felt it. The fact that you did means you're already on the other side of the line that matters most. Now go do something with it.

The inclusion conversation took a beating in 2025. Driven largely by political pressure in the United States, a lot of companies abruptly scaled back their diversity and inclusion efforts — or quietly stopped talking about them. The forecasts for 2026 suggest inclusion may reclaim ground as organizations remember that diverse teams are simply good business. But we're in a whiplash moment, and whiplash moments are dangerous for a specific kind of employee.

I want to talk about what happens to the truth-tellers when the winds shift — because they're the ones who get hurt first, regardless of which direction the wind is blowing.

The person who speaks up is always the one at risk

Here's a pattern I've written about before: in a toxic workplace, the person who names the problem becomes the problem. They don't argue with truth-tellers; they exile them. That dynamic doesn't care about your politics. It operates identically whether the truth being told is "we have a real bias problem here" or "this new initiative isn't actually working."

What the current moment does is give cover. When a topic becomes politically charged, it becomes easy to reframe anyone raising it as the troublemaker — to treat a sincere observation about culture as a political act, and to manage out the observer while claiming you're just "avoiding controversy." The employee who would have been praised for candor two years ago is now a liability for the same words. Nothing about them changed. The wind did.

How leaders get this wrong

They punish the messenger to avoid the message. Whatever the issue, the cowardly move is to make the discomfort go away by removing the person who raised it, rather than engaging with what they raised.

They follow the wind instead of their values. The leaders failing this moment are the ones whose commitments turned out to be weather-dependent — loudly committed when it was rewarded, silently abandoning when it got costly. Employees notice, and they never fully trust that leader again, because they've learned the values were performative.

They use "we're staying neutral" as a shield for staying silent on real problems. There's a difference between not wading into national politics and refusing to hear an employee tell you something true about your own workplace. Bad leaders blur that line on purpose.

How to avoid it

Separate the person from the politics. When someone raises a concern about how people are treated at your company, evaluate the substance, not whether the topic is currently fashionable. The question is "are they right?" — not "is this a safe thing to be associated with right now?"

Make it safe to tell you hard things, permanently. Psychological safety isn't a fair-weather policy. If people can only speak up when it's politically comfortable, you don't have a speak-up culture. You have a fair-weather one, and it'll fail you exactly when you need it.

Hold your actual values regardless of the wind. You don't have to be loud. You do have to be consistent. The leaders worth following are the ones whose treatment of people doesn't swing with the news cycle.

The truth-teller is the most valuable and most vulnerable person in any organization. They're the early warning system. When the culture starts punishing them — for any reason, under any political banner — that's the signal that the organization has chosen comfort over honesty. And organizations that choose comfort over honesty don't get to keep their best people, no matter which way the wind is blowing.

Let me start with a disclaimer I actually mean, because this topic gets ruined the second someone forgets it.

What follows is about patterns, not people. These are tendencies shaped by decades of socialization — the wildly different things boys and girls are rewarded and punished for from the time they can talk — not facts about biology, and absolutely not predictions about any individual you'll ever meet. There are self-effacing men and brashly self-promoting women, and they are not exceptions to be explained away. They're proof that we're talking about culture, not nature. The research is clear that men and women barely differ in actual leadership behavior; where they differ is in how they've been trained to express ego, and in how the world reacts to that expression. Hold all of that, and the rest of this is genuinely useful.

Because ego at work isn't a male problem or a female problem. It's a human problem that's been handed two different costumes. And both costumes, left unchecked, are dangerous to a company — just in opposite directions.

The male ego: built loud, rewarded for it

The classic male ego at work is agentic — outward-facing, dominance-oriented, built around status, recognition, and being seen as competent. This isn't an accident or a moral failing; it's the predictable output of a culture that, from boyhood, rewards males for assertiveness, self-promotion, competition, and projecting certainty, and quietly punishes them for visible doubt or need.

So here's how it tends to show up, and where it gets dangerous.

Overclaiming competence. The male-coded ego is comfortable asserting expertise it may not fully have, because confidence has always paid better than accuracy. Research consistently finds men self-promote more readily and rate their own performance higher than women do for identical work. In a leader, this curdles into the boss who can't say "I don't know," who bluffs through decisions, who mistakes the feeling of certainty for the fact of being right. Companies built on that kind of unearned confidence make confident, catastrophic mistakes.

Status as the scoreboard. When ego is wired to external recognition, the job quietly stops being about the work and starts being about the standing — the title, the corner office, the visible win, the credit. This is the manager who needs to be seen as the smartest in the room, who competes with his own team instead of developing it, who experiences a subordinate's brilliance as a threat to his ranking rather than a gift to the mission.

Confrontation and dominance. The male-coded ego tends to express threat outward — the raised voice, the territorial display, the public correction, the my-way-or-the-highway. It's the more visible form of bad ego, which is actually its one mercy: at least you can see it coming. It's loud, and loud is legible.

The danger to a company: a culture of overconfidence, suppressed dissent (who argues with the loud certain guy?), and decisions optimized for one person's status instead of the organization's health. People stop bringing problems forward because the ego in charge punishes anything that looks like a challenge.

The female ego: built quiet, rewarded for hiding itself

Here's where most takes on this topic chicken out, because it's uncomfortable to say. Women have egos too — every bit as capable of being self-serving, controlling, and destructive. The female-coded ego isn't smaller or nicer. It's camouflaged, because women are socialized from girlhood to express pride and ambition in ways that won't get them disliked. Studies are blunt about the trap: when women self-promote the way men do, they get penalized for it — rated as less likable, less hireable — for the identical behavior that earns men points. So the female ego learned to go underground.

And underground is, in some ways, the more dangerous place for an ego to live, because you can't see it operating. Here's how it tends to show up.

Ego routed through relationship instead of status. Where the male-coded ego competes openly for the top spot, the female-coded ego more often competes for closeness, alliance, and informal influence. It builds power through who's in and who's out, who has the inside track, who's been subtly frozen out. It's the manager whose dominance looks like warmth — the one who binds people with conditional intimacy, who plays favorites under the cover of mentorship, who runs the team through relationship rather than authority. It's harder to name because it never raises its voice.

Aggression that goes sideways, not forward. When a culture punishes women for direct confrontation, the ego doesn't disappear — it finds indirect routes. The undermining comment dressed as concern. The exclusion that's never quite provable. The reputation quietly managed through implication rather than accusation. (Remember the jealous boss who couldn't bear her subordinate's success and sent her home with a "reward"? That's this, exactly — ego expressing itself through relational control rather than open dominance.) It's not that women are more "catty," which is a lazy and sexist frame; it's that a person denied the front door to power will use the side door, and the side door is relational.

Self-effacement as its own kind of ego. This is the subtlest one. The female-coded ego can hide inside visible humility — the leader whose modesty is performed, whose self-deprecation fishes for reassurance, whose martyrdom ("I'll just do it all myself, it's fine") is a controlling move wearing the mask of selflessness. Suffering can be a bid for status too. An ego doesn't have to brag to be running the room.

The danger to a company: it's the invisibility that makes it lethal. A relational, indirect, camouflaged ego poisons culture in ways that don't show up in any incident report. Cliques form. Information flows by favoritism. Good people get quietly frozen out by a manager everyone describes as "so nice." Because nobody can point to a loud, obvious offense, the damage compounds for years before anyone names it — if they ever do.

The symmetry nobody likes to admit

Here's the analytical heart of it. Both egos are the same machine running in different costumes — the self, frightened of being ordinary, grasping for a way to feel significant and safe. Socialization just hands each one a different strategy:

The male-coded strategy is visible dominance: I will be significant by being the biggest, the most certain, the most recognized.

The female-coded strategy is relational control: I will be significant by being the most connected, the most needed, the most central to who's in and who's out.

And — this is the part that should make everyone equally uncomfortable — each one is invisible to the people who share its costume. Male-dominated cultures don't notice the overconfidence, because it just looks like leadership. Female-dominated cultures don't notice the relational maneuvering, because it just looks like closeness. Each ego type is camouflaged precisely within the environment that shares its assumptions. The fish doesn't see the water.

Which means a company optimizing against only one kind has left the other kind completely unguarded. The bro-culture startup that congratulates itself on having no "drama" is usually blind to overconfident men driving it off a cliff. The relationship-first organization that prides itself on warmth is often riddled with quiet exclusion and favoritism it refuses to see. Both are ego problems. Both are expensive. Both go unnamed until the good people leave.

What this means if you actually lead people

A few honest takeaways, because diagnosis without use is just gossip.

Learn to recognize ego in the costume your culture rewards. This is the hard one. You're naturally tuned to spot the other type's ego and to excuse your own type's as normal. The man who finds the loud guy obviously toxic may be blind to the relational freeze-out happening on his own team. The woman who clocks the relational maneuvering instantly may wave off the overconfident bluffing as harmless. Train yourself to see the kind your environment has taught you to call "just how it is."

Stop rewarding the costume and start measuring the substance. Companies hand promotions to the loudest self-promoter (usually male-coded) and overlook the quiet high performer (often female-coded) — and the research is explicit that this means they're rewarding confidence rather than competence, and systematically misreading their own talent. Fix the inputs. Evaluate actual contribution, not who tells the best story about themselves.

Don't moralize one and excuse the other. The temptation, depending on your politics, is to treat one of these as real ego and the other as understandable. Resist it. The overconfident bully and the warm manipulator are doing the same damage to the same company by different routes. A clear-eyed leader is critical of both, including the one that looks like them in the mirror.

The bottom line

Ego at work is not gendered in its existence — it's gendered in its expression. Men have been trained to wear it on the outside, where it's dangerous because it's domineering. Women have been trained to wear it on the inside, where it's dangerous because it's invisible. Neither is the safe one. Neither is the noble one.

The healthiest leaders, of any gender, are the ones who've done the actual work of dismantling the ego underneath the costume — who don't need to be the biggest or the most central, the most certain or the most needed. They're rare for the same reason in both cases: because it requires being secure enough to not need the workplace to tell you that you matter.

That security doesn't come in a male version and a female version. It's just maturity. And it's just as rare in everyone.

I want to write this down because for a long time I couldn't. For a long time I couldn't even call it what it was. I called it a hard year. A bad fit. A misunderstanding. A communication problem. I used every word except the right one, because the right one made it real, and real meant I had to look at what they did to me.

So here it is. This is what retaliation looks like. Not the version in the HR training video. The version that happens to you.

It starts the day you speak up

I'd love to tell you I knew exactly when it started. I didn't. Not until much later, when I sat down and lined up the dates and realized everything — everything — traced back to one conversation. One report. One moment where I said the quiet thing out loud because I genuinely believed that's what you were supposed to do.

That was the day my career at that company ended. I just didn't know it for another however many months.

The promotion that was always six months away

The first thing that goes is the future. Not in a dramatic way. Just — the conversations about your growth get a little vaguer. The promotion you were on track for becomes something we'll "revisit next cycle." Then next cycle becomes "let's see how this quarter goes." Then there's "feedback" you've never heard before from people who can't or won't name themselves. Then there's a new competency framework, and somehow you don't quite meet it, even though you exceed every part of your actual job.

You keep performing. You keep hitting the numbers. You keep thinking if you just do enough, the math will work again. It doesn't. The math was never going to work. The math was decided in a room you weren't in.

The productivity expectations that quietly become impossible

The targets shift. Not all at once — that would be too obvious. They shift in little ways. A deadline that used to be reasonable becomes a deadline you can only hit by working through the weekend. A scope that used to belong to three people becomes yours alone. A "stretch goal" gets quietly redefined as the baseline.

And when you say something, the answer is always some version of: well, this is what the role requires. This is the bar. We just need you to step up.

You start to wonder if you've gotten slower. You haven't. The track got longer and they didn't tell you.

The micromanagement that arrives after you report something

This one I felt in my body before I understood it in my head. Suddenly every email had to be cc'd. Every decision had to be checked. Every small judgment call I'd been making for years was now something I needed to "loop in" on. Calendar invites for things that used to be a hallway conversation. Documentation requirements that didn't exist for anyone else.

The message underneath was clear, even when nobody said it: we don't trust you anymore. Which was a lie, because the work hadn't changed. I hadn't changed. What changed was that I had become someone they wanted a paper trail on.

That's what micromanagement after a report actually is. It isn't oversight. It's evidence collection.

The gossip, the isolation, the hostility

This is the part I'm still working through. This is the part I'm not sure I'll ever fully be done with.

I started noticing that conversations stopped when I walked up. Not every time. Just enough to make me wonder, and then enough to make me sure. I'd hear about meetings I wasn't in where my name had come up. I'd get a forwarded message from someone kind enough to tell me what was being said. People I used to be close with became polite in a way that meant they'd been told something. Or they'd heard something. Or they'd decided it was safer not to be associated with me.

I want to describe what that does to a person, because I don't think people who haven't been through it really understand.

You stop sleeping. Not in the cute "I had a rough night" way. In the way where 3 AM becomes a place you live, where your brain runs the same five conversations on a loop, where you draft emails in your head that you'll never send, where you rehearse defenses against accusations nobody has actually made to your face. You wake up tired in a way that coffee doesn't touch.

Your body learns the building. You'll notice that your shoulders start to climb toward your ears about three blocks out. Your stomach knots up Sunday afternoon and stays knotted until Friday evening, and even Friday isn't really free anymore because Monday is coming. You get headaches that aren't from anything. You get sick more. You lose your appetite, or you find it in the wrong places. Your jaw hurts from clenching it in your sleep.

You start crying in places you didn't used to cry. The car. The bathroom at work. The grocery store, weirdly, the grocery store does it to a lot of us, I've learned. Something about the fluorescent lights and the not having to be on.

And the loneliest part — the part I think breaks people more than anything else — is that you can't always tell who's safe anymore. You learn to scan a room differently. You learn that a friendly face doesn't necessarily mean a friend. You learn that people you trusted will choose their own safety over telling you the truth, and you can't even fully blame them for it, because you've watched what happens to the people who don't.

The different standard

Everyone else can be five minutes late. You cannot. Everyone else can miss a deadline. You cannot. Everyone else's typo is a typo. Yours is a pattern. Everyone else's pushback is healthy debate. Yours is "tone." Everyone else's question is curiosity. Yours is insubordination.

You start checking your work three times. Four times. You start screenshotting your own sent emails. You start saving every Slack message. You're building a case you hope you'll never need, for a trial that isn't going to be fair anyway.

And the cruel part is, the more careful you get, the more it looks like guilt.

The meetings you used to be in

I noticed it slowly. A recurring meeting I'd been part of for over a year — I just stopped getting the invite for the next quarter. Nobody said anything. When I asked, it was "oh, we're trying to keep that one smaller now." Except it wasn't smaller. It was the same size. There was just someone else in my seat.

Then it was the strategy session I would've been pulled into automatically six months earlier. Then the client call. Then the planning offsite. Each one with a reasonable-sounding explanation. Each one, individually, something you could talk yourself out of being upset about.

But collectively? Collectively it was a map of my erasure. Someone had drawn a line around me and was slowly, deliberately, moving rooms to the other side of it.

The training that went to everyone but me

This one — I'll be honest, this one still makes my hands shake a little when I think about it.

Watching colleagues get sent to the thing I'd asked about. Watching budget that supposedly didn't exist materialize for someone else. Watching opportunities I would've been the obvious choice for go to people who hadn't even thought to want them. And being told, when I asked, that maybe next time. That it wasn't in the cards this year. That we needed to "focus on the fundamentals" — for me, apparently. Just for me.

You start to understand that you are being starved. Not fired. Starved. Of growth, of access, of the inputs you need to do the job well, of the visibility you need to be considered for what comes next. And then, eventually, you'll be evaluated on the very things they made sure you couldn't develop.

That's the whole machine, right there. They don't have to fail you. They just have to stop feeding you and then act surprised when you're hungry.

What this does to the person you used to be

Here's what I want anyone reading this to understand, especially if you're in it right now.

This is trauma. I don't use that word lightly. I used to be the person who rolled her eyes at that word being used for workplace stuff. I'm not that person anymore, because I lived inside a body that had stopped feeling safe in its own life, and I know now what that costs.

It costs your sleep. It costs your health. It costs the patience you used to have with the people you love, because you came home empty and there was nothing left to give them. It costs the hobbies you stopped doing because you couldn't remember why you ever liked them. It costs the version of you who used to walk into a room sure of herself, because that version got smaller and smaller until you weren't sure where she went.

It costs your trust in yourself. That's the deepest theft. You used to know things. You used to be able to read a room, write an email, make a call, and not second-guess any of it. And then you spent however many months in an environment that punished your judgment, and your judgment learned to flinch.

Mine is still flinching. I'm being honest about that. I am sitting here writing this and I am better than I was, and I am also not all the way back, and I might not ever be all the way back to who I was before. Some of what they took, I don't get to have returned.

But some of it — some of it I am getting back, slowly, in pieces. I'm getting back the part of me that knows what she's looking at. The part that can name what happened without softening it for anyone's comfort. The part that can write a sentence like they retaliated against me without first apologizing for the word.

If you're in the middle of this right now, I want to tell you a few things I needed to hear:

You are not imagining it. The patterns you're noticing are real. Your body is telling you the truth even when the org chart is telling you a lie.

You did not become bad at your job. They stopped letting you be good at it.

The isolation is not a sign that something is wrong with you. It is a sign that something is very wrong with them, and the people around them are too scared to say so.

You will sleep again. Not tonight, maybe. But eventually.

And the version of you that you can't quite find right now — she's not gone. She is waiting on the other side of this. She's going to be a little different when you meet her again. A little more careful about who she gives herself to. A little harder to fool. But she's still in there, and she remembers who she was before they tried to rewrite her.

I'm writing this so she knows I haven't forgotten her either.

I want to tell you the truth about how PXHR started, because I think the truth is more useful than the polished origin story.

PXHR started as a "told you so."

Not the petty kind, exactly — though I won't pretend there wasn't some petty in there, because I'm a human being and so are you. But the deeper kind. The kind where you sit in your car after another bad day and you think: they are wrong about me, and one day I am going to build something so undeniable that even I will have to believe it.

I needed to prove them wrong. I also needed to prove me wrong — the version of me they had spent so long teaching me to be. The version that flinched. The version that second-guessed every email. The version that had started to wonder if maybe, just maybe, they were right about me after all.

So I built a company. Out of spite, partly. Out of grief, mostly. And out of something else, something I didn't have a name for at the time, that I now know was the beginning of coming back to myself.

The thing I knew, that they spent a long time trying to make me forget

I am very good at HR.

I'm going to let that sentence sit by itself on the page for a second, because writing it without flinching took me longer than I want to admit.

I am very good at HR. I have always been good at it. I was good at it on my worst day at the worst job with the worst boss, and I was good at it before any of them ever met me, and I will be good at it long after they are footnotes in my own story. The thing they tried to convince me wasn't true about me is the most true thing about me. I see people. I read systems. I know what culture actually is, as opposed to what people put on their careers page. I know the difference between a policy and a practice, and I know which one is killing your retention. I know how to walk into a broken room and figure out what's broken about it without making anyone feel like the broken thing.

That's a real skill. It took me years to be willing to say so out loud, because the environments I came out of had a vested interest in me believing it wasn't.

Part of what PXHR is, is me refusing to be quiet about that anymore.

What the company became, once I let it be more than a told-you-so

Here's what I didn't expect when I started.

I thought I was building a company. What I was actually doing was building a place where the version of me that got buried could come back to the surface and do the work she was always supposed to be doing.

Every client conversation has been a small reclamation. Every time I sit with a leader who actually wants to be better, I get a little more of myself back. Every time I help someone navigate a hard moment with their team — the moment where they could either default to the way it was done to them, or choose something different — I am, in a real and not-metaphorical way, healing. Mine. Theirs. The whole chain of it.

I didn't know that's what I was signing up for. I thought I was starting a business. I was actually starting a recovery that happened to have an LLC attached to it.

Both things are true. And the business is real, and the recovery is real, and they have turned out to be the same thing.

What I want to say to the bad bosses, because they need to be said to also

This is the part of the post I want to be careful with, because it would be easy to make it sound like I've forgiven everything. I haven't. Some of what was done to me I am still working through, and I am allowed to still be working through it, and so is anyone else who's still working through theirs.

But here's what's also true:

Most bad bosses had bad bosses. Most people who hurt other people at work were hurt themselves first — at work, at home, in childhood, in a marriage, in a body that has been carrying too much for too long. None of that excuses any of it. None of it. The harm is still harm. The impact is still the impact. The fact that you were taught to be the way you are does not unteach the damage you do.

But it does mean something else, something I think is actually hopeful: the cycle is breakable.

The reason bad bosses keep producing more bad bosses is that nobody ever sat them down and said, kindly and clearly, this is what you're doing, and this is what it costs the people around you, and there is another way to be. They learned management by watching the people who managed them, and the people who managed them learned the same way, and the chain goes all the way back to a workplace culture that was, frankly, designed to keep people small.

You can opt out of the chain. You can be the person who breaks it. I have met leaders who have done it — who came into a session knowing something was off in how they showed up, who did the uncomfortable work of looking at their own patterns, who let themselves be coachable, and who came out the other side a different kind of boss than the one who hurt them. It is possible. I have seen it with my own eyes. It is one of the most encouraging things I know.

What I want to say to the leaders who are trying

If you're reading this and you're a manager or a founder or a team lead and some of these posts have made you wince — like, oh no, have I done that? — I want to tell you something.

That wince is the beginning of being a better boss.

The bad bosses I have known did not wince. They got defensive. They explained why it was different in their case. They reframed the question. They made the conversation about how unfair it was that someone had brought the conversation to them in the first place.

If you winced, you are already not them.

The next part is the work. The work is asking your team what you actually do, instead of what you think you do. The work is learning to receive feedback without making the person giving it pay for the discomfort of having given it. The work is noticing when you are about to default to the way it was done to you, and choosing differently. The work is hard, and it is uncomfortable, and it is also genuinely doable, and the people I have watched do it have not regretted it.

I want to be in that work with you. That's why PXHR exists.

What I'm building, and who I'm building it for

PXHR is for the employees who have been through what I've been through, and who need someone in their corner who can speak the language of the people who hurt them and translate.

It's for the leaders who don't want to be the boss in the LinkedIn horror stories. Who want to learn what they didn't get taught. Who are willing to look honestly at their own patterns and ask whether they're serving the people around them or just repeating what was done to them.

It's for the companies that are tired of pretending culture is a slide deck. That are ready to actually look at why people keep leaving, why their best people keep quietly disengaging, why the engagement survey results don't match the all-hands energy.

It's for the version of me at twenty-two who got told she looked like a sexy librarian and didn't know she was allowed to not laugh.

It's for the version of me a few years ago who walked out of a room in tears and spent the next two years trying to prove she wasn't what they said she was, when the truth was she was never what they said she was in the first place.

It's for the version of you who might be reading this from inside something that's hurting you right now, and who needs to know there is a world outside of it where work doesn't have to feel like this.

The journey, and the invitation

Everyone can heal. I really believe that, and I didn't always.

Everyone can change for the better, including the people who hurt you, though that change is theirs to do and not yours to wait for. You do not owe anyone your patience while they figure out how to stop harming you. Healing on their end is on their timeline; yours is on yours; the two timelines do not have to touch.

But the broader truth — that human beings, even the ones who have done damage, are capable of becoming different — is the thing I have staked my whole second career on. Because if it isn't true, there's no point in any of this. And if it is true, then the work in front of us is enormous and meaningful and worth doing.

I'm not asking you to forgive anyone. I'm asking you to come with me into a way of thinking about work where harm is not the default, where leadership is not a synonym for fear, where being good at your job and being a whole human being are not in opposition to each other.

That's the company. That's also the healing. They have turned out to be the same thing.

If you've read this far, I want to say something I don't say often enough, because I'm still learning how:

Thank you. For reading. For trusting me with your time. For being someone — whether you've been the employee or the boss or, like most of us, some version of both — who is willing to look at this stuff honestly instead of looking away.

Let's go.

I've spent eleven posts now dissecting real bad bosses — the jealous ones, the cowardly ones, the ones who couldn't use their words, the ones who fired good people over half an hour of misread payroll. Heavy stuff. So today, let's have some fun and talk about the most beloved terrible manager in television history.

World's Best Boss. It said so right on his mug. He bought it himself.

Michael Scott, regional manager of the Scranton branch of Dunder Mifflin, is, on paper, an HR catastrophe of such magnitude that I get a little dizzy thinking about the liability. And yet. We love him. We'd follow him into Lake Scranton (more on that in a moment). Let's figure out why a man who did everything wrong somehow remains the boss a lot of us secretly wish we had.

First, though — the rap sheet. And reader, it is long.

An HR professional's nightmare blooper reel

Let me put on my actual professional hat for a second and just survey the damage, because if Michael Scott walked into my office as a real client, I would need to lie down.

He declared open war on HR. Toby Flenderson, the mild-mannered HR rep, exists in Michael's mind as a personal nemesis — "the worst." Michael's entire posture toward the one department designed to protect both him and his employees was contempt. In real life, the manager who treats HR as the enemy is the manager who ends up in HR's files. Michael never learned this. Michael never learned most things.

Diversity Day. Asked to sit through a sensitivity training, Michael decided he could do it better, dismissed the actual professional, and proceeded to run a workshop so spectacularly tone-deaf that it has become shorthand for getting it exactly wrong. It was episode two. Episode two. The show told us immediately who this man was.

He outed an employee. In a moment that's genuinely hard to watch, Michael outed Oscar to the entire office and then — trying to "fix" it — made everything catastrophically worse. It's the kind of thing that, in a real workplace, isn't a cringe moment. It's a lawsuit and a person's dignity, both wrecked at once.

He fake-fired Pam to look tough. Trying to impress a new hire, Michael told Pam she was being let go for "stealing Post-it notes." She cried. It was a prank. He thought it would demonstrate his authority. It demonstrated something, all right.

"Scott's Tots." The single most painful episode in the entire series, the one whole swaths of fans physically cannot rewatch. Years earlier, Michael promised a class of underprivileged kids he'd pay for their college tuition if they graduated. He could not, of course. So he shows up to tell a room of hopeful teenagers, who made him a song, that he's giving them... laptop batteries. The secondhand embarrassment could power a small city.

And he drove a car into a lake because his GPS told him to, screaming "the machine knows," while Dwight tried to stop him. Not a management failure exactly. Just a representative sample of the judgment on offer.

I could go on. The Dundies. The roast. The diary that got read aloud in a deposition. The man was a walking compliance seminar's worth of "do not do this."

Why he was actually a terrible manager (the real diagnosis)

Strip away the comedy and Michael's core management flaw is painfully recognizable, because it's one I've written about in real bosses: he needed to be loved more than he needed to be effective.

He said it himself — he wanted to be "a friend first, a boss second, and an entertainer third." That ranking is the whole problem in one sentence. A manager whose top priority is being liked cannot make the hard call, cannot deliver the tough feedback, cannot sit in the discomfort of someone being upset with him. So he bribes, he performs, he makes everything about the relationship, and he avoids the actual job of management — which is sometimes being the person who says the unpopular true thing.

Everything Michael did wrong flowed from that fountain. The attention-seeking. The inability to let anyone else have the spotlight. The need to turn every situation into a referendum on whether his people adored him. He managed his branch like a kid throwing a party and praying everyone would stay.

In any of my other posts, this would be the part where I tell you how much damage that does. And it's true — a real Michael Scott would burn out his team with chaos and make them parent their own boss.

And yet. Here's why we love him.

But here's the turn, and it's the reason this character endures while a thousand competent fictional managers are forgotten.

Michael Scott genuinely, deeply cared about his people. Not as a performance. For real.

When Pam — who he'd tormented, fake-fired, and embarrassed — finally worked up the courage to show her paintings at a local art show, and not one of her cool coworkers bothered to come, who showed up? Michael. He walked in, looked at her work, and bought her painting of the office building. He hung it on the wall. He was, in that moment, the only person who saw that it mattered to her and decided that made it matter to him. It's one of the most quietly moving moments in the series, and it comes from the same man who drove into a lake.

That's the magic of him. The caring and the catastrophe come from the exact same place — a heart so big and so unguarded that it constantly overrides his (limited) judgment. He'll embarrass you at your wedding and then give you a kidney. He'll plan a disastrous, inappropriate party and the party will be because he wanted you to feel celebrated. His worst moments and his best moments share a single root: he wanted, more than anything, for the people around him to be happy and to like him for making them so.

And underneath the buffoonery, he was weirdly, genuinely loyal. He fought corporate for his people. He remembered everyone's personal details. He cried at their milestones. When push truly came to shove, Michael Scott would walk through a wall for any one of the employees he spent all day annoying. The Scott's Tots promise was insane and irresponsible — but it came from a man who looked at a room of kids with nothing and desperately wanted to give them everything. The follow-through was a disaster. The impulse was pure.

The actual lesson, for those of us who do this for real

Here's what Michael Scott teaches you if you manage people in the real world, and I mean this sincerely after eleven posts of much darker material:

Caring is necessary but not sufficient. And not caring is fatal.

Michael had the half that can't be taught and lacked the half that can. He had the heart, and no skill. Most of the genuinely bad bosses I've written about — the jealous ones, the cowardly ones, the Richards — were the reverse: plenty of competence at protecting themselves, no real warmth for the people under them. And given the choice between those two halves, here's the uncomfortable truth: Michael's half is the rarer one.

You can teach a caring manager to give structured feedback. You can teach them to document, to be consistent, to make the hard call, to loop in HR. Skills are learnable. But you cannot teach a cold, self-protective manager to actually give a damn about their people. That has to already be in there, and in most of the bad bosses I've known, it simply wasn't.

That's why we love Michael and merely tolerate the competent jerks we've worked for. Because deep down we know which deficiency is fixable and which one isn't. We'd rather have the boss who cares too much and bumbles than the boss who's polished and hollow. At least the bumbler is on your side.

Michael Scott would be a nightmare to actually report to. I'd spend my whole day cleaning up after him. And I'd take him in a heartbeat over half the real managers in this blog series, because at the end of the day, when it counted, that ridiculous man showed up to the art show.

That's the World's Best Boss. The mug was wrong about why. But it wasn't entirely wrong.

My first real job out of college was at a TV station, affiliated with one of the major networks. It was my first taste of corporate America, and I walked in the way most twenty-two-year-olds do: eager, earnest, certain that if I just worked hard and was good and kind, the rest would take care of itself.

I had no idea I wasn't meeting expectations. None. Nobody had told me. There had been no quiet conversation, no "hey, let's check in," no "I'm noticing something and I want to talk about it before it becomes a thing." Nothing. As far as I knew, I was doing fine.

And then, one week before my wedding, I was called into a meeting and formally written up. For a bad attitude. For insubordination.

I was not fine. I just didn't know it yet.

The meeting

I want to describe the room, because the details of that room are burned into me in a way that fifteen years haven't touched.

It was my boss. And it was my peer. Not a supervisor. Not a leader. Not someone with any authority over me at all. A colleague at my own level, sitting in on my formal discipline, as though her presence there were normal, as though this were a thing that happens. To this day I don't fully understand the logic of it, except that I've come to suspect the write-up was substantially her idea, and my boss brought her along because my boss didn't know how to do it alone.

They slid the document across. A bad attitude. Insubordination. Formal. In writing. In my file.

I froze. Complete shock. The kind where your ears do that underwater thing and the voices keep going but you've stopped fully processing the words. I had walked in with no warning that anything was wrong, and I was walking out with a disciplinary record, and the distance between those two facts was so vast that my brain simply couldn't cross it in real time.

And under the table, where they couldn't see, I was pinching my own thigh as hard as I could.

The thing sensitive people do

I've since learned I'm not the only one who's done this. There's something a lot of us discover, usually young, usually alone, in a moment where we are determined not to fall apart in front of someone: that a sharp physical sensation can pull your attention away from an emotional pain that feels like it might swallow you. So you pinch. Or you dig a nail in. Or you press your tongue to the roof of your mouth. Some small private act of hold it together, hold it together, do not let them see.

I'm not telling you to do this. Looking back, what that pinch really was, was a body in distress doing the only thing it could think of to stay in the chair. It wasn't a strategy. It was a flare going up. The healthier thing — the thing nobody had taught me yet — would have been to recognize that my body was screaming and to honor that, instead of overriding it to stay professional for people who hadn't extended me the same care.

But I was twenty-two. And I had decided, with everything I had, that I was not going to cry in that room.

I made it. I was professional. I held my face still and my voice level and I got through it. And the second it was over, I excused myself to the restroom, locked the door, and sobbed in the way you sob when you've been holding it underwater for an hour. Big, ugly, silent-because-the-walls-are-thin crying. And then I fixed my face and went back to my desk, because that's what you do.

A week later I got married. I'd like to tell you I was fully present for it. The truth is part of me was still in that conference room.

The part that confused me most

Here's what made it so disorienting, and what took me years to put words to.

They were telling me true things, woven together with things that were not true.

There were real events in what they described — meetings that had happened, moments that had occurred, exchanges that were real. But they'd been bent. Reframed. Recalled with the angles all wrong, so that a thing I remembered as ordinary came back to me as evidence of a crime I didn't know I'd committed. It's a deeply destabilizing experience, being handed a version of your own behavior that contains just enough truth to be unarguable and just enough distortion to be unrecognizable.

You can't defend yourself, because half of it really happened. And you can't accept it, because the meaning they've assigned to it is alien to you. So you sit there, frozen, pinching your leg, trying to reconcile a story about a difficult, insubordinate person with the person you know yourself to be — and failing, because they don't match, and you don't yet have the framework to understand that they're not supposed to match, because the story was never really about you. It was about something happening between the people in the room that you weren't being told.

I stayed. (Yes. I know.)

And then — because this is apparently who I am — I stayed.

I stuck it out. That's a whole psychology of its own, and I won't pretend it isn't. There's a particular kind of person who responds to being told they're not good enough by deciding to stay and prove it isn't true, and reader, that is me, that has always been me, and I have learned to hold that part of myself with equal parts gratitude and concern. It's the same engine that built a company years later. It's also the engine that keeps people in rooms they should have walked out of.

But here's what happened when I stayed: about a year later, the peer left for a new role. And with her gone, something cleared. And I excelled.

I did the job I'd actually been hired to do, and I did it well. And — this is the part I love — that station is where I found HR. I started doing the hiring. The onboarding. The training. I built and grew a team. I became the creative team lead and grew my whole department. I even managed a group layoff and downsizing, reassigning teams, handling people's worst days with a care that — I realize now — was shaped partly by the memory of how uncarefully my own hard day had been handled.

The place that wrote me up for a bad attitude is the same place I discovered I was extraordinary at the work of caring for people in organizations. There's a symmetry there I didn't choose but have come to appreciate.

The conversation by the printer, or wherever it was

Years into all of this, after I'd more than proven what I could do, our general manager asked me something in passing. The kind of question someone asks when it's clearly been turning over in the back of their mind for a while and just surfaced.

He asked, basically: what happened, back then? He referenced how much my old peer had disliked me. Said it almost like he was finally letting me in on something.

I just shrugged.

But I took the opening. I'd earned it by then, and I asked him the question I'd been carrying for years: Why didn't anyone ask me? Why did you go straight to formal discipline? Why was my first piece of feedback a written warning with a peer in the room, instead of a conversation?

And he shrugged back. And he said — and I will never forget this, because it reframed the entire experience in one sentence —

"To be honest, I had no clue what to do."

What that one sentence taught me

I had spent years — years — carrying that write-up as a verdict on my character. A bad attitude. Insubordinate. I had let it live in me as a true thing I had to disprove. And the man near the top of that org casually told me that the whole thing happened not because I was bad, but because the people in charge didn't know how to manage a personality conflict and reached for the only tool they recognized: punishment.

They didn't write me up because I'd done something write-up-worthy. They wrote me up because someone disliked me and the leadership didn't have the skill, the courage, or the framework to handle that like adults. Formal discipline wasn't the considered response to a real performance problem. It was what you grab when you have no clue what to do and you need the discomfort to stop.

That's the thing about so much bad management. It isn't malice. It's incompetence wearing the costume of authority. A document slid across a table can end a person's sense of themselves for years, and the people sliding it can be doing it simply because they don't know any other move. The damage doesn't require intent. It just requires power without skill.

What I'd tell the twenty-two-year-old pinching her leg

I'd tell her to stop pinching. Gently. I'd put my hand over hers under that table and tell her she's allowed to feel exactly as blindsided as she feels, and that holding it in for the comfort of the people hurting her is not the same thing as strength.

I'd tell her the document is not a verdict. It's a confession — theirs, not hers. It's a piece of paper that says we didn't know how to handle a human situation, so we reached for a hammer.

I'd tell her that the confusing mix of true and untrue isn't her failing to understand. It's the actual signature of being scapegoated, and one day she'll be able to name it in two seconds flat, and she'll use that skill to protect other people from sitting where she's sitting now.

And I'd tell her the thing it would take her the longest to believe: that she's going to walk out of that restroom, fix her face, go back to her desk — and eventually become so good at the work of taking care of people that the place that wrote her up will be the place she found her calling.

Get married this weekend. Be as present as you can. The conference room doesn't get to come with you. It only gets to come with you if you let it, and one day, much later, you won't.

He had no clue what to do.

I, on the other hand, eventually figured it out. And I built a career making sure that the version of leadership that blindsided a twenty-two-year-old a week before her wedding gets named for exactly what it was — not strength, not standards, just people with power and no idea what to do with it.

I know what to do with it now.

Here's a scenario that plays out in workplaces constantly. An employee does brilliant work — spots the pattern nobody else caught, hyperfocuses through a problem for six straight hours, brings a kind of thinking the team genuinely needs. And that same employee gets dinged on their review for "poor eye contact," "needs to be more of a team player," "struggles with ambiguity," or "doesn't always pick up on social cues."

What's often happening there isn't a performance problem. It's a manager looking at a neurodivergent employee through a neurotypical lens and writing down everything that doesn't match — while completely missing the value standing right in front of them.

Let's talk about it, because this is one of the most common and most expensive blind spots in modern management.

First, the numbers — because this is not a niche

If you think you don't manage anyone neurodivergent, the odds say you're simply not aware of who they are.

Estimates put somewhere around 15% to 20% of the population as neurodivergent, and some sources put it higher. The diagnostic picture has shifted dramatically: autism diagnoses have increased by a remarkable 787% in the past two decades, and prescriptions for ADHD medication have surged by 800%. That rise isn't an epidemic of new conditions — it largely reflects better recognition, broader diagnostic criteria, and more adults finally getting language for how their brains have always worked.

The conversation is opening up, too. Nearly 2 in 3 employed adults (64%) agree that people talk more openly about their neurodivergence at work now than in the past, rising to about 3 in 4 among adults who identify as neurodivergent. And here's a stat that should make every executive look up: according to a 2025 Forbes report, 45% of C-level executives and 55% of business owners self-identify as neurodivergent. The wiring that gets a junior employee labeled "difficult" is, in many cases, the same wiring driving people at the very top.

But the opportunity is being squandered. Unemployment rates among neurodivergent people can reach as high as 40% — roughly eight times higher than for neurotypical individuals. An enormous pool of capable, talented people is locked out or pushed out, not because they can't do the work, but because workplaces were built to reward one narrow way of being.

What these employees can actually look like

Neurodivergence is a wide umbrella — it includes autism, ADHD, dyslexia, dyspraxia, dyscalculia, dysgraphia, Tourette syndrome, and more — so there's no single picture. But here are some of the things a manager might see, often without understanding what they're looking at:

The person who's brilliant on the deep-focus task and scattered on the administrative busywork. The one who's blunt and literal in a way that reads as "abrupt" but is actually just honest and efficient. The employee who struggles in the open-plan office with its constant noise and interruption, but produces extraordinary work in a quiet space. The one who needs instructions in writing, not rattled off verbally in a hallway. The person who doesn't make much eye contact, or who stims, or who processes a question for a beat longer before answering. The one who asks "why are we doing it this way?" — not to challenge authority, but because they genuinely need the logic to engage.

A bad boss sees this list and reads a problem employee. A good boss sees a different operating manual and asks how to work with it.

What they need (and it's mostly cheap)

Here's the part that should be liberating for managers: the accommodations that unlock neurodivergent performance are usually small, cheap, and — this is the secret — good for everybody.

Clear, written, specific expectations instead of vague verbal direction. Control over their sensory environment — noise-canceling headphones, a quieter desk, the option to work where they focus best. (Worth noting: hearing someone talking while reading or writing can reduce productivity by up to 66%, and open-plan noise harms everyone, not just the neurodivergent.) Flexibility in how and when work gets done, judged on output rather than optics. Feedback that's direct and concrete rather than hinted at. Advance notice instead of surprise. A meeting agenda sent ahead so processing can happen before, not on the spot.

None of that is exotic. Most of it is just good management that neurotypical employees quietly benefit from too.

How leaders get this wrong

They penalize the wiring instead of managing the work. The review full of "poor eye contact" and "doesn't read the room" is a manager grading someone on neurotypical social performance instead of on their actual contribution. It's like docking a brilliant writer for bad handwriting.

They force masking, then wonder about burnout. 77% of all adults agree that neurodivergent employees feel pressure to "mask" or conform to neurotypical behaviors at work, rising to 82% among neurodivergent individuals. Masking — suppressing your natural way of being to seem "normal" all day — is exhausting, and a workplace that demands it is paying for performance and getting performance-of-normalcy instead.

They make accommodations feel dangerous to ask for. 70% of adults agree there's stigma around asking for a workplace accommodation, up from 60% the year before. When asking for what you need feels like confessing a weakness, people don't ask — they struggle silently and underperform, and the manager never learns why.

They confuse "different" with "less." This is the root error. A manager who unconsciously believes there's one right way to communicate, focus, and behave will experience every deviation as a deficit, and will systematically undervalue people whose strengths don't come in the expected packaging.

How to avoid it — and treat these employees as the assets they are

Manage to strengths, not to a template. Creative insight, outside-the-box thinking, problem-solving, and visual-spatial ability are increasingly recognized as real strengths neurodivergent employees bring. Add to that pattern recognition, deep focus, honesty, and the willingness to question assumptions everyone else accepts. Figure out what someone is exceptional at and build their role toward it.

Make accommodation normal and easy. Offer flexibility and sensory options to everyone, so no one has to "out" themselves or beg for basics. When the default environment is humane, the stigma of asking evaporates.

Give clarity, always. Written expectations, concrete feedback, agendas in advance, logic for decisions. This costs nothing and helps your whole team.

Separate the work from the wrapping. Before you write "abrupt" or "doesn't fit the culture," ask: is this actually affecting their work, or is it just not how I would do it? The answer matters enormously, and getting it wrong drives out exactly the people who think differently enough to be valuable.

And know the business case is real. Companies with neurodivergent hiring programs see 48% higher retention among those employees, and 89% of companies adopting neuroinclusive practices report better morale and engagement. This isn't charity. It's a competitive advantage that most organizations are leaving on the table.

The bottom line

The neurodivergent employee who keeps getting labeled "difficult," "not a culture fit," or "hard to manage" is very often a high-value asset being assessed against the wrong rubric. The failure isn't theirs. It's a management culture that mistook conformity for competence and never learned the difference.

The best leaders don't ask neurodivergent people to become someone else in order to succeed. They build a place flexible enough that different kinds of minds can all do their best work — and then they reap the benefit of having thinking on their team that their competitors, still optimizing for sameness, will never get access to.

Difference isn't the problem to be managed. It's the advantage your company keeps accidentally firing.

Part 1 of 2. Read the companion piece: When the Neurodivergent One Is the Boss (story #31 on this page).

Last time I wrote about the neurodivergent employee — the one whose strengths keep getting mislabeled as "difficult." Now let's flip the org chart, because there's a version of this story that gets talked about far less: when the neurodivergent person is the one in charge.

And here's the twist that should reframe the whole conversation: neurodivergent leaders are not rare. According to a 2025 Forbes report, 45% of C-level executives and 55% of business owners self-identify as neurodivergent. The wiring we so often pathologize in junior employees is, at the top of organizations, doing a remarkable amount of the driving. Some of the most innovative leaders you've worked for were almost certainly neurodivergent — you just may not have known it, and neither, sometimes, did they.

This post is for two audiences: the neurodivergent leaders themselves, and — especially — the neurotypical people who report to them and want to do it well.

Why this is suddenly everyone's issue

The pipeline is changing fast. With a striking share of younger workers identifying as neurodivergent — by some counts over half of Gen Z — the old assumption that "leader" means "smooth, charismatic, socially effortless extrovert" is colliding with reality. Traditional leadership models, built and tested almost entirely in neurotypical settings, simply don't describe how a growing share of capable leaders actually operate.

And there's a real intellectual reckoning underneath this. Researchers now openly question whether classic leadership theories even apply universally — one study found that elements of "transformational leadership" that typically energize neurotypical employees actually increased anxiety in autistic ones. The point isn't that one style is right. It's that we've been treating one neurological default as "leadership itself," and that was always a mistake.

The unique strengths a neurodivergent leader brings

When the fit is right, these leaders bring things conventional leadership often lacks:

Systematic thinking — breaking messy, complex problems into structured, logical components. Pattern recognition — spotting the trend, the risk, or the connection everyone else missed. Intense focus — deep, sustained concentration on the priority that matters, when the environment is structured to allow it. Innovative approaches — solving problems from outside the conventional frame, because they were never fully inside it to begin with. And maybe most valuable: authentic, direct communication — honest feedback that, once you understand it, builds genuine clarity and trust because there's no hidden subtext to decode.

There's also a quieter gift. Leaders who know firsthand what it's like to think differently often have a deep appreciation for the different strengths others bring. Many neurodivergent leaders are unusually good at seeing and using the unique abilities of their people, precisely because they've spent a lifetime aware that minds don't all work the same way.

The unique challenges they face

Let me be honest about the hard parts, because pretending they don't exist helps no one.

Here's the uncomfortable truth the research names directly: a lot of management is social. Reading group dynamics, navigating organizational politics, managing unpredictable interpersonal currents, juggling a dozen half-defined priorities at once — the unstructured, ambiguous, people-reading parts of leadership can be genuinely taxing for someone whose strengths lie elsewhere. There's a common story: a brilliant individual contributor gets promoted on technical excellence, then struggles with the formless social swirl of management, and the organization quietly wonders if the promotion was a mistake — when what's actually missing is a little structure and support, not capability.

Other real challenges: the exhausting pressure to mask — to perform neurotypical leadership all day — which burns people out. Sensory and focus demands in back-to-back meetings and noisy open offices. Communication mismatches, where directness reads as blunt or a processing pause reads as disengagement. And the cruel double bind that the very traits driving their success can be the ones flagged in their performance reviews.

How this gets handled wrong — by organizations and by reports

Organizations promote for technical brilliance, then offer zero leadership accommodation. They'll happily accommodate a neurodivergent junior employee but assume a leader should have it all figured out — leaving capable managers to struggle silently against an environment that never flexed for them.

They judge leadership by style instead of results. If a manager isn't the charismatic, glad-handing archetype, they get read as "not leadership material," even when their team ships better work. That's evaluating the wrapping, not the outcome.

And reports misread difference as deficiency or disrespect. This is the one I most want neurotypical employees to hear. When your boss is blunt, you may read coldness that isn't there. When they don't do warm small talk, you may invent a disapproval that doesn't exist. When they want everything in writing, you may feel micromanaged when they're actually trying to communicate clearly. Most friction with a neurodivergent manager is a translation problem, not a character problem — and assuming the worst poisons a relationship that didn't need to go bad.

How to work well with a neurodivergent manager (a guide for neurotypical reports)

This is the practical heart of the post. If you report to a leader who's wired differently, here's how to make it work — and most of it just makes you a better employee, period.

Take direct communication as a gift, not an attack. If your manager is blunt, that bluntness is usually honesty without political padding, not hostility. You will always know where you stand. That's rarer and more valuable than the boss who's warm to your face and vague forever. Don't read tone that isn't there.

Say what you mean; don't make them decode it. If you need something, ask for it plainly. Hinting, hoping they'll "pick up on it," or burying the real issue under social cushioning is how misunderstandings start. Clear, specific, direct requests land best. (Honestly, they land best with every manager.)

Ask how they prefer to communicate, and adapt. Some want written updates, some want scheduled check-ins rather than drop-bys, some need an agenda before a meeting so they can process. Asking "how do you like to receive updates?" is a small act of respect that pays off enormously.

Don't take processing time as disengagement. A pause before a response often means they're thinking carefully, not tuning you out. Silence isn't rejection. Give the moment room.

Bring solutions and specifics. Many neurodivergent leaders thrive on concrete, well-structured input and find vague, open-ended emotional ambiguity draining. "Here's the issue, here are two options, here's what I'd recommend" is gold.

Extend the same grace you'd want. You'd want a manager who looked past your quirks to your contribution. Offer the same in reverse. The goal isn't to walk on eggshells — it's to stop assuming that "different from how I'd do it" means "wrong."

The bottom line

We've spent a long time defining "leader" so narrowly that we accidentally wrote off some of the most capable minds in the building — or promoted them and then set them up to struggle by changing nothing about a system built for someone else.

The future is pointing the other way. Homogeneous leadership teams lack the range to handle the full spread of modern challenges; diverse leadership — including the distinct ability patterns of neurodivergent people — is increasingly understood as essential to innovation, not a concession to it. The organizations that win will be the ones that broaden their definition of leadership and give all kinds of leaders the structure to thrive.

And if you're a neurotypical employee with a boss who thinks differently than you do? You're not being managed by a problem. You may be working for exactly the kind of mind your competitors wish they had — and learning to work with it well might be one of the more valuable skills you pick up in your whole career.

Part 2 of 2. Read the companion piece: The Neurodivergent Employee Your Company Keeps Mislabeling as Difficult (story #30 on this page).

Ask a hundred managers what they find hardest about leading people, and somewhere near the top of every list is the same thing: giving honest feedback. Not the easy praise — the real stuff. The "this isn't working," the "you're falling short here," the conversation you rehearse in the shower and dread all week.

I've delivered a lot of feedback in my career. I've also been on the receiving end of every bad reaction there is to it. So let me talk honestly about why this is so hard, what happens when it goes wrong, and the one reframe that changes everything.

Why managers think it's hard

Most of us were raised on a single rule: "If you don't have anything nice to say, don't say anything at all." That message gets ground into us in childhood, and then we walk into management — a job whose entire purpose sometimes requires saying the not-nice thing — and we freeze. The instinct to keep the peace is decades deep.

On top of that, feedback feels like conflict, and most people are conflict-avoidant by nature. We worry the person will be hurt. We worry they'll be angry. We worry they'll like us less — and a lot of managers, whether they admit it or not, badly want to be liked. We worry we'll say it wrong, or that we're wrong, or that it'll blow up. So we do the thing that feels safe in the moment and is poison over time: we say nothing, or we soften it into mush, or we wait for the annual review and dump it all at once.

Why it's actually hard (the part nobody warns you about)

Here's the thing they don't tell you: sometimes feedback is hard because of you, and sometimes it's hard because the person genuinely cannot handle it — and those are different problems.

I've had people walk out on me. Stand up mid-conversation and leave the room. I've watched feedback land and turn into malicious compliance — the employee who, stung, decides to do exactly and only what they were told, to the letter, in a way calculated to prove a point and watch things break. I've seen feedback curdle into a grudge that poisoned a whole team dynamic for months.

And I'll be honest about the effect that has on a manager: it creates fear. Once you've had a feedback conversation explode on you, you start bracing before the next one. You start avoiding. You start managing around the difficult person instead of through the issue, because the blowup cost you so much last time. That fear is real, and it's one of the quiet reasons so many teams run for years on feedback nobody's willing to give.

But here's what I learned from those blowups, and it's the heart of this whole post: **most of the time, it wasn't what I said. It was how I said it.**

It's not what you say. It's how you say it.

This is where Kim Scott's Radical Candor changed how I think about the whole thing.

Scott's framework is a simple two-by-two built on two questions: Do you care personally about the person, and do you challenge them directly? Cross those axes and you get four quadrants:

Radical Candor — high care, high challenge — is the goal. You say the honest, direct thing and you genuinely give a damn about the person you're saying it to. Scott describes it as feedback that's kind, clear, specific, and sincere. It's not brutal honesty. The difference is the care.

Obnoxious Aggression — high challenge, no care — is the blunt jerk who tells you the truth without a shred of warmth. The feedback may be accurate, but delivered without care, it just feels like an attack, so people defend instead of grow.

Ruinous Empathy — high care, no challenge — and Scott argues this is the most common management failure. It's the nice manager who cares so much about your short-term feelings that they won't tell you the hard thing you need to hear. It feels kind. It's actually a quiet betrayal, because it leaves you blind to the problem until it's too late to fix.

Manipulative Insincerity — no care, no challenge — the worst quadrant: dishonest and cold. Empty flattery, political silence, feedback shaped to serve the manager rather than the employee.

Here's why this reframe is so freeing. When my feedback blew up, I'd usually landed in the wrong quadrant. When someone walked out, I'd often been direct without making the care visible first — obnoxious aggression, even when I didn't feel aggressive. When feedback quietly accomplished nothing, I'd drifted into ruinous empathy, softening the truth until it disappeared. The content was rarely the problem. The combination was.

How leaders get this wrong

They confuse caring with not challenging. The ruinously empathetic manager thinks they're being kind. They're being unkind in slow motion, denying the person the information they need to grow.

They confuse challenging with being harsh. The obnoxiously aggressive manager thinks directness is the job and warmth is optional. So their feedback gets rejected even when it's right, because no one absorbs criticism from someone they don't believe cares about them.

They let one bad reaction scare them into silence forever. After a blowup, they retreat into not-saying-anything — which feels safe and guarantees the same problems recur, unspoken, until someone has to be managed out over issues they were never clearly told about.

How to do it well

Care first, and make the care visible. Before you challenge, the person has to know you're on their side. That's not a manipulation tactic — it's the foundation that lets honest feedback be heard as help instead of attack. Care personally, then challenge directly.

Be specific, kind, clear, and sincere. Vague feedback ("you need more ownership") is useless and a little cowardly. Specific feedback ("in Tuesday's meeting, when you committed to the deadline and then went quiet, the client lost confidence — here's what I'd do differently") is something a person can actually act on.

Do it early and often, in small doses. Feedback saved up for the annual review arrives as an avalanche. Feedback given in the moment, kindly, as a normal part of working together, never has to become a Big Scary Conversation in the first place.

Don't manage your fear by avoiding — manage it by getting better at delivery. The walkouts and the malicious compliance taught me to improve my how, not to stop. The answer to a feedback conversation gone wrong is rarely silence. It's care made visible next time.

Accept that some reactions aren't yours to control. Even perfect radical candor will occasionally meet someone who can't yet hear it. You're responsible for delivering feedback with care and clarity. You're not responsible for managing another adult's entire emotional response to the truth. Do your part well, and let go of the part that was never yours.

The bottom line

Giving feedback is hard because we were taught silence is kindness, because we fear conflict, and because we've been burned. But the burns usually came from landing in the wrong quadrant — too cold, or too soft — not from the honesty itself.

The fix isn't to stop being honest. It's to never be honest without being kind, and never be kind without being honest. Care personally. Challenge directly. Do both at once, and feedback stops being the scariest part of your job and becomes the most valuable thing you do for the people you lead.

In Part 2: the other side of the table — why receiving feedback is just as hard, why silence from your team is a warning and not a compliment, and how to actually give your own boss feedback without torching your career.

Part 1 of 2. Read the companion piece: The Feedback You're Not Getting Is the Feedback That Should Scare You (story #33 on this page).

In Part 1, I wrote about how hard it is to give feedback, and how Kim Scott's Radical Candor — care personally while challenging directly — fixes most of what goes wrong. But there's a second half to this that managers love to skip, because it's even less comfortable.

You also have to receive it. From the people who report to you. And you have to actually want it — which is a much higher bar than most leaders realize.

Why receiving feedback is so hard

Giving feedback makes you feel exposed. Receiving it makes you feel attacked — even when it's gentle, even when it's right, especially when it's right.

There's an instinct that fires the second someone says "can I give you some feedback?": the stomach drops, the defenses come up, the brain starts building the rebuttal before the sentence is even finished. It's deeply human. Nobody enjoys hearing they fell short. And for managers specifically, there's an extra sting — a quiet belief that being the boss means being the one who gives the feedback, not the one who takes it. Accepting criticism from someone "below" you on the org chart can feel, to an insecure ego, like a threat to your authority.

That instinct is exactly the thing you have to overcome, because it leads to the single most misread signal in all of management.

The silence trap: why "no feedback" is not a good sign

Here's the thing I most want managers to internalize:

When your team gives you no critical feedback, that is not evidence that you're a great manager. It's evidence that you're not someone your team feels safe being honest with.

Read that again, because it's counterintuitive and it matters enormously. The quiet, agreeable, no-one-ever-pushes-back team feels like a sign you're doing great. It's usually the opposite. People always have feedback for their boss — always. If none of it is reaching you, the feedback didn't cease to exist. It just went somewhere else: into private Slack channels, into venting at home, into their decision to quietly start job hunting. The absence of feedback isn't peace. It's a communication breakdown you've mistaken for success.

I've seen managers genuinely believe they were beloved because no one complained — right up until their best people left and the exit interviews revealed a mountain of concerns nobody ever felt safe raising. The silence was the warning. They just heard it as applause.

How leaders get this wrong

They take silence as a compliment. The most dangerous managers are often the ones convinced they're doing great because nobody's told them otherwise. Comfort with your own performance, in the absence of real input, is just a blind spot wearing a smile.

They punish the first person brave enough to speak. Someone finally works up the courage to tell you something hard, and you get defensive, argue, or — worst — hold it against them later. Congratulations: you just taught your entire team that honesty is dangerous, and the channel closes for good.

They ask for feedback without making it safe. "My door is always open!" means nothing if people have learned that walking through it costs them. Solicited feedback only works if the person believes there's zero penalty for being honest.

How to actually want — and get — feedback

Ask specifically, not generally. "Any feedback for me?" gets you "nope, all good." Specific questions get real answers: "What's one thing I could do differently in our meetings?" "Where am I making your job harder than it needs to be?" "What's something I do that you wish I'd stop?" Narrow the question and you make it answerable.

Reward the messenger, every single time. When someone gives you hard feedback, your only job in that moment is to make them glad they did. Thank them. Sincerely. Sit with it instead of defending. The "wince and walk toward it" reflex — getting curious about the thing that stings instead of fighting it — is the whole skill. One defensive reaction can undo a year of "my door is open."

Act on something, visibly. Nothing proves feedback is safe like seeing it change something. When you take a piece of input and actually adjust, you tell your whole team that speaking up is worth the risk.

Watch the silence like a dashboard light. If nobody's challenging you, treat it as a problem to solve, not a grade to celebrate. Go dig for the feedback that isn't coming to you.

And the hardest one: how to give your boss feedback

Everything above flips when you're the one who needs to tell someone with power over your career that something isn't working. This is genuinely risky, and I won't pretend otherwise — not every boss has earned it, and reading the safety of your specific situation matters. But here's how to do it as well as it can be done:

Ask permission first. "Would you be open to some feedback on how the project kickoff went?" gives them a second to shift into receiving mode instead of being ambushed, and it's far more likely to land.

Lead with shared goals, not grievance. Frame it around something you both want. "I want to make sure we hit this deadline, and I think there's something getting in the way" is heard completely differently than "you keep doing this thing." You're on the same team, aimed at the same target.

Be specific and behavioral, never characterological. Talk about a specific action and its specific effect — "when the meeting time changes without notice, I lose prep time and it shows in my work" — not about who they are as a person. Give them something fixable, not a verdict.

Use radical candor in reverse. The same framework works upward. Show you care — about the team, the goal, their success — and be direct. Care personally, challenge directly, even when the person you're challenging signs your reviews.

Read the room and protect yourself. If your boss has a track record of punishing honesty, calibrate. You can be more careful, choose smaller stakes, document things, and recognize that some environments genuinely aren't safe for upward candor — and that's information about the environment, not a failing in you. Bravery isn't the same as recklessness.

The bottom line

A great feedback culture runs in both directions. The manager who can dish it out but can't take it isn't building a team — they're building an echo chamber that will eventually fail them quietly and all at once.

So want the feedback. Hunt for it. Make it so safe to tell you the truth that your people actually do. Because the leaders who get told the hard things early are the ones who get to fix them early — and the ones who hear nothing but agreement are usually the last to find out they were the problem all along.

The silence isn't safety. The honesty is. Go make room for it — in both directions.

Part 2 of 2. Read the companion piece: Why Giving Feedback Terrifies Us (story #32 on this page).

Most leaders, if you asked them, would say they're responsible for their team. It's the natural way to think about it. You're accountable for the output, the results, the performance, the people. The buck stops with you. That's leadership 101.

But there's a second preposition that almost nobody talks about, and it changes everything. The best leaders understand they are responsible for their team and responsible to their team.

Two tiny words. Completely different relationships. Let me unpack what each one means and why holding both is the whole game.

Responsible for: the part everyone already gets

Being responsible for your team is the downward, outward-facing accountability. It's what most people picture when they think "manager."

You're responsible for the results — the targets, the deliverables, the quality of what your team ships. You're responsible for the people's performance and growth, for making sure the right work gets done by the right people in the right way. When the team succeeds, you're accountable for having steered it there; when it fails, you don't get to point down the org chart and blame your reports. The responsibility stops with you.

This is real and it matters. A leader who isn't responsible for their team is just a person with a title. But here's the trap: when "responsible for" is the only frame a leader holds, it quietly curdles into something worse. It becomes ownership in the possessive sense — my team, my numbers, my people as instruments of my success. The team becomes a resource to be managed for outcomes, and the humans inside it become means to an end. "Responsible for" alone is how you get bosses who optimize people like spreadsheet cells.

That's where the second preposition saves you.

Responsible to: the part that changes everything

Being responsible to your team is the upward-facing obligation that runs in the other direction. It's the recognition that your team is not just something you're accountable for to the company — they are people you owe something to, directly.

What do you owe them? Clarity, so they're not guessing at what success looks like. Honesty, so they can trust what you tell them. Advocacy, so that when decisions get made above your head, someone is in the room fighting for them. Protection, so they're shielded from chaos and blame that isn't theirs to carry. The conditions to do their best work — the resources, the air cover, the removal of obstacles. Your genuine attention to their growth, not because it serves your numbers, but because you have a duty to the development of the people who've placed their working lives partly in your hands.

"Responsible to" means your team is a stakeholder you answer to — not just your boss, not just the company. It means that when you make a decision, "is this fair to my people?" sits at the table alongside "does this hit the goal?" It means you serve them as much as they serve the mission.

Why holding both reframes everything

Here's the magic, and it's in the tension between the two.

A leader who is only responsible for their team tends toward control, extraction, and using people. The team exists to produce. Results justify means. This is the boss who hits the number while burning out everyone who got them there — and calls it leadership.

A leader who is only responsible to their team — caring, protective, but unwilling to hold accountability — tends toward the other failure: the people-pleaser who can't challenge anyone, avoids hard calls, and lets standards slide in the name of being liked. Warm, and ultimately ineffective.

But a leader who holds both at once lives in the productive tension that actually defines great leadership. They drive results and they answer to the people producing them. They challenge directly and they have your back. They're accountable to the company for the team's output and accountable to the team for the conditions of their work. The two responsibilities check and balance each other — the "for" keeps the "to" from going soft, and the "to" keeps the "for" from going cruel.

That balance point has a name, really. It's just good leadership. The reframe is simply the clearest way I know to find it.

How leaders get this wrong

They collapse the two into one. Most bad leadership comes from holding only "responsible for" and never noticing the "to" exists. They genuinely don't believe they owe their team anything beyond a paycheck and instructions. The idea that they answer to their reports would strike them as backwards.

They think "responsible to" means "ruled by." Some leaders resist the second frame because they hear it as "let the team run the show" or "never make an unpopular decision." It's neither. You can owe someone clarity, honesty, and advocacy while still making the hard call they don't like. Being responsible to people doesn't mean being controlled by them — it means being honest and fair with them.

They flip the direction of service entirely. The worst version treats the team as responsible to and for the leader — there to make the boss look good, absorb the boss's blame, and serve the boss's ambitions. The arrows all point the wrong way, and everyone underneath can feel it.

How to live the reframe

Run decisions through both questions. Before you act, ask not only "does this serve the goal I'm responsible for?" but "is this fair and honest to the people I'm responsible to?" When those two answers conflict, you've found the exact spot where real leadership happens. Don't auto-default to the goal.

Tell your team you answer to them, then prove it. Say out loud that part of your job is creating the conditions for them to succeed — and then ask what's getting in their way and actually remove it. Advocacy and obstacle-removal are how "responsible to" becomes visible instead of theoretical.

Take the blame down and push the credit out. The clearest behavioral test of which frame you're holding: when things go wrong, do you protect your team (responsible to) or expose them (responsible for, possessively)? When things go right, do you share the credit or collect it? Leaders who are responsible to their teams absorb blame and distribute credit. The reverse tells you everything.

**Hold the standard and the human at the same time.** You don't choose between accountability and care. The reframe insists you do both: challenge their work because you're responsible for the results, support them as people because you're responsible to them. That's not a contradiction. That's the job.

The bottom line

"Responsible for" makes you a manager. "Responsible to" makes you a leader. Holding both, in tension, every day, is what separates the people who merely run teams from the people teams would run through walls for.

The shift is small enough to fit in a single word. But once you start asking "what do I owe these people?" with the same seriousness you ask "what do these people owe me?" — the whole relationship changes. Your team stops being a resource you're accountable for and becomes a group of humans you're accountable to.

And here's the part that should sell it even to the most results-obsessed leader: teams led by someone who feels responsible to them outperform teams that are merely managed. People give their best, most discretionary, most creative work to leaders they believe have their backs. The "to" isn't the soft part you do instead of getting results. It's how you get the results that last.

Here's a sentence that's true and dangerous at the same time: hurt people hurt people.

True, because it almost always is. The boss who couldn't give feedback was probably never given any. The one who ruled by fear was likely managed by fear himself. The credit-stealer learned somewhere that there wasn't enough to go around. The one who dumped his emotions on his staff never learned anywhere safe to put them. Behind most bad bosses is a long chain of other bad bosses — and often a childhood, a marriage, a life that taught them this was how power works.

Dangerous, because that same sentence, handled carelessly, becomes the most sophisticated excuse ever invented for letting harm continue.

So let me try to hold both at once, because I think that's the only honest place to stand.

Why the compassion is real

I've written a lot of posts in this series naming the damage bad bosses do. I stand by all of it. And I also believe, genuinely, that almost none of those people woke up wanting to be the villain in someone's story.

The fearful, controlling manager is usually someone terrified of his own inadequacy being exposed. The jealous boss who couldn't bear her subordinate's success was guarding a wound that predated that subordinate by decades. The avoidant one who couldn't have the hard conversation was probably never shown that conflict could be safe. The rigid rule-worshipper doesn't trust his own judgment because, somewhere, someone taught him his judgment couldn't be trusted. When you look closely at a bad boss, you very rarely find a monster. You find a frightened person who was handed power they didn't have the inner resources to wield well.

That's worth real compassion. Not performative compassion — actual understanding that the person hurting you is, in some meaningful sense, also a person who was hurt. It can soften the rage. It can keep you from internalizing their behavior as a verdict on you. Understanding that "this is about their wound, not my worth" is genuinely freeing.

Why the compassion is not the same as a pass

And here is where I have to be absolutely clear, because this is exactly where the sentence turns dangerous.

Understanding why someone harms you is not the same as excusing it. And it is definitely not your job to absorb the harm because you understand its origins.

I've said this in other posts and I'll keep saying it: the harm is still harm. The impact on you is still real, regardless of how sympathetic the cause. A person can have the saddest backstory imaginable and still be doing genuine damage to the people who report to them, and that damage doesn't get smaller because you can explain it. A wound that explains a behavior does not dissolve the behavior's consequences. You can hold deep compassion for why your boss is the way they are while still naming, clearly, that the way they are is unacceptable.

The trap — and it's a trap that catches kind, empathetic people especially — is letting your understanding become a reason to keep tolerating the intolerable. "He's going through a divorce." "She had a terrible mentor." "He doesn't know any better." All might be true. None of them are reasons for you to be the place his pain lands. Your empathy is not an obligation to be someone's punching bag with a backstory.

How this gets weaponized (sometimes by the boss, sometimes by ourselves)

They use their wound as a shield. Some bad bosses learn that their struggles buy them a pass — that if everyone knows about the divorce, the hard childhood, the stress, then the behavior gets excused. The vulnerability becomes a tool. Watch for the leader whose pain is always deployed right when accountability comes knocking.

We excuse them faster than we'd excuse ourselves. Empathetic people will extend a boss endless grace they'd never extend to their own behavior. "He's just stressed" becomes a reflex that lets harm slide for years. The compassion is real, but it's being aimed in a way that protects the powerful person and sacrifices you.

We confuse forgiving with staying. Here's a subtle one: you can forgive someone — even genuinely wish them healing — and still leave. Forgiveness and proximity are not the same thing. You're allowed to understand your boss completely, hold no hatred for them, and still get yourself out of range of their behavior. Compassion does not require you to stay in the splash zone.

How to hold both, in practice

Let the compassion be for your benefit, not theirs. Understanding your boss's wound is most useful as a tool for your peace — it stops you from taking their behavior personally. It is not a debt you owe them. Use it to protect your own head, not to justify staying somewhere harmful.

Name the behavior regardless of the cause. "I understand you're under enormous stress, and the way that's landing on the team isn't okay" is a complete sentence. You can acknowledge the wound and hold the line in the same breath. The cause is context; the behavior is still the behavior.

Don't accept the wound as currency. When someone's pain is offered as a reason to excuse ongoing harm, you're allowed to decline the transaction. Sympathy for their struggle, yes. Permission to keep hurting you, no.

Know the difference between your compassion and your safety. Compassion is something you can feel from any distance, including a great one. If a boss's behavior is damaging you, the compassionate-toward-yourself move and the compassionate-toward-them move can both point to the same exit. You can wish them well and go.

**And if the bad boss is you:** This is the one that matters most. If you recognize yourself — if you suspect your own wounds are leaking onto your team — the chain stops with the person willing to do the work. "Hurt people hurt people" is a description, not a destiny. Plenty of deeply hurt people become extraordinarily good leaders precisely because they refused to pass the pain down. Get the help. Do the work. Break it.

The bottom line

Your bad boss is probably also someone's victim. That is almost always true, and it deserves real compassion — the kind that helps you understand their behavior isn't a measure of your worth.

But compassion for the wounded person and accountability for the harmful behavior are not in conflict. They're meant to be held together. The wound explains; it does not excuse. Understanding why someone hurts people is a gift you can give yourself — a way to stop carrying their damage as if it were yours. It is not a sentence you serve on their behalf.

Hurt people hurt people. True. But hurt people can also heal, and healed people lead differently — and the whole point of naming the cycle is not to forgive our way into tolerating it forever. It's to find the place where it finally stops.

Feel the compassion. Hold the line. And if you need to, walk — with understanding in your heart and your dignity fully intact.

In my last post I argued that flexibility is a system, not a lack of one. Now I want to go a layer deeper, into the actual science — because "fairness" isn't just a feeling or a value. It's one of the most studied concepts in organizational psychology, and the research has a lot to say about where managers get it wrong.

The headline finding, which trips up well-meaning leaders constantly: treating everyone equally and treating everyone fairly are not the same thing. Sometimes they're even opposites.

Let's get into what the science actually says.

Equality vs. equity: the distinction that breaks most managers

Start with the two words people use interchangeably and shouldn't.

Equality means everyone gets the same thing, regardless of their circumstances or contribution. Same resources, same treatment, same outcome — split evenly, like cutting a cake into identical pieces.

Equity means outcomes are based on inputs and needs — people who contribute more, or who face greater barriers, are treated accordingly. It's the difference between giving everyone an identical-height box to see over a fence (equality) versus giving each person the box height they actually need to see (equity).

This isn't just a DEI slogan — it's rooted in decades of research. In the distributive justice literature, equality and equity are two distinct "distributive norms," different rules for how rewards and resources get allocated. Under an equality norm, everyone gets an equal share regardless of input. Under an equity norm, members' outcomes are based on their contributions — someone who gave more time, energy, risk, or effort should receive more than someone who gave less.

Here's the catch that rigid managers miss: both can be fair, and both can be unfair, depending on the situation. Equal pay for radically unequal contribution feels unfair to your top performers. Identical treatment of wildly different circumstances feels unfair to the person whose situation you ignored. Real fairness means knowing which norm the situation calls for — not defaulting to "treat everyone identically" and calling it justice.

The science of equity theory: people are always running the math

Why does this matter so much? Because of something psychologist J. Stacey Adams identified back in the 1960s called equity theory, and it explains a huge amount of workplace behavior.

Equity theory says employees are constantly, often unconsciously, calculating a ratio: what I put in (effort, skill, time, loyalty) versus what I get out (pay, recognition, opportunity) — and then comparing their ratio to their coworkers' ratios. People aren't actually obsessed with getting the most. They're obsessed with the ratios being fair relative to others.

And when that comparison feels off — when someone perceives their input-to-output ratio is worse than a peer's — the research is clear about what happens: they become unhappy, demotivated, and they adjust. They reduce their effort to rebalance the equation. They disengage. They start looking elsewhere. The unfairness doesn't just hurt feelings; it directly changes behavior and tanks productivity.

This is why the manager who gives everyone an identical raise feels fair and often backfires: the high performer's ratio just got worse relative to the slacker's, and equity theory predicts exactly what they'll do about it.

The four kinds of fairness (most managers only think about one)

Here's where the science gets genuinely useful. Organizational justice research — going back to Greenberg in the 1980s — finds that fairness at work isn't one thing. It's four distinct things, and employees judge all of them:

Distributive justice — is the outcome fair? Are pay, promotions, resources, and workloads distributed fairly? This is the one everyone thinks of.

Procedural justice — is the process fair? Were the decisions made through consistent, unbiased procedures? Crucially, the research shows people will accept an unfavorable outcome far more readily if they believe the process was fair. How you decide matters as much as what you decide.

Interpersonal justice — were people treated with dignity and respect in the process? The same decision delivered with care lands completely differently than one delivered coldly.

Informational justice — were people given honest explanations for decisions that affect them? Silence and opacity read as injustice even when the decision itself was sound.

That second one is the quiet superpower most leaders miss. Procedural justice research consistently finds that giving people voice — a genuine say in the process, the feeling of being heard — dramatically increases their sense of fairness, even when the outcome doesn't change. Fair process communicates that employees are valued members of the group. You can deliver hard news fairly. You just have to be fair in how, not only in what.

How leaders get this wrong

They equate fairness with sameness. The most common error: believing "I treat everyone identically" is the gold standard. The science says identical treatment of different inputs and circumstances often produces perceived injustice, not fairness.

They obsess over outcomes and ignore process. Managers tend to assume employees only care about the result — the raise, the promotion. But the research shows procedural and interactional justice matter enormously. People can absorb a "no" they didn't want if the process was transparent, consistent, and respectful. They rebel against a "yes" that arrived through a process that ignored them.

They underestimate how much people are comparing. Equity theory is relentless: your team is always measuring their ratio against their peers'. The manager who quietly over-rewards a favorite, or under-recognizes a quiet high performer, is creating perceived inequity that will express itself as disengagement — whether or not anyone says a word.

They forget that explanation is part of fairness. Making a sound decision and then never explaining it reads as unjust. Informational justice is nearly free to provide and hugely protective when you do.

How to apply the science

Ask which norm the situation calls for. Before you default to "treat everyone the same," ask whether this situation calls for equality (equal shares) or equity (shares based on input or need). Distributing a team bonus by contribution is equity; giving everyone the same snow day is equality. Match the norm to the moment.

Invest in fair process, not just fair outcomes. Make your decision-making consistent, transparent, and bias-checked. Let people have voice — a real chance to be heard — even when you can't give them the outcome they want. The research says this single move buys enormous goodwill and perceived fairness.

Deliver everything with dignity and explanation. Interpersonal and informational justice are the cheapest fairness wins available. Treat people with respect in the process and explain your reasoning, and even hard decisions land as fair.

Watch the ratios. Pay attention to whether your rewards and recognition track with actual contribution. Equal treatment of unequal effort demotivates your best people; that's not a morale problem, it's equity theory doing exactly what it predicts.

Be transparent about the principle. When you treat two people differently, be able to articulate the fair principle behind it — the input, the need, the circumstance — so it reads as equity, not favoritism. Unexplained difference looks like bias; explained difference looks like justice.

The bottom line

Fairness isn't a vibe, and it isn't "treat everyone exactly the same." It's a well-studied, multi-dimensional thing: fair outcomes, fair processes, respectful treatment, and honest explanation — calibrated to whether a given moment calls for equality or equity.

The rigid manager who insists on identical treatment thinks they've solved fairness. The science says they've barely understood the question. Real fairness sometimes means treating people differently — by contribution, by need, by circumstance — and doing it through a transparent process, with respect, and with an explanation everyone can see.

Treating people fairly is harder than treating them the same. That's exactly why so few managers actually do it — and why the ones who do end up with teams that trust them, stay with them, and give them their best work.

There's a certain kind of bad boss who wears their rigidity like a badge of honor. No exceptions. Rules are rules. If I do it for you, I have to do it for everyone. They say these things with the conviction of someone who believes inflexibility is the same as integrity — that bending, ever, for anyone, is the first step toward chaos.

They've made a fundamental error, and it's one I made myself early in my career, so I say this with sympathy and certainty both: they've confused flexibility with the absence of rules. They think the only alternative to rigid, identical treatment is a free-for-all where everyone does whatever they want. So they cling to the rigidity, because at least it feels safe.

It isn't safe. And the thing they're avoiding isn't chaos. It's the harder, better work of building a system.

The false choice at the heart of rigid management

The rigid boss operates on a hidden assumption: that there are only two options. Either you apply the rule identically to everyone, every time, no exceptions — or you abandon the rule entirely and descend into favoritism and anarchy.

That's a false binary, and almost every bad policy decision flows from believing it.

Because there's a third option, and it's the one good leaders actually use: flexibility as a system. A consistent, principled, evenly-applied framework that includes the ability to flex for circumstances — and applies that flexibility fairly to everyone in the same situation. That's not the absence of policy. That's a more sophisticated policy. It's the difference between a law that says "no one may ever park here" and a law that says "no one may park here, except for loading, emergencies, and accessibility needs — and those exceptions apply equally to everyone."

The rigid boss looks at the second version and sees weakness. It's actually the stronger system, because it survives contact with reality. Rigid rules shatter the first time real life presents a case they didn't anticipate. Flexible systems bend and hold.

What "flexibility as a system" actually means

This is the crux, so let me be precise, because the rigid boss's real fear — that flexibility means favoritism — is a legitimate fear. They're just solving it the wrong way.

Flexibility as a system means the principle is consistent even when the application varies. You don't have one rule for the people you like and another for the people you don't. You have one framework — a clear sense of what the policy is for — and you apply that framework evenly, which sometimes produces different outcomes for different circumstances because the circumstances are different.

The test is simple and it's the thing that separates real flexibility from favoritism: Would I extend this same consideration to anyone else in this same situation, regardless of how I feel about them? If yes, you're being flexible and fair. If you'd only bend for your favorites, that's not flexibility — that's bias, and the rigid boss is right to fear it. The answer isn't to ban all bending. It's to make sure the bending follows a principle, not a preference.

So when an employee needs a temporary schedule shift for a family emergency, the flexible system asks: is this a circumstance our framework should accommodate, and would we do it for anyone in this spot? If yes — grant it, document it, and mean it. That's not the erosion of fairness. That is fairness. Treating genuinely different situations identically isn't equality; it's just rigidity wearing equality's clothes.

How leaders get this wrong

They mistake rigidity for fairness. "I treat everyone exactly the same" sounds fair and often isn't. Identical treatment of different circumstances produces unfair results — it punishes the person with the sick kid exactly as hard as it constrains the person with no constraints, and calls that justice.

They mistake rigidity for strength. The inflexible boss feels strong and decisive. In reality, rigidity is often a hiding place for managers who don't trust their own judgment. Rules don't require judgment; you just apply them. Flexibility requires you to think, to weigh, to be accountable for a call — and that's exactly what the rigid boss is avoiding. Their "strength" is frequently just fear of having to decide.

They use "consistency" as an excuse to avoid hard thinking. It's genuinely easier to say "no, policy" than to evaluate whether a situation warrants an exception. Rigidity is the lazy option dressed up as principle. The flexible leader does more work, not less.

They create the favoritism they claim to prevent. Here's the irony: rigid cultures often breed more unfairness, not less, because the exceptions still happen — they just go underground. The favored employee gets the quiet break off the books while the official line stays "no exceptions." A transparent, systematic flexibility is far fairer than a rigid rule that everyone secretly bends for the right people.

How to do it right

**Know what every rule is for.** A policy is a tool serving a purpose. When you understand the purpose, you can tell the difference between an exception that violates it and one that serves it. The rigid boss enforces the letter of the rule while betraying its spirit; the flexible leader protects the spirit, which sometimes means flexing the letter.

Build the flexibility into the system, not the mood. Make reasonable accommodations a documented, evenly-available part of how things work — so flexibility is a feature anyone can access, not a favor you grant your favorites. That's how you get the humanity of flexibility and the fairness of consistency at once.

Apply the "anyone in this situation" test, every time. Before you flex, ask whether you'd do the same for anyone else in the same spot. That single question is what keeps flexibility honest and turns it from favoritism into fairness.

Trust yourself to make judgment calls — and be accountable for them. The whole point of moving from rigidity to a flexible system is that it requires judgment. Don't hide from that. Make the call, explain your reasoning, apply it consistently, and own it. That's harder than "rules are rules." It's also the actual job.

The bottom line

Rigidity is not the opposite of chaos. A system is the opposite of chaos — and the best systems have flexibility built right into them, applied evenly, grounded in principle rather than preference.

The boss who brags about never bending isn't demonstrating strength or fairness. They're demonstrating that they've never learned the difference between a rule and its purpose, and that they'd rather hide behind "no exceptions" than do the harder work of judging each situation on its merits while staying fair to everyone.

Flexibility, done right, isn't the absence of standards. It's the highest form of them. It says: we have clear principles, we apply them consistently, and we're wise enough to recognize that treating different situations differently — fairly, transparently, for anyone — is what fairness actually looks like in the real world.

Anyone can follow a rule. It takes a real leader to run a system.

Time for a lighter, more general-knowledge entry — a numbers-driven look at women in leadership. Where they actually are in the org chart, what the research says about how they lead, and how their teams tend to function. Some of these stats surprised me, and I work in this field.

Fair warning up front: I'll keep this balanced. The "women make better leaders" genre tends to cherry-pick, and I'd rather give you the real picture, caveats included.

Where women actually are (and aren't)

Let's start with the representation gap, because it's stark and it's the backdrop for everything else.

Women make up roughly 43% of the global workforce but hold only around 30% of leadership positions worldwide. The higher you climb, the thinner it gets — this is the famous "leadership pipeline" leak. Representation drops from about 48% at entry level to roughly 29% in the C-suite. At the very top, women hold somewhere around 9-11% of Fortune 500 CEO roles — a record high, and still fewer than 1 in 10.

The bottleneck has a specific, well-documented starting point. For every 100 men promoted to that first manager role, only about 81 women get the same promotion — the so-called "broken rung." It's not the glass ceiling that does the most damage; it's that very first step up. Fewer women become managers, so the pool shrinks at every level above it.

And the gap compounds brutally for women of color. Women of color occupy under 8% of board seats. Black women are less than 2% of Fortune 500 CEOs. The pipeline isn't just leaky — it leaks unevenly.

One more sobering number: women CEOs last an average of about 5 years, compared to roughly 8 for men. Even when women reach the top, they tend to face higher scrutiny and shorter tenures — sometimes via the "glass cliff," the documented pattern of women being handed leadership of organizations already in crisis, then blamed when the crisis they inherited doesn't magically resolve.

What kind of leaders do they make?

Here's where it gets interesting, with the caveat I promised: individual variation dwarfs gender averages, "how women lead" is shaped far more by socialization and circumstance than biology, and plenty of these findings are correlational. With all that said, the research does show some consistent patterns.

Women leaders skew toward what researchers call a transformational and relational style — emphasizing mentorship, collaboration, communication, and the development of the people they manage. The data backs the on-the-ground effect: around 60% of employees say women leaders improve workplace culture. Women managers are documented as taking more action to support their teams — helping people manage workloads, checking in on wellbeing, and doing the often-invisible work of keeping a team healthy.

They also tend to build more diverse teams beneath them. Companies led by female CEOs have a noticeably higher share of women on their boards and leadership teams — about 33.6% vs. 27.9% at S&P 500 companies overall. Representation at the top tends to pull representation up throughout the organization.

How do their teams tend to function?

Following from the style, the team-level patterns the research associates with women's leadership:

Stronger culture and trust. The supportive, communicative style correlates with teams that report feeling more respected and valued — which itself is linked to higher motivation and better work.

Better decision-making through diversity. Gender-diverse leadership teams are repeatedly found to make better decisions and drive more innovation, largely because diverse groups bring a wider range of perspectives and are less prone to groupthink.

Attention to the whole person. The wellbeing-checking, workload-managing behaviors mean teams under women leaders often report feeling more seen — which connects to retention and engagement.

Narrower pay gaps and more balanced outcomes. Boards with a critical mass of women have been associated with narrower CEO-to-worker pay ratios and broader performance metrics, which in turn correlate with higher employee-trust scores and lower frontline turnover.

And the headline business numbers

This is the part that tends to make executives sit up, so here it is — with the reminder that correlation isn't causation, and the direction of the arrow is genuinely debated:

Companies with more women in leadership are frequently reported as around 25% more profitable. Gender-diverse leadership teams are roughly 20-27% more likely to outperform their peers financially. One widely cited figure: over a 10-year span, companies led by women CEOs posted a 223% return on equity versus 130% for those led by men.

The honest caveat: some of this is likely reverse causation — already-healthy, well-run, forward-thinking companies are both more profitable and more likely to promote women, so women's leadership may be partly a marker of a good company rather than purely a cause of one. The truth is probably some of both. But even read conservatively, the data thoroughly demolishes the old myth that promoting women is a trade-off against performance. At worst it's neutral; at best it's a real edge. There's no version of the data where it's a cost.

So are women better leaders?

Here's my honest take, since this is the question the whole post circles.

No — and yes. "Better" is the wrong frame. The most effective leaders of any gender share the same core traits: they care personally and challenge directly, they build trust, they develop their people, they make room for diverse perspectives. Those aren't female traits; they're good-leadership traits.

What's true is that women, on average, are socialized toward some of the relational and supportive behaviors that good leadership requires — and our culture has historically undervalued exactly those behaviors while overvaluing the loud, dominant, command-and-control style. So part of what the data shows isn't "women are innately better." It's that the workplace spent a long time mistaking confidence for competence and dominance for leadership, and systematically overlooked people who led in quieter, more developmental ways.

The rise of women in leadership is, in part, the workplace slowly correcting that error — and discovering that the leadership traits it undervalued were the valuable ones all along.

The bottom line

The numbers tell a two-part story. Part one: women are still dramatically underrepresented in leadership, the gap starts at the very first promotion, and it's worst for women of color. Part two: where women do lead, the research consistently associates their leadership with stronger cultures, more supported teams, more diverse organizations, and business performance that's at minimum no worse and frequently better.

Put those together and you get the actual headline: we have systematically underused a huge pool of leadership talent that the data suggests is, at the very least, every bit as effective — and we're only now, slowly, beginning to fix it. That's not a story about women being better than men. It's a story about a workplace finally learning what good leadership looked like all along, and noticing it was standing in front of a lot of it without promoting it.

There's a popular idea that motherhood is secret leadership training — that raising kids builds exactly the skills a great manager needs. There's also a much older, much creepier idea lurking nearby: that managing employees is like parenting children, that a boss is a kind of parent, and a team a kind of family.

These two ideas get tangled together constantly, and they shouldn't be. One contains a real insight. The other is the root of some genuinely toxic management. Let's separate them carefully.

The case that motherhood builds leadership skills

It's not nothing. Parenting — and I'd extend this to any intensive caregiving, not just mothers — develops a genuinely transferable skill set.

You learn patience under pressure that would break most people. You learn to stay calm while someone melts down. You get very good at reading nonverbal cues, at sensing when something's wrong before anyone says it. You learn to manage competing needs, triage crises, and make decisions with incomplete information while exhausted. You develop endurance, the kind that shows up for the boring middle of things, not just the exciting start. You learn that different people need different things, and that fairness isn't sameness. And — maybe most relevant — you get a crash course in helping someone grow into their own capability rather than doing everything for them.

Those are real leadership competencies. So yes, the experience of raising kids can absolutely sharpen skills that translate to leading people. A parent returning to work isn't "behind" — they may have spent those years in an intense leadership-development program nobody gave them credit for.

But here's where it goes wrong

The problem isn't the skill transfer. The problem is when we slide from "parenting builds skills useful in leadership" to "leadership is parenting" — and start treating employees like children.

Because employees are not children. And the differences are not small.

Employees are autonomous adults who chose to be there. A child is dependent, developmentally immature, and didn't consent to the relationship. An employee is a fully formed adult, your legal and moral equal, who entered into a voluntary professional exchange. The power a parent holds over a child is total and is meant to be; the power a manager holds over an employee is limited, conditional, and easily abused. Confusing the two is how you get bosses who feel entitled to control their reports' lives.

The goal is completely different. A parent's job is to raise a child toward independence — you're shaping a whole person. A manager's job is far narrower: to enable an adult to do good work and grow professionally. You are not responsible for molding your employee's character, values, or life. The moment you think you are, you've overstepped a boundary that doesn't belong to you.

The relationship is professional, not unconditional. Parental love is supposed to be unconditional and permanent. The employment relationship is a conditional, professional arrangement that either party can end. Pretending otherwise — "we're a family here" — is usually the prelude to exploitation, as I've written about before. Families don't lay you off. Companies do.

Why "I treat my team like my kids" is a red flag

When a manager says they treat their team like their children, they usually mean it warmly. But listen to what's underneath it, because it points at real dysfunction:

It infantilizes. Treating capable adults like children means assuming they can't handle the truth, can't make their own decisions, need to be protected from information, need you to know best. It's condescending, and competent people feel it instantly. The "I know what's best for you" manager is exhausting to work for even when they mean well.

It justifies control. "I'm doing this for your own good" is something you say to a child. When a manager says it to an adult, it's a license for overreach — micromanagement, boundary-crossing, treating professional decisions as theirs to make on your behalf.

It sets up the rescue dynamic. The parent-boss often needs to be needed — and as I've written about with controlling managers, that need to be the rescuer, the wise protector, the one who knows best, is the engine of some genuinely manipulative leadership. The "I'm like a parent to you" boss and the boss who breaks people down so they can heroically build them back up are often closer than they look.

It distorts accountability in both directions. Some parent-bosses can't deliver hard feedback because you don't want to "hurt" your kid; others wield disappointment like a disapproving father. Both turn a professional relationship into an emotional one the employee never signed up for.

So what actually transfers, and what doesn't?

Here's the clean way to sort it. The skills of caregiving transfer beautifully. The posture of parenting does not.

Transfers: Patience. Empathy. Reading people. Developing others. Staying calm in chaos. Understanding that different people need different things. Endurance. The deep knowledge that growth takes time and support.

Does not transfer: Authority over someone's whole self. The assumption that you know best. The right to make decisions on their behalf. Treating the relationship as permanent or unconditional. Seeing the other person as someone to be molded rather than supported. The expectation of gratitude or loyalty as a child might owe a parent.

The great manager who happens to be a parent takes the skills into work and leaves the hierarchy at home. They treat their reports as capable adults who deserve support — not as kids who need raising.

And the flip side: not all great leaders are parents

It's worth saying plainly, because the "motherhood makes you a better leader" framing has an ugly shadow: it implies people without children are missing something. They're not.

Plenty of extraordinary leaders have no kids. The caregiving skills that transfer can be developed a hundred other ways — through mentorship, through caring for other family members, through coaching, through life. And plenty of parents are bad managers, because raising kids doesn't automatically teach you to lead adults, and some people import exactly the controlling, parental posture we just spent this whole post warning about. Parenthood is neither necessary nor sufficient for good leadership. It's one possible path to some useful skills, not a credential.

The bottom line

Does being a mother make you a better leader? It can sharpen real, transferable skills — patience, empathy, reading people, developing others — and those skills are genuinely valuable. So the experience can help.

But should we compare employees to children? No. Employees are autonomous adults in a voluntary professional relationship, and the moment a leader starts treating them like kids — knowing best, controlling for their "own good," expecting a child's gratitude and loyalty — caregiving curdles into control.

The best version of "leading like a parent" keeps the warmth, the patience, and the genuine investment in people's growth, while fully respecting that the people in front of you are adults who get to run their own lives. Take the skills. Drop the hierarchy. Treat your team like the capable grown-ups they are — and you'll have taken the best of what caregiving teaches without any of the condescension that ruins it.