The best advice I ever received came from my VP of Engineering. We were on a quick call, discussing a growing problem that was starting to slow down development. I had just explained that I noticed a metric spiking in a way that could eventually hurt product quality. I was ready to act, to drop everything and fix it myself.
After all, that’s what a good engineer does, right? Find the issue. Fix the issue. Move on.
She listened carefully, then said something that didn’t land right away:
“We need leaders, not heroes”.
At first, it honestly felt a little harsh. I was trying to help. I wanted to protect the product. How could that be wrong?
But that single line stayed with me long after the call. I kept replaying it in my head, wondering what she really meant. And, over time, it turned into one of the most transformative lessons in my career.
The Moment It Clicked
I started researching what she might have meant. Articles like Don’t Confuse Leaders with Heroes and Heroes vs. Leaders helped me understand it better.
Heroes are the ones who step in when things go wrong. They act fast, take ownership, and often put themselves on the line to save the day. They thrive on intensity and sometimes even chaos.
Leaders are the ones who prevent those same fires from happening again. They see the system, not just the symptom. They don’t jump in to be the solution; they enable others to become part of it.
That difference sounds small, but it’s huge.
Heroes act with urgency.
Leaders act with intention.
Heroes handle the present.
Leaders shape the future.
The Context Behind the Lesson
When I brought that problem to my VP, I was ready to pause everything I was working on. I wanted to fix the metric spike myself. It was important, but not critical, and it wasn’t prioritized by leadership at the time.
Her decision to keep me on my current project made total sense in hindsight. She wasn’t telling me not to care. She was showing me how to scale care through leadership.
And that distinction changed everything.
Redefining My Approach
After that conversation, I started thinking less like a “problem fixer” and more like a “problem designer”. I asked myself: What would a leader do here?
The answer wasn’t to fix the metric directly. It was to make it everyone’s problem in a structured and sustainable way.
Here’s what I did next:
-
Mapped the landscape.
I reached out to people across different teams such as QA, backend, frontend, and design to understand how their workflows might relate to that metric. I didn’t want to assume. I wanted to observe.
The biggest insight was that most people didn’t even know their changes could influence that number. It wasn’t negligence; it was lack of visibility. -
Built context first, not solutions.
Instead of trying to patch things, I created a small internal simulator that replicated the conditions behind those metric spikes. It became a learning tool more than a technical one, a way for teams to see what could go wrong before it did. -
Facilitated ownership.
Once people saw the simulator, they started engaging. We created shared reports where each team tracked their own error patterns. No one needed to be told what to do; they just needed a clearer view of how their actions fit into the system. -
Turned chaos into rhythm.
We built a lightweight process to review these reports weekly. Each recurrence was discussed, patterns were identified, and priorities were naturally defined based on impact.
The Results
Within a few weeks, around 80% of the recurring issues were gone. No one stopped their work. No one burned out. And no single person “saved” anything.
The fix happened because everyone became aware.
That’s when it truly hit me. My VP was right. The company didn’t need someone to jump into the fire every time something went wrong. It needed people who could build systems so that fires stopped spreading in the first place.
We didn’t have heroes. We had leadership.
The Hidden Cost of Hero Culture
In tech, “hero behavior” is easy to glorify. We praise the engineer who stays up late to fix the release blocker. We applaud the person who catches bugs minutes before deployment. We admire those who go above and beyond.
But the truth is, over time, that culture eats away at sustainability.
Heroes burn out.
Heroes hide systemic issues.
Heroes make success depend on individuals instead of processes.
Leaders, on the other hand, make themselves less necessary over time. They design systems that work even when they’re not around. That’s the kind of stability high-performing teams are built on.
It’s not about being the loudest or the most visible. It’s about enabling quiet consistency, and that’s much harder.
From Heroic Effort to Scalable Leadership
Looking back, that one situation changed how I operate daily. When something breaks or feels off, I still have that instinct to dive in and fix it. But now, I pause and ask myself a few questions:
- Does this need me, or does it need a system?
- Am I solving this in a way others can repeat?
- Am I building independence or dependence?
If the answer points toward dependence, I know I’m leaning too much into hero mode.
Leadership, I’ve learned, isn’t about solving problems faster. It’s about making sure problems get solved without you.
What I Took Away
That conversation with my VP changed my understanding of impact.
Impact isn’t about visibility. It’s about scalability. It’s about creating environments where everyone can act with clarity, where success doesn’t rely on one person’s effort but on collective alignment.
When leaders empower others to own parts of the solution, things start to move faster and more predictably. That’s when you stop firefighting and start engineering the fireproofing.
And ironically, that’s when real influence begins.
Closing Thoughts
Sometimes leadership doesn’t sound heroic at all. It sounds like saying no to things you could fix because you’re focusing on enabling others to fix them better.
It means thinking long term, trusting others, and designing for autonomy instead of applause.
So now, whenever I face a problem that feels urgent, I remind myself:
You don’t have to be the hero. You just have to be the leader who makes heroes unnecessary.