I’ve watched enough of them now to know the answer. It’s not that people weren’t smart. It’s that the mechanics were designed to be invisible. You don’t feel the walls going up because they go up slowly, and each brick is wrapped in the language of belonging, purpose, and meaning.

The researchers who study these groups have mapped the playbook. It doesn’t matter the setting, the era, or the cause being sold. The mechanics are almost always the same.

First, they give you a language. Words that mean something different inside the group than outside it — that signal belonging when you use them correctly, and signal threat when you don’t. Then they give you an identity. Not your own — a shared one. Your personal story gets rewritten as a chapter in the group’s story. Your ambitions get reframed as contributions to the collective mission. Then they manage dissent. Not with force — that’s crude. With language. The person who asks hard questions isn’t pushed out, they’re “not a fit.” The one who pushes back isn’t silenced, they’re “not aligned with where we’re going.”

And underneath all of it, there is a transaction. You give your belief, your identity, your discretionary effort. In return, you get belonging — or the performance of it. The warmth of being inside. The low-grade anxiety of what it would mean to be out.

I used to watch all of this and think I’d never fall for it.

Then I started paying closer attention to my own career. And I realized I’d been in that room. We all have. It just had better coffee and a Slack channel.

These researchers aren’t only studying compounds in the desert or movements that made the news. They’re describing companies.

The vocabulary shifted so gradually most people didn’t notice. Employees became “team members,” “partners,” or — God help us — “family.” Work became a “mission.” Your job description became a “purpose.” Leaving became “not being aligned with where we’re going.” Every word doing the work of softening the edges. Every phrase chosen to make the transaction feel like something more.

Because if you’re not just earning a paycheck but fulfilling a purpose, you’ll work longer hours. You’ll answer emails at midnight. You’ll feel guilty when you don’t. You’ll tolerate things you shouldn’t, because the cause is bigger than your discomfort.

That’s not culture. That’s a cost reduction strategy with better branding.

Decode what you actually hear at work and it sounds like this.

The translation

“She wasn’t a culture fit” = she asked questions we didn’t want to answer.

“We’re a family here” = we expect family loyalty on a contractor’s salary.

“He wasn’t aligned with where we’re going” = he disagreed with leadership.

“We need someone who lives and breathes the mission” = we want your identity, not just your hours.

None of this means your company is a high-control group. It means the tactics used to build “strong culture” overlap with the tactics used to build unhealthy group dependency more than anyone is comfortable admitting. The difference between a movement and something more coercive is often just whether the cause is real — and who gets to decide that. Leadership. The same people selling you the mission and measuring your belief in it.

Here’s what happens when the belief meets reality. Someone invests six years. Builds the culture. Trains the people. Believes the words on the wall. Then gets a fourteen-minute Zoom call, a script, and a last day that is a Friday.

The mission statement in the glossy PowerPoint they handed you on day one doesn’t protect you from the restructure on day 2,190. It just makes it more disorienting when it comes.

So here is what I want you to hear — and I mean this not as cynicism but as liberation.

Your career does not belong to any company. It never did. Your career is the full arc — the skills you’ve built, the problems you’ve solved, the people you’ve led, the judgment you’ve earned through every hard room you’ve sat in. That arc belongs entirely to you. A company is one place where part of it happened. An important place, maybe. A formative one, even. But one chapter. Not the book.

A career spent at only one company isn’t a career. It’s a tenure. And tenure, without the breadth that comes from navigating different environments, different leadership styles, different failures — it’s a narrow thing. Rich in loyalty, thin in range.

The people who own their careers don’t leave companies. They graduate from them.

This reframe changes everything about how you show up. You can play the game fully — bring your best thinking, invest in the mission, care about the work — without confusing the game for your identity. You can wear the hoodie without becoming the hoodie. You can commit to a chapter without losing track of the book.

And when they decide it’s time for you to leave? It isn’t betrayal. It isn’t failure. It’s them recognizing that you’ve outgrown them, but calling it a bad fit.

The people who struggle most when companies downsize, restructure, or simply drift aren’t the ones who cared least. They’re the ones who handed over the pen. Who let the company write their story for so long that they forgot they were holding it. When the chapter ends — and it always ends — they don’t know who they are without the title, the badge, the belonging.

That is the real cost of the hypnosis. Not the long hours or the midnight emails. The identity debt. The disorientation of waking up one Wednesday and realizing that the thing you called a career was actually someone else’s mission — and they’ve just announced they’re pivoting.

You don’t have to leave to reclaim it. You just have to remember it’s yours.

Engage fully. Contribute generously. Build something real inside this place. And while you do — keep your own ledger. Track what you’re learning. Name the skills you’re sharpening. Notice what you’re becoming. Stay connected to people outside the building. Maintain the relationships that exist independent of your current role, because those relationships are yours too, and they will outlast every org chart you’ve ever appeared on.

Know your number. Know what you’re worth in the market. Not because you’re always looking — but because the person who knows their value negotiates differently than the person who’s afraid to find out. Scarcity is a tool the hypnosis uses. Knowledge is the antidote.

Play along if the chapter is good. Leave when it isn’t. Do both without guilt, because neither is a moral failing — they’re just decisions made by someone who understands that a career is long, companies are temporary, and the only constant in the whole arc is you.

The hypnosis only works if you forget you walked in voluntarily. You can walk out the same way.

That hoodie from the last place? Wear it for yard work.

If this landed — forward it to someone who’s been at the same company so long they’ve forgotten what they’d be without it. Not because they should leave. Because they should know they could.

I knew the principles. Studs need to be plumb. Headers carry the load. Every wall needs to be secured to something structural — the existing walls, the floor, something that has already proven it can bear weight. I had a pile of reclaimed wood, a saw, a drill, and enough hard-won knowledge to know what actually matters versus what the rulebook says matters.

So I started measuring. Cutting. Screwing walls together. Adjusting. The room took shape without a single call to a contractor or a glance at a building code.

It is now the sturdiest corner of a 175-year-old barn.

Not to code. Absolutely not to code. But in a building that has survived two centuries of New York winters, code was never really the point. Code is written for modern materials, modern contexts, modern assumptions about what a structure needs to be. My barn predates all of it. Following the rulebook would have meant ignoring the reality in front of me — the existing walls, the salvaged wood, the actual forces at work. Instead, I built to principle. And the thing I built holds.

I have been building this way my entire life.

I am a leadership consultant. I spend my days inside organizations asking the questions nobody else will — why is this structured the way it is? Who decided that was the right approach? What are you assuming that you have never actually tested? The discomfort in the room is always the same. Not because the questions are hard. Because the answers reveal how much of the organization was built to code without anyone stopping to ask whether the code applied.

Inherited structures. Unexamined defaults. Rules written for a different context, a different era, a different version of the problem — followed faithfully long after the conditions that created them have changed.

I recognize this pattern so clearly in organizations because I dismantled it so completely in my own life.

I am in my late fifties. I have never married. I don’t have children. I live deliberately and contentedly, in a life I designed from scratch — not because the conventional one was unavailable to me, but because I examined it the way I examined that barn, and decided the standard blueprint didn’t fit what I was actually building. The code was written for different materials, different loads, different conditions. Following it would have meant ignoring the reality in front of me.

So I built to principle instead. I understood what I actually needed — honesty, autonomy, deep connection without entanglement, the freedom to pivot without unraveling — and I built toward that, with whatever materials were available. Some of them reclaimed. Some of them unconventional. All of them load-bearing.

My mother showed me this was possible. In the 1970s, she left a good marriage to a good man because she wanted more of herself returned to herself. In her town, in her time, that was not done. Divorce was shameful. A woman rewriting her life mid-course was suspicious at best. But she understood the difference between the rulebook and the principles underneath it. She knew what her life actually needed to hold. And she built accordingly — quietly, without apology, without waiting for permission.

I watched, and what I absorbed wasn’t the specific choices she made. It was the underlying habit — the willingness to look at an inherited structure and ask: does this actually serve what I’m building? Or have I just never questioned it?

That habit is the most valuable thing I bring into any boardroom.

Because here is what decades of consulting have taught me: the gap between where a leader is and where they could be is almost never a skills gap. It is a blueprint gap. It is the distance between the structure they inherited and the one they would design if someone gave them permission to start from first principles. Between the code they’ve been following and the actual forces at work in their organization right now.

The leaders who transform their organizations — and I have watched many of them do it — are not the ones who found a better rulebook. They are the ones who stopped long enough to understand what their structure actually needs to hold. What loads are real. What walls are load-bearing and which ones just look like they are. And then they built accordingly, with whatever materials were available, some of them reclaimed, some of them unconventional.

Sturdier than anything spec’d from the standard plan.

This is not an argument against structure. The barn room has studs at about sixteen inches. The walls are plumb. The headers are sized for the spans they carry. I didn’t throw out the principles — I just distinguished between the principles and the rulebook. Between what makes something actually hold and what makes it merely compliant.

That distinction is available to anyone willing to make it. In a building. In a career. In a life.

You don’t have to make my choices. You don’t have to want my life or my barn. But I’d invite you to try the habit just once — in one corner of your organization, one assumption you’ve inherited, one structure you’ve been maintaining without ever asking whether it’s actually load-bearing.

Tape out a rectangle on the floor. Figure out what the thing genuinely needs to hold. And then build to that — not to the code someone else wrote for a different building, in a different century, with different materials than the ones you actually have.

You might find that what you build without the blueprint is the sturdiest corner of everything you own.

There’s a difference — real and consequential — between wellbeing and being well. The first has been claimed by industry: it appears on supplement labels, in the names of apps that promise to track your sleep score and optimize your recovery windows, in the language of programmes designed with good intentions to help people take better care of themselves. Wellbeing, as it’s now framed, is a destination. You work toward it. You invest in it. You succeed or fail at it.

Being well is something older and harder to name. It doesn’t appear on dashboards. It can’t be gamified. It’s less a state you arrive at and more a quality of attention you bring to the hours of your life — the way a musician doesn’t just play notes but lives inside the music, inside the phrase.

To live in something is different from achieving it. You don’t arrive at a life — you settle into one. You figure out what you actually need, as opposed to what you’re supposed to want. You stop being a visitor in your own days. That’s closer to what being well means.

To be well, in this sense, is to be in right relation — to your body, to other people, to time itself. It’s less a product you can acquire and more a posture you can practice.

The problem isn’t the programs

The commercial wellness industry — the supplements, the optimization apps, the biometric dashboards — has reframed health as primarily a private project of self-improvement. That what ails us is our own cortisol. That the solution is a better morning routine. This isn’t entirely wrong. But taken alone, without context or community, it’s incomplete.

Workplace wellness programs are a different thing, and worth distinguishing. The best of them — the ones behind the conferences that leave you genuinely thinking differently — are never really about the supplements or the sleep scores. They’re about creating conditions in which people can show up whole. Flexible arrangements. Permission to rest. A culture that doesn’t treat exhaustion as a badge. These are real inputs to being well. They’re the organization saying, in effect: we know you’re a person, not a resource.

Where wellness falls short isn’t in offering paths — it’s when paths are mistaken for destinations. A meditation app can open a door. It can’t do the walking. Being well is relational all the way down. A person can have perfect sleep data and be genuinely struggling in every way that matters. And a person can be grieving, ill, exhausted — and somehow still be, in some fundamental sense, well.

The ancient traditions that thought seriously about how to live — Stoic, Confucian, Sufi, Indigenous — shared a common assumption: that you can’t be well alone. That the self isn’t a sealed chamber but a membrane, permeable to the lives around it. That your wellbeing is inseparable from the wellbeing of those you live alongside.

Three things, not one

If being well is a practice rather than a product, what does it actually involve? Not a protocol — but perhaps three things, each necessary, none sufficient on its own.

The first is presence: the capacity to be genuinely here. Not performing attention but actually giving it. To eat a meal, hold a conversation, feel grief — without the mind already in the next moment. This is rarer than it sounds.

The second is continuity: a thread of self that holds through difficulty. Not rigidity, but the ability to remain recognisably yourself when circumstances push hard against you. The ground beneath disruption.

The third is belonging: the felt sense of mattering to someone, somewhere. Of being known accurately and valued in that accuracy — not for a performance, but for who you actually are.

Notice what’s absent from this list: productivity, achievement, optimism. These aren’t unimportant — but they tend to follow from being well, not precede it. You can’t engineer belonging by optimising your social calendar. You can’t manufacture presence by scheduling mindfulness. These things come as a consequence of something else.

The body knows first

There’s a dimension of being well that’s easy to overstate but impossible to ignore: the body. We’re not minds that happen to have bodies. The body carries what the mind hasn’t yet processed. Tension in the shoulders is often an unspoken argument. Sleeplessness is often existential before it’s physiological. The gut that feels hollow after a betrayal isn’t being metaphorical.

