The work your people shouldn't be doing

Somewhere in your business right now, one of your most capable people is doing work that no person should be doing — and everyone has quietly agreed not to notice.

It rarely looks like a problem. It looks like the job.

Someone exports a report from one system and types it into another. Someone copies figures from an email into a spreadsheet, then from that spreadsheet into a third tool that was supposed to make the spreadsheet unnecessary. Someone spends the first hour of every Monday chasing statuses that already exist, just not anywhere they can be seen at once. Someone reformats the same document, the same way, every single week.

None of it is broken. All of it works. That is exactly why nobody questions it.

We tend to measure this kind of work by the time it takes, which is the wrong measure and makes it easy to wave away. An hour here, twenty minutes there — it never looks expensive enough to fix. But the cost was never the hours. It was where those hours would have gone.

The cost was never the hours. It was where those hours would have gone.

Every repetitive task handed to a person is a quiet decision about what that person won't be doing instead. The afternoon spent reconciling two systems is an afternoon not spent with a customer, or on the work only they can do, or thinking about anything at all. The friction doesn't just cost time. It costs attention — and attention is the most expensive thing your business owns.

Most companies file this under IT, or under operations, or under "something we'll streamline once things calm down." Things never calm down, and so the work stays. But it was never really a technology problem. It's a question of how your business runs — and how your business runs is part of what your business is.

How your business runs is part of what your business is.

A customer feels the difference between a company whose machinery runs smoothly and one whose people are quietly drowning in admin, even if they could never name it. The delayed reply. The detail that slipped. The thing they had to ask for twice. None of that reads as a process failure to the person on the other end. It reads as you. Your operations are a brand surface, whether or not you've ever treated them as one.

There's a reason this work has survived so long, and it's a fair one. Building software that fit your business exactly used to be a serious undertaking — a development team, a long timeline, a budget that only made sense at real scale. So everyone reached for the same answer: buy the off-the-shelf tool the rest of the category buys, and bend the business to fit its assumptions.

That trade has a cost almost nobody counts. When you run on the same software as every competitor, you inherit the same constraints, the same workflows, the same idea of how a business like yours is supposed to operate. You start to look like everyone else from the inside out — which is the quiet beginning of looking like everyone else from the outside in.

That's the part that has changed. The cost and complexity of building something bespoke have collapsed. A tool shaped around how your business actually works — not how a software company assumed it should — is now within reach of a five-person studio, a single clinic, a local restaurant. The thing that was once a luxury of scale is becoming a question of intent.

Which turns the useful question around. It isn't "what could we automate?" — that list is endless, and it leads to automating things that shouldn't exist at all. The better question is sharper: what is a person doing right now that a person should never have been doing in the first place?

Start there, and you'll find it isn't the dramatic work that's the problem. It's the small, repeated, invisible tasks — the ones done by hand so long they've stopped looking like a choice. The Monday report. The double entry. The status chase. The reformatting nobody remembers assigning to anyone.

That work isn't a sign your people aren't capable. It's a sign of what they could be doing instead.

The work your people shouldn't be doing is usually the work they've done so long that nobody thinks to question it.

The work your people shouldn't be doing is usually the work they've done so long that nobody thinks to question it.

Find it. Then hand it to a machine — and hand your people back to the work only they can do.