Search Everything in One Place

Explore the web, images, videos, news, and more – all in one place.

Finance

The approval trap: Why your team keeps coming back to you

The Approval Trap: Why Your Team Keeps Coming Back to You

Illustration: Getty Images

If every decision needs you, you built a bottleneck.

If every decision needs you, you built a bottleneck.

If your team needs your approval for every move, it’s easy to blame a lack of initiative. But the problem usually isn’t your people. It’s a lack of clarity. 

People do not wait because they are passive. They wait because they are unsure what they are allowed to do. That is a structure problem, not a people problem. 

1. Clarify decision boundaries. 

Your team needs to know where their authority begins and ends.  

Are there decisions they can make on their own? What requires your input? What should be escalated and under what circumstances? 

Without clear answers to those questions, the safest move is always to ask. You have accidentally trained your team to check in by never making it clear that they do not have to.  

Write it down if you must. The more explicit you are about what falls within someone’s lane, the less often they will knock on your door. 

2. Share your thinking. 

Telling people what to do only works in the moment. If you want your team to make good decisions without you, they need to understand how you think. 

Walk them through your reasoning when you make calls. Explain what you weighed, what you prioritized, and why you landed where you did. Share examples of decisions that went well and ones that did not.  

Over time, your team starts to internalize your judgment and apply it on their own. That is the only way delegation actually scales

3. Normalize smart risk-taking. 

If every mistake gets treated as a problem, people will stop acting without permission. That is a rational response to the incentives you have created.  

Why take initiative if getting it wrong is worse than not trying? 

Build an environment where thoughtful risk is acceptable. When something goes wrong, the first question should be what can be learned, not who is to blame.  

Confidence comes from feeling safe enough to act, not from being told to be more confident. 

4. Recognize ownership. 

When someone makes a strong call, say so. Name it specifically. Make it visible to the team. The behavior you acknowledge is the behavior that spreads.  

If the only decisions that get noticed are the ones that go sideways, you are shaping your culture in the wrong direction. 

Ownership becomes a norm when it is treated like one. 

What changes when this works 

A team that waits creates a bottleneck at the top of the org chart. Every decision that flows through you is a decision that slows down. Multiply that across a week and you can see where your time goes. 

A team that acts moves the business forward without you in the room. Your job is not to be the decision maker for everything. It is to build the structure and trust that lets your team decide without you. 

That is the difference between a business that depends on you and one that does not. 

This post originally appeared at inc.com.

“Click here to subscribe to the Inc. newsletter: inc.com/newsletters"

Read full story on Inc.

Related News

More stories you might be interested in.

Top