Being well involves listening to the body not as a machine generating performance metrics, but as something more like a first responder — one that registers what’s happening in a life long before conscious thought catches up. The question isn’t how to optimise it, but how to become more fluent in what it’s already saying.

To be well in the body means to be at home in it — not despite its limits, but honestly including them.

Difficulty is not a sign you’re doing it wrong

Perhaps the most corrosive idea in wellness culture is this: that suffering, difficulty, and low moods are evidence of inadequate self-care. That if you were doing it right, you would feel better. This is both factually wrong and quietly cruel.

Human life contains suffering that’s appropriate to the situation. Grief after loss. Anxiety before real uncertainty. Weariness when things have been hard for a long time. These aren’t malfunctions. They’re the mind and body registering reality accurately. To be well doesn’t mean to be undisturbed. It means to be able to carry what’s actually there without being destroyed by it — and, eventually, to be changed by it in ways that make you more rather than less.

The Stoics had a word for the capacity to meet difficulty without losing yourself: apatheia — not apathy, but steadiness. The still point from which all weathers can be faced. Being well, in their understanding, wasn’t about engineering good conditions. It was about building the internal capacity to meet any conditions clearly.

What being well costs

Being well isn’t free. Not always in the financial sense — though sometimes it costs that too. More often it costs in what you must be willing to relinquish. The person who arranges their life around what actually works for them often does so by declining arrangements the world considers obviously correct: the city, the career ladder, the proximity to opportunity and noise.

These refusals are a form of self-knowledge acted upon. To choose rural quiet over urban proximity, remote work over the corner office, isn’t retreat dressed up as virtue — it’s a decision to take seriously what you’ve learned about yourself. Most people know what makes them well and live in contradiction to it anyway, because the financial pressure is real, because stepping off expected trajectories carries a social cost, because it’s easier to optimise the life you have than to build a different one.

Being well sometimes asks us to become illegible to the world that would measure us — to trade the currency of proximity and ambition for something that has no ticker symbol.

The world has many ways of telling you you’re falling behind. Very few of them know what you’re running toward. To be well, in this sense, is to have made your peace with that — to have decided that the life you can actually live in matters more than the life that reads well from the outside.

You lose it. You return.

Being well isn’t something you achieve once. It’s something you return to. You lose it in the ordinary disruptions of a life — illness, betrayal, a long season of exhaustion — and then, gradually, you find your way back. The returning isn’t failure. It’s the practice.

The musician who hasn’t played in months doesn’t discard the instrument. She returns to it. The notes feel unfamiliar at first. The phrase that came so easily before requires attention again. But the hands remember, and slowly, it comes back. Being well is like this — not a permanent condition but a recurring orientation, a way of turning yourself, again and again, toward what is most real in your life.

To be well is, finally, a form of fidelity — to the self that persists through time, to the people who share your days, to the life that is actually yours rather than the one you imagine you should be living.

Wellness is something you can buy. Being well is something you can only do — quietly, imperfectly, again and again, in the ordinary hours of an ordinary life.

Nothing is wrong with you. You just expected the job to do something it was never designed to do: fulfill you.

That’s the promise “meaningful work” made. Find the right job, and it will complete you. Align your passion with your paycheck, and you’ll never work a day in your life. It sounds like freedom. It’s actually the most elegant trap ever designed. Because now you don’t just owe the company your time. You owe it your sense of self. And a person whose identity lives inside an organization will do almost anything to protect their place in it.

A conspiracy theorist might say this was all by design. Detach people from real community. Make work the only place they belong. Create dependency. Then, when the job disappoints---and it always disappoints---deliver a misery so personal and so specific that it’s hard to organize around. Hard to name. Hard to fight.

You can’t unionize against existential emptiness.

I’m not saying it’s a conspiracy. I’m saying it works like one. Whether it was planned or just the inevitable outcome of systems optimizing for compliance over humanity, the result is the same: a workforce that is professionally exhausted and privately starving. Too burned out from work to build a real life. Too invested in work to admit it isn’t one.

I’m not saying meaningful work isn’t real, or possible. The desire for it is deeply human and worth honoring. But there’s a difference between doing meaningful work and outsourcing your meaning to a job. The people who seem most alive at work are not the ones who gave everything to it. They’re the ones who brought something to it---a clear sense of who they are, what they value, what they’re building in the larger project of their lives. The meaning was already theirs. The work just got to be part of it.

That’s a completely different relationship with work. And it’s the one the system never teaches you, because a person who generates their own meaning is much harder to retain with a mission statement and a ping-pong table.

“Bring your whole self to work” started with decent intentions. Don’t make people perform robot. Don’t build cultures so sterile that humanity has to wait in the parking lot. That was the point. We blew past it at ninety miles an hour and never looked back. Now “whole self” means your growth, your belonging, your legacy, your friendships---all of it, delivered in exchange for your labor. Companies didn’t build that expectation alone. We handed it to them willingly, because somewhere along the way we confused engagement with salvation.

They were delighted to accept the transaction.

When I push back on “do what you love,” I’m not saying hate your job. That’s not the point and it’s not the answer.

If your job is making you miserable, that matters. Misery is a signal. The question is what it’s signaling. We only have two cultural scripts for this. Passion or martyrdom. Either you’re chasing your calling or you’re grinding through misery and calling it hustle. Nobody talks about the third option---work that is solid, fair, reasonably engaging, and valuable precisely because it makes space for everything else. Work you don’t love every minute of but don’t dread either. Work that is good enough to fund the life you’re actually building.

That’s not settling. That’s clarity. There is enormous dignity in knowing what work is for.

The job that lets you leave at 5 PM with energy left over---that’s not a consolation prize. That might be exactly what you need. The job that pays well, treats you decently, and asks nothing of your soul after hours---that can be a gift if you’ve built something worth coming home to. The question isn’t whether you love your job. The question is whether your job works for your life.

The job was never built for this. It was built to exchange your time and skill for compensation. Everything we’ve layered on top---the belonging, the identity, the sense of mattering---that’s not in the original architecture. We added it ourselves. Or we let it be added for us. And then we’re surprised when the structure can’t hold it. When it collapses, we call it burnout. We treat it like a personal failure. We go looking for what’s wrong with us instead of what’s wrong with the expectation.

The load was just wrong for the container.

So why do some people seem genuinely lit up at work? It’s not that they found the perfect job. It’s that they arrived whole. They brought a self that wasn’t on the table to be defined or validated by the work. They cared about the mission without needing it to be their mission. They built relationships at work without needing them to be their only relationships. They did excellent work because excellence was already part of who they were---not a performance for an audience that controls their sense of worth.

Build the life first. The friendships that have nothing to do with your industry. The creative work nobody is paying you for. The sense of purpose that doesn’t appear on your LinkedIn profile. The community that would still be there if you changed jobs tomorrow.

Then bring that person to work. Watch what happens.

Work doesn’t create whole people. Whole people show up to work and light it from the inside. The direction of the energy matters---and right now, for most people, it’s running the wrong way.

So if your job is making you miserable, ask the harder question before you quit, before you spiral, before you conclude the problem is you. Ask whether you’ve built anything outside of it. Ask whether what you’re feeling is a broken workplace---or a broken expectation.

Sometimes it’s the workplace. Leave.

Sometimes it’s the expectation. That one, you carry with you.

The move that breaks the cycle is the same either way: build a real life, with real people, outside those walls. Not because work doesn’t matter. Because you matter more than what you do for money.

That’s not a radical act. But right now, it might be the most subversive thing you do.

I had a point of view sharp enough to cut. A plan. An updated professional brand that finally said out loud what I’d spent two decades saying in conference rooms to people who nodded, took notes, and changed nothing. I had that specific energy that comes from finally deciding to stop being the dog they hire to bark and then punish for biting.

Twenty years. That’s how long I’d been inside organizations trying to turn the ship. Working within systems I could see were broken, making the case in the language those systems understood—data, frameworks, business outcomes—and watching the argument land and then get quietly absorbed into the very dysfunction I was diagnosing. You learn, after enough of those moments, that the ship doesn’t want to turn. The ship has decided that staying the course is safer than admitting how far off course it already is.

So I stopped trying to turn it from the inside.

I was hanging out my own shingle. Looking for leaders who already knew something was wrong—who’d felt it in the attrition numbers, in the exit interviews nobody acted on, in the meetings where everyone performed alignment and then went back to their desks and did whatever they were going to do anyway. I wanted the ones who were done with the performance. Who wanted someone to come in, call it what it was, and help them build something that actually worked for the humans inside it.

Yesterday, I caught up with a friend for the first time since. After the pleasantries burned off, she asked: “What happened to all that?”

Here’s what I told her.

I lost the desire for a fight that felt like only I was showing up to.

The systems are broken—profoundly, expensively, quietly broken in ways that cost people their careers, their confidence, their willingness to care. I knew that then. I know it now. But knowing a building is on fire while everyone else adjusts their chair and asks about the agenda—that’s not a mission. That’s a slow erosion.

The problem wasn’t the caring. The problem was the echo.

Comfort is not a logic problem. You can’t out-data someone’s survival strategy. The workplace doesn’t resist change because it’s stupid. It resists change because it’s terrified. And terrified people don’t want a visionary—they want reassurance that the thing they’ve always done is still good enough.

I couldn’t give them that. It would have been a lie.

* * *

Her question cracked something else open.

Not what happened to my fire. But why I’d handed the definition of meaningful work over to the very systems I was trying to fix.

Somewhere between genuine and gospel, purpose got repackaged. It got put in job postings and annual reports, stitched into company values and keynote slides. It became the thing organizations use to ask more of you while offering less in return.

“We’re mission-driven” became the professional version of exposure pays the bills.

Purpose stopped being something you discovered. It became something you owed. And when the chase exhausted you, the myth made it personal—told you the emptiness was a signal to keep searching, not a signal to question the premise.

The premise being: that your employment and your meaning should be the same thing.

They were never meant to be.

* * *

So I write here.

I put the work out there—how to lead differently, how to stop participating in systems that are costing everyone something. I publish it and let it move however it moves. Maybe one reader sends it to someone. Maybe that someone passes it to a leader who reads it at 6am with coffee going cold and thinks, yes, finally, this—and picks up the phone.

Maybe not. That’s fine too.

I’m not fighting for a room that doesn’t want to be rattled. I’m building something for the people who are already rattled—who feel the dysfunction but don’t yet have the language for it, who know something is broken but have been told so many times it’s normal that they’ve started to believe it.

They’re not in every boardroom. They’re not always the loudest voice. But they exist. And when they find this work, they know it’s for them.

A lighthouse doesn’t go looking for ships to guide. It just stands there, steady, shining—whether anything is coming or not. The ships that need it find it. The ones that don’t, don’t.

That’s enough. That’s always been enough.

Not because it’s the worst thing happening in corporate America. It’s not. But because it’s a perfect little artifact of everything wrong with how we pretend to care about people at work. A Hallmark-sized case study in performative engagement disguised as culture.

You know the ritual. The card shows up in a manila folder, passed desk to desk like a classified document nobody asked for. You open it. Twelve signatures already crammed into every corner. “HBD!” and “Have a great one!” and the guy from accounting who always writes “Many happy returns” like he’s drafting a telegram from 1943.

You find the last remaining sliver of white space, somewhere between the fold and the barcode, and you write something. Not something meaningful. Something that fits. “Happy Birthday! Hope it’s a good one!” You cap the pen. You pass the folder. You move on with your life.

Process complete.

The digital version is somehow worse. Platforms like Kudoboard and Confetti removed the space constraint and replaced it with infinite room to say nothing. Now instead of twelve rushed signatures, you get forty “Happy Birthday!” tiles arranged in a cheerful grid. Same energy. More pixels. The sentiment didn’t expand with the real estate. It just got louder.

But here’s where this gets interesting. Somewhere along the way, someone in HR decided that birthday recognition was an employee engagement lever. Not a human gesture. A lever. Something to track, measure, and optimize. The birthday card became a KPI in disguise.

Companies started building birthday celebrations into their engagement platforms. Automated emails. Slack bot reminders. Calendar integrations that ensure nobody forgets, which sounds thoughtful until you realize that “nobody forgetting” and “somebody caring” are two completely different things.

The system remembers your birthday so humans don’t have to. And then we call that culture.

I’ve watched this play out at multiple companies. The birthday spreadsheet gets maintained by someone on the People team. Reminders go out the week before. A card circulates or a digital board launches. The birthday person gets a stream of notifications from colleagues who are responding to a prompt.

The whole thing runs on the same engine as the engagement survey. Automate participation. Measure completion. Call it connection.

But what about the people who don’t want it?

I’m one of them. And before you assume that makes me difficult or antisocial or allergic to joy, let me explain something. I don’t advertise my birthday on social media. Haven’t for years. Not because I’m ashamed of getting older. Because I got tired of the annual experiment in who actually remembers versus who got a notification from Facebook.

