Skip to main content

Survival vs. Strategy: Balancing Firefighting and Early Wins in a New Role

 


When I started a new role leading a business unit, I discovered fires burning everywhere. Major internal and external issues demanded immediate attention, and I spent my first few months solely addressing these crises.

While necessary, this exclusive focus on firefighting came at a cost: it crowded out the proactive early wins needed to establish my credibility and jumpstart the business strategy.

Success in a new role requires a dual-track approach. It is not an either/or decision; a leader must simultaneously manage urgent operational threats (Firefighting) while executing proactive improvements (Early Wins). A common pitfall is mistaking the "busyness" of crisis management for effectiveness. To succeed, you must distinguish between the "must-do" tasks that protect the business and the "should-do" tasks that advance it.

The simplest way to distinguish between the two is this: Firefighting returns you to zero. Early wins move you to +1.

What is Firefighting?

Firefighting is the allocation of resources to urgent problems that jeopardize the business. The goal of firefighting is stabilization and return to the status quo. 

Key Characteristics: 

  • Fixing the Past: You are repairing what is broken. 
  • "Must Do, Cannot Fail": These issues must be resolved quickly and effectively. 
  • Reactive vs. Proactive: You are correcting a problem, not improving the business. 

Examples:

  • A quality issue goes undetected, resulting in a large shipment of defective product to multiple customers.
  • An inadequately tested software update triggers a surge in customer complaints.
  • A key manager quits unexpectedly, leaving a critical gap in leadership.
  • A high-value client encounters an unexpected issue and threatens to cancel their contract.
  • A new product launch is significantly delayed, jeopardizing future sales revenue. 

Note: Firefighting is often a "necessary evil" in a new role. You may not have lit the match, but as the leader, you are responsible for putting out the fire. However, be careful not to stop at temporary fixes. You must identify root causes to prevent the flames from recurring.

What Are Early Wins?

Early wins are the proactive execution of high-visibility, low-effort initiatives that deliver immediate value. Unlike firefighting, which is forced upon you by circumstance, an early win is a strategic choice.

Key Characteristics: 

  • Building the Future: These wins generate strategic momentum. 
  • Impact over Urgency: Decisions are driven by value creation, not by panic. 
  • Proactive vs. Reactive: While firefighting restores normalcy, an early win creates improvement.

Examples:

  • Install a straightforward machine upgrade to improve operator ergonomics and boost throughput.
  • Eliminate a redundant approval step in the procurement process to speed up the delivery of critical supplies.
  • Renegotiate a software subscription or vendor contract to secure a quick cost-saving without cutting headcount.
  • Streamline the month-end close process to give faster visibility to financial performance.
  • Make a final "Go/No-Go" decision on a project that has been stuck in approval limbo for months to unblock the team.

How to Identify Potential Early Wins

A great source of ideas for early wins is the 'Listening Tour' that you should conduct at the beginning of your new role. Look for the intersection of High Reward and Low Effort when evaluating potential early wins. 

  • Chronic pain points (solving these brings relief).
  • Leadership’s "wish list" (delivering buys political capital).
  • Strategic stepping stone (sets the foundation for long-term goals).

Caution: Avoid "low-hanging fruit" that has no strategic value. The best wins are those that signal your future direction while solving a problem today.

Tips for Early Wins Execution:

  • Scope It: Select no more than 2-3 early wins to avoid diluting your focus.
  • Timebox It: Ensure each initiative can be completed within a few weeks.
  • Formalize It: Treat it as a real project. Define the successful outcome and assign a project lead (ideally a direct report)
  • Manage It: Hold weekly check-ins to monitor progress and remove obstacles.
  • Market It: When the win is achieved, celebrate it! Use town halls and newsletters to signal that change is happening.

Conclusion: From Firefighter to Architect

Stepping into a new leadership role often feels like walking into a burning building. The heat of the immediate crises can be overwhelming, and the temptation to spend every waking hour holding the hose is strong. But remember: Firefighting is about survival, not success.

If you spend your entire tenure reacting to the urgent, you will exhaust yourself merely to keep the business running in place. You will remain stuck at "zero." To truly lead, you must have the discipline to step back from the heat and plant the seeds of the future.

Your goal is not just to be the hero who saves the day; it is to be the architect who builds a better tomorrow. By deliberately carving out space for early wins—those small, strategic moves that take you to "+1"—you earn the trust, momentum, and credibility needed to transform your organization.

So, put out the fires that threaten survival, but don't let the smoke obscure your vision. Find your early wins, execute them quickly, and start building.

 

Comments

Popular posts from this blog

Why I Needed to Leave Toyota

Leaving Toyota was one of the most difficult experiences of my career.  Working there was a transformative experience. I fit naturally into Toyota’s deep-seated culture of continuous improvement, and my values were in total alignment with the company’s. The phrase, “Toyota builds people, not cars,” was completely true. I was given challenges and opportunities, and I experienced rapid growth. Within two years, I had been promoted from specialist to assistant manager. The future was bright, and I envisioned proudly spending the rest of my career at Toyota. And then, my life circumstances changed. I found myself having to leave the company I had grown to love. I grieved this loss for months, even after starting a new job in full-time continuous improvement. It seemed I would never be as happy as I had been at Toyota. I don't subscribe to the "everything happens for a reason" cliché, but I soon became aware of an unexpected silver lining forming around the cloud of my departu...

Scaling the A3 System: Turning Problem‑Solving into an Organizational Capability

Does this sound familiar? A well‑intentioned leader decides it's time to deploy structured problem-solving throughout the organization. They roll out “A3” (or a similar problem‑solving methodology) training sessions, distribute templates, and set expectations that every employee will complete an A3 each quarter. There's energy and focus for a while. But soon, the effort starts to fizzle. The forms get filled out, yet A3 thinking never truly becomes “the way we do business.” In my  last article , I shared the story of my first A3 at Toyota - the crumpled drafts, the red ink, and the eight revisions it took to successfully complete the certification process. That experience taught me that A3 problem‑solving isn’t about filling out a form; it’s about developing a way of thinking. Yet here’s the real challenge:  How do we move beyond individual skill to organizational capability?  How do we scale problem‑solving so it becomes the way the organization continuously improves- no...

Beyond the Template: The Messy Reality of My First Toyota A3

  I walked out of my mentor's office feeling dejected. I had just given him a progress update on my A3 project. "You do not fully understand the problem,” he said. “Go back and redo the second step.” At Toyota, I was required to earn A3 certification by applying the methodology to a real-life problem. It took 8 cycles of revision before the A3 was complete. The picture above shows the final document. What is not shown is the many crumpled versions covered in red ink. The most important lesson I learned from the experience is this:  The power of the A3 is having the courage to stare at the broken process until you understand why it broke. Many leaders fail at problem-solving because they are afraid to look at the "Current State" (the truth). They jump straight to "Future State" (the solution) to avoid the discomfort of the unknown. This bias for action is paradoxically what prevents effective problem-solving.   The following are my core takeaways from...