Mike, a sales leader at a global technology company who was five months into his new role, faced a choice that felt impossible. He needed to compile a report for an executive meeting. He could do it himself—another late night, another task added to an already crushing workload—or he could delegate it.
But he hesitated. Explaining the nuances, training the team to meet his standards and answering the inevitable follow-up questions felt like it would take more time than he actually had. So, he did it himself. Again.
But he hesitated. Explaining the nuances, training the team to meet his standards and answering the inevitable follow-up questions felt like it would take more time than he actually had. So, he did it himself. Again.
Here's the paradox many leaders face: As you move higher and have a bigger team, it feels like you should have more support. But often, the higher you go, the more overwhelmed you feel as a leader.
Mike isn't alone. According to Deloitte's Global Millennial and Gen Z Survey, "48% of workers and 53% of managers admit they are burned out at work." Research by Harvard Business Impact found that 85% of mid-level leaders experience burnout weekly.
Most leaders assume they feel overloaded because they're doing too much—too many meetings, too many decisions, too much work. But that's not always what's actually happening. Leaders often feel overloaded because they're carrying work the system wasn't designed to handle.
Mike isn't alone. According to Deloitte's Global Millennial and Gen Z Survey, "48% of workers and 53% of managers admit they are burned out at work." Research by Harvard Business Impact found that 85% of mid-level leaders experience burnout weekly.
Most leaders assume they feel overloaded because they're doing too much—too many meetings, too many decisions, too much work. But that's not always what's actually happening. Leaders often feel overloaded because they're carrying work the system wasn't designed to handle.
How Leaders Get Overloaded
When work doesn't get handled at the team level, it moves up to the leader level. Leaders often absorb unclear ownership. They field implicit expectations. They bridge coordination gaps. They make decisions that have no defined owner. They often don't do it by choice. They are expected to fill those gaps by default.
Every unclear task creates a question that flies to your inbox. Every vague expectation creates a follow-up conversation. Every undecided boundary creates a decision that defaults to you. Individually, these moments may seem small. But collectively, they turn you into the organizational glue holding fragmented work together.
The choice that Mike faced—do it myself or take time I don't have to explain it—wasn't really a choice at all. It was a symptom of a system that hadn't been designed to function without him.
Why Capable Teams Still Escalate
You may have a team of experts who still aren't operating at their best. And this doesn't happen because they lack capability or engagement. The real reason is that no one made ownership and expectations explicit enough to let them decide with confidence.
Teams escalate issues not because they're incompetent but because the system rewards "just checking" upward. When boundaries are unclear and expectations are implicit, it is safer to ask questions than to decide. This happens to good teams with strong leaders. And it's not about the people—they come and go, but the problem stays the same. The issue is that the work itself hasn't been integrated into roles that let the team function without constant escalation.
The Real Cost
The real cost is both individual and organizational. On the individual level, we have burned-out leaders. But together with that, we also have disengaged teams—teams that don't own their decisions or have full control over their work and teams that are slowed down by leadership bottlenecks. And despite everyone having the very best intentions, organizations are left with overloaded and burned-out leaders and disengaged teams.
The Three Pillars Of Integrated Work
So, how do leaders break this cycle? By moving from "solving" to "system building." This shift is a core component of integrated work—one of the five pillars of the CLICK framework I developed for building self-sufficient teams.
As I explore in my book, CLICKING, true integration allows a team to handle what currently defaults to the leader by navigating three specific shifts:
1. From Implicit To Explicit Ownership
Capable teams escalate not because they lack skill but because boundaries are fuzzy and it's safer to ask than decide.
Mike's account executives used to ask for approval before offering any customer concessions—every single time. Mike clarified ownership in two sentences: "You own the customer relationship. If a concession fits the deal strategy, it's yours to decide." Escalation of routine concessions dropped immediately.
2. From Saving To Designing
Leaders break through when they stop "saving" their teams and start designing systems.
Mike invested time up front to create clear decision frameworks—time he didn't think he had but that proved essential for building self-sufficiency. He established simple rules: Account managers could approve customer requests up to $20,000 or 5% of the contract value—whichever was lower. "Just let me know what the case was and what decision you made," he told them. His team stopped waiting for approval and started solving problems themselves.
3. From Workload To Architecture
Burnout is rarely a "volume of work" problem; it's a "design of work" problem. If your calendar is full of tasks that shouldn't require your input, it's a signal for a redesign.
Mike asked his team to list every decision where they felt dependent on him. Then, in a team session, they mapped those decisions into four zones:
• Decisions Owned By Leaders: Strategic decisions requiring broad context (hiring, budgets, cross-functional trade-offs)
• Decisions Shared By The Team: Decisions affecting how the team functions together (norms, meeting cadence, priorities)
• Decisions Owned By Individual Contributors: Day-to-day decisions where speed and autonomy matter (task approach, tools, client issues)
• Decisions That Must Be Escalated: High-risk decisions requiring senior input (compliance, cross-department coordination)
Once the architecture was clear, Mike's calendar freed up. His team knew exactly what they owned—and what required his involvement.
If your calendar is full of meetings and tasks that shouldn't require your input, the question isn't how much you're working. It's what your team design is forcing you to carry—and whether you're ready to invest the time now to build systems that let your team handle what currently defaults to you.
When work doesn't get handled at the team level, it moves up to the leader level. Leaders often absorb unclear ownership. They field implicit expectations. They bridge coordination gaps. They make decisions that have no defined owner. They often don't do it by choice. They are expected to fill those gaps by default.
Every unclear task creates a question that flies to your inbox. Every vague expectation creates a follow-up conversation. Every undecided boundary creates a decision that defaults to you. Individually, these moments may seem small. But collectively, they turn you into the organizational glue holding fragmented work together.
The choice that Mike faced—do it myself or take time I don't have to explain it—wasn't really a choice at all. It was a symptom of a system that hadn't been designed to function without him.
Why Capable Teams Still Escalate
You may have a team of experts who still aren't operating at their best. And this doesn't happen because they lack capability or engagement. The real reason is that no one made ownership and expectations explicit enough to let them decide with confidence.
Teams escalate issues not because they're incompetent but because the system rewards "just checking" upward. When boundaries are unclear and expectations are implicit, it is safer to ask questions than to decide. This happens to good teams with strong leaders. And it's not about the people—they come and go, but the problem stays the same. The issue is that the work itself hasn't been integrated into roles that let the team function without constant escalation.
The Real Cost
The real cost is both individual and organizational. On the individual level, we have burned-out leaders. But together with that, we also have disengaged teams—teams that don't own their decisions or have full control over their work and teams that are slowed down by leadership bottlenecks. And despite everyone having the very best intentions, organizations are left with overloaded and burned-out leaders and disengaged teams.
The Three Pillars Of Integrated Work
So, how do leaders break this cycle? By moving from "solving" to "system building." This shift is a core component of integrated work—one of the five pillars of the CLICK framework I developed for building self-sufficient teams.
As I explore in my book, CLICKING, true integration allows a team to handle what currently defaults to the leader by navigating three specific shifts:
1. From Implicit To Explicit Ownership
Capable teams escalate not because they lack skill but because boundaries are fuzzy and it's safer to ask than decide.
Mike's account executives used to ask for approval before offering any customer concessions—every single time. Mike clarified ownership in two sentences: "You own the customer relationship. If a concession fits the deal strategy, it's yours to decide." Escalation of routine concessions dropped immediately.
2. From Saving To Designing
Leaders break through when they stop "saving" their teams and start designing systems.
Mike invested time up front to create clear decision frameworks—time he didn't think he had but that proved essential for building self-sufficiency. He established simple rules: Account managers could approve customer requests up to $20,000 or 5% of the contract value—whichever was lower. "Just let me know what the case was and what decision you made," he told them. His team stopped waiting for approval and started solving problems themselves.
3. From Workload To Architecture
Burnout is rarely a "volume of work" problem; it's a "design of work" problem. If your calendar is full of tasks that shouldn't require your input, it's a signal for a redesign.
Mike asked his team to list every decision where they felt dependent on him. Then, in a team session, they mapped those decisions into four zones:
• Decisions Owned By Leaders: Strategic decisions requiring broad context (hiring, budgets, cross-functional trade-offs)
• Decisions Shared By The Team: Decisions affecting how the team functions together (norms, meeting cadence, priorities)
• Decisions Owned By Individual Contributors: Day-to-day decisions where speed and autonomy matter (task approach, tools, client issues)
• Decisions That Must Be Escalated: High-risk decisions requiring senior input (compliance, cross-department coordination)
Once the architecture was clear, Mike's calendar freed up. His team knew exactly what they owned—and what required his involvement.
If your calendar is full of meetings and tasks that shouldn't require your input, the question isn't how much you're working. It's what your team design is forcing you to carry—and whether you're ready to invest the time now to build systems that let your team handle what currently defaults to you.