There’s a specific kind of loneliness that comes from receiving forty “Happy Birthday!” posts and knowing that thirty-nine of them were triggered by an algorithm. The one person who texted you at midnight because they actually know the date? That’s the one that matters. The rest is noise wearing a party hat.

At work, this dynamic gets even stranger. “What did you do for your birthday?” is the Monday-morning cousin of “What did you do this weekend?” Both questions sound casual. Both carry an invisible expectation that your answer will be interesting, or at least palatable. Both assume you want to share.

I don’t. Work is work and personal life is personal life. That’s not a wall I built out of coldness. It’s a boundary I maintain out of self-preservation. Because once you start performing your personal life for colleagues, the performance never stops. Every Monday becomes a small audition. Every birthday becomes a public event you didn’t organize and can’t opt out of.

I learned this early. In high school German class, we had to recap our weekends in German every Monday. Forced storytelling in a language I was still wrestling with, about a life I didn’t feel like narrating. So I made things up. Invented weekends I could conjugate. Said I went to the movies or visited some relatives because those were sentences I could construct with confidence.

The truth was simpler and less shareable. My weekends were mine. Quiet. Unstructured. Valuable precisely because nobody was watching or evaluating them. The pressure to manufacture something “worth sharing” taught me early that not every experience needs an audience.

That instinct followed me into corporate life. And the office birthday celebration is where it collides with a system that doesn’t understand boundaries it didn’t build.

At one company, I asked how to opt out of the birthday recognition program. You’d think I’d asked how to opt out of gravity. The People team was genuinely confused. Not because they were unkind. Because the system had no mechanism for someone saying “no thank you.” There was no field in the spreadsheet for “please don’t.” No toggle in the platform for “skip me.” The infrastructure assumed universal participation because the infrastructure assumed universal enthusiasm.

That’s the tell. When a system designed to make people feel valued has no way to accommodate someone who doesn’t want that particular version of value, the system isn’t about the people. It’s about itself.

This is the same pattern that runs through every chapter of broken corporate engagement. Build the process. Assume participation. Measure completion. Declare success. Never ask whether anyone actually wanted what you built.

The engagement survey does it with questions. The performance review does it with forms. The birthday card does it with cake. Different rituals, same operating system. Participation is the metric. Feeling is optional.

And the people who push back? They’re outliers. Difficult. Not team players. The system has language for people who don’t participate, and none of it is flattering.

Here’s what I want to be clear about. I am not against birthdays. I am not against kindness. I am not against colleagues who want to celebrate each other. If the person in the next office loves a big birthday moment, give them the whole production. Balloons, cake, a Slack thread that goes forty messages deep. Beautiful. That’s their thing and they deserve it.

Some people want the spotlight. Some people want a quiet acknowledgment from someone who means it. Some people want to be left alone. All three of those are valid. And a system that can only deliver option one while pretending it covers all three isn’t an engagement strategy. It’s a participation trophy for the People team.

Genuine care is the colleague who remembers that you hate public attention and sends a quiet text instead of blowing up the Slack channel. It’s the manager who asks “how do you like to be recognized?” before defaulting to the company playbook. It’s the system that builds an opt-out with the same enthusiasm it built the opt-in.

So we get the card. The bot. The automated “Happy Birthday!” from a platform that knows your date of birth but not your name pronunciation.

And we call it culture.

The birthday card industrial complex isn’t the disease. It’s the symptom. The small, frosted, annually recurring symptom of organizations that have confused systems for care, automation for attention, and participation for connection.

If you’re building a People strategy and your birthday program doesn’t have an opt-out, you haven’t built a people strategy. You’ve built a broadcasting system. And some of us would like to change the channel.

This is part 3 of a series examining how performance ratings stopped measuring performance:

Part 1: “Bonus Theater“ - How ratings inflate when managers need to move money

Part 2: “When High Standards Meet The Bell Curve“ - How ratings deflate when organizations force distributions

We’ve established that performance ratings inflate when managers need to move money through bonus channels. We’ve seen how they deflate when organizations force bell curve distributions on high-performing teams.

Same system. Opposite manipulations. Both having nothing to do with actual performance.

So what are performance ratings actually measuring?

The uncomfortable answer: Manager discretion disguised as objective assessment. Made by people who were never trained to make these judgments. Using criteria nobody can define. Producing outcomes nobody trusts.

And we’ve built entire HR infrastructures around pretending this is rigorous performance management.

The Qualification Problem

Here’s the question nobody asks: What qualifies a manager to assess performance?

Not “Do they have authority to do it?” That’s obvious. They’re the manager.

The real question: What expertise do they have in evaluating complex knowledge work? What training have they received in distinguishing excellent performance from merely good performance? What framework do they use to separate someone being difficult from someone raising difficult truths?

For most managers, the answer is: None. Zero. They were promoted because they were good at the work, not because they demonstrated any capability to assess other people doing the work.

They got a title, a team, and a template. Then HR told them to fill out the form by next Friday. Maybe they attended a two-hour training on “effective performance conversations” that taught them how to deliver ratings, not how to determine them.

That’s it. That’s the qualification.

The Inherited Framework

Performance ratings weren’t designed by organizational psychologists or performance experts. They were invented by the military during World War I to quickly sort through millions of enlisted men. The goal was simple: identify who to promote, who to deploy, and who to send home.

Then Jack Welch popularized forced ranking in the 1980s. Rank everyone. Reward the top 20%. Cut the bottom 10%. GE soared. Harvard wrote case studies. Every executive wanted the same system.

But here’s what nobody mentioned: Welch wasn’t an expert in human performance assessment. He was an executive who found a way to avoid difficult decisions about individual capability. The system looked rigorous but was actually just rigid.

And when it finally collapsed under the weight of its own contradictions, we didn’t question the qualifications of the people who’d designed it. We just rebranded it. Softened the language. Called it “continuous feedback” and “development conversations.”

Same unqualified assessors. Same inherited frameworks. Just better PR.

What Gets Measured vs. What Gets Rated

Let’s be precise about what managers are actually doing when they rate performance:

What they think they’re measuring:

• Quality of work output

• Impact on business results

• Demonstration of company values

• Growth and development

• Collaboration and teamwork

What they’re actually rating:

• How comfortable the person makes them feel

• How much the person looks and acts like them

• How well the person navigates office politics

• How much the person challenges their decisions

• How easy the person is to manage

The first list requires expertise in performance assessment. The second list requires nothing but personal preference.

And most managers don’t know the difference. They genuinely believe their comfort level with someone is an accurate proxy for that person’s performance. They’ve never been taught to distinguish between “this person makes me nervous” and “this person is performing poorly.”

So they rate based on comfort and call it performance management.

The Calibration Theater

Organizations know this is a problem. So they invented calibration meetings to create the illusion of objectivity.

Eight managers sit around a table with laptops open, ostensibly ensuring “consistency across ratings.” In reality, they’re negotiating human worth like they’re dividing up a pizza.

Watch what actually happens:

Manager A says Sarah “far exceeded” this year. Manager B questions whether that’s too high. Manager A defends with examples. Manager B backs down because who’s going to argue when someone builds a compelling case?

But here’s what nobody asks: What qualifies this committee to override individual managers who actually work with these people daily? What expertise does this group have in evaluating work they don’t see, in contexts they don’t understand, with people they barely know?

None. But they have authority. And we’ve confused authority with expertise.

The calibration meeting isn’t about creating objective assessments. It’s about distributing accountability so no single person has to own the decision. It’s about making subjective judgments feel rigorous through process.

It’s performance theater. And everyone in the room knows it.

The Three Types of Unqualified Assessors

The system is filled with people making qualification decisions they’re not equipped to make. They fall into three categories:

Type 1: The Survivor

Been at the company for seven years. Survived three reorganizations. Knows how to avoid getting fired. Got promoted because they were safe, reliable, never rocked the boat.

Now they’re managing people whose job it is to rock boats. They’re assessing performance they can’t recognize and capabilities they don’t possess. When someone moves too fast or pushes too hard, the Survivor slows them down. Not because the performance is bad, but because change feels risky.

They rate based on comfort. They call it “collaboration.”

Type 2: The Politician

Knows the game. Understands that ratings are currency. Has learned to write compelling paragraphs that make weak performance sound strategic and strong performance sound concerning.

They inflate ratings for people they want to retain. Deflate ratings for people they want to move out. Use performance language to justify decisions that are really about politics, budget, or personal preference.

They rate based on strategy. They call it “talent management.”

Type 3: The Believer

Actually thinks the system works. Faithfully fills out the forms. Documents conversations. Builds cases. Attends calibration meetings and genuinely tries to be fair and consistent.

But they’ve never questioned what qualified them to make these assessments. They’ve never examined whether the criteria they’re using actually correlate with performance. They’ve never considered that their good intentions don’t compensate for lack of expertise.

They rate based on process. They call it “rigorous performance management.”

None of these people are malicious. They’re all working within a system they inherited. But none of them are qualified to make the decisions they’re being asked to make.

What Qualification Actually Requires

If organizations were serious about performance assessment, here’s what they’d require:

Training in cognitive bias: Understanding how first impressions, similarity bias, recency bias, and halo effects distort judgment. Being able to separate performance from likability, impact from visibility, growth from comfort.

Expertise in the work: Deep understanding of what excellent performance actually looks like in this role, in this context, with these constraints. Not just “I know it when I see it,” but “I can articulate why this is excellent and that is merely good.”

Track record of development: Evidence of having grown people who went on to do great things. Ability to spot potential others miss. Skill in distinguishing between someone struggling and someone challenging.

Separation from outcome bias: Ability to assess performance independent of results. Understanding that excellent decisions can have poor outcomes and poor decisions can have lucky outcomes.

Most importantly: Humility about the limits of assessment. Knowing when someone is qualified to judge and when they’re not. Being able to say “I don’t know” instead of forcing a rating.

How many managers meet these standards? Almost none.

How many organizations require them? Zero.

The Honest Alternative

If performance ratings are really just manager discretion—and they are—then organizations need to be honest about it.

Stop pretending there’s an objective standard. Stop calibrating as if there’s a scientific method. Stop documenting cases as if they prove something.

The alternatives:

Option 1: Separate development from compensation

Development conversations happen continuously. Real-time coaching. Immediate feedback. Honest discussions about growth, gaps, and what’s next.

Compensation decisions happen separately. Based on manager judgment, market rates, budget constraints, retention risk, and business value. No ratings required.

The two serve different purposes. Stop forcing them into the same conversation.

Option 2: Admit it’s discretion and own it

Give managers a compensation pool and let them distribute it. Their decision. Their accountability. Their justification to their team.

Direct conversation about value, contribution, and compensation. No ratings. No paragraphs. No cases.

At least then it’s honest about what the system actually is.

Option 3: Qualify the qualifiers

If we’re going to keep performance ratings, then actually train people to give them. Not two-hour workshops on “difficult conversations.” Real training in performance assessment, cognitive bias, fair evaluation, and human development.

Require evidence that managers can actually develop people before giving them authority to rate people. Make qualification for assessment an actual requirement, not an assumed capability.

And accept that most current managers won’t meet the standard. Because they were never supposed to. They were promoted for doing the work, not for assessing others doing the work.

The Pattern Across All Broken Systems

Here’s what connects all of this—the bonus manipulation, the bell curve constraints, the unqualified assessors:

We keep letting people who’ve never been trained to make these decisions have authority to make these decisions.

The manager who inflates ratings to move money? Never trained in compensation strategy.

The committee that forces bell curves on high-performing teams? Never trained in statistical validity.

The calibration room full of executives overriding individual assessments? Never trained in performance evaluation.

It’s the same pattern everywhere: Authority without expertise. Process without qualification. Judgment without training.

And we call it performance management.

What Dies When We Get This Right

The comfortable lie that ratings are objective. The illusion that authority equals expertise. The pretense that process creates rigor.

The protection of managers who’ve learned to rate based on comfort instead of capability. The systems designed to avoid difficult conversations while claiming to enable them.

Most importantly: The acceptance that this is just how it works. That performance ratings will always be subjective, so we might as well dress them up in objective language and hope nobody notices.

What Lives When We Connect New Dots

Honest conversations about what’s actually happening when performance gets assessed. Separation of development from compensation. Training for assessors who actually need to assess.

Recognition that manager discretion isn’t inherently bad—it’s just bad when organizations pretend it’s something else. Acknowledgment that most managers aren’t qualified to make these judgments because they were never supposed to be.

And most radically: The possibility of building something better. Something that actually develops people instead of just documenting them. Something that separates growth conversations from compensation decisions. Something that admits what it is instead of pretending to be what it isn’t.

The Choice Every Manager Faces

Every time a manager fills out a performance rating, they’re making a choice:

Participate in the fiction that this is objective assessment. Play the game. Write the paragraphs. Build the cases. Pretend comfort level with someone is the same as their performance quality.

