← Back to the blog

The difference between labor and authority

Last week my card was flagged for fraud, not for the first time this year, and not for the last. I called in. The person who answered was based in the Philippines, professional and clearly capable, and completely unable to help me. She could not unlock the card, could not clear the flag, and could not do anything except tell me that someone in the US would need to handle it, and that person was not available yet. I run a business across three time zones. It did not matter. I waited.

The rep I spoke to was doing exactly what she was trained and authorized to do. That is the part worth sitting with. The problem was never her. The problem was that the authority to actually solve my problem had never been given to the person answering my call. It lived somewhere else, on a schedule that had nothing to do with mine.

This is not really a story about a bank. It is a story about a pattern that has now repeated itself twice in a generation, and is quietly repeating itself inside a lot of growing businesses too.

Outsourcing moved the labor, not the authority

The first wave was outsourcing. The logic was straightforward: find the same task performed somewhere cheaper, move it there, and keep the rest of the operation as it was. What rarely got examined was where the authority to resolve anything actually sat. A call center rep, wherever they are based, can typically follow a script and process a request. What they usually cannot do is deviate from it, override a system, or make a judgment call that falls outside a defined set of options. That authority stayed exactly where it always was. The work moved. The power to actually fix something did not.

For the customer, or the client, or the internal team member on the receiving end, this produces a very specific kind of frustration. Someone is available, polite, and present. Nothing gets resolved, because the person present was never equipped to resolve it.

Then AI moved the front line even further

The second wave is happening now. AI tools have moved the front line even further from the point of authority than outsourcing ever did. A chatbot has less discretion than a call center employee, not more. It can answer questions that fit its training and escalate everything else, which sounds efficient until the thing you need falls outside the pattern it recognizes. The promise, in both waves, was the same: lower cost, comparable service. The result, in both waves, has also been the same, because the constraint was never about who was doing the labor. It was about who had been given the power to actually decide something.

The same pattern shows up inside growing businesses

This is not only a story about banks and call centers. It is the exact structure behind why so many founders and executives stay stuck being the bottleneck in their own business, long after they have hired good people to help them.

A founder hires an executive assistant. The calendar improves. They hire a project manager. Delivery gets more organized. They hire an operations person. One function stops requiring daily attention. And the founder is still fielding decisions that should not require them, still the last call when something breaks, still the person everyone waits on when a judgment call needs to be made.

The pattern is identical to the call center problem. Each hire added labor to a specific task. None of them were given the authority, or the accumulated context, to actually decide things on the founder's behalf. The work moved. The decision-making stayed exactly where it was.

What actually closes the gap

Closing this gap is not about finding a more capable individual hire, and it is not about adding another layer of task coverage. It requires someone, or some function, that holds enough context across the business to make the calls a founder would make, without needing to ask first every time. That kind of trust is not something you can hand someone in a job description. It gets built deliberately, over time, by someone who is close enough to the actual decisions for long enough to be trusted with them.

That is the real difference between task support and an operating layer. Task support adds hands. An operating layer adds judgment, positioned where the context already lives, so the work below your level actually stops routing back to you.

If your business still runs on you being the last line of defense for every decision that does not fit a script, the fix is not another hire closing one more gap. It is a properly staffed operating layer, built around someone who earns the authority to act on your behalf.

Helm starts with a strategy session: ninety minutes to map where the authority in your business actually sits, and what it would take to close the gap.

athelm.io/strategy