The plastic trophy in Kevin’s hand reflects the harsh overhead fluorescent lights of the conference room, catching a glimmer of mock-gold that makes my eyes ache, though that might just be the lingering pressure in my sinuses after I just sneezed seven times in a row. It’s a rhythmic, violent sort of sneezing that leaves you momentarily disconnected from reality, which is fitting, because the reality being presented on the small stage at the front of the room is entirely fictional. Our CEO is currently describing Kevin as a ‘Rockstar,’ a title that apparently comes with a $113 gift card and the collective, silent resentment of the 33 people sitting in the third row. Kevin ‘single-handedly’ launched the new user interface. He ‘carried’ the project. He is the solo hero of a narrative that management has been writing since the fiscal year began.

It’s a lazy way to run a company. It is infinitely easier for a manager to point at one person and say ‘He did it’ than it is to understand the complex, messy, and deeply interconnected web of contributions that actually move a product from a whiteboard to a user’s screen. By lionizing the Rockstar, management creates a culture of visibility over competence. People stop asking ‘How can I help the team?’ and start asking ‘How can I make sure I’m the one holding the plastic trophy next month?’ It turns a collaborative environment into a zero-sum game of perception.

The Escape Room Architect: Collective Truth

I recently spent an afternoon talking with Grace M.-C., a designer of high-end escape rooms who understands human dynamics better than most HR directors I’ve met. Grace builds environments where success is physically impossible without collective effort. She told me about a room she designed that required 13 different inputs to be triggered simultaneously. One person can be as fast and ‘brilliant’ as they want, but they cannot be in 13 places at once. If they try to dominate the room, the timer runs out and everyone loses. Grace M.-C. explained that the most satisfying experiences for her clients aren’t the ones where one person solves every puzzle. Those are actually the rooms where people leave feeling cheated. The best experiences are where 3 or 4 people realize they are each holding a piece of a larger truth.

In business, we have done the opposite. We have designed ‘rooms’ where we actively encourage the loudest person to grab all the keys, and then we wonder why the other 13 people in the room are checked out, scrolling through job listings on their phones. I’ve been that person. I’ve been the one who did the invisible work, the 213 lines of tedious data cleaning that allowed the ‘data scientist’ to produce a single, beautiful chart that the board of directors raved about. I didn’t get a gift card. I got a ‘thanks for the support’ in a Slack channel that was buried under 53 other notifications within ten minutes.

Systemic Fragility: The Bus Factor

This isn’t just about hurt feelings or ‘fairness,’ which is a word that corporate types tend to dismiss as being too soft. It’s about systemic fragility. When you build a culture around a Rockstar, you create a single point of failure. If Kevin leaves for a competitor, or if he finally burns out from the pressure of maintaining his own myth, the whole house of cards collapses because nobody else was empowered to understand the core of the work. We call this the ‘Bus Factor.’ If Kevin gets hit by a bus-or more realistically, if he gets a 23% raise elsewhere-how many people are left who actually know how the machine works? If the answer is zero, you haven’t built a high-performing team; you’ve built a cult of personality.

The Necessity of Roles

There is a better model for this, and interestingly, it comes from the world of digital entertainment. If you look at high-level competitive gaming, the ‘Rockstar’ or the ‘Carry’ is a recognized role, but everyone knows they are useless without the ‘Support.’ You cannot have a legendary damage-dealer without a healer who is keeping them alive through 83 different attacks. In environments like EMS89, the thrill of the game comes from the synchronization of roles. The community understands that the person who gets the final kill is often the least important part of the sequence; it was the 3 people behind them providing cover, buffs, and tactical information who actually won the match. The gaming world has figured out a way to make the invisible work visible through data and shared objectives. Why can’t we do that in a plush office in midtown?

I’m not saying that individual talent doesn’t exist. Some people are faster, some are more creative, and some have a knack for seeing patterns that others miss. But talent is a multiplier, not a standalone value. A Rockstar is just a person with a loud instrument; without the rhythm section, they’re just making noise. We need to stop rewarding the noise and start looking at the harmony.

The Architect’s Mandate

Grace M.-C. often says that a well-designed game doesn’t make you feel like the designer is smart; it makes you feel like you are smart. Management should be the same. A great manager shouldn’t be looking for a Rockstar to save the day. A great manager should be an architect of systems where 23 average people can achieve something extraordinary together. If you need a hero to save your project, your process is broken. If you need one person to work 73 hours a week to meet a deadline, your planning is a failure.

We need to start celebrating the ‘Ghosts’-the people who prevent the fires so that the Rockstars don’t have to ‘heroically’ put them out. We need to reward the person who writes the clean, boring code that doesn’t break. We need to value the person who spends 43 minutes explaining a concept to a junior developer instead of the person who just does it themselves to save time. These are the behaviors that build resilient, scalable companies.

System Resilience Score

The Cost of Solo Light

As the meeting breaks up, I see Kevin walking back to his desk. He looks tired. He’s 23 years old and he already has the permanent slouch of someone who is carrying a burden he didn’t ask for. He knows, deep down, that he can’t keep this up. He knows that his ‘brilliance’ is a borrowed light, reflected from the people around him who are currently sighing and returning to their 133 unread emails. I want to tell him that it’s okay to not be a Rockstar. I want to tell him that he’d be a lot happier if he were just part of a really good band.

Maybe tomorrow I’ll say it. For now, I need to go find Sarah and see if she wants to grab a coffee. I want to ask her about those 43 bugs she fixed. I want to hear the story of the work that nobody saw, the work that actually kept us afloat while the music was playing. Because if we don’t start telling those stories, the Rockstars will eventually find themselves playing to an empty room, wondering where the audience went and why the lights won’t turn on.

Rewarding the Ghosts

We need to start celebrating the ‘Ghosts’-the people who prevent the fires so that the Rockstars don’t have to ‘heroically’ put them out. We need to reward the person who writes the clean, boring code that doesn’t break. We need to value the person who spends 43 minutes explaining a concept to a junior developer instead of the person who just does it themselves to save time. These are the behaviors that build resilient, scalable companies.

If you need a hero to save your project, your process is broken. If you need one person to work 73 hours a week to meet a deadline, your planning is a failure.