Or admit what’s actually happening: Making a subjective judgment based on limited information, personal preference, and inherited frameworks. Using discretion they were never trained to exercise. Producing ratings that everyone knows don’t actually measure performance.

The system wants the first choice. It needs people to keep playing along. To keep filling out the forms. To keep pretending the emperor has clothes.

But teams need the second choice. They need honesty about what these ratings actually are. They need admission that the system is broken. They need permission to stop pretending that numbers next to their names mean anything real.

Performance ratings aren’t performance management. They’re discretion dressed in objectivity. Authority masquerading as expertise. Process pretending to be rigor.

And until organizations are willing to admit that, the cycle continues: ratings inflate for bonuses and deflate for distributions, while everyone pretends something meaningful is happening about human development.

The ratings aren’t the problem. The unqualified people making them are.

And that includes most managers currently in the system.

Then review season arrives. The directive lands: bell curve distribution. Only 10% can exceed expectations.

Here’s the problem nobody will say out loud: If a manager’s standards are higher than the organization’s, and the team meets those standards, what the hell does “exceeds expectations” even mean?

I’ve watched this play out more times than I can count. The math never works. The system always wins. And the people who built the best teams always pay the price.

The Two Interpretations

Interpretation 1: The bar is higher for the team

That manager’s “Exceeds Expectations” means something different than another manager’s “Exceeds.” The team operates at a level where meeting that bar already exceeds the organizational standard. So the 10% who exceed are the absolute top performers in the entire company.

This interpretation makes logical sense. Different contexts, different standards, different meanings for the same rating.

But it creates an absurd outcome: The entire high-performing team gets rated lower than mediocre teams with lower standards. Because they’re being compared to each other instead of to organizational reality.

The consequence? The best people look average on paper. They get paid like average performers. They get promoted slower than people on easier teams. They eventually figure out the game and leave for teams where the bar is lower and the ratings are higher.

Excellence gets punished for being excellent.

Interpretation 2: They’re all Exceeds Expectations

If the entire team is performing above organizational standards—and they are, because standards were built higher than everyone else’s—then by definition, they’re all exceeding expectations. The organizational expectation. The baseline that everyone else is measured against.

This interpretation makes performance sense. A team where everyone operates at a level most teams only dream about. That’s the whole point of high standards and real accountability.

But it violates the bell curve. It suggests that the manager either can’t differentiate performance (which is false—performance management happens every day), or that ratings are being inflated to protect the team (also false—the standards are provably higher).

The consequence? The manager gets told to “be more realistic about ratings.” To “ensure proper differentiation.” To force 90% of the team into lower rating categories regardless of their actual performance compared to the organization.

Building excellence becomes a problem that needs correction.

The Real Question Nobody Asks

What qualified any organization to demand a bell curve in the first place?

Did they study team dynamics? Do they understand performance distribution in high-functioning versus low-functioning teams? Have they researched whether forcing distributions improves or destroys performance cultures?

Across every company I’ve worked with, the answer is no. They wanted a clean way to limit compensation costs and create the illusion of objectivity. The bell curve isn’t about performance. It’s about budget management wrapped in statistical language.

And then they ask managers to destroy the cultures they built to satisfy a mathematical abstraction that has nothing to do with how teams actually work.

What the Bell Curve Actually Measures

Here’s what the 10% cap reveals: The organization believes that excellence is normally distributed. That in any group of people, most will be average and only a few will be great.

This is true for random populations. It’s not true for deliberately constructed high-performing teams.

When a manager sets high standards, performance manages continuously, builds peer accountability, makes mediocrity uncomfortable—they change the distribution. The team is no longer a random sample. It’s a filtered, developed, optimized group.

The bell curve doesn’t apply. It’s the wrong statistical model for the population that was created.

But the organization doesn’t care about statistical validity. They care about limiting the number of people who get high ratings. The curve is a constraint tool, not an assessment tool.

So the manager faces a choice: Preserve the integrity of the team’s actual performance, or comply with a distribution requirement that treats high performers like they’re average.

The Manipulation Managers Are Asked to Perform

Here’s what’s actually happening: Organizations are asking managers to lie.

Not explicitly. They’ll use language like “appropriate differentiation” and “realistic assessment” and “consistent standards.” But what they mean is: pretend some of the high performers aren’t high performers so the math works out.

The directive is to take people who exceed organizational standards and rate them as “meeting expectations” because the 10% quota of “exceeds” has already been filled.

This isn’t performance management. It’s performance theater designed to make compensation decisions look like merit-based assessments.

Managers get asked to tell people who are objectively outperforming the organization that they’re just “meeting expectations.” To rate people lower than their performance warrants so the distribution curve stays clean.

The Impossible Position

There’s no winning move here.

Rate the entire team as “Exceeds”—which might be accurate compared to organizational standards—and the manager gets told they can’t differentiate performance. Credibility gets questioned. HR forces calibration sessions where ratings get adjusted to fit the curve.

Comply with the 10% cap—rating 90% of a high-performing team as “Meets”—and the manager is lying to their people. Telling them their performance is average when it demonstrably isn’t. Teaching them that excellence doesn’t matter if too many people achieve it.

Either way, the team loses. The only winner is the bell curve, which stays intact regardless of performance reality.

What This Reveals About Standards

Here’s the uncomfortable truth: High standards are only valuable if the organization recognizes them.

A manager can build the best team in the company. Set bars that make other teams look amateur. Create a culture where mediocrity can’t survive.

But if the organization forces that team to be rated on a curve designed for average teams with average standards, then those high standards become a liability. It gets harder for people to get recognized, not easier.

The perverse incentive is clear: the system rewards managers who lower their standards. Who make teams easier to manage. Who let some mediocrity creep in. That way, when review season comes, there are clear “Meets Expectations” candidates who make the “Exceeds” ratings more defensible.

The system rewards managers who build worse teams because the rating distribution looks better.

The Question That Breaks the System

Here’s the question that stumps every HR team it gets put to: “If a manager builds a team where everyone operates above organizational standards, what rating should they receive?”

The honest answer is “Exceeds Expectations.” The policy answer is “Most should be Meets, because bell curve.”

HR will say something about “relative performance within the team” or “differentiation at the margin” or “comparing people to each other.”

Which means: The system doesn’t actually care about organizational standards. It cares about limiting the number of high ratings.

And that reveals what the whole system is really about: Budget control disguised as performance management.

How Managers Navigate It

There are three paths. None of them are good.

Option 1: Comply and manage the damage

Rate 10% as “Exceeds” and explain to the other 90% that “Meets Expectations” means something different on this team. That they’re actually exceeding organizational standards, but the rating system can’t reflect that.

The team hears: “You’re being punished for being on a good team.”

Some accept it. Most start wondering if they’d be better off on easier teams where the same performance gets higher ratings.

Option 2: Fight it and document reality

Rate the team based on organizational standards, not internal distribution. Document how each person’s performance compares to the broader organization. Make the case that forcing a bell curve on a high-performing team is statistically invalid and culturally destructive.

HR pushes back. The manager gets told to “recalibrate.” Credibility gets questioned.

But at least it’s honest. And it creates a record that shows the absurdity of applying normal distributions to non-random populations.

Option 3: Name the game and play it anyway

Be transparent with the team about what’s happening. The organization requires a bell curve. Here’s how ratings are being distributed and why. Compensation will reflect the actual assessment of performance, not the rating category.

Then use bonus and merit increases to reflect actual performance differentiation. Let the ratings be the fiction they are, and make the money tell the truth.

The team appreciates the honesty. They still hate the system. But they trust that their manager sees them clearly.

What Should Happen Instead

If organizations actually cared about high performance instead of comfortable distributions, here’s what they’d do:

Abandon forced distributions. Let managers rate people based on actual performance against actual standards. If a team full of high performers all exceeds expectations, that’s a success story, not a statistical problem.

Calibrate standards, not ratings. Instead of forcing rating distributions, ensure managers are using consistent definitions of what “Meets” and “Exceeds” mean. Focus on the bar, not the curve.

Separate ratings from compensation. If the real goal is budget management, say so. Give managers bonus pools and let them distribute based on performance. Stop pretending ratings are about assessment when they’re really about cost control.

Reward managers who build high-performing teams. The organization should be celebrating when an entire team exceeds standards. That’s what good management looks like. Instead, those managers get told to make their high performers look average so the distribution stays neat.

The Answer to the Question

So: Is the bar higher for “Exceeds Expectations” on a high-standards team? Or are they all “Exceeds Expectations”?

The honest answer: They’re all exceeding organizational expectations. That’s what happens when a team is built with higher standards than everyone else’s.

The political answer: Only 10% can be rated that way, so 90% get told their performance is average even when it isn’t.

The real answer: The question reveals how broken the system is. Because any performance management system that punishes managers for building high-performing teams is a system designed to protect mediocrity, not recognize excellence.

The team isn’t the problem. The bell curve is.

And until organizations admit that forcing distributions on non-random populations is statistically invalid and culturally destructive, managers are stuck choosing between honest assessment and policy compliance.

The Pattern Emerges

Here’s what we’ve learned across these two systems:

When managers need to move money and merit pools are dry, they inflate ratings. “Far Exceeded” becomes a compensation tool, not a performance measure.

When organizations need to control costs and force distributions, they deflate ratings. “Meets Expectations” becomes a budget constraint, not a performance assessment.

Same rating system. Opposite manipulations. Both serving goals that have nothing to do with actual performance.

Which raises the obvious question: If ratings inflate when we need money and deflate when we need distributions, what are they actually measuring?

Not performance. That’s clear.

So what are performance ratings really? And who’s actually qualified to assign them?

Next in this series: “What Performance Ratings Actually Are” - The uncomfortable truth about who’s making these decisions and why they’re not equipped to make them.

I’ve watched this pattern repeat across companies for over a decade. Merit increase pools dry up. Managers still need to retain people or reward work. So they inflate performance ratings to move money through the bonus channel instead. A “Far Exceeded” rating stops being about performance and becomes about compensation strategy.

The mechanism is simple. Most companies tie bonus percentages to rating tiers:

• Meets: 5-8% bonus

• Exceeds: 10-15% bonus

• Far Exceeds: 18-25% bonus

When merit budgets get constrained to 2-3%, suddenly every manager discovers that half their team “far exceeded” expectations this year. Not because performance improved. Because the rating became the only lever left to move money.

The Qualification Problem

Nobody is equipped to challenge these ratings. The criteria for “Far Exceeded” is typically vague: “Consistently delivers exceptional results beyond role expectations.”

What does that mean? Anything the manager can write a paragraph about. And any manager can write a compelling paragraph about almost anyone.

Watch what happens in calibration meetings:

Manager A: “This person far exceeded this year. They rebuilt our client portal.”

Manager B: “That was in their job description though.”

Manager A: “They did it three months early and reduced customer complaints by 80%.”

Manager B: Silence. Because who’s going to argue with that?

But here’s what nobody asks: Did this person actually far exceed expectations, or did their manager just learn how to describe normal excellent work using superlatives?

The system creates no way to tell the difference. There’s no objective standard. No independent verification. No expertise required to make the assessment. Just a manager’s ability to build a case, and a committee’s willingness to accept it.

The Manipulation Cascade

When ratings become compensation tools instead of performance assessments, the whole system collapses:

The inflation problem: If everyone can be rated “Far Exceeded” with the right paragraph, then nobody is actually far exceeding anything. The rating stops measuring performance and starts measuring manager advocacy skills.

The credibility erosion: Employees watch someone get “Far Exceeded” for work that looks identical to work that got someone else “Exceeded” last year. They learn the rating is arbitrary. They stop trusting the system.

The expectation spiral: This year’s “Far Exceeded” becomes next year’s baseline. Rating someone lower after a Far Exceeded triggers a difficult conversation nobody wants to have. So ratings can only go up or stay flat. The rating scale loses meaning.

The quiet mediocrity: The easiest people to rate as Far Exceeded are the ones who don’t threaten anyone. The ones who make managers comfortable. The ones who hit their numbers without making leadership nervous. Meanwhile, the people who actually push boundaries, who take risks, who challenge broken systems—they’re “difficult to rate” because their impact is harder to defend in a paragraph.

What Actually Happens

A manager needs to get someone more money. The merit pool is 2%. On a mid-range salary, that 2% lands somewhere around $1,900 a year. $158 a month before taxes.

So the manager runs the bonus math instead:

• Exceeds (12% bonus): $11,400 one-time

• Far Exceeds (22% bonus): $20,900 one-time

The difference is $9,500. To get that same money through merit increases would require budget approval from three levels up and trigger equity reviews across the entire team.

Or the manager can just write a better performance rating paragraph. Same money, zero scrutiny.

So that’s what happens. The rating gets inflated. The bonus gets paid. The employee gets their money. And nobody admits that the “Far Exceeded” rating was a compensation vehicle, not a performance assessment.

