The difference between a team and people who happen to work for you
You call them a team because they're on the payroll. A team is wired to each other, and yours is wired to you.
You've got good people. Some of them are great. They show up early, they care about the customer, and each of them would tell a stranger they're on your team. You'd say you're building a real team, and you'd mean it. Then you're out sick for two days, and the work stops in six places at once, each pile waiting on the same thing. You.
A team is wired, not hired
Picture a pile of engine parts on a shop floor. Pistons, rods, a crankshaft, every one of them machined clean. Nobody calls that an engine. It becomes an engine when the parts are bolted to each other, so the force from one turns the next without anybody standing there passing it along by hand.
A team is no different. It isn't a headcount and it isn't a mood. It's people connected to each other, so work moves from one seat to the next and comes out the far end finished. People who happen to work for you each connect to exactly one thing, and that thing is you.
Draw it on a napkin and you get a wheel. Every spoke runs to the hub. No spoke touches another. Good spokes, strong spokes, and every bit of load they carry, they carry to the middle.
The quality of the parts was never the question. What holds them together is.
Every handoff runs through your desk
The problem doesn't live inside anyone's job. Your people are mostly fine at their jobs. It lives in the space between two jobs.
Your salesperson closes a deal and it needs to reach the person who does the work. Does it go straight there? Or does it come to you first, so you can look it over, add the thing only you know about this customer, and pass it along? Your office manager hears about a problem in the field. Does she call the lead? Or does she call you, so you can call the lead?
Each person is competent at their own piece. What's missing is the line between the pieces, and since nobody ever built it, you became it. You're not the head of the team. You're the hallway between rooms that don't have doors to each other.
You probably think your people need you for answers. Mostly, they need you for passage.
The work isn't stuck in their jobs. It's stuck in the gaps, and the gaps are shaped like you.
What being the hallway costs
Run a simple example. Say you've got six people, and each one hands off four pieces of work a day to someone else. That's 24 handoffs. If every one of them stops at your desk for five minutes, a question, a glance, a forward, that's 120 minutes. Two hours a day of you working as plumbing.
Ten hours a week. Over a 50-week year, 500 hours, which is more than twelve full 40-hour weeks spent standing between two people who sit twenty feet apart. And that's the conservative version, because it only counts your minutes. It doesn't count the waiting.
The waiting is the bigger bill. A handoff that runs through you sits until you're free. You're on a call, it waits. You're at a site, it waits. The customer on the other end of it waits too, and they don't know or care that the hold-up is a hallway, and the hallway is you.
Now hire a seventh person to take some load off you. Same example, four more handoffs a day, every one of them routed through the middle. You hired help and bought yourself more traffic.
Headcount on a wheel doesn't add capacity. It adds traffic to the hub.
Why team-building makes it worse
So you work on the team. A dinner. An offsite. A values poster in the break room. Maybe a weekly all-hands so everybody's on the same page. That stuff isn't bad. People do better work next to people they like, and some of those dinners matter.
But it treats a wiring problem like a mood problem. Everyone likes each other a little more and still hands everything to you, because liking the person at the next desk doesn't give you a line to them.
Look hard at the all-hands. Everyone sits in one room and reports to you, one at a time, while the rest wait their turn. That's the wheel with chairs.
And the culture work hides the gap. Morale's up, people are smiling, so you figure the team part is handled. Then you go back to wondering why you're still the bottleneck on everything, and the answer is sitting in the room you just spent a Saturday decorating.
You can't fix the wiring with a pizza party. The parts get happier and stay unbolted.
Trace the last finished job backward
Take the last piece of work that came out finished. A job, an order, a customer problem that got solved. Trace it backward from the end. Count how many times it passed from one of your people to another. Then count how many of those passes went through you.
If the second number sits close to the first, you've got people who work for you. If it's near zero, and you found out the thing was done after it was done, you've got a team.
There's a harsher version. Ask whether two of your people have ever settled a problem between their two jobs without telling you until it was settled. Not whether they could. Whether they have. If you can't name a time, the line between them doesn't exist yet, no matter how well they get along.
A team finishes things you hear about later. A wheel can't finish anything without a lap around the hub.
Building a real team is a wiring job
The fix isn't better people. It isn't more meetings or another trust exercise. It's structural. The work gets a path from one seat to the next that doesn't need you standing in it, and the people on either end of that path know what finished looks like when it leaves their hands.
When it's in, nothing dramatic happens. That's how you know it worked. Work moves while you're on a call. A problem gets settled between two people and shows up in your week as a line in a report instead of a knock on your door. You come back from two days out and the stack on your desk is the stuff that genuinely needed you, which turns out to be a much shorter stack.
You don't build a team by gathering people. You build it by connecting them to each other.
Being needed isn't the same as leading
Being the hub feels good. Everything comes to you, so you know everything. People need you, and being needed feels a lot like leading. When someone says the place couldn't run without you, it lands like praise.
It isn't praise. It's a description of a wheel. And it's the exact sentence a buyer hears as a warning the day you put the business up for sale, because one that stops when its founder stops is worth a lot less than one that keeps going.
You hired good people. Stop asking them to be a better team while they're built to be better spokes. Connect them to each other, step out of the middle, and find out what they could do the whole time.
The people were never the missing part. The bolts were.
I wrote a whole book about this. It's called Built to Break. It's why founder-led businesses fall apart the second the founder steps back, and what's really going on underneath.
It's on Amazon. Go read it.