A director I'm coaching answered one question last month that changed how she leads.
The question: "What would happen if you took 30 days off?"
She didn't hesitate:
"My entire team would panic. Nothing's documented. I'm the only one who knows how things work."
She's not struggling. Her numbers are up. Her team delivers. She's been promoted twice in three years. By every organizational metric, she's a success story.
But her success can't survive without her in the room.
I see this pattern constantly — not just with individual leaders, but across entire management layers. And it points to a development gap that most L&D teams aren't measuring.
The Difference Between Accumulating and Compounding
When I work with leadership teams, I draw a distinction that usually lands hard:
Accumulating success means more output requires more input. More clients means more hours. More revenue means more of the manager's personal involvement. Growth is linear and fragile — it breaks the moment the person driving it steps away.
Compounding success means this month's work makes next month easier. Systems replace individual effort. The team operates from shared frameworks, not one person's memory. Growth sustains itself.
Most organizations are developing managers who accumulate. They reward individual heroics. They promote the person who stays latest, remembers everything, and personally handles every escalation. Then they're surprised when those managers burn out, when their teams can't function independently, and when succession planning is a fiction.
The 30-day question reveals the truth: if your best manager disappeared for a month, would their team keep running? If the answer is no, you don't have a leadership success. You have a single point of failure with a title.
Why This Is an L&D Problem
This isn't a performance problem — these managers are performing. It's a development problem. Somewhere in their growth, they learned that their value comes from being needed rather than from building something that doesn't need them.
Most leadership development programs reinforce this accidentally. They teach managers how to lead better — run better meetings, give better feedback, make better decisions. All critical skills. But they don't teach managers when to stop doing and start systematizing.
The gap shows up in three ways I see repeatedly across organizations:
The Knowledge Hoarder
Not malicious — just never taught to document. They hold institutional knowledge in their head because no one ever showed them that writing it down was part of the job. Their team is dependent by default, not by design.
The Quality Gatekeeper
They review every deliverable because they believe quality requires their personal touch. The team learns to wait for approval instead of developing judgment. Decisions bottleneck. Speed drops. And the manager works 55 hours a week calling it "high standards."
The Heroic Firefighter
They handle every escalation personally because they're good at it and it feels urgent. The team never learns to resolve conflict, manage difficult clients, or make calls under pressure. Six months after this manager gets promoted, the team collapses — and the organization blames the new manager instead of the missing system.
All three patterns share the same root: a manager who was developed to perform, not to compound.
What Development That Compounds Looks Like
The organizations I've seen get this right — from Fortune 100 companies to mid-market teams scaling fast — do something counterintuitive. They teach managers to make themselves less essential, not more.
Here's what that looks like in practice:
1. They build "systematize" into the management competency model.
Not as an afterthought. As a core expectation. When a manager's performance review includes "what did you document, delegate, or automate this quarter?" the behavior shifts. The message stops being "be indispensable" and starts being "build something that outlasts your involvement."
2. They teach systems thinking before strategic thinking.
A new manager doesn't need a leadership philosophy. They need to know how to turn the meeting they run every week into a template someone else can run. How to turn the decision they make every time into criteria their team can apply. How to take the thing they do on autopilot and make it visible, repeatable, and transferable. One system per month changes a manager's entire operating model within a quarter.
3. They measure team independence, not just team performance.
A team that hits its numbers because the manager personally drives every outcome looks great on a dashboard. A team that hits its numbers when the manager is on vacation — that's a developed team. The distinction matters for succession planning, for scale, and for the manager's own sustainability. The organizations that track this are the ones that retain their best leaders longest, because those leaders aren't burning out to hold things together.
4. They create transition support, not just training events.
The 90 days after a promotion or role change determine whether a manager builds compounding habits or accumulating ones. A two-day offsite in Q3 doesn't address what happens on the first Monday. Weekly check-ins, a simple decision framework, and explicit permission to stop doing their old job — that's what shapes the leader they become.
The Culture Signal
Here's what I tell every CHRO and VP of Learning I work with: the way your managers operate is a culture statement.
If your best managers are working 55 hours a week and their teams can't function without them, that's not a badge of commitment. That's a development failure with a retention clock on it. Those managers will leave. Or they'll stay and decline. Either way, you lose.
The organizations building activated leaders — leaders who are clear, focused, and creating systems that compound — are the ones asking a different question in development conversations. Not "how do we make our managers better?" but "how do we make our managers' impact last beyond their personal capacity?"
That's the shift from accumulating to compounding.
And it starts with one question:
What would happen if they took 30 days off?
If you don't like the answer, that's not a management problem. That's your next L&D priority.
Leadership Workshops — Half-day intensives where your management team diagnoses what's accumulating vs. compounding, builds their first systems, and creates accountability structures that outlast the workshop.
Explore here →
Keynote Speaking — Bring The Activated Leader methodology to your next leadership summit, SKO, or manager development cohort. Your people leave with a framework they use on Monday.
Book Lilah →
The Activation Diagnostic — For individual leaders navigating a transition. One paid session. One clear answer. One action plan.
Book your diagnostic →