The Second-Order Costs

This manipulation creates damage beyond just rating inflation:

Loss of signal: When ratings become negotiable, the ability to identify actual high performers disappears. The data becomes meaningless. It can’t be used for succession planning, promotion decisions, or talent development because it’s been corrupted by compensation strategy.

Manager skill atrophy: Instead of learning to develop people or have difficult performance conversations, managers learn to game rating language. They get good at writing compelling paragraphs, not at building high-performing teams.

Expectation confusion: Employees don’t know what excellence actually looks like because the rating system doesn’t reflect it. They learn to optimize for whatever gets rated highly, which might have nothing to do with what the organization actually needs.

Trust destruction: Once employees figure out the game—and they always do—they stop believing anything leadership says about performance, merit, or fairness. The cynicism spreads.

The Real Problem

The bonus distribution system isn’t broken because ratings are subjective. It’s broken because we’re using performance ratings to solve a compensation flexibility problem.

Companies want to reward people differentially without committing to permanent salary increases. They want discretion to move money around based on business needs, retention risks, and manager judgment. But they can’t admit that’s what they’re doing because it would expose how arbitrary the whole system is.

So they wrap it in performance language. They create rating tiers and calibration processes and documentation requirements. They build elaborate theater around “objective assessment” and “consistent standards” and “fair evaluation.”

But underneath, it’s just managers trying to get people money using the only lever they have left. And that lever happens to be a performance rating system that was never designed to be a compensation tool.

The Other Side of the Coin

But here’s what makes this even worse: Rating inflation isn’t the only way the system breaks.

While some managers are inflating ratings to move money, other managers are being forced to deflate ratings to fit distribution requirements. Bell curves that demand “only 10% can exceed expectations” regardless of actual team performance.

Ratings gaming upward to solve compensation problems. Ratings forced downward to solve distribution problems. The same rating system. The same performance categories. Completely opposite manipulations.

Which means the rating has stopped meaning anything at all.

It’s not measuring performance. It’s measuring manager strategy, organizational constraints, and compensation politics. The number in someone’s file tells them nothing about their actual work and everything about the games being played around them.

What It Should Be

If bonuses are going to stay tied to ratings, the industry needs to admit what’s actually happening: managers are being given discretion to distribute money based on their judgment.

That’s fine. But it should be honest. Stop pretending there’s an objective standard for “Far Exceeded.” Stop calibrating ratings as if there’s a scientific method. Stop documenting cases as if they prove something.

The simpler version: Give managers a bonus pool and let them distribute it. Their decision. Their accountability. Their justification to their team.

No ratings required. No paragraphs. No cases. Just “Here’s your bonus. Here’s why. Here’s what I expect next year.”

At least then it’s honest about what the system actually is: manager discretion over compensation. Not performance management. Not merit recognition. Just money distribution based on human judgment.

Because that’s what it’s always been. It just got dressed up in performance language to make it feel fair.

It isn’t. And everyone knows it.

The only question is whether anyone’s ready to stop pretending otherwise.

Next in this series: "The Bell Curve Trap" - What happens when you build a high-performing team and the organization forces you to rate 90% of them as "meeting expectations."

In this article, I wrote about surviving mergers by being the Hero—the person who solves problems, builds bridges, and makes things work when everything’s falling apart.

But I left something out. Something that’s been eating at me since I hit publish.

The Asshole Problem isn’t what you think it is.

The Obvious Jerks Are Easy

You might be brilliant. You might deliver results. But if you’re also toxic, condescending, or impossible to work with? You’re on borrowed time.

Mergers are the perfect excuse to clean house. Leadership won’t tolerate jerks when they’re rebuilding culture. Being great at your job isn’t enough if you’re terrible at being human.

Excellence without humanity is just expensive liability.

That part’s obvious. The person who insults people in meetings, who openly dismisses others’ ideas, who makes people feel stupid—that person gets identified and dealt with. Eventually.

But here’s the tricky part: you might not actually be an asshole. You might just have high standards. You might see problems clearly and name them directly. You might challenge bad ideas and push for better solutions. You might move fast and expect others to keep up.

And some people—especially people who are insecure, conflict-averse, or protective of mediocrity—will call that assholery.

The Real Danger Is Subtle

The real danger isn’t the obvious jerk who insults people in meetings. That person gets identified and dealt with quickly.

The real danger is the subtle toxicity that looks like excellence. The behaviors that seem professional on the surface but leave people feeling diminished, invisible, or stupid.

The subtle patterns that destroy trust:

You ask someone to present their work in a meeting, then spend the entire time on your laptop. When they finish, you look up and say, “Sorry, can you start over? I want to make sure I catch this.” You weren’t intentionally rude. You were just busy. But you just told that person their work wasn’t worth your attention.

You consistently “build on” other people’s ideas in meetings without acknowledging they said it first. “I love what Sarah started with, and what if we took it further and...” becomes “So here’s what I’m thinking...” You’re not stealing credit intentionally. You’re just excited about the idea. But Sarah now wonders if anyone noticed she said it first.

You send meeting invites without context or agendas. People show up not knowing why they’re there or what you need from them. When they ask for clarity, you say, “Let’s just jam on it and see where we land.” You think you’re being collaborative. They think you’re wasting their time because you didn’t prepare.

You respond to questions with questions that make people feel like they should have known better. “What do you think we should do?” sounds like you’re coaching. But if the person already felt uncertain enough to ask, you’ve just made them feel stupid for not having the answer.

You consistently redirect conversations to your experience. Someone shares a challenge and you respond with, “Oh yeah, when I dealt with that at my last company...” You’re trying to be helpful by sharing context. But you just made their problem about you.

You send messages after hours and on weekends, not demanding immediate responses but creating an ambient pressure. “Just thinking about this and wanted to share...” at 11 PM. You’re just excited about the work. They’re now anxious about whether you expect them to be working too.

These Patterns Aren’t Obvious Assholery

They’re death by a thousand paper cuts.

The person doing them often has no idea they’re having this effect. They’re not trying to be dismissive or condescending or controlling. They’re just... not paying attention to their wake.

And that’s the problem. Because intent doesn’t matter when impact is the issue.

The Test Most People Fail

Do people bring you problems or do they solve them without telling you? If your team is constantly coming to you for input, great. If they’re solving things without involving you, pay attention. They might be taking initiative. Or they might be avoiding you.

Do people speak up in meetings when you’re there? Or do they stay quiet and have the real conversation after you leave? If you’re getting silence followed by sidebar conversations, that’s not respect for your authority. That’s people protecting themselves from you.

Do people volunteer for projects you’re leading? Or do they find reasons why they’re too busy? If you’re always short on volunteers and long on excuses, you might be the reason.

When you give feedback, do people engage with it or do they just nod and leave? If every development conversation ends with “thanks for the input” and no follow-up questions, they’re not learning from you. They’re enduring you.

The Difference Between High Standards and Toxicity

High standards: “This isn’t quite there yet. Here’s specifically what needs to improve and why it matters.”

Subtle toxicity: “Hmm. This isn’t what I was expecting.” (Then moving on without clarity about what was expected.)

High standards: “I need this to be excellent because it’s going to the executive team. Let’s make sure we’re representing our best work.”

Subtle toxicity: “I guess this is fine for now. We can always revise it later if needed.” (Implying it’s not actually fine but not saying what’s wrong.)

High standards: “I disagree with this approach. Here’s my concern and here’s what I think we should consider instead.”

Subtle toxicity: “Interesting. I’m not sure that’s the direction I would have gone.” (Casting doubt without offering an alternative.)

See how subtle it is? The toxic versions aren’t obviously cruel. They’re just vague enough, dismissive enough, unclear enough to make people doubt themselves while giving you plausible deniability.

You Can Have High Standards Without Making People Feel Small

The person with high standards says: “This is good work and it’s not ready yet. Here are the three things that need to change and here’s why they matter. Let me know if you want to talk through any of this.”

The subtle toxicity says: “I think we need to take another pass at this.” (No specifics. No timeline. No clarity. Just ambient disappointment.)

The person with high standards raises the bar and helps people reach it. The subtle toxic person raises the bar and watches people struggle to figure out where it is.

Watch Your Patterns, Not Just Your Moments

You might be great in any individual interaction. Patient, thoughtful, clear. But if you’re consistently late to meetings other people organized, consistently distracted when others are presenting, consistently “forgetting” to include certain people in decisions that affect them—your patterns are telling a story your words aren’t.

People don’t leave jobs because of one bad interaction. They leave because of the accumulated weight of small slights that add up to feeling disrespected.

Read the Room—And Adjust Your Approach

During a merger, everyone’s on edge. People are defensive. Anxious. Protecting their turf. Worried about their jobs. In that environment, even your normal operating mode might land differently.

The direct feedback that usually works might feel like an attack. The high standards that usually motivate might feel like criticism. The fast pace that usually energizes might feel like pressure.

That doesn’t mean you should lower your standards or slow down or stop being direct. It means you need to check your wake more carefully. Add more context. More acknowledgment. More humanity.

“I know we’re all stressed and this is tough” isn’t soft. It’s strategic. It’s acknowledging reality before you ask people to do hard things in that reality.

The People Who Weaponize “Difficult”

Some people will call you difficult because you won’t let them slide on subpar work. They’ll call you intense because you ask hard questions. They’ll call you demanding because you expect follow-through.

That’s not about you. That’s about them protecting their comfort.

But if multiple people—especially people you respect—are giving you the same feedback, pay attention. “You’re hard to work with” from one person protecting mediocrity is noise. The same feedback from three different high performers is signal.

You might be right about the work. But if you’re losing people in how you land your point, you’re limiting your own effectiveness.

Managing Your Head When Everything’s Uncertain

Mergers mess with your emotions. That’s not a character flaw. That’s being human. The uncertainty is real. The anxiety makes sense. Your fear about the future is valid.

But Heroes don’t pretend they’re not scared. They just don’t let the fear make their decisions.

Separate what you know from what you’re imagining.

Your brain will catastrophize. It’ll spin worst-case scenarios on repeat. Most of them won’t happen. Write down what you actually know versus what you’re worried might happen. The list of facts is usually much shorter and less terrifying than the list of fears.

What you know: the merger is happening, some roles will change, decisions are being made.

What you’re imagining: you’ll definitely get fired, your entire team will be eliminated, your career is over, you’ll never find another job.

See the difference? One is information you can work with. The other is panic masquerading as prediction.

Control what you can control.

You can’t control the merger timeline. You can’t control who makes the final decisions. You can’t control whether your role survives exactly as it is.

You can control how you show up. What you deliver. How you treat people. The effort you put in. The relationships you build. The problems you solve.

Focus there. Not because it guarantees anything, but because it’s the only place your energy actually matters.

Give yourself permission to feel it, then get back to work.

You’re going to have bad days. Days when the uncertainty feels crushing. When you can’t focus. When every conversation feels loaded with subtext about who’s staying and who’s going.

Feel it. Don’t stuff it down. Don’t pretend you’re fine when you’re not. Give yourself ten minutes to be anxious, frustrated, scared. Then get back to being the Hero.

The person who never admits they’re struggling isn’t strong. They’re brittle. Real strength is feeling the fear and doing the work anyway.

Find your people and be honest with them.

You don’t have to perform composure all day, every day. Find a few people you trust—inside or outside the organization—and be real with them. “This is hard. I’m worried. I don’t know what’s going to happen.”

Honesty isn’t the same as spiraling. Heroes don’t do this alone. They just choose carefully who they’re vulnerable with.

Remember: this is temporary.

Mergers feel endless when you’re in them. But they’re not. Decisions will get made. The org chart will settle. Life will normalize. This acute uncertainty has an expiration date.

You won’t feel this way forever. The person who can hold onto that truth while everyone else is spiraling has a real advantage.

And here’s the part people forget: once decisions get made, you get to make yours too. Maybe they keep you and the role is great. Maybe they keep you and the role sucks. Maybe they cut you and you take the severance and find something better.

But you have power in this. You don’t have to wait for someone else to seal your fate. You can look at what they’re offering and decide if you want it. You can start exploring options now. You can build your exit strategy while you’re building your survival strategy.

The Hero isn’t just someone who survives the merger. It’s someone who positions themselves to have choices when the dust settles. That’s the real win.

What Hero Leaders Say to Their Teams

If you’re leading people through this merger, they’re looking to you for stability. Not false promises. Not fake positivity. Stability. Here’s what that sounds like.

“I don’t have all the answers, and I won’t pretend I do.”

Your team knows when you’re blowing smoke. Don’t insult them by pretending you know more than you do. Admit the gaps in your knowledge. It won’t make them trust you less. It’ll make them trust you more.

“I don’t know yet what the final structure will look like. When I know, you’ll know. Until then, here’s what I do know...”

“Here’s what I can tell you.”

