Stop Making Your Team Wait for You

The leader who has to approve everything has built a job, not a team.

There is a difference between being responsible for the result and being the only person allowed to make a decision. Too many leaders mix those up. They call it oversight. The crew calls it waiting.

A supervisor needs to change a handoff. The team has already found the gap, tested a better way, and agreed on who will use it. But the supervisor cannot put the change in place until somebody above them says yes. That person is busy. The request sits. Another shift comes through the same gap.

Nothing stopped the improvement except a rule nobody remembers choosing.

If you want people to take ownership, give them something real to own. Not just the work after somebody else makes the call. The call itself.

THE WAIT IS PART OF THE COST

Here is how that wait plays out.

A packing crew finishes each shift with a short email about unfinished work. The next crew regularly misses one piece of it because the information is buried between a dozen other messages. The people doing the handoff want to put a simple status board beside the existing work schedule. Open items, next action, person responsible. The next crew can see the work before it starts.

They are not changing a product. They are not buying equipment. They are not bypassing a required check. They are changing how the same information gets passed along.

The supervisor agrees it is worth trying. Then comes the sentence that kills more improvements than any spreadsheet ever will: “I need to run it up the chain.”

The manager is traveling. The next meeting is Thursday. On Thursday, somebody asks whether all the shifts have been consulted. Nobody wants to make the wrong call, so the team is told to put together a short proposal.

Meanwhile, the missed handoffs keep happening.

Look at what this teaches. The team did the hard part. They found the problem, built a simple answer, and offered to test it. The system rewarded that effort with a delay. The next time somebody sees a problem, staying quiet becomes the easier choice.

People learn from what happens after they speak up. If every improvement gets parked, they stop bringing improvements.

Now change one rule. Let the supervisor test a reversible handoff change for two shifts, provided it does not alter safety controls, customer requirements, protected information, or spending. Keep the old method available. Name who checks whether the next crew gets the right information.

The team puts up the board. The next crew can tell them within minutes whether it helps. If it does not, they change it or take it down. Nothing has been hidden. Nothing has been gambled.

The difference is not that leadership stopped caring. It is that leadership stopped making the team wait to care.

THE TRAP HIDES IN GOOD INTENTIONS

Most approval chains begin with a sensible concern. Somebody made an expensive mistake. Somebody changed something without telling the next shift. Somebody had to clean up a mess. So a leader adds a check.

One check becomes two. Two checks become a meeting. Soon nobody can remember which decisions actually carry the risk that started the rule.

The approval remains long after the reason disappears.

This is how organizations end up working harder to protect the old way than to improve the work. Every added permission feels small. Together, they teach people that their judgment is not trusted.

It also creates a problem at the top. When every choice lands on one desk, that desk becomes the slowest point in the operation. A leader spends the day answering questions that the people closest to the work are already capable of answering.

Then the leader complains that the team never takes initiative.

You cannot ask people to own the outcome while keeping every useful decision in your pocket.

TRUST IS NOT A FREE PASS

Removing a needless approval does not mean turning people loose without a standard.

Some decisions should stop at a real boundary. Spending money needs an authorized budget and approval. Safety controls stay in place. Legal obligations, customer specifications, security access, and protected information do not become optional because somebody wants to move faster.

The mistake is treating every small, reversible choice as if it carries the same consequence.

A good standard tells people where they can act, what they must protect, and what to do when they reach the edge. It does not make them hunt down a manager just to prove they asked.

Give the team a clear boundary. If the action stays inside it, they make the call. If the action crosses it, they bring the facts and a recommendation to whoever holds that authority.

That is accountability. The team owns a decision it can make. Leadership owns the boundaries that must not be crossed.

And when the team gets something wrong, the first question is not “Who approved this?” It is “What did the process make hard to see, and what would keep the next crew from repeating it?”

Failure remains possible. That is why the recovery matters.

START WITH ONE DECISION, NOT A REORGANIZATION

