You say you're accessible. Your calendar says you're interruptible. There's a difference — and most leaders have confused the two for so long that they've quietly built a team that can't function without them.
The open door is one of leadership's most durable myths. Keep it open, the thinking goes, and your team will know you're available, approachable, and invested. What actually happens is more complicated.
Every time someone walks through that door to ask you to bless a decision they could have made themselves, you train them. Not to make better decisions — to escalate instead of think. To route judgment upward rather than exercise it in place. The pattern becomes self-reinforcing: the more you're available, the more they check with you. The more they check with you, the more they need to.
Availability feels supportive. It reads as servant leadership. It signals that you're not the kind of leader who disappears behind closed doors. These are real virtues, misapplied.
Over-availability doesn't build a capable team. It builds a hesitant one. A team that checks with you on everything will blame you for everything — because they've never been given the conditions in which to own anything. They've been given access to your judgment instead of the opportunity to develop theirs.
A team that checks with you on everything will blame you for everything. Ownership grows in the space you stop occupying.
The solution isn't to become unavailable. It's to be available in a way that develops capability rather than substituting for it. Three structural moves make the difference:
Define decision rights in writing. Not as a general policy — as a specific map. Which decisions does each role own outright? Which require input from you? Which require your sign-off? When these boundaries are explicit, people stop asking not because they're afraid to, but because they know. Ambiguity is what drives escalation, not deference.
Set two office-hour windows per week. Bounded availability is more useful than open availability. It communicates that you are genuinely accessible — on a schedule that allows you to give real attention rather than half-attention throughout the day. And it forces the person preparing to raise something to decide whether it actually needs to wait for you, or whether they can resolve it themselves.
Return questions with a question. When someone comes to you with a decision they could make, try this: "What would you do if I were unavailable?" Not as a rebuke — as a genuine question. You'll find that most people have an answer. They just needed permission to trust it.
Here's a question worth sitting with: if your team had to operate for 30 days without access to you, what would break first?
If your honest answer is "the quality of decisions," that tells you something important. Not about their capability — about what you've built. The most capable leaders I work with are the ones whose teams could function at a high level in their absence. Not because they've delegated everything, but because they've built genuine decision-making capacity into the people around them — not just access to their own.
Accessibility is a virtue. Interruptibility is a habit. The Accessibility Trap is what happens when leaders mistake one for the other — and the team pays the price.
The accessibility trap is the confusion between being accessible to your team and being interruptible by them. Leaders who conflate these two things end up always available for small decisions, which signals to their team that every problem should come to them. Over time, this creates dependency — the team stops developing the judgment to handle things independently because they know the leader will handle it for them. The leader feels useful. The organization becomes fragile.
Constant accessibility trains the team to outsource judgment upward. When the leader is always one message away from resolving ambiguity, people stop developing their own capacity to sit with uncertainty and decide. The organization's effective decision-making capacity becomes bounded by the leader's availability — which is far smaller than what the organization needs to move at the speed it claims to want.
Leaders should distinguish between being accessible for high-stakes input — the conversations where their judgment genuinely adds value — and being available for routine problem resolution that others should be handling. The practical version is structured availability: specific times for open questions, combined with a clear signal that most decisions should be made without them. Over time, this forces the team to develop the capability that constant accessibility was preventing.
The Velocity Gap Assessment surfaces where your organization's decision-making is bottlenecked at the leadership level — and what it takes to distribute that capacity where it belongs.