The fluorescent hum of the meeting room has that particular frequency—not quite a sound, more a pressure behind the eyes, the ambient drone of a building that never fully exhales. It's 4:47 PM on a Thursday, and Nadia is facilitating the post-incident review with the kind of calm that makes you forget there was an incident at all. She reads the room the way a sailor reads weather—adjusting pace when attention drifts, drawing out the quiet engineer in the corner with a question so precisely aimed it lands like a key in a lock, defusing the product manager's frustration by reflecting it back in words he didn't know he needed.
She's the best facilitator I've ever watched work.
After the room empties, she stays behind, stacking papers she doesn't need to stack, rearranging markers in a cup that doesn't need rearranging. The choreography of someone delaying their own exit.
"You made that look easy," I say.
She doesn't look up. "I dread every single one of these."
The word dread lands in the room with a thud that doesn't match the woman I just watched hold twelve people's attention for an hour. I wait. Three seconds. Five. The silence does what it always does when you let it breathe—it creates a door.
"I used to write the architecture proposals," she says, finally. "I used to be the one solving the design problems. Now I'm the one making sure other people's conversations don't fall apart." A pause. "I'm good at it. Everyone says I'm good at it. And I hate it."
I've been thinking about this particular trap—the one where competence becomes a cage. Not the kind with bars you can see, but the kind made of praise and dependency and the slow, almost imperceptible rerouting of a career around the thing you do best rather than the thing you most want to do.
There's a word for what happens when organizations discover someone's gift and begin optimizing them into it. We call it growth, development, and leveraging strengths. But from the inside—from Nadia's side of the table, rearranging markers she doesn't need to rearrange—it feels more like a narrowing. Like being poured into a mold that fits perfectly and wondering why a perfect fit feels so much like confinement.
I've been turning a phrase over lately. Augustus claimed, "I found Rome a city of brick and left it a city of marble". History records this as triumph—humble origins elevated to grandeur, the rough made magnificent. Two thousand years of nodding along. Nobody thought to ask whether marble was actually better, or just more impressive. But I keep thinking about the brick.
Brick is load-bearing. It absorbs heat slowly and releases it slowly. A brick wall that cracks can be repointed by anyone with a trowel and an afternoon. Brick is honest—compressed earth, fired into permanence, a material that doesn't pretend to be anything other than what it is. A city of brick is a city built for living in.
Marble is beautiful. Marble is also, almost always, cladding. In Roman construction, those gleaming facades were thin sheets laid over the concrete and brick that did the actual structural work. The marble wasn't the city. It was the city's costume. Marble cracks under thermal stress, stains where it's touched, and erodes in rain. A marble city demands permanent upkeep of its own image.
Marble is, geologically speaking, limestone that's been subjected to extreme heat and pressure until it recrystallizes into something prettier. The same material, transformed by force into a more refined version of itself. More valued. More admired. More fragile.
Augustus took something resilient and covered it in something luminous and called it progress. Nobody mentioned that the brick was the one actually holding it all together.
I think about that when I think about Nadia.
Watch how it starts. It's never a single moment, never a contract signed or a role accepted with full knowledge of what it costs. It begins with a compliment that doubles as a claim.
"Nobody runs these like you do."
Said with warmth. Received with pride. And underneath, an invisible clause: therefore, you will keep running them. The compliment and the assignment arrive in the same sentence, wearing the same clothes, and it takes years to notice they're different creatures entirely. One is recognition. The other is a leash made of silk—so soft you forget it's attached to anything.
I think about the dojo, the way certain students would get assigned to teach the beginners. Always the ones with the cleanest technique, the most patience, the steadiest temperament. The coordinator would say, 'You're ready to teach,' and they'd hear honor. And there's truth in the idea that teaching deepens understanding — that explaining a throw strips it back to its bones and you see things you missed when your body was doing the knowing. But there's a difference between choosing to teach because it sharpens your own practice and being assigned to teach because your competence made you useful in someone else's system. What they didn't hear — what none of us heard until years later — was that teaching the basics instead of advancing to the next form wasn't development. It was a redeployment. Their competence had redirected their trajectory. They became essential to a function that had nothing to do with their own becoming
Some of them loved it. Some of them built an identity around it, the way a river builds a canyon—through repetition, not choice. And some of them, years later, stood on the mat with a look I've learned to recognize: the particular exhaustion of someone who is performing excellence in a domain that no longer feeds them.
The pattern replicates itself in organizations with a precision that should unsettle anyone paying attention. Here's how the architecture assembles, piece by piece, without a single architect:
First, the exception. "Could you handle this one escalation? You know the system best." Reasonable. Kind, even. A recognition of capability in a moment of need. But "just this once" has a half-life that nobody tracks. Six months later, the exception is an assumption. Your name appears on the escalation path not because anyone decided it should be there permanently, but because it was never removed after the last emergency. The architecture of indispensability is built from accumulated exceptions that nobody remembers were temporary.
Then, the applause. The retrospective where someone mentions that Nadia—it's always Nadia—stayed late to save the release. The room murmurs appreciation. The tech lead says, "Let's give a shout-out to Nadia." Everyone nods. Warm smiles. Genuine gratitude. And the conversation moves on. Nobody asks the question that the applause so efficiently buries: Why did the release need saving? The standing ovation becomes a gavel. It converts a system failure into a personal triumph, and once you've clapped, the inquiry into root cause feels ungrateful. We celebrated our way past the real conversation.
Then, the calendar. I once glanced at a colleague's schedule—not snooping, just coordinating—and noticed that every recurring meeting was there because one person's knowledge hadn't been shared. Each block was a monument to a conversation that should have been documentation, a process that should have been automated, a decision that should have been delegated. The calendar doesn't lie. It's a topographic map of organizational dependency, and the peaks are always shaped like the same few people.
And finally, the promotion. The one that appears to be recognition but functions as calcification. "We're creating a new role—you're perfect for it." What the organization actually did was look at the hero pattern and, instead of distributing the capability, build a job description around the bottleneck. The cage got a nameplate. The narrowing got a title. And the person inside it—the person who used to write architecture proposals, who used to solve the kind of problems that made her feel like herself—received a compensation adjustment, a LinkedIn update, and the quiet understanding that this is who she is now.
Marble. Thin, gleaming marble—laid over the brick that's still doing all the holding.
Because here's the counterintuitive thing about hero culture: it isn't a culture of strength. It's a culture that has made one person's presence load-bearing because it never invested in the foundation. The hero isn't celebrated for their excellence—they're celebrated for absorbing the consequences of organizational fragility. Every standing ovation is also a confession: We don't know how to do this without you, and we've decided to call that your gift rather than our gap.
The organization found a city of brick—functional, distributed, repairable—and replaced it with a city of marble. One brilliant surface where there used to be a hundred ordinary, load-bearing walls. And then it stood back and admired the gleam, not noticing that the whole structure now depends on a material that cracks under pressure and can't be patched by anyone with a trowel and an afternoon. It requires specialists. It requires her.
Nadia doesn't see it this way. Not yet. She describes her situation the way most of us describe our cages—as choices. "I chose to take on the facilitation." "I chose to be the escalation point." And there's truth in that. The hero does volunteer. They take on the critical incident because the alternative—sitting with the discomfort of someone else doing it worse, slower, differently—feels like negligence. Their standards become the lock. The organization just learns to stop trying the door.
But I keep hearing the other voices in her story—the manager who said "nobody runs these like you," the retro where they applauded her late night instead of questioning why it was necessary, the "temporary" escalation path that's been running for fourteen months. She built a cage, yes. At the same time, the materials were delivered to her door with a card that read "Thank you for your leadership."
I notice the pattern in myself, too. The question-as-scalpel I've developed—that habit of asking "Why?" when someone offers a comfortable abstraction—started as genuine curiosity. But somewhere along the way, people started routing their thinking through me. "Can I run something by you?" became the opening line of conversations that increasingly took on a dependency-like quality. My calendar is filled with one-on-ones that exist because I've become good at a particular kind of attention. The thing I do best has begun to colonize the space where other things might grow.
There's a question I've started asking—not to Nadia, not yet, but to myself, and occasionally to others when the silence makes room for it:
"Who told you this was your job?"
Not the role description. Not the official responsibilities. The unwritten expectation—the one that says you'll be the person holding everything together when the system creaks. Watch the answer. It's never a name. It's always "nobody, I just..." And that trailing silence is where the whole story lives. Nobody assigned you the cage. You walked in because it fit, and everyone quietly locked the door behind you by never building another way.
The thing about competence is that it's the one form of vulnerability our professional lives reward. We can't afford to be uncertain, to fumble, to not know—but we can afford to be excellent. So we pour ourselves into the thing we're best at, and it becomes a shelter. A place where we're safe from the exposure of incompetence. And slowly, so slowly, we don't notice, the shelter becomes a cell. The skill that once protected us is now consuming us. We built it as a room, and it became our world.
I wrote about this in a different key—the thing you stopped practicing, the abandoned hobbies, the guitar cases migrating to attics. But this is the other side of that same coin. Those practices died, in part, because competence at work expanded to fill every available space. We didn't just lose the painting or the music. We lost it to something—to the specific, rewarded, organizational version of ourselves that had no room for fumbling, for beginner's mind, for being bad at something without it registering as failure.
Maybe this is what the Greeks would have called a failure of sophrosyne—that quality of occupying oneself completely, of being sound in one's own mind. Not just the individual failure of losing touch with what feeds you, but the organizational failure of mistaking someone's capability for their calling. Of building cities of marble and forgetting that marble is only ever a surface. That the real city—the one that holds weight, that can be repaired, that doesn't demand a specialist to maintain—was always brick.
Nadia is still in the meeting room. The markers are now perfectly arranged, a task that never needed completing. The fluorescent hum continues its indifferent drone.
"What would you do," I ask, "if you could stop being good at this?"
She looks at me—really looks, not the facilitator's attentive gaze but something less practiced, more startled. The question sits between us like an object she wasn't expecting to encounter in this room.
"I don't even know what I'd do instead," she says. "I've been this for so long I'm not sure what's underneath."
Underneath. I think about that word. About the brick beneath the marble. How it's been there the whole time—load-bearing, patient, unpolished—waiting for someone to remember it exists.
I nod. Because I know that particular vertigo—the moment when you realize the cage and the self have grown together, like a tree that's absorbed the fence it was planted beside. Removing one means cutting into the other. And you can't tell, from the inside, which parts are the marble and which parts are you.
The late afternoon light has shifted to that grey register where the fluorescents win—where everything looks institutional, honest, stripped of the flattering angles that morning provides. Nadia picks up her laptop and pauses at the door.
"The architecture proposals," she says. "I was good at those too."
She says it quietly, the way people describe a house they grew up in but no longer own — precise about the rooms, vague about why they left.
I don't say anything. Some recognitions need to arrive in their own time, settle at their own weight. But I notice that she said was. Past tense. And I wonder if the brick remembers it was there first.
Walking back to my desk through the building's evening hum, I think about Augustus—how he announced the marble as his greatest achievement, and everyone has been applauding ever since. Two thousand years of standing ovations for the man who replaced something resilient with something that gleams. How history remembered the surface and forgot who laid the brick. How the gleaming became the story, and the thing that actually held the weight became invisible.
How do we do this to people, too? How do we do it to ourselves? How we clap.
How many people are sitting in rooms they're brilliant at, doing work they're celebrated for, gleaming—while something underneath, something load-bearing and honest and theirs, waits in the quiet for someone to ask:
What's beneath the marble?
The brick is still there. It always has been. Patient as stone. Waiting for someone to remember that the city was a city before it learned to shine.
If this landed somewhere familiar—if you recognized the architecture, the silk leash, the standing ovation that buried the real conversation—send it to someone whose calendar looks like a dependency map. They might not know the brick is still there either.