You do not need a new chart, a committee, or a speech about empowerment. You need to find one decision that keeps coming back to your desk and move it closer to the work.

Start with five recent requests for your approval. Do not pick the biggest projects. Pick ordinary requests that somebody waited on.

For each one, ask:

Could the person closest to the work see the facts needed to decide?

What could go wrong if they made the call without me?

Could they undo the change, or recover quickly, if it failed?

What rule or requirement actually demands my involvement?

What would I need to teach or provide so they could make this decision next time?

If the answer is “They already knew what I would say,” you probably found your first approval to retire.

Do not replace it with a hidden requirement to keep you informed before they act. That is still permission with a different name.

Write one sentence that tells the team what it owns. For example: “The shift lead can change the handoff format when every shift can read it, the required information stays intact, and the previous version is kept for recovery.”

That is a decision rule. It tells people what they may do and what must remain true.

Now name the person who checks the result. Not somebody whose job is to bless the change before it happens. Somebody who can look at the next shift and answer a useful question: did the handoff improve?

If it did, keep it. If it did not, fix it. If it created a new problem, restore the old method and learn where the boundary failed.

One decision. One owner. One visible result.

THE FIRST TWO SHIFTS TELL THE TRUTH

A rule is only useful if it changes the work.

On the first shift, the person who owns the problem tries the agreed change. They explain what will be different, where to find the information, and how to report a miss. There is no need to turn this into a production.

On the second shift, somebody who did not design the change uses it. That person is the real test. Can they find what they need without calling the first crew? Can they tell what was finished, what is still open, and what happens next?

If the answer is no, the owner learns where the handoff broke. That is better information than another meeting about whether the idea sounded good.

Then look at the next few handoffs. Did the same miss repeat? Did the fix add extra work? Did a new person understand the process without a private explanation?

Keep the check simple. You are trying to make work easier to finish, not create another record nobody reads.

There is a difference between a manager receiving useful information and a manager demanding permission. A good team sends the first without waiting for the second.

WHAT LEADERS HAVE TO GIVE UP

Some leaders say they want a team that thinks for itself. What they mean is a team that anticipates their answer.

That is not the same thing.

If every decision still has to look like yours, people will learn to guess your preference rather than examine the work. They will come to you with safe answers. They will stop trying a better one.

You have to let someone choose a different path within the agreed boundaries. You have to judge the result against the standard, not against whether they would have done it exactly your way.

That can be uncomfortable. It should be. Leadership is not the comfort of being included in every conversation. It is the work of building people who can move when you are not there.

The first few decisions may be clumsy. That tells you where teaching, information, or the boundary is weak. Fix those things. Do not grab the decision back because somebody needed a second try.

When a team brings you a question it should already own, do not just answer it. Ask what information is missing and where the decision should live. Give the answer this time if the work needs it. Then remove the reason they had to ask.

Otherwise, you have solved today’s question and guaranteed tomorrow’s line at your door.

WHAT TO DO ON YOUR NEXT SHIFT

Find the last ordinary approval you gave. Ask the person who brought it what they already knew before they asked you.

If they had the facts, the authority was probably sitting in the wrong place.

Agree on the boundary, the recovery, and the check. Put the decision with that person for the next shift. Then pay attention to what happens.

If they handle it well, do not congratulate yourself for delegating. Change the standard so nobody has to ask for that same permission again.

If it goes poorly, find the gap and fix the system. Keep the ownership where it belongs unless the risk proves the boundary was wrong.

This is how trust turns into something people can use. Not a poster. Not a speech. A real decision made by the person doing the work, with a standard that survives the leader’s absence.

If you want one of these worked through every week, the BBG Leadership Brief takes an ordinary problem from the floor and turns it into a move you can test on your next shift.

A company does not get stronger because every answer runs through one person.

It gets stronger when the work keeps moving without that person in the room.

BIG BEARDED GINGER
Leadership • Systems • Results
bigbeardedginger.com