What running IT services taught me about scaling trust before scaling teams

For years, I was the one doing the work. Every client call, every server migration, every 2 a.m. incident, I was in the middle of it. That's how you build a services business in the early days, and it's also the habit that will quietly cap how big that business can get.

The trap of being indispensable

Being indispensable feels like a strength right up until it becomes the ceiling. Every process that lives only in your head is a process that can't scale past you. The first real unlock wasn't hiring more people, it was writing down how I made decisions well enough that someone else could make them too.

Trust is built in public

Delegation fails quietly when it's treated as a private handoff. It works when the reasoning behind a decision is visible; what tradeoffs were considered, what "good" looks like, where the guardrails are. Teams don't need less oversight, they need better context.

What I'd do differently

If I were starting over, I'd invest in documenting decisions earlier, not just outcomes. The outcome tells someone what happened. The reasoning teaches them how to think about the next one.