The Hidden Tax of Manual Work

Manual work isn't the enemy.

Some of the most important work is manual by nature: listening, noticing, deciding, shaping a message, handling an exception, making a call that requires taste and judgment. That work is the craft.

The problem is different. It's the manual work you keep doing because the system was never designed to stop asking you to do it.

Google has a clean word for that category: toil. Work that tends to be manual, repetitive, automatable, tactical, and devoid of enduring value. And it scales linearly as volume grows.

That's the hidden tax. Not because manual work is bad, but because toil steals the attention your team needs for the work only humans should do.

Why This Tax Keeps Growing Quietly

Toil doesn't announce itself. It shows up as "just get it done."

Copy and paste between systems. Reformat a spreadsheet. Re-enter the same data twice. Move files into the right folder. Chase down missing fields. Build a weekly report by hand because nobody trusts the automation. Fix the same exception again because it's faster than redesigning the intake.

Each step feels small. The combined effect is huge.

ServiceNow found managers spend more than 15 hours per week on routine administrative tasks outside their core job function. 20% spend three days or more. That's not a productivity problem. That's an operating model problem.

And the more your volume grows, the more that tax scales, because toil scales with volume.

The Distinction That Keeps You Sane

If you take one thing from this issue, let it be this:

You don't want to automate everything. You want to automate the work that is stable, repeatable, and predictable, so your people can spend their time on judgment, creativity, relationships, and the decisions that actually move outcomes.

This is why "automate everything" always backfires. You end up automating chaos, then paying for it in maintenance and exceptions.

Even AWS frames this as a discipline: identify repetitive toil, set a high standard for automation with limited allowance for manual work, and continually reduce that allowance over time.

That's the intent. Not removing humans. Removing the needless repetition that keeps humans from doing the work that matters.

A Practical "Toil Filter" You Can Apply in Real Time

When you spot a manual step, don't debate it. Run it through a quick filter:

Automate it when it is:

• Frequent: you do it multiple times a week
• Repeatable: the steps don't change much
• Rule-based: you can describe the logic clearly
• Error-prone: small mistakes create rework or risk
• No enduring value: nothing improves because a human did it

Keep it manual when it is:

• Trust-sensitive: it affects reputation, relationship, or customer confidence
• High variability: edge cases are the norm, not the exception
• Compliance-heavy: wrong outputs create real risk
• Still being learned: you need to understand it before you systematize it

This keeps you from automating what shouldn't be automated, and it keeps you from tolerating toil just because it's familiar.

Where Teams Usually Miss the Leverage

Most teams think the leverage is "AI."

Sometimes it is. More often, the leverage is earlier.

Toil exists because inputs are inconsistent, ownership is unclear, and handoffs are sloppy. AI can help, but it can't rescue a workflow that's ambiguous by design.

If you want the fastest wins that actually hold up, prioritize in this order:

1. Standardize the input

Replace free-text chaos with structure where it matters: dropdowns, required fields, naming conventions, templates.

2. Automate the handoff

When something comes in, it should land in the right place with an owner and a next action. This is where you reclaim time immediately.

3. Add a visible exception path

If it fails, it should fail loudly, route to a queue, and have a clear owner. Silent failure is where automation becomes theater.

4. Use AI to reduce resets

Summarize, classify, extract, draft, and route. Not to create more output, but to reduce the number of times a human has to restart their brain.

The Real Payoff Is Reclaiming Attention

This is what most leaders miss.

Toil doesn't just consume hours. It consumes cognitive bandwidth. It erodes the team's ability to think strategically because the day is spent stitching.

Google's SRE framing is helpful here, even if you're not in software: excessive toil slows progress, creates confusion about what the team is actually for, and sets a precedent that the team exists to do manual work.

That's exactly what happens inside modern marketing and operations teams when manual repetition becomes normal. People stop building. They start maintaining.

The unlock isn't "do less work." It's "move the work up the value chain."

The Signal Shift

Here's a one-week challenge, meant to be small on purpose. This isn't a transformation program. It's a weekly habit that compounds.

The Signal Shift (7 days): Reclaim one pocket of human attention.

1. Spot one piece of toil you did at least three times this week (copy-paste, reformatting, chasing missing fields, manual routing).
2. Name the trigger (what starts the work) and the outcome (what "done" looks like).
3. Fix the input with one constraint (template, dropdown, required field, naming rule).
4. Automate the handoff (create the record, assign the owner, create the next task, post the summary to the right channel).
5. Add an exception lane (if it fails, it routes to a queue and alerts an owner).
6. Write the rule down in one place so the system survives you.

That's it. One shift per week. In a month, you've removed four recurring drains. In a quarter, the team feels like it has room again.

Manual work isn't inherently bad. But repeating what a system could do for you is one of the fastest ways to burn down your attention without realizing it.