Most managers are actually terrified of letting go. They say they want to "delegate," but what they really do is hover. It’s that nervous energy where you give someone a task and then Slack them every twenty minutes to see how it’s going. Honestly, that isn't leadership. It’s babysitting. If you want to know how to empower your team, you have to start by accepting one uncomfortable truth: they might do it differently than you. And that’s fine.
Actually, it’s better than fine. It’s necessary.
The psychological safety trap
Google spent years on something called Project Aristotle. They wanted to figure out why some teams crushed it while others, filled with equally smart people, just flopped. They found that "psychological safety" was the biggest predictor of success. It’s not about being "nice." It’s about whether a junior designer feels like they can tell the Creative Director their idea is kind of dated without getting fired or mocked.
When people feel safe, they take risks. When they take risks, they own the outcome.
I’ve seen too many bosses try to "empower" people by giving them more work but zero authority. You’ve probably been there. You get assigned a project, you spend forty hours on it, and then your boss changes every single slide because "it’s not how I would have phrased it." That’s the fastest way to kill morale. People stop trying. They just start waiting for your instructions because why bother put in the effort if it’s going to be overwritten anyway?
Stop being the bottleneck
If every decision has to cross your desk, you aren't a leader. You're a clog.
High-growth companies like Netflix use a concept called "Context, Not Control." Reed Hastings, the co-founder, famously bragged about how few decisions he actually made. The goal is to provide your team with all the information they need—the "why," the budget, the deadline, the stakes—and then get out of the way.
Why transparency matters more than "vibe"
You can’t empower people if they’re working in the dark. If they don't know the company's financial health or the long-term roadmap, they're just guessing. Empowerment requires data.
👉 See also: Town & Country Collision Service: Why Your Choice of Body Shop Actually Matters
- Give them the messy spreadsheets.
- Invite them to the "boring" stakeholder meetings.
- Share the feedback from the board, even the harsh stuff.
When people have the same context you do, they usually make the same decisions you would. Or better ones.
The "70% Rule" for decision making
A lot of managers struggle with how to empower your team because they’re perfectionists. They think if a task isn't done 100% the way they’d do it, it’s a failure. That is a trap.
Try the 70% rule: If a team member can do the task at least 70% as well as you can, let them do it. That remaining 30% gap is where their growth happens. If you step in to fix it, you’re stealing their learning opportunity. It’s basically professional development disguised as restraint.
It feels risky. It is risky. But the alternative is you working 80-hour weeks while your team gets bored and quits.
Real talk: Coaching vs. Fixing
Most people think they are coaching when they are actually just giving orders with a smile. Coaching is about asking questions.
Instead of saying, "You should call the client and apologize," try asking, "How do you think we should handle the client's frustration?" It takes longer. It’s frustrating when you already know the answer. But the moment they come up with the solution themselves, they own it. They’ll work harder to make their solution work than they ever would for your solution.
Edgar Schein, a former professor at MIT Sloan, wrote a whole book on this called Humble Inquiry. His take? We live in a world where "telling" is rewarded, but "asking" is what actually builds capability.
The feedback loop needs to be a circle
Stop doing annual reviews. They’re useless. By the time December rolls around, nobody remembers what happened in March. Empowered teams need real-time, radical candor. If something is off, say it now. If something is great, shout it out immediately.
But here is the kicker: you have to let them give you feedback too. If you can't take a hit on your leadership style from a direct report, you haven't built an empowered team. You've built a hierarchy of fear.
Let them fail (within reason)
You have to create "safe-to-fail" zones. In software engineering, this is why we have "sandboxes." It’s a place to play where you won't break the main site. Leadership is the same.
📖 Related: Other Words for Invest: Why the Language of Money is Changing
Give your team a project with a small budget and a non-critical deadline. Let them run the whole thing. If they blow the budget or miss the mark, don't scream. Sit down and do a post-mortem. Ask: "What did we learn? How do we not do that again?"
If you punish every mistake, you’re essentially training your team to be invisible. They’ll do the bare minimum to stay safe.
The "Ownership" mindset vs. "Renting"
Think about the difference between someone who owns a house and someone who is renting an apartment. A renter might ignore a leaky faucet because it’s not their problem. An owner fixes it because they care about the long-term value.
To figure out how to empower your team, you have to give them "deeds," not just "tasks." Give them an entire outcome. Instead of "Write three social media posts," try "Grow our engagement by 10% this month." The first one is a chore. The second one is a mission.
People want to feel like their work matters. They want to see their thumbprints on the final product.
Actionable steps for Monday morning
Stop overthinking it. Start small. Empowerment isn't a grand speech you give in the breakroom; it's a series of small, daily choices to trust people more than your own ego.
- Audit your calendar. Look at every meeting you’re in. Could a team member lead it instead? Could they just attend and report back? Pick one and hand it over.
- The "What do you think?" challenge. For the next 48 hours, every time someone asks you for a decision, don't give it. Ask, "What do you think we should do?" and then—this is the hard part—actually listen.
- Define the "No-Go" zones. Be clear about what they can't do (e.g., spend over $5k, fire a vendor). If it’s not in the no-go zone, they have the green light.
- Stop CC'ing yourself. If you trust them to handle a project, stop monitoring every email thread. It signals distrust.
- Celebrate the process, not just the win. If someone took a big swing and missed, but their logic was sound, acknowledge the effort. You want to encourage the behavior of taking initiative.
Empowerment is basically just professional maturity. It’s realizing that you aren't the only person in the room with a good brain. Once you get that, the "how" becomes a lot easier. You just have to be brave enough to be unnecessary for a little while.
Focus on building systems where people can succeed without you. That is the only way to scale. If the business breaks the moment you go on vacation, you haven't built a team—you've built a dependency. Start breaking those dependencies today. Give away your "secrets." Give away your authority. Watch what happens when people actually feel like they're in charge of their own desks.