Share what you actually know. Even if it’s limited. Even if it’s not what they want to hear. Uncertainty is harder than bad news. Give them whatever solid ground exists.

“I know our team’s work is critical to the transition. I know we’re being evaluated on how we perform during this period. I know I’m fighting for this team in every conversation that matters.”

“Here’s what we’re going to focus on.”

Give them something concrete to channel their energy toward. Not busy work. Real work that matters. Work that demonstrates value. Work that keeps them visible and relevant.

“We’re going to make sure every project we touch runs smoothly. We’re going to document our impact. We’re going to be the team other teams want to work with. That’s what we can control.”

“I see you, and I’m with you.”

Acknowledge that this is hard. That the uncertainty sucks. That they’re doing great work in terrible conditions. Don’t minimize what they’re feeling. Validate it.

“I know this is exhausting. I know you’re worried. I’m worried too. But I also know you’re showing up every day and doing work that matters. That doesn’t go unnoticed.”

“We’re going to get through this together.”

Don’t make promises you can’t keep about who will stay or what roles will exist. But promise what you can: that you’re in it with them. That you’ll be honest. That you’ll fight for them. That you won’t disappear when things get hard.

“Whatever happens, I’m not leaving you in the dark. We’ll figure this out together. I’ve got your back.”

“Keep doing what you do best.”

Remind them that their job is still their job. That the work still matters. That performing well during chaos is how you prove you’re worth keeping.

“The merger doesn’t change what makes you valuable. Keep solving problems. Keep delivering. Keep being the person this team counts on. That’s how we make it through.”

What Not to Say

Don’t lie. “Everything’s going to be fine” when you don’t know that is worse than saying nothing.

Don’t overpromise. “No one on this team is getting cut” when you can’t guarantee that destroys trust forever.

Don’t deflect. “Just focus on the work” without acknowledging their fears makes you seem tone-deaf.

Don’t disappear. Your team needs to see you present and engaged, not hiding in your office avoiding the hard conversations.

Don’t fake confidence. There’s a difference between “I believe we’ll be okay” and “I’m certain nothing bad will happen.” One is leadership. One is delusion.

The Bottom Line

Excellence doesn’t require making people feel stupid. High standards don’t require vague disappointment. Moving fast doesn’t require leaving people behind.

The Hero makes people better. The subtle toxic person makes people doubt themselves.

And during a merger, the person who destroys confidence—even unintentionally—is just as much a liability as the obvious jerk who insults people in meetings.

Maybe more, because at least the obvious jerk gets dealt with. The subtle toxicity just... accumulates.

Check your wake. Not just your words.

Because even if you survive the merger by being brilliant, you won’t survive it by making everyone around you feel small.

Your move.

Claude is AI and can make mistakes.
Please double-check responses.

You get to decide which one you are.

The Four Types Mergers Create

The Hero: Sees problems, builds solutions, makes leadership’s job easier. Gets kept.

The Squeaky Wheel: Complains loudly, offers nothing useful, drains energy. Gets cut.

The Ghost: Does solid work, stays quiet, gets forgotten. Gets reassigned or eliminated.

The Asshole: Brilliant but toxic. Creates value, destroys culture. Gets managed out eventually.

Your goal? Be the Hero. The one who makes things work while everyone else is panicking.

What Heroes Do During Mergers

They see gaps and fill them. Don’t wait for someone to tell you what’s broken. Notice it. Fix it. Document the before and after. Make yourself indispensable by solving the problems leadership doesn’t have time to see.

They translate chaos into clarity. Mergers create confusion. Heroes take messy situations and make them understandable. They answer questions before they’re asked. They create clarity when everyone else is creating noise.

They build bridges, not walls. The teams merging don’t trust each other yet. Heroes connect people. They introduce the right person to the right problem. They make collaboration easier, not harder.

They stay calm when everyone else is spiraling. Anxiety is contagious. So is composure. Heroes don’t panic. They don’t catastrophize. They stay grounded and help others do the same.

They make their boss’s job easier. Your manager is drowning right now. Don’t add to the pile. Anticipate needs. Deliver without drama. Be the person they can count on when everything else feels unstable.

What Heroes Don’t Do

They don’t complain without solutions. Yes, mergers suck. Yes, things are uncertain. No, your Slack rants aren’t helping. If you see a problem, bring a fix. Or stay quiet.

They don’t hoard information. Knowledge isn’t power during a merger—collaboration is. Share what you know. Help others succeed. Your job security isn’t built on keeping secrets.

They don’t play politics. Mergers bring out the worst in some people. Don’t be one of them. Don’t backstab. Don’t gossip. Don’t position yourself by tearing others down.

They don’t wait to be told what to do. Initiative matters more during mergers than at any other time. Don’t sit around waiting for instructions. Figure out what needs to happen and start doing it.

The Bare Minimum Will Make You Invisible

When uncertainty hits, most people’s instinct is to put their head down and just do their job. Keep quiet. Don’t rock the boat. Wait for the dust to settle.

That feels safe. It’s not.

The person who does exactly what’s asked and nothing more becomes part of the furniture. Functional but forgettable. When leadership sits down to decide who’s critical and who’s cuttable, you won’t even make it into the conversation.

You’re not bad. You’re just not memorable. And in a merger, memorable is what survives.

Doing the bare minimum puts you in the middle bucket. The “solid performer but nothing special” category. The group that gets divided up based on spreadsheet math, not strategic value. Some will stay. Some will go. It’s a coin flip. And your fate will be decided by people who barely know your name.

Here’s the brutal truth: mergers don’t reward competence. They reward demonstrated value. If your contribution isn’t visible, it doesn’t exist. If your impact isn’t documented, it didn’t happen. If leadership can’t immediately recall what you bring that others don’t, you’re replaceable.

You might be doing great work. You might be reliable, steady, someone your team depends on. But if no one outside your immediate circle knows it, you’ve made yourself vulnerable.

The person who solves problems quietly is doing important work. The person who solves problems and makes sure the right people know about it? That’s someone leadership can’t afford to lose.

The Fine Line: Standing Out Without Being a Jerk

Standing out during a merger is tricky. You need visibility, but you can’t trample people to get it. You need to demonstrate value, but you can’t do it by making others look bad.

The difference between the Hero and the Asshole is this: the Hero makes everyone around them better. The Asshole makes everyone around them smaller.

What standing out the right way looks like:

You volunteer for the project no one wants because it’s hard and messy. You figure it out. You bring others along with you. You share credit. When it succeeds, people remember you led it and also remember you made them part of the win.

You notice someone struggling and help them without being asked. You share information that makes your teammate’s job easier. You connect people who need each other. You build up your colleagues publicly and give them credit for their contributions.

You speak up in meetings when you have something valuable to add. You ask the question everyone’s thinking but no one wants to ask. You offer solutions, not just critiques. And when someone else has a better idea, you support it enthusiastically.

You take initiative, but you do it collaboratively. “I noticed this problem and started working on a fix. Want to take a look and tell me what I’m missing?” That’s leadership. “I fixed this problem you all were too slow to address” is just being a jerk with initiative.

What standing out the wrong way looks like:

You take credit for team efforts. You position your wins by contrasting them with others’ failures. You volunteer for high-visibility projects and then delegate all the actual work while keeping the spotlight.

You share information selectively, keeping the good stuff for yourself so you can be the hero. You throw teammates under the bus in meetings to make yourself look better by comparison. You backstab, gossip, and politic your way into leadership’s good graces.

You dominate every conversation. You interrupt. You dismiss other people’s ideas so yours can shine. You make sure everyone knows how busy and important and critical you are.

That might get you noticed. But it also marks you as someone who builds their success on other people’s failure. And smart leadership knows that’s not sustainable.

Standing Out as a Team Player

The best way to stand out during a merger is to become the person who makes the team work better.

Be the one who connects the dots between what the old team knew and what the new team needs. Be the translator who helps people from different cultures understand each other. Be the bridge between groups that don’t trust each other yet.

When someone’s struggling, help them. When someone’s overwhelmed, offer to take something off their plate. When someone does great work, make sure it gets recognized. When your team wins, talk about “we” not “I.”

Leadership is watching for people who make organizations stronger, not just people who make themselves look good. The person who helps five people succeed is more valuable than the person who succeeds alone.

You can be visible and collaborative. You can be ambitious and kind. You can stand out without stepping on people.

In fact, that’s the only kind of standing out that actually works long-term. Because the person who climbs by pushing others down eventually runs out of people willing to work with them. The person who rises by lifting others? They build a reputation that follows them everywhere.

How to Actually Stand Out

Document your impact—and make it visible.

Keep a running record, but not just for yourself. When you solve something, write it up. Send a brief update to your manager. Post wins in team channels. Make your contributions part of the organizational memory, not just your personal file.

The person who fixed the onboarding process six months ago but never mentioned it? They’re invisible. The person who documented the problem, the solution, and the business impact? That’s someone leadership remembers when decisions get made.

Track three things: what was broken, what you did, what changed. Numbers help. “Reduced processing time by 40%” beats “improved efficiency” every time.

Build relationships across teams—strategically.

Don’t just network randomly. Identify the people who will matter in the new structure. Who’s making decisions? Who has influence with leadership? Who’s already connected to both sides of the merger?

Then make yourself useful to them. Offer to help with their projects. Share information they need. Introduce them to people they should know. Create reasons for them to remember your name when opportunities come up.

But do it authentically. People can smell opportunism from a mile away. Help because you genuinely want things to work, not just because you’re playing chess.

Be visible without being annoying—there’s a formula.

Visibility isn’t about talking more in meetings or sending more emails. It’s about showing up when it matters and adding value when you do.

Speak up when you have something worth saying. Share work that demonstrates your capabilities. Volunteer for the projects everyone’s avoiding because they’re hard but important. That’s how you get noticed for the right reasons.

Bad visibility: dominating every conversation, taking credit for everything, making sure everyone knows how busy you are.

Good visibility: solving the problem no one else wanted to touch, helping someone else succeed publicly, being the person who can be counted on when stakes are high.

Stay adaptable—and prove it with action.

Everyone says they’re flexible. Few people actually demonstrate it. The difference is whether you resist change or help implement it.

When new processes roll out, be the first to adopt them. When priorities shift, shift with them without complaint. When the team needs someone to learn a new system or take on unfamiliar work, raise your hand.

The person who keeps saying “but we’ve always done it this way” is marking themselves for elimination. The person who says “let me figure out how to make the new way work” is marking themselves as essential.

Adaptability isn’t passive. It’s active. It’s visible. It’s choosing to be part of the solution instead of mourning the old way.

Take care of yourself—you can’t perform if you’re burned out.

Mergers create chronic stress. People make terrible decisions when they’re exhausted, anxious, and running on fumes. You need to stay sharp when everyone else is losing their edge.

That means protecting your sleep. Taking actual breaks. Saying no to the things that don’t matter so you can say yes to the things that do. Staying connected to people and activities outside work that keep you grounded.

This isn’t soft advice. This is strategic. The person who maintains their composure and judgment while everyone else is spiraling has a massive advantage.

Burnout doesn’t make you a hero. It makes you a liability. Take care of yourself like your job depends on it. Because it does.

Insurance Policy No One Talks About

Here’s the part most merger survival guides won’t tell you: everything you do to survive this merger also sets you up to land somewhere better if you don’t.

The documented impact? That’s your resume writing itself in real time. The relationships you’re building? Those are your references and future opportunities. The visibility you’re creating? That’s your professional reputation extending beyond this company’s walls.

The person who spends a merger complaining and hiding has nothing to show for it if they get cut. No story to tell. No wins to point to. No relationships to leverage. They leave diminished.

The person who showed up as the Hero? They leave with proof. Proof they can handle chaos. Proof they solve problems under pressure. Proof they make organizations better even when those organizations are falling apart.

Your LinkedIn profile practically writes itself. “Led cross-functional integration during merger, reducing process redundancies by 40% and creating clarity for 200+ employees during organizational transition.” That’s not survival mode. That’s executive presence.

The people you helped? They remember. They become your network. They refer you. They vouch for you when their companies are hiring. They connect you to opportunities you didn’t even know existed.

The skills you’re building right now—translating chaos, building bridges, staying composed under pressure—those aren’t merger-specific. Those are leadership fundamentals that make you valuable anywhere.

So yes, do all of this to increase your odds of staying. But do it just as hard knowing that if you don’t stay, you’re leaving with more than you came in with. You’re leaving as someone who performed when it mattered. Someone who has evidence of their value. Someone other companies will want.

The squeaky wheel who gets cut? They’re just unemployed and bitter. The Hero who gets cut? They’re a proven commodity with a track record and a network.

Either way, you win. But only if you show up like someone worth keeping.

Mergers reward people who make things work and eliminate people who make things harder.

You can’t control the merger. But you can control how you show up in it.

Be the person leadership wants to keep. The one who solves problems, builds bridges, and makes everyone around them better.

