The Day I Realized
I Was the Bottleneck

I was sitting in my truck at seven in the morning, eating a sandwich I'd brought from home, answering my third call of the day from a project manager who wanted to know whether he should order OSB or go back to the supplier for plywood. Same supplier we'd used for five years. Same project manager I'd been employing for two. He was calling me because that's how I'd trained him to operate. I hadn't noticed yet that I was the one who'd done the training.

That call is when I should have understood what was happening. It took me a few more months.

Why I Thought I Was Running a Tight Operation

For a long stretch, I genuinely believed that being across every detail was a sign of professionalism. I knew every open deficiency on every project we had running. I knew where each crew was that day, which inspections were coming up that week, what was on backorder and what had shipped. If anyone needed to know anything about a job, they called me, and I had the answer. I thought that meant the company was under control.

What it actually meant was that the company was under me. Which is different. Every decision waited at my desk. Every issue that came up in the field funnelled up through whoever was on site to whoever was managing that project to me, at which point I'd make the call and send it back down. The chain worked. It just worked slowly, and it worked through a single point of failure, and that point of failure was me.

The PM who eventually told me what was going on had been with me for two years. He was capable, experienced, and had better instincts on residential work than I did in a few specific areas I'd quietly learned to rely on him for. None of that mattered structurally, because structurally he was making recommendations and I was making decisions. He was flagging problems and I was resolving them. He was present on every project and empowered over nothing meaningful. The gap between his job title and his actual authority was wide enough to park a truck in, and he'd been living in that gap long enough to be done with it.

When he told me he was thinking of leaving, he was polite about it. He said he didn't feel like he was actually managing anything. He was right. I'd hired a project manager and then continued managing the projects myself, just with an additional layer of communication overhead in the middle.

The Honest Cost of Having Everything Run Through You

When your business can't function without you at the centre of every decision, it has a ceiling. The ceiling is you: your hours, your attention, your capacity to hold information and respond to calls at seven in the morning while you're eating a sandwich in a truck. The business cannot grow past your personal bandwidth. And your personal bandwidth, it turns out, is not infinite.

There's a second cost that's harder to see in the moment. When every decision runs through the owner, the people on your team who are capable of making good decisions stop trying to develop that capability. Why would they? There's no incentive to build judgment you're never allowed to exercise. The good ones either adapt (meaning they stop growing) or they leave. The ones who stay and adapt are the ones who've accepted the terms, which means you've been quietly selecting for the employees who are most comfortable with dependency.

I lost the PM eventually. He left. I don't blame him. What I regret is that I'd spent two years with a capable person on payroll, essentially wasting his professional development because I couldn't stop managing the things I'd hired him to manage. The knowledge that lives only in your head is a liability, not an asset. The habit of centralizing decisions has the same effect. It keeps knowledge locked at the top of the organization instead of distributing it to the people who need it.

What Delegation Actually Requires

The thing I had wrong about delegation was that I thought it was primarily about trust. I trusted my PM. I thought I was delegating because I wasn't standing over his shoulder on site every day. But trust and delegation aren't the same thing. I can trust someone completely and still not be delegating if I'm the one making every final call.

What delegation actually looks like when it works is simpler and harder than most owners expect. You define the outcome. You set the parameters they have to work within: budget, timeline, quality standard, non-negotiables. You establish when you want to hear from them, and what constitutes something that needs to come to you versus something they handle. And then you leave them alone until those check-in points, and you let them do the job.

The hard part is the middle of that. Leaving them alone. Tolerating a decision you might have made differently (not a wrong decision, just a different one) without jumping in to correct it or redirect it. Watching someone solve a problem a different way than you would have and accepting that the result was fine, possibly even better. That took me longer than I'd like to admit, because my instinct when I saw anything I'd have done differently was to say something. Every time I did, I was training my team that my involvement was normal and expected, and that they should wait for it.

The Signals I Missed Along the Way

Looking back, the signals were there for years before the conversation that finally made it land. My phone was constant. Every experienced person I hired seemed to plateau within a few months at a ceiling that, in retrospect, was exactly where my management style stopped them. The projects that ran best were the ones where I got busy enough with something else that I accidentally left people alone to work. And the people who stayed the longest, the ones who seemed happiest, were generally the ones who'd found small pockets of the business where I wasn't paying close attention.

That last one is worth sitting with. The happiest, most effective people on my team were thriving in the spaces where I wasn't present — the early shape of a crew culture that holds its standards when you're not watching. That's not a compliment to my leadership. That's a data point.

The sales gap that opens up when you're stretched too thin is one version of this problem. When the owner is buried in operations, the pipeline dries up because nobody else is managing it. But the operational version is just as costly and a lot less visible. You don't always see the decisions that didn't get made because someone was waiting to run it past you. You don't see the speed you bled waiting for approvals. You see the result, eventually, usually in a margin that's softer than it should be or a team that's moving slower than the workload demands.

Building a Business That Runs Without You in Every Conversation

The shift, when I finally made it, wasn't elegant. I didn't read a book and implement a framework. I told the PM I had at the time (a different one by then) that I was going to try something and I needed his help. I was going to stop answering questions he could answer himself. I was going to let him make certain calls without running them by me first. I told him what those calls were and what the criteria were. And I told him that if something went sideways, I wanted him to come to me after he'd already tried to address it, not before.

It was uncomfortable for both of us. He'd been trained to check in, and breaking that habit took longer than I expected. I had to sit on my hands a few times when I wanted to call and ask what was happening. But within a couple of months, the dynamic had genuinely shifted. He was making better decisions faster than I would have through the old chain of communication. He was solving problems in real time on site instead of waiting for my input, which sometimes came hours later. And he stayed. Several more years. Because for the first time, he was doing the job he'd been hired to do.

The Bottom Line

If your business runs because every decision eventually gets to you, it's not running. It's depending. You are the load-bearing wall in a structure that needs to be reframed. That's not a permanent condition. It's a design problem. But you have to stop treating your involvement as a quality control mechanism and start treating it as a constraint, because that's what it is.

The question worth asking is not whether you trust your people. You probably do. The question is whether you've actually built a structure where their authority matches their responsibility. If your best people keep leaving or keep plateauing, the answer is probably no. I say that as someone who took years longer than necessary to figure it out. If you want help building the structure that lets your business move without you at the centre of every call, that's exactly the kind of work my construction business coaching is built around with trades and construction owners.