When being helpful starts creating dependence—and what intentional availability looks like.
Have you ever had one of those days when it feels like everyone needs something from you?
A question turns into a phone call. The phone call runs into a meeting. Someone needs a quick decision before the meeting ends, and when you finally get back to what you planned to work on, another message comes through. None of these things is necessarily unimportant. Most of them probably deserve an answer at some point.
That is what makes availability such an interesting leadership problem.
For a long time, I viewed being available as one of the signs of a good leader. I still believe leaders need to be accessible. People should feel comfortable bringing us problems, asking for help, challenging an idea, or telling us when something isn’t working. I never want someone on my team thinking they can’t reach me when it matters.
But there is another side to availability that took me longer to recognize. If I am available for every question, every decision, and every problem, I can unintentionally create a team that needs me for every question, every decision, and every problem.
At that point, availability isn’t strengthening the team anymore. It is creating dependence.
The challenge isn’t deciding whether leaders should be available. Of course we should. The harder question is what kind of availability actually helps people grow.
When Being Helpful Stops Being Helpful
Most leaders don’t create dependency because they want control. I think it usually starts from a much better place: we want to help.
Someone brings us a problem we have seen before, and we know the answer. Giving it to them takes two minutes. Coaching them through the problem might take fifteen. When the calendar is already full, the efficient choice seems obvious.
So we answer.
The next time they have a similar problem, they come back. We answer that one too. Eventually, neither person really notices the pattern. The employee has learned that asking the leader is the fastest and safest way forward, and the leader has learned that answering the question is faster than developing the person.
Both are being rational in the moment.
The problem shows up later.
I have seen how easy it is for capable people to become hesitant when they get used to checking with the leader before moving. They aren’t incapable of making the decision. They simply haven’t had enough opportunities to exercise that judgment without someone above them confirming the answer first.
That matters because judgment is developed by using it. We can talk about empowerment and accountability all we want, but if every meaningful decision still comes back to the leader, we aren’t really giving people either one.
Sometimes the most helpful thing I can do is not give someone the answer I already know.
That can be difficult, especially when I could solve the problem quickly. But my responsibility isn’t only to get today’s decision right. I also have a responsibility to help someone become better prepared to make tomorrow’s decision without me.
Support Is Different From Rescue
There is a distinction I have learned to pay attention to in leadership: am I supporting someone through the problem, or am I rescuing them from having to work through it?
They can look very similar from the outside.
Support might mean helping someone clarify the problem, giving them context they don’t have, asking questions, talking through risk, or making sure they understand the boundaries around the decision. The person still owns the problem and, whenever possible, the decision.
Rescue is different. Rescue is when the problem changes owners.
The person brings it to me, and I take it from there.
There are absolutely times when that is appropriate. Safety issues, ethical concerns, serious customer harm, significant financial exposure, legal issues, or decisions beyond someone’s authority may require a leader to step in immediately. Good leadership doesn’t mean turning every situation into a coaching exercise.
Most daily decisions aren’t at that level, though.
When someone brings me a problem, I’ve found that a few questions usually tell me whether they need my decision or whether they need help trusting their own.
What do you think is really happening here? What have you already tried? What options have you considered? What do you recommend? What are you worried could happen if you make that choice?
Those questions slow the conversation down, but that isn’t wasted time. The conversation itself is part of the development.
If I continually make decisions for someone, I can’t be surprised when they continue bringing decisions to me.
Every Yes Comes From Somewhere
There is another side to constant availability that has less to do with the team and more to do with the leader.
That sounds obvious, but I don’t think we always lead as if it’s true. We look at an open spot on the calendar and think we have time for another meeting. We answer a message at night because it will only take a minute. We accept another responsibility because technically we can fit it in.
The problem is that time doesn’t work in isolation. That thirty-minute meeting doesn’t just cost thirty minutes. It may replace the time I needed to think through a decision. The message I answer during dinner doesn’t take long, but it takes my attention away from the people sitting in front of me. The problem I solve for someone else may push my own work later into the evening.
This is one place where Stoicism becomes very practical for me.
Seneca wrote about time as something people guard far less carefully than money, even though time is the one resource we can never recover. Nearly two thousand years later, the problem hasn’t changed much. We just have more ways to give our time away.
Leadership doesn’t make time less finite.
So the question I have started asking isn’t simply, Do I have time for this?
Usually, I can find the time.
The better question is, What will this replace?
That forces a different kind of decision. Another meeting might be worthwhile, but it isn’t free. Another yes may be the right answer, but it means something else is receiving a no.
Good Boundaries Should Make Leadership Clearer
I think the word boundaries sometimes creates the wrong picture in leadership. It can sound like putting up a wall between ourselves and everyone else.
That isn’t what I mean.
Good leadership boundaries should create clarity, not distance.
People don’t necessarily need unlimited access to their leader. They need to know when they should involve the leader, what they have authority to handle themselves, how quickly they can expect a response, and where they can go when something truly can’t wait.
That kind of predictability can create more trust than being constantly available.
If I respond immediately to everything, the team has no reason to distinguish between a real escalation and normal uncertainty. Everything gets treated the same because everything receives the same response.
A better approach is to make the difference clear.
There are things I want brought to me quickly: safety concerns, ethical issues, serious customer harm, significant legal or financial exposure, and decisions that exceed someone’s authority or could create lasting consequences.
But there are also plenty of decisions where the person closest to the work should be able to move without waiting for me.
One question I think leaders and teams could ask more often is simple: Was this really an escalation, or were we just uncomfortable making the decision?
Those aren’t the same thing.
If every uncomfortable decision gets pushed upward, we eventually create an organization where people become very good at escalating and very cautious about owning.
Responsibility Without Authority Doesn’t Work
This is where the conversation about availability becomes a conversation about accountability.
We often tell people we want them to take more ownership. But ownership becomes difficult when someone is responsible for an outcome without having enough authority to make the decisions required to produce it.
We can’t tell a manager, This is yours, and then require approval for every meaningful choice along the way.
If we want people to operate with less dependence on us, we have to give them a clear field to operate within. They need to understand what they can decide, where the limits are, what standards aren’t negotiable, what level of risk is acceptable, and when the decision moves beyond their authority.
Then we have to let them use that authority.
That last part can be uncomfortable for leaders.
Someone may choose a path we wouldn’t have chosen. They may make a decision differently than we would have. They may even make a mistake.
The question can’t always be, Did they do it exactly the way I would have done it?
A better question is whether they used sound judgment within the boundaries we established.
Then we can debrief the decision. What worked? What did they miss? What would they do differently next time? What did we learn that should change the way we approach a similar decision in the future?
That is where accountability and development start working together.
If I take the decision back the moment I become uncomfortable, I haven’t really delegated authority. I’ve delegated the work while keeping control.
Being Needed Can Feel Like Leadership
There is another part of this that is probably worth admitting.
Being needed can feel good.
There is something satisfying about being the person people call when they don’t know what to do. We know the history. We have experience. We can often see the answer faster because we have encountered the problem before.
It can make us feel valuable.
I don’t think there is anything inherently wrong with that. Leaders should bring value. Experience should matter.
But there is a trap if being needed becomes the way we measure whether we are leading well.
If every important decision needs me, what happens when I’m gone?
If the team performs well only when I’m in the room, have I built a strong team, or have I built a team around me?
Those are different accomplishments.
For me, one of the better measures of leadership is what continues to happen when the leader isn’t there. Can people make good decisions while I’m on vacation? Can two leaders disagree, work through it, and move forward without asking me to decide who is right? Can someone explain the reasoning behind a decision rather than saying, Brad told us to do it this way?
Those moments tell me something.
They mean judgment is spreading.
The goal isn’t to make ourselves unnecessary in the sense that our leadership no longer matters. The goal is to stop making ourselves necessary to every decision.
There is a big difference.
Look at What Happens When You’re Gone
One of the clearest ways to understand whether our availability is helping or hurting may be to pay attention to what happens when we aren’t available.
Vacation is particularly good at exposing this.
If decisions pile up waiting for our return, that is information. If routine work slows down because people aren’t sure what they are allowed to decide, that is information too. If the same people who are confident when we’re present suddenly become hesitant when we’re gone, we should pay attention to that.
Our first reaction might be frustration with the team.
I think there is a better response.
What have I taught them?
Maybe I haven’t made decision authority clear enough. Maybe I have answered too many questions instead of asking enough. Maybe people have learned through my behavior that getting my approval is more important than exercising their own judgment.
Those aren’t reasons to blame ourselves either. They are feedback.
And feedback gives us something to work on.
A leader who comes back from vacation to a list of decisions waiting for approval doesn’t necessarily need to become more available. The better opportunity may be to ask why those decisions couldn’t happen without them.
Intentional Availability Makes Us More Present
None of this is an argument for leaders disappearing behind their calendars.
I don’t want to lead that way.
There are moments when our people need us, and I want to be there for those moments. Sometimes someone needs coaching. Sometimes a difficult conversation requires our full attention. Sometimes the stakes really are high, and the decision belongs with us. Sometimes a person doesn’t need a process or another question; they just need their leader to listen.
Those moments are part of the job.
But being partially available to everyone all the time can make it harder to be fully available when it actually matters.
That’s the distinction I want.
Intentional availability means deciding where my presence adds the most value and protecting enough of my attention to actually be present there. It means being willing to let a routine question wait so I can give a difficult conversation my full attention. It means protecting time to think instead of allowing every empty space on the calendar to be claimed. It means making room for my health and family instead of assuming they will somehow fit around whatever work leaves behind.
It also means recognizing that saying no, not now, or you can make this decision isn’t a withdrawal of leadership.
Sometimes it is exactly what leadership requires.
The dichotomy of control at work has been useful for me here. I can’t control whether everyone likes a boundary or whether someone would prefer an immediate answer. I can control whether I am clear, consistent, fair, and available when the situation genuinely requires me.
That is enough.
A Better Measure of Leader Availability
Maybe we have been asking the wrong question about availability.
Can my people reach me when they need me? still matters. I don’t want to lose that.
But I think there is another question worth adding:
Does the way I make myself available help people become more capable without me?
That changes how I look at my calendar, my interruptions, and even the questions people bring me.
The goal is no longer to answer as quickly as possible. It is to understand what the moment requires. Sometimes that will be an answer. Sometimes it will be a question. Sometimes it will be coaching, context, or clearer authority. And sometimes the best thing I can do is leave the decision where it belongs and give someone the opportunity to make it.
Time is finite. So is attention. We cannot be available for everything without becoming less available for something else.
The discipline is deciding what deserves our presence and what needs enough space to grow without it.
The best availability doesn’t make the leader more necessary.
It makes the people around them more capable.