Be the Hero. Not the squeaky wheel. Not the ghost. Not the jerk.

The Hero.

Because even if this company doesn’t keep you, the next one will want you.

Three paragraphs. Perfectly formatted. Development goals that sounded specific without actually being specific. Action items that could apply to anyone on the team.

Jordan read it twice, then opened ChatGPT and pasted in a prompt: “Write a performance review for a mid-level marketing manager showing strong initiative but needing growth in strategic thinking.”

The output matched their review almost word for word.

Their manager hadn’t written this. An algorithm had.

And the thing is—Jordan got it. End-of-year reviews are brutal when you’re managing twelve people and none of them are actually struggling. Everyone’s doing fine. Nobody’s a problem. So you sit there trying to manufacture meaningful feedback for people who just need you to not get in their way.

The AI makes it faster. Cleaner. Less painful for everyone.

Except it doesn’t.

Because what Jordan needed wasn’t a document. It was a conversation with someone who’d been paying attention. Someone who could name the specific moment when Jordan had stepped up, or point to the pattern they’d been missing, or explain why the promotion wasn’t happening yet despite the work being promotion-level.

The AI couldn’t give them that. And apparently, neither could their manager.

Not because the manager was lazy or incompetent. Because the system had made it possible to manage twelve people without actually managing any of them. To check the boxes without doing the work. To outsource the hard part—the actual observation, judgment, and courage required to develop people—to a tool designed to sound thoughtful without being thoughtful.

The AI didn’t fail Jordan. The AI did exactly what it was built to do: generate plausible-sounding corporate text that mimics feedback without requiring any of the human work that makes feedback useful.

The system failed Jordan. The system that turned performance management into a calendar event. That separated development from daily work. That made it possible for someone to be responsible for twelve people’s growth without ever watching them actually work.

The AI just made it easier to pretend otherwise.

Here’s what your AI prompt can’t capture: the specific Tuesday morning when Jordan walked into a disaster no one else wanted to touch. The way they navigated the politics. The client call where they salvaged a relationship someone else had damaged. The hundred small decisions that added up to someone ready for something bigger.

Your AI can generate “demonstrates strong initiative” without knowing what initiatives Jordan actually demonstrated. It can produce “opportunities for growth in strategic thinking” without defining what strategic thinking means or showing the specific moment when tactical execution was the wrong call.

It can create the appearance of management without requiring any actual managing.

And that’s not the AI’s fault. That’s ours.

We built performance management systems so divorced from actual work that an algorithm trained on corporate mediocrity can reproduce them perfectly. So formulaic that ChatGPT can’t tell the difference between thoughtful feedback and template-filling.

The AI didn’t break performance reviews. It revealed they were already broken.

Watch what happens when managers discover AI review generators. Relief. Finally, a way to get through the tedious ritual without having to recall specific details or form coherent thoughts about someone’s year.

Drop in their name and job title. Maybe add a few bullet points about projects if you’re feeling thorough. Let the AI weave it into something that sounds managerial and development-focused.

Twenty reviews completed in an afternoon. Efficiency achieved.

Except everyone receiving these reviews knows immediately what happened. They can feel the generic weight of it. The way it could describe anyone doing roughly similar work. The absence of anything specific enough to prove you were actually there.

And they learn something about the system they’re in: caring has been automated. Observation has been outsourced. The hard work of actually seeing people has been replaced by the easy work of generating text about them.

The AI isn’t replacing good management. It’s exposing how little management was happening in the first place.

If you can plug someone’s name into a prompt and get a complete performance review, your review process was already worthless. The AI is just making the emptiness visible.

Here’s what actual performance feedback requires: watching people work. Not checking boxes about projects completed, but observing how they approach problems, navigate relationships, handle pressure, develop others.

Remembering specifics. The meeting where they said what nobody else would say. The project where they struggled and how they worked through it. The pattern you’ve noticed over months about how they engage with feedback.

Caring enough to form actual opinions. About their strengths, gaps, potential, trajectory. Opinions you can defend because they’re based on accumulated observation, not generated text.

Having the courage to say hard things directly. To name the problem you’ve been avoiding. To give the feedback that might be uncomfortable. To have the conversation instead of hiding behind pleasant-sounding development goals.

And doing all of this without a template or script or AI assistant that makes it easier.

Because the only way to give useful feedback is to actually know the person you’re giving it to. And the only way to know them is to do the work of managing them all year long.

If you’re using AI to write performance reviews, you’re not solving a writing problem. You’re revealing a management problem.

What you should use AI for: organizing notes you’ve already taken, flagging patterns you’ve already noticed, helping structure thoughts you’ve already formed, checking language for legal risks or unintended bias.

What you shouldn’t use AI for: generating observations you haven’t made, creating feedback you haven’t thought through, producing reviews for people you haven’t actually managed.

The difference matters. In one case, AI amplifies your management. In the other, it replaces it.

If your relationship with someone is strong enough that you could write their review without AI, then use AI to make it better. If you need AI to write it at all, the problem isn’t insufficient technology. The problem is insufficient attention.

Jordan figured this out within minutes of reading that review. Not because they’re exceptional at detecting AI-generated text, but because they’d been waiting all year for someone to actually see their work. To notice what they’d been building. To care enough to form a specific opinion about where they were and where they could go.

The AI-generated review told them everything they needed to know: their manager had been managing around them, not managing them. Checking boxes, not creating development. Filling forms, not building relationships.

Two weeks later, Jordan accepted an offer elsewhere.

In the exit interview, they explained exactly what had happened. About the AI-generated review. About the year of being managed by someone who never actually saw their work. About deciding to find a place where someone might actually pay attention.

HR thanked Jordan for the feedback and promised to review performance management practices.

Then they went back to sending managers the AI tool recommendations. Because efficiency.

The talent war isn’t lost to competitors with better salaries or shinier benefits. It’s lost to the quiet surrender that happens when people realize their managers care so little that they’ve outsourced caring to an algorithm.

Your people are worth more than AI-generated corporate speak. They’re worth the actual work of being seen, being known, being developed by someone who paid attention.

I get it. When your organization rewards process over presence, AI feels like a lifeline. It gives you the structured approach that makes your boss comfortable while handling the "leadership thinking" you're not sure you trust yourself to do.

But ask yourself this: what happened the last time you followed an AI-generated framework in a real human moment?

Did it feel authentic? Did your team member respond the way the algorithm predicted? Did you feel more connected to them afterward, or more distant?

You probably already know the answer. You might have even felt that weird disconnect when you realized you were performing management instead of actually managing.

That's your early warning system. That uncomfortable feeling when you're executing someone else's template—human or digital—instead of trusting your own judgment about what this specific person needs in this specific moment.

The leaders who learn to trust that discomfort will have a massive advantage in the next five years. The ones who learn to suppress it will become professionally obsolete.

The AI Amplification Effect

I was coaching a senior director at a Fortune 500 company who proudly showed me how she'd used ChatGPT to structure a performance conversation with a struggling team member. The AI had given her a framework: opening statement, specific examples, impact discussion, future expectations, closing commitment.

"It saved me hours of prep time," she said. "I just followed the script and got through it efficiently."

When I asked how the conversation went, her face changed. "Well, he seemed defensive. Kind of shut down halfway through. I think he took it the wrong way."

Of course he did. Because AI had given her a framework for having a conversation, not for seeing a human being. The script helped her deliver information, but it couldn't help her notice that he was dealing with a sick parent, a recent divorce, and the stress of being the only person of color on his team.

The framework protected her from having to develop the emotional intelligence to read his struggle. The AI made it easier for her to avoid the human work that actual leadership requires.

Here's what's probably happening to you right now: every time you use AI to structure a leadership interaction, you're getting slightly better at executing frameworks and slightly worse at reading humans. You're optimizing for process consistency while accidentally destroying relational authenticity.

Your team can sense this, even if they can't articulate it. They start experiencing you as someone who's performing management rather than practicing it. And once they feel that disconnect, trust becomes much harder to rebuild.

They Already Know

Your team spotted it weeks ago.

That Monday morning motivation email with the rocket ship emoji and "Let's crush this week, team!" energy that sounds nothing like how you actually talk. The Slack message with perfectly structured bullet points and a tone that's weirdly formal compared to your usual style. The feedback that uses phrases like "opportunities for growth" and "areas of development" when you've never talked like that before.

They notice when your one-on-one notes suddenly follow the exact same structure every time. When your meeting agendas start looking suspiciously polished. When your response to their struggles sounds like it came from a corporate handbook instead of a human who actually cares.

"I can always tell when he's using ChatGPT," a product manager told me about her director. "The emails suddenly have this weird enthusiastic energy with emojis he's never used before. And in person? He's completely different. It's like he becomes a motivational poster when he types."

Gen Z and younger millennials grew up with AI. They can spot generated content instantly. More painfully, they can sense when you're using algorithms to avoid actually connecting with them.

The performance doesn't just fail to land—it actively erodes trust. Because now they know you'd rather outsource the human work of leadership than develop the capability to do it yourself.

The Hollowing Out

This is what's happening across corporate America right now. Leaders who were already hiding behind HR templates are now hiding behind AI-generated templates. The crutch got an upgrade, but the muscle atrophy accelerated.

Your team notices the pattern. Ask for help with something messy and human? You reach for an algorithm. Ask for something that requires actual judgment about who they are? You reach for a framework.

"How do I give difficult feedback?" gets answered with a perfect five-step process. "How do I motivate a disengaged team member?" generates a comprehensive action plan. "How do I handle conflict between team members?" produces a detailed mediation framework.

All of it procedurally correct. None of it humanly effective.

Because AI can't tell you that Thomas is struggling because he's bored, not because he's incompetent. It can't read the micro-expression that tells you Sarah is about to cry. It can't sense that the "personality conflict" between Jennifer and David is actually about David feeling threatened by Jennifer's capabilities.

That requires presence. Attention. The ability to see patterns in human behavior that no algorithm can detect. Skills that most leaders spent the last two decades outsourcing to HR departments and consulting firms.

Now they're outsourcing them to chatbots. And wondering why their leadership feels increasingly hollow.

The Choice You Can't Avoid

The frameworks and processes that felt like protection are about to become obsolete. The templates that provided comfort are about to be available to everyone instantly. The systems that rewarded conformity are about to reward capability.

You weren't hired to execute frameworks. You were hired to see humans clearly and help them do their best work. That's the one thing AI can't do for you.

The question isn't whether AI will change leadership. It's whether you'll let it destroy the human capabilities that made you a leader in the first place.

Your team can already sense which kind of leader you're becoming. The one who performs management through algorithms, or the one who practices leadership through genuine human connection.

They're deciding right now whether to trust you with their truth or just their performance.

Choose quickly.

I learned this when I slowed my own life down enough to listen.

There comes a time when the call to wander grows quiet, when the restless heart finds its rhythm in familiar places. The wanderer in me hasn't disappeared—she simply finds adventure in a place called home.

The passport stamps fade and the suitcases gather dust, but the experiences remain. I’ve traced the edges of foreign neighborhoods, followed traffic lights down unfamiliar streets, filed away sights, textures and smells. This wandering, an anthropological study of how life might be lived.

Now I am writing the next chapter. The same girl with a head full of wanderlust, whose feet are planted intentionally in one place. A quiet, meandering life that is uncluttered and soft. A daily environment that feeds my soul without requiring departure.

Garden soil on my shirts replaces boarding passes. Tomatoes eaten straight from the vine become my exotic cuisine. Birds, bunnies, the sound of singing frogs and cicada. The nature around me reveals its secrets only when I slow down enough to notice.

Others may question my contentment, mistaking stillness for stagnation. They treat wanderlust as virtue and staying put as failure of imagination. There's this unspoken expectation that if you have money and time, you should be exploring the world—but travel sounds exhausting now: delayed flights, missed connections, lost luggage, questionable seatmates. I've eliminated those stressors from daily life. Why voluntarily add them back?

The morning light on my kitchen counter holds the same wonder as sunrise over foreign mountains. My backyard contains as much mystery as distant shores. Country roads offer their own form of getting lost.

Simple isn't boring. Simple is full of joy that doesn't rattle the nervous system. Depth and breadth are different kinds of wealth, and I have chosen depth.

I am not settling. I am building home with what satisfies my soul. The greatest journey now lies not in seeing new places, but in truly inhabiting the place I have chosen.

Come visit my discovered peace. Stay a while and how it feels to do life like any other Tuesday, when Tuesday is exactly where you want to be.

Not "inspirational motivation" versus "intellectual stimulation." Not the elaborate style distinctions we've built entire consulting practices around. Just one thing that explains nearly all the variance in how followers rate their leaders: the affective quality of the leader-follower relationship.

People don't follow frameworks. They follow humans they trust.

