Written by: David Carneal –  Digital Efficiency Consulting Group (DECG)

Read Time: 3 min

"Automation is coming for our jobs" sounds strategic. In practice, the pain is usually tactical: retyping, chasing approvals, rebuilding the same report every week, and answering status questions that exist because nobody can see the work.

A calmer, more accurate way to talk about this is to separate tasks from roles. Tasks change all the time. Roles change slower. That difference is where you find sensible automation targets and a message your team can actually live with.

The Useful Boundary: Automate Tasks, Protect Judgment

Most office roles are a bundle of tasks. Some are predictable and rules-based. Others require context, negotiation, and human judgment. Automation shines on the predictable parts so people can spend more time on the messy, valuable parts.

  • Good candidates: copying data, routing requests, validating fields, scheduling routine follow-ups, producing standard summaries.
  • Keep human: customer exceptions, vendor negotiation, policy decisions, quality judgment, anything where "it depends" is the honest answer.

Why This Framing Helps Managers

When people fear job loss, they interpret every change as a threat. When you talk in task language, you lower the temperature and get everyone focused on a shared enemy: wasted human attention.

It also forces better decisions. If you can't describe the task clearly, you can't automate it safely. That's not a technology limitation. That's a clarity problem.

A Simple Message That Reduces Fear

You don't need a keynote speech. You need one clear statement that removes ambiguity.

  • What's changing: we're removing busywork and building clearer workflows.
  • What's not changing: we're not eliminating roles to make room for a tool.
  • How feedback works: we'll run a pilot, review exceptions daily at first, and adjust openly.

Mini Case: The Role Stayed. The Tasks Changed.

Consider a coordinator who spends mornings re-entering request details into three systems, afternoons chasing approvals, and evenings updating a status spreadsheet because leadership wants "visibility." That role looks busy on paper and exhausted in real life.

Automate the predictable tasks and the role becomes what it should have been all along: a coordinator. They can focus on exceptions, communication, and keeping the process healthy. The job didn't vanish. The sludge did.

Score-Yourself Rubric: Are You Automating the Right Thing?

Take one task and score each line 1-3. Total 12-15 means "pilot it." Total under 12 means "fix the inputs first."

  1. Frequency: happens often enough to matter (1 rarely, 2 weekly, 3 daily/constant).
  2. Clarity: the decision rule can be explained plainly (1 fuzzy, 2 mostly, 3 crystal).
  3. Inputs: the data is usually complete and consistent (1 messy, 2 workable, 3 clean).
  4. Exceptions: weird cases are easy to spot and route (1 unknown, 2 some, 3 obvious).
  5. Risk: if it fails, the impact is contained (1 high impact, 2 medium, 3 low).

This rubric keeps you from "automating" something that is actually a policy problem wearing a process costume. If the rules aren't clear, the answer isn't "more automation." The answer is "decide what you mean."

CTA: Pick one task and run the rubric today. If it scores high, pilot it with guardrails. If it scores low, your next improvement is ownership and inputs, not a new platform.