They're the most capable person on the team. Big clients need them. Complex problems need them. Critical decisions need their approval. They're exhausted — but proud: "No one can do what I do."
But their team? Everyone waits for their approval. Nothing moves without their sign-off. They're increasingly exhausted, the team increasingly dependent. They complain: "Why am I so tired, yet the team still can't move?"
You've probably felt the same. You're not managing — you're "fighting fires."
✧ A Real-Life Scenario That Stings
Years ago, I coached a medical device company's sales director. Let's call him Mr. Lin. Fifteen years in the industry, eight sales teams, five national championships. He was the best "seller" I'd ever met.
But one evening, he sat across from me, worried: "James, my people are busy every day, but we're losing customers. I don't know what's wrong."
I asked: "What are your people busy with?"
"Our product managers take turns visiting clients. A Product goes one day, B Product another, C Product another. Each product manager talks about their own product line. Clients are annoyed; our people are exhausted. Travel costs are millions a year, but returns are declining."
I pressed: "What do clients say?"
He smiled wryly: "Clients say, 'Can't you just send one person who can solve all my problems at once? I don't want to explain our situation over and over.'"
Mr. Lin's team wasn't lazy. They were trapped by "functional islands."
✧ A Perspective-Shifting Insight
You think you're managing a team — you're actually just "fighting fires."
Gartner found that 84% of marketing leaders report experiencing high "collaboration drag" — too many meetings, too much peer feedback, unclear decision rights. Organizations with high collaboration drag are 37% less likely to achieve revenue targets.
Another study notes that in organizations with high turnover, productivity losses can reach hundreds of millions annually. The organization is like a one-legged stool — looks like it can sit but falls with the slightest push.
A "Firefighter's" core value is "I can solve problems." A "Fire Prevention Designer's" core value is "I can help more people solve problems."
Traditional managers make teams dependent on them. Growth Architects make teams independent of anyone.
✧ Four Pillars to Transition from "Firefighting" to "Fire Prevention"
In Catalytic Leap, I propose the Growth Architect's Four Pillars:
Pillar 1: Market Insight and Value Definition — Not just seeing "what customers want," but "why they need it."
Pillar 2: Composite Team Building — Cultivating "T-shaped" talent with deep expertise and broad capability, building resilient teams with "mutual backup."
Pillar 3: Agile Decision-Making and Empowerment — Letting "those who hear the artillery" make decisions, while keeping risks under control.
Pillar 4: Organizational Experience Internalization and Replication — Making every success replicable, every failure learnable.
These four pillars aren't four separate tasks — they're a value chain from input to consolidation: Insight tells you, "Where to go," Team makes you "able to move," Empowerment makes you "move fast," and Internalization makes "every step count."
✧ Mr. Lin's Transformation
We took Mr. Lin's team through in-depth customer interviews. A device procurement director at a second-tier city hospital said something unforgettable: "I don't care about the difference between your A Product and B Product. I care about whether my department runs smoothly, whether my equipment doesn't break down, whether my patients get the best care."
What customers needed wasn't a "product" — it was a "solution."
We restructured the team from "product managers" to "account managers" — each responsible for a region's "full customer lifecycle management," equipped with an "expert resource pool."
Where a quote once required five approval layers, we redesigned empowerment boundaries: standard solutions had independent pricing authority; custom solutions needed expert pool support but no layered approvals.
We also required each account manager to submit three "best practice" cards quarterly. Within six months, the team had accumulated 47 experience cards — new hire onboarding time dropped from 6 months to 2 months.
Mr. Lin was no longer the "busiest person." He became the "freest person" — not because there was nothing to do, but because the team could run itself.
The best managers don't make teams dependent on them — they make teams capable of winning even when they're not there.
✧ Three Questions to Reframe Your Role
If you also want to transition from "firefighter" to "fire prevention designer," ask yourself:
-
Is your team overly dependent on you? — If you're not here today, can they operate independently?
-
Are you "solving problems" or "designing systems"? — The former exhausts you; the latter strengthens the team.
-
Are you "doing it yourself" or "teaching the team"? — One person's capability has a ceiling; a system's impact has no limit.
✧ This Article Is Just an Introduction
What you just read is the tip of the iceberg — core concepts from Chapter 13 of Catalytic Leap: "Growth Architect: Building a Composite Team That Can Fight Hard and Handle Change."
How did Lao Lin's team evolve from "one-person management" to "team management"? How do you use "Sandbox Simulation" to "fight" before you act? How do you use the "T-Shaped Talent Capability Matrix" to cultivate versatile talent?
These answers are in the book.
Catalytic Leap will take you through Diagnosis, Methods, Enablement, Internalization, and Practice — when you're constantly drained by "firefighting," this book will become your "fire prevention system design guide."
If you also want to evolve from "firefighter" to "fire prevention designer" —
① Get a free sample of Catalytic Leap (includes complete Diagnosis section + Change Agility Assessment)
② Visit www.jameschin.sg for the Manager Dilemma Self-Assessment
③ Book a 30-minute free consultation for a direct conversation with the author
This article draws from Chapter 13 of Catalytic Leap. Want to know how to evolve from "firefighter" to "fire prevention designer"? The full answers are in the book.