Beneath all our sophisticated leadership theories lies something embarrassingly simple—the emotional bond between leader and follower. The trust. The genuine care. How someone feels about their leader, not how many competency boxes that leader checks.

I spent years teaching leadership capabilities and frameworks, and I always had this pit in my stomach. Something felt wrong about breaking human connection into competency models. About teaching empathy like it was a foreign language instead of our native tongue. We turned leadership into a performance instead of letting it be a practice.

Watch any toddler and you'll see the entire leadership development curriculum playing out in real time. They cry when excluded from play—social rejection activates the same neural pathways as physical pain. They demand to "do it myself"—autonomy and mastery drive from day one. They ask "why" about everything—curiosity and exploration need no encouragement. They know instantly when someone is being mean—moral intuitions precede any formal ethics training.

Every single impulse that makes great leadership already lives in us. We don't need to be taught to care about fairness. We need permission to act on that caring. We don't need to learn empathy. We need systems that don't punish us for showing it.

But somewhere between the playground and the corporate office, we convinced ourselves these instincts weren't professional enough. We labeled them "soft skills"—as if reading people accurately was somehow weaker than reading spreadsheets. We decided that natural human responses needed frameworks to be valid. That trust required a training module to create.

We took the most essential part of leadership—seeing people clearly and responding with care—and made it feel amateur. Unprofessional. Something you needed to upgrade with a certification.

The result? Managers who can recite the five elements of psychological safety but can't tell when someone on their team is falling apart. Leaders who know the feedback sandwich by heart but can't have an honest conversation about performance. Executives who can facilitate listening sessions but have forgotten how to actually listen.

We didn't make leadership better. We made it safer. And safety, it turns out, is the enemy of authenticity.

I've watched this happen over and over. Someone spots compliance issues with a client account—their gut screaming that something's wrong. But instead of trusting their instincts, they follow the escalation framework. Document concerns using proper templates. Build business cases with the right stakeholders. Perform the role of a concerned employee instead of being one.

Weeks later, their instincts prove right. Months later, investigators ask why no one acted on the obvious red flags. They had the right instincts. The system taught them not to trust them.

I've seen managers feel their team's energy dying weeks before anyone says anything explicit. They sense people checking out, going through motions, the spark dimming in real time. Their instincts tell them to address it directly—call everyone together and say, "Something feels different. What's happening?"

Instead, they deploy the engagement framework. Surveys, team-building activities, psychological safety workshops. They treat symptoms with techniques instead of addressing disease with truth.

When people quit in waves, exit interviews say the same thing: "Leadership stopped caring about us as people." They cared deeply. They just stopped showing it in ways that felt real.

Eva's research explains why every "revolutionary" leadership approach eventually feels the same. Why transformational leaders and servant leaders and authentic leaders all seem to produce similar results when they're actually effective. Because underneath the style differences, they're all doing the same fundamental thing: creating relationships where people feel valued, trusted, and empowered.

The delivery mechanism doesn't matter. The underlying human connection does.

You know this intuitively when you stop trying to be a "transformational leader" and start being yourself. When you trade inspirational quotes for honest conversations. When you stop facilitating psychological safety and start creating it through presence.

Performance doesn't improve because you mastered a new leadership style. It improves because people finally feel seen by someone who gives a damn about their growth. That's not a technique. That's humanity. And humanity doesn't need training—it needs permission.

We took the most human part of work—how people care for each other, build trust, create meaning together—and turned it into a learnable skill set with measurable outcomes. We made people doubt their instincts about other people. We taught them to perform connection instead of creating it.

But safety is the enemy of authenticity. And authenticity is what followers actually respond to.

Stop teaching people to doubt their instincts. Start giving them permission to trust what they see about the humans around them. Permission to respond to struggle when they notice it. Permission to address problems directly instead of channeling everything through proper processes.

You don't need transformational leadership training to see when someone is drowning in their quarterly presentation. You need permission to trust your instincts and say, "This seems hard for you. How can I help?"

That conversation changes everything. Not because you applied the right framework, but because you trusted your human ability to see someone struggling and did something about it.

Measure success not by how well someone executes inspirational motivation, but by how deeply their people feel valued. Not by their scores on servant leadership assessments, but by whether their team would choose to follow them without the title. Not by their mastery of frameworks, but by their willingness to be human at work.

The research is clear. The frameworks are noise. The relationship is signal.

Time to stop teaching people to perform humanity and start giving them permission to practice it. Because the people you lead don't need you to be a better transformational or servant or authentic leader. They need you to be a better human being.

And that's not something you learn in training. That's something you choose in moments.

While companies debate return-to-office mandates and tweak org charts, women are building the infrastructure for how work actually gets done. Not someday. Right now.

Female-led consultancies that solve problems in weeks, not quarters. Fractional executive networks that deliver strategy without the bureaucracy. Strategic partnerships that produce results because they're built on competence, not politics.

We're not asking for permission anymore. We're not waiting to be chosen. We're creating the blueprint for what business looks like when excellence isn't constrained by systems designed to contain it.

The VP who left last month didn't leave because she couldn't handle it. She left because she was tired of compensating for organizational failure. Projects that succeeded despite the system, not because of it. Teams that thrived because she protected them from the dysfunction above them.

Now she charges three times her old salary to solve the same problems in half the time. Because when you don't have to navigate politics, explain your tone, or manage up to people who don't understand the work—you can just do the work.

We're done.

Done giving our best ideas to committees that water them down. Done carrying the emotional labor of entire teams while watching incompetent men get promoted above us. Done being the "glue" that holds everything together while being told we're "not quite ready" for actual authority.

Done explaining our tone. Done softening our insights. Done making everyone comfortable with our competence.

This isn't retreat. This is strategy.

The pattern is unmistakable. Twice we had the opportunity to put a woman in the most powerful seat in our country. And twice the majority chose the polar opposite. Not because she wasn't qualified—because she didn't look or sound like the version of leadership they'd been trained to trust.

That failure of imagination wasn't just a political moment. It's how leadership gets chosen everywhere. The reluctance to put real, unfiltered female competence at the top isn't about capability. It's about comfort.

And we've learned something: the system isn't going to choose us. So we're choosing ourselves.

The research will tell you women are leaving for work-life balance. That's corporate gaslighting. We're not stepping back from ambition. We're stepping forward into structures that don't punish us for having it.

While you debated whether we belonged in leadership, we studied how leadership actually works. While you questioned our readiness, we built the competence you couldn't recognize. While you managed our advancement, we engineered our independence.

The female-led consultancy market isn't a trend—it's an exodus. Women who spent years being told they needed "more seasoning" are now being hired at premium rates for the expertise their former employers couldn't see. The fractional C-suite isn't a fallback career. It's revenge, served profitable.

Here's what we learned: once you've experienced being paid solely for the value you create—without having to manage perception or navigate politics—you don't go back. Not because we're bitter. Because we're finally free to be as good as we actually are.

Ten years from now, the most effective teams won't be full-time employees grinding through performance theater. They'll be networks of specialists who show up, solve the problem, and move on. Led by women who got tired of proving themselves to people unqualified to assess them.

Your old company posted her job three times. Extended the search. Hired consultants to understand why they can't find anyone with her "unique skill set." They could call her—she'd fix their problem in six weeks. But they'd have to pay what she's worth and admit they should have recognized her value three years ago.

Most companies aren't ready for that level of honesty.

But they will be. Because excellence doesn't wait for permission. And we're done pretending incompetence deserves deference just because it came with a corner office.

You didn't want to listen when we were asking for advancement. Fine. Now you can hire us when you need transformation. At consultant rates. With consultant boundaries. And zero tolerance for the bullshit that made us leave in the first place.

We're not leaning in. We're walking out. With our capabilities intact, our standards raised, and blueprints for what business looks like when competence finally gets matched with authority.

The system lost us. We didn't slip away quietly. We left on purpose, with our middle fingers raised and our invoices ready.

And we're building what comes next. With or without you.

It started with a kiss-cam. Coldplay. Gillette Stadium. Two senior leaders caught in a moment they didn't expect. The crowd noticed. The internet noticed harder. Within hours, what could've been a private moment became a public question about power, ethics, and how culture actually works inside the companies we trust.

Most coverage has focused on the CEO and the CPO—what they did, who said what, who flinched first. That's not the real story.

The real story is what the rest of the leadership team does now.

Leadership moments don't happen in a vacuum. Neither does accountability. When trust fractures at the top, most companies follow the same playbook. Legal reviews. Sanitized PR statements. Generic apologies from whoever holds the highest title. We saw exactly that here—an underwhelming CEO statement that dodged more than it owned.

Translation: We're hoping this blows over so we can get back to business as usual.

What we haven't heard—and what we desperately need—is the voice of the remaining executive team. Because this isn't just about who got caught. It's about who has the spine to step up next.

Here's what the remaining C-Suite should say: "We were as shocked as you were. This moment exposed more than poor judgment—it exposed how power operates when people think no one's watching. What you saw doesn't represent this company. Not our standards. Not our people. Not what we're building here. Two people made choices that reflect their character, not ours. And we're not going to let their failure define hundreds of people who show up every day doing the right thing. We're leading this moment forward. With integrity. With transparency. With the values we actually believe in."

No lawyers. No corporate speak. Just humans taking responsibility for the culture they're paid to protect.

Every company has people who post the values on LinkedIn. What you need now are the ones who will protect them when it costs something. This is the moment for the CFO, CMO, CTO, COO to stand together and make it clear: this business isn't built on charisma or proximity to power. It's built on trust.

And trust isn't restored through silence. It's rebuilt through action that proves the rules apply to everyone—especially the people at the top. The message is simple: We are still here. And we are not them.

The real damage isn't reputational. It's internal. Employees wondering if integrity is just a poster in the break room. Customers wondering who's really making decisions. Board members wondering what else they don't know about.

This is organizational drift. The moment when everyone's watching to see if anyone's actually leading. Most companies choose performance over presence. Crisis management over character. Damage control over doing the right thing.

But drift isn't destiny. It's a choice.

The choice to lead when leading is hard. To speak when speaking is risky. To stand for something when standing is uncomfortable.

Your culture isn't broken. It's just waiting for leaders brave enough to carry it forward.

Time to find out who those leaders are.

One VP of Sales I worked with flipped that script. She refused to promote anyone until they'd proven they actually wanted to lead—not just claimed they wanted it.

Here's the truth: promoting someone and then teaching them how to lead is like throwing someone into the deep end and then handing them a swim manual. The damage is already done. Not just to them, but to the team they're now fumbling through, to the high performers who suddenly find themselves under a flailing new manager, to the company culture that just absorbed another amateur in a critical role.

So this VP built something different. Six months of leadership development before anyone got a team. Candidates chosen by her. Curriculum sketched out by her. She didn't wait for HR approval or corporate blessing because she understood something most leaders miss—if you want strong leaders, you have to build them yourself.

When you train people before you promote them, you get clarity. For them and for you. You create a leadership greenhouse where people can try on the role before the stakes get high, before someone's paycheck depends on them, before they're too proud or scared to admit they're not ready.

The ones who want to lead step forward clearer and more prepared. The ones who don't want to lead self-select out with dignity—not because they're lesser, but because they're honest about what energizes them. Your investment wasn't wasted. It was protective of your culture, your performance, your people.

I can attest to it working. I interviewed fifteen of her leaders. Every single one was strong. Not performing strength—actually strong. The kind who could handle hard conversations, develop their people, and deliver results without destroying morale.

Here's what she built that most companies miss:

Real succession planning. Not the annual exercise where HR asks "who's your backup?" and gets a shrug. Actual pipeline development with people ready to step up.

Ongoing talent spotting. Requiring leaders to nominate candidates meant they were constantly watching for leadership potential in real time. Who stepped up during the crisis? Who coached the struggling teammate?

A team culture where leadership was part of the success ecosystem. Leadership development wasn't fluffy—it was tied directly to results. Team performance improved. Retention went up. Revenue targets got hit more consistently.

That VP understood something most organizations miss entirely: leadership is not a gift you bestow. It's a craft you build. And you don't wait for permission to build it.

If this is your first go at structured leadership training, don't force existing managers through the series. They don't have time and won't make time.

Start with the program as designed—for non-managers who might become leaders. Give existing managers a study guide so they know what their nominees are learning. Build in moments where attendees share insights from the program.

You create productive status pressure where someone who works for them now has more leadership skills than they do. Build momentum until existing managers start asking for the training themselves. That's when real change happens—when leaders want what you're offering instead of resenting what you're requiring.

What about managers hired from the outside? Because of this program, that rarely happened on the VP's teams. But when it did, that new manager had runway to take the leadership training before they were assigned their team. It's rethinking everyone. It's forcing you to keep building the next leaders top of mind.

If we stopped treating leadership like a reward and started treating it like a responsibility, this kind of proactive training wouldn't be rare. It would be standard.

Because every time we promote someone and then start their development, we're already too late.