Anjali collapsed into her desk chair at 11 PM, finally closing her laptop after another "emergency" resolved. The proposal was submitted. The crisis was averted. Her team had rallied once again because she'd gathered everyone together, synthesised their inputs, and heroically pulled it all together in the final 48 hours.

She felt that familiar high - the rush of being needed, of being the one who could make it happen when it mattered most.

But beneath that high was something else. A bone-deep exhaustion that no weekend could fix. A creeping resentment toward her calendar and a nagging question she kept pushing away: "Why does it always have to be like this?"

We tell ourselves stories about why the chaos is necessary.

"This is just how important work gets done."

"We're moving too fast to slow down."

"My team needs me to step in - no one else can do it as well."

"Real, messy work looks like this."

But here's what I've seen working with leaders caught in this cycle: The constant firefighting isn't a sign that you're doing important work. It's a sign that something fundamental isn't working.

The pattern looks like this:

A fire erupts. You step in heroically. The crisis gets resolved. There's relief, maybe even some praise. Then a lull. Then another fire and another. Each time, you tell yourself it's just the nature of your work, your industry, and your team's current stage.

But watch what's actually happening beneath the surface:

Your team is learning they don't need to plan ahead because you'll save them at the last minute. Your calendar is so packed with urgencies that you never get to the important work that would prevent future fires. Your identity becomes so wrapped up in being the hero that you unconsciously create conditions that require heroics.

The real cost: The growth of your organisation - and your own personal and professional development - gets shackled to this pattern.

I watched a founder struggle with this for years. Brilliant, capable, deeply committed to her mission. But every project followed the same arc: things would hang until the final days before deadline, then she'd gather the team, collect their inputs, and heroically assemble everything herself because "only she could do it right."

Her excuse was always the same: too many things on her to-do list, not enough time.

But the truth underneath? A combination of perfectionism, lack of trust in her team, poor prioritisation, and a self-identity built on being indispensable. The chaos wasn't happening to her. She was creating it.

Her team saw it clearly. They were frustrated and burned out by the predictable cycle of poor planning but she never acknowledged the real issue, so nothing changed.

Today's Permission Slip:

You have permission to let some fires burn - because not every fire deserves your attention, and putting out every fire is putting out your future.

This feels dangerous because you believe two things that feel true but aren't:

First, that if you don't step in, everything will fall apart. (It won't - at least not the things that actually matter.)

Second, that constant firefighting is what important, meaningful work looks like. (It's not - it's what unsustainable work looks like.)

Here's what leaders who do genuinely important work without constant chaos understand: They know the difference between being a matchstick that burns with a spark and flames out quickly, versus being a candle that burns evenly for a long time.

Matchstick leaders create bright, impressive moments. Candle leaders create sustainable impact.

The shift requires getting comfortable with three uncomfortable truths:

• Your team doing "good enough" work is better than you doing "perfect" work at the cost of everything else.
• Some problems are higher leverage than others - and your job is to focus on those, not to solve everything.
• Some fires will burn themselves out or force others to develop capability - and that's not abandonment, that's development.

This Week's Practice:

This week, when something urgent lands in your lap, pause and ask yourself one question before jumping in:

"Is this problem going to kill the business or project if I don't personally solve it right now?"

If the honest answer is no, then your job isn't to solve it. Your job is to let your team solve it, even if their solution looks different from yours.

Yes, there might be a team conflict that sorts itself out.

Yes, a deliverable might be good enough rather than perfect.

Yes, someone might struggle and learn rather than having you swoop in.

That's not negligence. That's leadership.

Because here's the truth nobody tells you: The fires you keep putting out are burning you down and the organisation you're trying to save by being everywhere is actually being limited by your inability to step back.

This Week's Question:

Which fire are you putting out this week that would actually be better if you let it burn?

Here's to leading differently,

Raghav

P.S. I've launched a youtube channel where I speak with real everyday leaders in the trenches, not influencers, about their careers, the decisions they made, the failures they had and the tradeoffs it took.

If you are tired of hearing the same leadership influencers everywhere, give this a try. The latest episode is live with Matthew Klick Ph.D. on why development is messier than what the textbooks say. https://youtu.be/hvXceX8tbHw​