Ops Knowledge Garden

Stop Being the Answer

Work in progressLast tended 5 min read

Stop Being the Answer

One of the things I was really good at as a supervisor was answering questions.

Which, looking back, might have been a problem.

I knew the operation. I knew the policies. I had usually dealt with some version of whatever was being brought to me, and—if I am being completely honest—I liked being the person people came to. It feels good to be useful. It feels like leadership when someone brings you a problem and you can make it disappear.

But every time I gave someone an answer, I was also teaching them something.

Sometimes I was teaching them how to think through the problem. Sometimes I was teaching them to come back to me the next time it happened.

Those can look exactly the same in the moment.

Expertise creates a strange trap

You usually become a supervisor because you were good at the work. Then you spend a surprising amount of your time proving that you are still good at it.

The clinical question comes to you. The policy question comes to you. The schedule exception, the difficult customer, the unusual call, the employee who is not sure whether they are allowed to make the obvious decision—all of it comes to you. You answer quickly because you can, which reinforces the idea that bringing it to you was the correct move.

Eventually you become a permission queue.

The operation may even look efficient while this is happening. Decisions are getting made. Problems are getting solved. You are busy all day and everybody can point to how much you handle.

Then you take a day off.

The real measure of supervisory work has always been what happens when you are not there. That idea is already inside my leadership philosophy, but I do not think I understood all of its implications at first. Making yourself unnecessary is not only about training people well. It is also about noticing the ways your own usefulness has become part of the system’s design.

Not every question is the same question

I do not think the answer is to become the annoying manager who responds to everything with “What do you think?”

There are times when someone needs an answer. There are decisions they should not have to make alone. Sometimes the information is genuinely held at another level. Sometimes policy or law fixes the boundary. Sometimes a question is really an employee saying, “I need you to own this risk with me.”

Bringing the question to you may be good judgment rather than dependence.

But there are also questions that reach a supervisor because nobody has ever made it clear that the employee is allowed to answer them.

That is a different problem.

I started thinking about what would happen if a supervisor logged every question that reached them for two weeks. Nothing complicated: what was asked, how risky it actually was, whether it had come up before, and whether the person could reasonably have decided without you.

I suspect patterns would become obvious very quickly.

You might find an experienced employee asking permission for a routine schedule change. You might find that every complaint escalates because nobody knows where their authority ends. You might find ten slightly different questions that are all actually the same missing process. Or you might learn that the team is escalating appropriately because leadership has not given them access to what they need.

I would not judge the exercise by whether the number of questions fell. I would use it to understand what the questions revealed.

Authority has to move with responsibility

“Use your judgment” sounds empowering. It can also leave a person completely exposed.

If a team member is responsible for an outcome but has to return to you for every meaningful decision, they do not own the outcome. You do. You have simply added another person to the communication chain.

Real delegation includes a boundary:

  • You can decide this independently.
  • You can decide it, then tell me.
  • Bring me a recommendation before you act.
  • Stop and escalate before doing anything.

The categories are simple. Their value is in making the boundary explicit before somebody has to guess.

I would start with the five most frequent, lowest-risk decisions. Not because small decisions are the most important, but because they are somewhere safe to practice moving authority. As judgment grows, the boundary can move.

The person should know what they can decide, what kind of risk changes the answer, and whether leadership will support a reasonable decision that did not produce the hoped-for outcome.

That last part matters. If the first imperfect decision causes you to seize the authority back, the original delegation was theater.

Empowerment can become abandonment

There is a version of “empowerment” that is really just leadership refusing to help.

Handing someone a problem without context, authority, or support and telling them to own it can leave them alone with a risk leadership should still be carrying.

I am still trying to locate the line between helping someone develop judgment and making them feel alone with a decision they were not prepared to make. I think the line moves by person, by risk, and sometimes by day. Someone can be completely capable and still need a second brain after a difficult shift.

Maybe the work is not to stop answering questions. Maybe it is to become more deliberate about what an answer is doing.

Is it transferring knowledge? Sharing risk? Clarifying a boundary? Or quietly keeping you at the center of the operation?

That is the question I wish I had asked more often.

Connected notes

Graph View

Backlinks