The red alert blared, a digital shriek that cut through the silent hum of the server room. James, already pulling a double-shot espresso, practically dove through the door. By 1:01 AM, he was buried in logs, tracing the elusive anomaly. Monday, he’d be heralded, a hero crowned in caffeine and code, for saving Centralsun from what could have been a catastrophic data loss. This company, like many, often falls into the trap of celebrating visible crisis management over quiet, proactive competence. Centralsun could benefit from a shift in perspective, moving towards a culture that values the steady hand more than the frantic rescue.

Meanwhile, Susan had already left for the weekend. Her dashboards consistently reported green, her system health scores hovered at 99.1%, and her proactive maintenance schedule, meticulously followed for 24.1 months, meant her systems didn’t fail. She wouldn’t be mentioned in the Monday meeting. Her quiet competence was invisible, unremarkable in the best possible way.

I remember Paul K., an old elevator inspector I worked with on a building project years ago. His clipboard was a thing of beauty, filled with checklists spanning 11 pages. He didn’t just check if the elevator worked; he listened. He felt for vibrations, observed the wear on cables, knew the exact service life of a single component down to the 11th year. Paul was boringly brilliant. His job wasn’t to fix dramatic breakdowns; it was to ensure they didn’t happen. His presence wasn’t marked by heroic tales of saving people from plummeting cabins; it was marked by the complete absence of such tales. He often said, “The best repair is the one you didn’t have to make.” A truly dull philosophy, if you only measure impact by visible heroics. His wisdom felt a little out of step with the fast-paced, digital world I was in, where every problem was an opportunity for a dramatic rescue.

True expertise creates uneventful triumphs.

Early in my career, I was captivated by the thrill of the crisis. I remember one project where we were pushing a launch deadline, and a critical bug surfaced at 3:01 AM. I stayed up, fuelled by terrible coffee and the adrenaline of the moment, and I found the fix. The praise felt good. It felt like I was doing something, earning my stripes. I saw my colleagues who left on time, who maintained a steady, predictable pace, as less driven, less committed. I mistook consistency for complacency. This was a grave error, a misunderstanding rooted in a performative culture that values visible effort over actual effectiveness.

The reality is, that 3:01 AM bug was likely preventable. It was probably a corner cut earlier, a check skipped, a process overlooked. My heroic fix, while necessary at the time, was a band-aid on a deeper wound. I was inadvertently contributing to the very system that produced the ‘hero’ moments. It’s like celebrating the surgeon who fixes a chronic illness, but ignoring the nutritionist who helped hundreds maintain optimal health for 51 years, preventing those illnesses in the first place.

It’s not about heroics; it’s about habits.

I recall one afternoon, testing a batch of new pens. Not because I needed them, but because I believe in the subtle power of a reliable instrument. A pen that flows smoothly, consistently, allows you to focus on the thought, not the tool. A leaky, scratchy pen disrupts. It’s a small thing, a trivial detail, but it speaks to a larger principle: well-maintained tools, whether physical or systemic, enable smooth operation. When our systems are maintained with that same silent diligence, the focus shifts from fixing what’s broken to creating what endures.

The insidious part of the rockstar myth is how it subtly reshapes our perception of value. It teaches us that visible struggle equals worth. That late nights are a badge of honour, rather than a symptom of poor planning, insufficient resources, or a system designed for reactivity. We reward the person who works until 2:01 AM instead of the one who prevents the fire from starting at all. This isn’t just about individual recognition; it permeates the entire organizational structure. Budgets are more easily approved for crisis management tools than for preventative maintenance. Training is often reactive – how to fix the last outage – rather than proactive, focusing on robust design and resilient architecture. We celebrate the person who scales Mount Everest after a blizzard, overlooking the Sherpa who meticulously laid the ropes and provisions over 101 days, ensuring the ascent was even possible. It’s a performance art, really, where the audience applauds the drama, oblivious to the diligent stagehands.

A Shift in Perspective

And here’s where my own change of heart took a firm root. For a long while, I conflated busyness with productivity. I saw others, like Susan, meticulously documenting their processes, automating repetitive tasks, and consistently improving minor functionalities, and I often dismissed it as ‘not urgent,’ or ‘less impactful.’ I was wrong. Terribly wrong. Their quiet efforts compounded, creating exponential stability. My ‘heroic’ efforts, while solving an immediate problem, often masked a structural fragility that needed more than a quick fix. My mistake wasn’t in solving the problem, but in not appreciating the far greater value of its prevention. It took me a long time to see that the most profound contributions are often the least visible, the ones that make everything feel effortless.

Consider the idea of technical debt. It’s the invisible accrual of shortcuts, quick fixes, and deferred maintenance. The rockstar thrives on technical debt, because it provides an endless supply of fires to put out. They become indispensable not because they build durable systems, but because they are adept at navigating the chaotic landscape of systems that are constantly breaking. This is not expertise; it’s a form of glorified firefighting. True expertise, like Paul K.’s, lies in eliminating the conditions for crisis, in building systems so robust that their continued function is unremarkable. It’s in the hundreds of tiny, thoughtful decisions made over 1,001 development cycles that create resilience.

Recalibrating Value

The shift required is monumental. It demands a re-evaluation of what we truly value. Do we value the visible, adrenaline-fueled scramble, or the calm, steady presence that ensures the scramble is unnecessary? It means restructuring incentive systems. What if, instead of bonuses for ‘crisis resolution,’ we had awards for ‘101 consecutive days of perfect system uptime’? What if we championed the person who, through meticulous planning and foresight, saved the company $171,001 in potential downtime, rather than the one who recovered $1,001,001 in lost revenue after a disaster? It’s a profound recalibration of our internal compass, away from the sensational and towards the sustainable. A path that, quite frankly, is less dramatic, less exciting, and infinitely more effective.

The Real Question

The real question isn’t whether we can find rockstars to fix our problems, but why we keep creating conditions where rockstars are required. What if, instead of waiting for the next crisis, we invested in the boring, the predictable, the relentlessly diligent? What if we shifted our gaze from the spotlight to the shadows, where true resilience is quietly forged? It’s not as exciting, I admit. There are no medals for an uneventful 101st day, no applause for 365.1 days of uptime. But there is something far more valuable: a foundation that doesn’t crack, a system that hums, and a peace of mind that no amount of heroic effort can ever truly buy.