A leader can keep meeting visible obligations long after the quality of their attention has changed.
They answer messages early and late. They eat at their desk. They keep projects moving. But when someone asks what they think, the opinion that once came easily takes longer to find. Their direct reports begin making decisions without them—not because the leader has invited more ownership, but because waiting for their input has become its own obstacle.
It is tempting to call this a time-management problem. Take a break. Protect your calendar. Get better at switching off.
Those may help. But sometimes the deeper problem is that availability has become part of the job—and part of how the leader knows they are doing it well.
When every unanswered message feels like a dropped responsibility, responsiveness becomes reassuring. You are needed. You are involved. You are still in control of what happens next.
Until the cost shows up in the work that matters most. You are present for the meeting but less able to think in it. You keep tasks moving but have less patience for the people doing them. Your team may still get answers, but it gets less of your judgment.
That is a difficult trade to notice because the activity looks like commitment. A full calendar and a fast reply can make you seem dependable. They can also conceal that the team has learned to route too much through you.
There are real exceptions. Some roles carry genuine urgency, and some decisions cannot safely wait until morning. A leader cannot simply stop responding if doing so shifts serious risk onto someone else. But if nearly everything requires your immediate attention, the answer may not be to get better at absorbing interruptions. The work may be organized around a bottleneck.
And a short break cannot fix a workload that remains unreasonable when you return.
Rest is often treated as a reward for finishing. The problem is that leadership work rarely announces that it is finished. The quarter closes; another one begins. A launch ships; the next deadline appears. If you wait until the work is done to recover, you may be waiting for an ending the job does not provide.
The first step is not to declare yourself burned out or prescribe a dramatic reset. It is to notice what has changed. Are you still offering considered judgment, or mostly reacting? Are your people waiting for decisions that could belong to them? Do you keep checking messages after work because something is truly urgent, or because not checking leaves you feeling less useful?
Then make a boundary where the work allows one. You might tell the team when you will next review a nonurgent request rather than answering it immediately. You might protect a meal from becoming another work session. You might ask which decisions genuinely need your involvement—and what would have to change for others to own them.
These are not magic fixes. If deadlines, staffing, or expectations are the source of the strain, those conditions need attention too. A leader cannot recover their way out of a system that keeps demanding more than it can sustain.
But constant availability is not neutral. It trains people to wait for you, and it trains you to treat every pause as a risk. Eventually, being available can crowd out the reason people needed your leadership in the first place: your attention, judgment, and ability to help the team do its work.
Notice what your availability is protecting. Then ask what it is costing—and whether the team has a way to work when you are not the answer.
