The Dopamine Hit of Crisis

The blue light of my monitor is vibrating against my retinas at 2:45 AM, not because I am a hero, but because I am watching the Slack channel ‘#General‘ erupt in a series of fire emojis. Dave just pushed a hotfix. The CEO is already typing, his ‘is-typing’ bubble dancing for 15 seconds before he unleashes a paragraph of unadulterated praise. ‘Dave, you’re a legend! Saving the launch at the eleventh hour! This is the 10x energy we need!’

I feel the heat rising in my neck, a physical manifestation of a frustration I’ve been nursing for 255 days. I know why the launch was failing. I know because I saw the pull request Dave slammed through 5 days ago-a chaotic mess of 555 lines of code that bypassed every safety check we have. He didn’t save the launch; he set the building on fire and then showed up with a garden hose to a standing ovation. We are rewarding the arsonist for his skills as a volunteer firefighter.

This is the pervasive, toxic myth of the ‘rockstar’ employee. We are obsessed with the individual who ‘carries’ the team, the lone wolf who works 85 hours a week and writes code that looks like poetry to him and like a ransom note to everyone else. But here is the contradiction I’ve lived: these rockstars are usually the primary source of organizational debt. They create systems that only they can understand, ensuring their own job security while simultaneously making the organization fragile and prone to catastrophic failure. We praise the ‘genius’ because his brilliance is visible, while we ignore the ‘professional’ whose brilliance lies in making the complex look boringly simple.

The Invisible Infrastructure

While the CEO is busy crown-shaping Dave, Sarah is probably asleep. Sarah is the engineer who finishes her work at 5:05 PM every day. She has never pulled an all-nighter. She has never ‘saved’ a launch. Why? Because Sarah writes tests. She documents her edge cases. She spends 45 minutes explaining a logic flow to a junior dev so that they don’t have to ask her again next month. Sarah’s work is invisible because it doesn’t break.

“

In the eyes of a management team addicted to the dopamine hit of ‘crisis-resolution,’ Sarah is just a baseline performer. In reality, Sarah is the only reason the company hasn’t collapsed under the weight of 150 different ‘hotfixes.’

In the eyes of a management team addicted to the dopamine hit of ‘crisis-resolution,’ Sarah is just a baseline performer. In reality, Sarah is the only reason the company hasn’t collapsed under the weight of 150 different ‘hotfixes.’

I’ve been thinking about this a lot lately, mostly because I spent 25 minutes yesterday comparing the prices of two identical ergonomic keyboards on three different sites. One was listed for $105 and the other for $125. The more expensive one was marketed as ‘Pro Gamer Elite Gear.’ The cheaper one was just an ‘Office Peripheral.’ They had the same switches, the same travel distance, and the same plastic housing. We are conditioned to pay a premium for the ‘rockstar’ branding, even when the utility is exactly the same-or in the case of employees, often worse. We pay for the drama, the narrative, and the ego, rather than the consistent output.

When Flair Destroys Accessibility

My friend Jade S., a closed captioning specialist, knows this better than anyone. In her world, the ‘rockstar’ captioner is a disaster. If a captioner decides to get ‘creative’ with the pacing or tries to interpret the tone with non-standard flourishes, the accessibility fails. Jade S. spends her days ensuring that every word is timed to the millisecond, a process that requires a level of ego-less precision that would make a rockstar weep with boredom. If Jade does her job perfectly, no one notices she exists. If she tries to be a hero, 55,000 people can’t follow the dialogue. The value is in the system, not the flair.

When you build a culture around a few ’10x’ individuals, you are essentially building a house where the entire roof is supported by 5 toothpicks. If Dave gets a better offer, or decides to go on a 15-day hike in the mountains, or simply burns out, the knowledge silo he built collapses. The ‘rockstar’ creates a dependency that feels like strength but is actually profound weakness. They don’t mentor; they gatekeep. They don’t collaborate; they dictate. And the rest of the team? They stop trying. Why bother contributing a thoughtful, measured solution when Dave is just going to rewrite it at midnight and get a public shout-out for ‘fixing’ it?

Erosion of Reliability

This dynamic creates a 45% increase in resentment among the ‘reliable’ middle. These are the people who do the documentation, the code reviews, the manual testing, and the thousand little chores that keep a company’s heart beating. When they see the person who ignores all the rules getting the biggest bonuses, they learn that the rules are for ‘average’ people. And when your best people stop following the rules, you no longer have a company; you have a collection of egos competing for the spotlight.

I realize I’m being harsh. I’ve been Dave. I remember the rush of being the only one who could solve a problem. It’s addictive. But I also remember the 15 mistakes I made in that ‘heroic’ code that some poor intern had to fix 5 months later. I was a liability wrapped in a cape. We need to stop looking for heroes and start looking for systems that make heroes unnecessary.

Replacing Guesswork with Registry Logic

Consider how we handle major life events, like a baby shower. In the old model, one ‘rockstar’ friend or parent would try to guess everything the new parents needed, manage the guest list, and handle the logistics, often resulting in 5 duplicate strollers and a very stressed-out host. It was a hero-based system. The modern approach is to use a collaborative registry where the work is distributed and the needs are transparent. It turns a chaotic individual effort into a collective success.

This is exactly how LMK.today functions-by replacing individual guesswork and heroics with a shared, organized system that ensures the burden is shared and the result is perfect for everyone involved.

I’ve spent the last 35 minutes looking at the Slack thread again. The fire emojis have died down. Dave is likely sleeping now, basking in the glow of his digital accolades. Meanwhile, Sarah just logged on. It’s 8:05 AM. She opened the ticket tracker, saw the mess Dave left in the production environment, and quietly began writing a regression test to make sure it never happens again. She didn’t post in ‘#General.’ She didn’t tag the CEO. She just did her job.

The Keyboard Test

We are so blinded by the flash of the rockstar that we don’t see the steady light of the professional. We reward the 105% effort on a single night, but we ignore the 100% effort given every single day for 5 years. This is how organizations die-not by a single mistake, but by the slow erosion of the systems that were supposed to protect them, traded away for the ego of a few ‘geniuses.’

Is your company’s success dependent on a person or a process? If Dave left tomorrow, would your company lose its ‘magic,’ or would it just lose a source of high-octane chaos? Maybe it’s time we stop applauding the fire and start thanking the people who built the sprinklers.