She Did Everything Right
What fifteen years of reliable delivery cost one high performer and what the organizations behind her owe people they optimized instead of grew.
TL;DR: A few weeks ago, a message arrived from a former employee I didn’t know personally. She sent it privately because she didn’t want to look naïve online. She wasn’t naïve; she was disoriented, and there’s a meaningful difference. This piece is about that difference, about the organizational design choices that produce it at scale, and about what leaders owe the people who gave their best years to systems that were never designed to grow them back.
The Message I Didn’t Expect
A few weeks ago, a message landed in my inbox that I haven’t been able to stop thinking about.
It came from a woman I’ll call Ann. A former employee I didn’t know personally, she found me through a post and wrote something thoughtful, measured, and a little heartbreaking. She’d spent nearly fifteen years at a professional services firm where I was once CEO. High performer. Reliable. The kind of person organizations lean on to get things done without drama.
She wasn’t passed over, exactly. Projects came through a resourcing function. She delivered. The cycle repeated. For fifteen years.
What never came, she wrote, was an invitation. Not once did anyone pull her aside and say: here’s a stretch assignment you probably aren’t ready for, want to try it anyway? Not once did a leader ask where she wanted to go, what she was curious about, what she was building toward. The system fed her work. It never grew her.
So she left. Confident, reasonably so, based on a long track record. Then the market handed her a reality she hadn’t seen coming.
Her words: “I get into the current marketplace and realize I’m years behind the next generation’s skill set.”
Fifteen years of high-level delivery, and the hidden cost of that consistency was being optimized for one context. She was excellent at what the firm needed. She just hadn’t been developed into what she was capable of becoming.
One more line stopped me. Inside the organization, she had always felt a step above her immediate team. Not with bitterness or arrogance, but as a benchmark observation. When the people around you are your only mirror, and no one is deliberately expanding your field of view, you carry a confidence that turns out to be a closed loop. You think you’re ahead. You don’t know what you don’t know. And no one with organizational authority ever cared enough, or had the tools, to show her.
She did everything right. The system just wasn’t designed to grow her while she delivered for it.
And that’s the part I can’t shake.
The Invisible Architecture of Stagnation
There’s a pattern underneath Ann’s story that I’ve seen in too many organizations to call it exceptional. Nobody broke this. It was built to run exactly like this.
Call it the loyalty tax.
High performers who are reliable and consistently delivering become load-bearing walls. The system needs them exactly where they are. Not through malice, but through incentive architecture that rewards utilization over development, and through structural decisions that stack up over time into a ceiling.
Utilization pressure is the first mechanism. In professional services firms, the metrics that drive decisions are billable hours, project margins, and headcount efficiency. When you have a reliable performer available, you staff her. Pulling her off billable work to stretch her into something unfamiliar creates short-term risk and a potential drag on margins. The rational, metrics-aligned decision is always to put her where she’s already proven so efficiency is maximized. Do that enough times and you haven’t managed her career. You’ve optimized her out of one.
Resource gatekeeping is the second. Centralized resourcing functions exist for legitimate reasons: visibility, coordination, demand smoothing. But they redefine capability as availability without anyone noticing. In the day-to-day, when matching supply to demand, the question asked is “who can do this?” The question never asked is “who should grow into this?” Career development stops being a mutual leadership and employee responsibility and becomes a privilege for whoever happens to be in front of the right sponsor at the right moment.
Closed internal benchmarks are the third, and the one that makes the first two invisible. If you’re the strongest consultant on your team, you feel competent. What you can’t see is how that competence stacks against the external market, against peers elsewhere, against challenges you haven’t been given. The gap forms in the dark. By the time it’s visible, it’s usually large enough to feel like personal failure rather than what it actually is: an organizational design flaw working exactly as intended.
Let me say something plainly. The firm I led was in the workforce development business. We built client organizations’ capabilities at scale. We did not fully apply that discipline to our own people. I’m calling this out because the leaders most likely reading this are probably running the same sort of contradiction right now, probably not even realizing it.
Two Generations, One Broken Mirror
The conversation didn’t end with Ann.
Her daughter, I’ll call her Laura, 24 years old, was having her own version of the same crisis. Different surface. Same disorientation underneath.
Laura had done everything right by her generation’s rules. Fluent across every relevant platform. Building custom GPT workflows before her company had a policy about them. Producing a polished first draft of almost anything in twelve minutes. Her manager loved her.
And she had no idea what to do with any of it.
She had tool access without the judgment to use it well. She could produce, but she couldn’t yet tell when her output was good, when it was directionally wrong, or when the question she was answering wasn’t the question worth asking. In an environment that rewarded speed and volume, nobody had told her that was a problem yet.
There’s a lazy assumption in leadership circles that Gen Z arrives future-ready because they grew up digital. Proximity to tools is not capability with them. A 24-year-old who has used AI since college has built fluency, not judgment. Those are different things, and confusing them is an organizational liability.
I’m also seeing a real AI backlash inside that generation. People read it as technophobia. It’s actually the sound of a cohort whose implicit career promise is straining, the promise that said: be adaptable, stay current, build skills, and the system will reward you. That promise is starting to feel as hollow to Laura as the loyalty-and-performance promise felt to Ann.
Two generations. Decades apart. One broken mirror.
Ann did everything asked of her and found herself structurally capped. Laura did everything asked of her and found herself technically capable but developmentally empty. Neither failure came from cruelty. Both came from design. The same loyalty tax, collected at different points in a career arc, produces the same result: people who are useful to the organization and underserved by it.
The antidote is critical thinking, pattern recognition, and relational judgment, the things genuine human development builds and the loyalty tax wears down over time.
What I Told Her, and What I Should Have Said to Leaders Earlier
To Ann, the message was simple: you are not behind. You spent years developing things that are actually hard to develop. Client engagement. Reading a room. Knowing when a team is falling apart before anyone raises it as an issue. Learning something new without losing your footing. None of that shows up in a job description with any specificity, and almost none of it can be replicated by a model that doesn’t know your client is going through a divorce and that the timeline is slipping because of it. That judgment is yours. The distance between where you are and where you think you need to be closes faster than you expect, because you already have the foundation that makes new tools useful instead of dangerous.
To Laura, the message was different in texture but the same at the core. Tools matter less than what you do with them. The ability to generate a polished draft in twelve minutes is genuinely useful, right up until the moment you can’t tell whether it’s answering the right question. Critical thinking is the actual edge. And her mother has been modeling it for years. She just never had a label on it, and no one ever held it up and said: this is what good looks like, and you are doing it.
That last part is where I should have stopped advising individuals and said something harder to the organizations behind them.
The message I sent Ann should never have been necessary. What both she and Laura needed was an organization that worked as a mirror. Stretch assignments built into development architecture, not handed out as favors when someone is already halfway out the door. Market benchmarking as a living conversation, not a discovery you make only when you interview elsewhere.
You are not behind. You are recalibrating. Big difference. That line belongs in a performance conversation delivered by a manager who has earned enough trust to make it land. Not in a message someone reads at 11pm wondering if she still has a future.
The Questions Worth Staying With
These aren’t rhetorical. I mean them as an actual invitation to stay with the discomfort.
Who in your organization is performing well by every internal metric while a capability gap opens up underneath, out of sight? Not the obvious underperformers. The reliable ones. The ones you count on. The ones consistent enough that nobody has asked lately what they actually need.
When your best, most loyal people leave, are they more capable and marketable than when they arrived? Or are they slightly behind and grateful to have made it out? The exit interview rarely captures this. The answer usually shows up months later, when you see where they land.
What does your talent architecture actually reward when delivery and development compete for the same calendar? Not what your culture deck says. What happens in practice in October, when the quarter is tight and someone has a development conversation scheduled.
And the one that takes longest: if someone gave your organization fifteen years, what did your organization give them back?
Ann is still recalibrating. She’ll find her footing faster than she thinks, because she came in with the foundation that actually matters. But someone in your organization is doing the same math right now and saying nothing. They’re measuring the distance, wondering if the gap is closable, deciding whether the organization they’ve given years of their working life to is still the right place to close it.
They just haven’t sent the message yet.
You have time to change the equation before it arrives. Before the exit interview. Before fifteen years of someone’s best work becomes a reckoning nobody planned.
That is not a burden. It’s the work of leadership.
The systems you build, and the ones you tolerate, shape people in moments you can’t see. That’s what I mean when I talk about mentorship as legacy. It isn’t only the conversations you have. It’s the architecture you leave behind for the people who will live inside it.