"My team needs too much hand-holding."
"I can't find anyone who takes initiative."
I hear these from owners every week. And most of the time, I have to say something they don't love hearing: your team isn't the problem. Your team can't take initiative on information they don't have.
Why Your Team Keeps Waiting on You
Here's what I see constantly. The owner has a capable team. Good people who show up, know their work, and want to deliver. And the owner is still the first call when anything needs to move. Still the person whose phone has to ring before the next step can happen.
That's not a people problem. It's an information problem. Everything still flows through the owner.
A Real Example: Calvin and the Sold Job
I'll call this client Calvin. He runs a service company in Pennsylvania, and he built it the way most of you did: on expertise, on hustle, one job at a time.
When we started working together, he had a solid team. His project manager, Brian, knew the operation inside out. The crew was experienced. From the outside, it looked like the team could run everything.
Here's what was actually happening. When a customer signed and said yes, Brian didn't know about it until Calvin told him. The crew didn't know what was coming until Calvin put it on the board. Scheduling, ordering, and paperwork all waited on Calvin to give the word.
When I asked Calvin why the sold-job update still ran through him, he said: "Huh. Old habits."
I pushed back. Old habits for who? What does that habit cost your team?
He was quiet for a second, then said: "Well, it's not helping them, that's for sure."
Meanwhile, Calvin was on the road generating sales, which is exactly what he should have been doing. He was also the reason his own operation was running behind. Brian, who was more than capable, was standing around waiting. Not because he didn't know how, but because the trigger that started his work lived in Calvin's head.
How to Empower Employees: Move Information Around You
Here's my verdict, and I want you to hear it clearly: a team can't be ready for a business that isn't built to let them work.
I've spent 30 years watching this exact pattern. The owner hires, trains, trusts, and then stays in the middle as the information source. Not on purpose. Just because nobody ever built a system to move the information around them. Think of yourself as the hub of a wheel. As long as you're the hub, nothing moves without you.
Empowering employees isn't a pep talk or a trust exercise. It's plumbing. Here's how we fixed Calvin's.
1. Map the handoffs, not the tasks
Ask: where does information have to go, and who does it flow through to get there? Not tasks. Handoffs. The moments where work can't continue because information hasn't moved yet. For Calvin, the biggest one was the sold job.
2. Let the system make the handoff
When a customer accepted a proposal, it was already recorded in the accounting software. So we built the chain from there: the office admin sees it and creates the job in their job management system, Brian gets notified automatically, and that notification comes with a checklist of everything that needs to happen before the job starts.
Not from Calvin. From the system.
When I walked Calvin back through the new process, I pointed out that he wasn't in it at all. He said one word: "Correct." I could hear the relief.
3. Flip the weekly meeting
The Monday meeting no longer starts with Calvin downloading information to Brian. It starts with Brian reporting to Calvin: how many jobs sold last week, where each one stands, what's been ordered, what kickoff meetings are done. (It's the same flip that helps you stop micromanaging.)
4. Repeat for every handoff
Estimate follow-ups moved to the admin. Pre-start checklists moved to Brian. The question was never "does this person know how to do it?" They knew. The question was "have we built the trigger that tells them when to start?"
The Results
When Calvin and I started, his business was at $1.8 million. The last time we spoke, he was targeting $4.2 million, and he was running it from the road, closing sales, while his team ran the work.
Brian checks in once in the morning and once at night. Not emergencies. Just closing the loop. And his crew told him something I want every owner to hear someday:
"We don't have to chase you anymore. We know what's coming up. We know what's on the board."
That's what a business that doesn't depend on you for everything sounds like.
Your Challenge: Fix One Handoff
Not all of them. One. Find a place where your team can't take the next step until you confirm something, pass something along, or tell someone the job is a go. Then ask three questions:
- Who needs this information?
- What triggers the handoff?
- What would it take to remove me from it?
Build that one handoff. Test it. Calvin didn't fix everything at once. He fixed the sold-job notification, and it compounded from there.
Want to see where your business depends on you most? Take the free Operational Risk Scorecard. You can also hear Calvin's full story on the podcast: Your Team Isn't the Problem. And if you'd like help mapping your handoffs, book a strategy call.
