Automate the Work, Not the People

Every organization has work that quietly consumes more time than it deserves: copying numbers between systems, chasing the same approval every week, rebuilding the same report by hand. Necessary work, perhaps—but not necessarily work that needs a person doing every step.

I see automation as a servant-leadership question, not just a technology question. Instead of starting with “What can we automate?” I’d rather ask: “What is keeping our people from their best work, and how can we get it out of their way?”

Start with the people, not the tool.

Before choosing software, ask your team: “What part of your week feels like a waste of your talent?” Then listen. The answer might be duplicate data entry, unclear approvals, or a process that requires five emails to accomplish one simple thing.

Sometimes the right solution is automation. Sometimes it’s removing an unnecessary step. Automating a broken process can just help it create problems faster.

Automate the repeatable. Protect the relational.

Routing requests, sending reminders, moving routine data and producing standard reports are useful places to look for automation—with checks for accuracy and a clear owner when something fails.

Coaching, difficult conversations, customer relationships and decisions that affect people deserve human attention. A system can help someone prepare for those moments. It shouldn’t become an excuse to avoid them.

Give the time back on purpose.

Saved hours can disappear into more busywork unless we decide where they should go. Better service? Professional development? Time to solve a recurring problem instead of patching it again?

Efficiency matters. But if every improvement only raises the workload, people may reasonably wonder who the improvement was for.

A servant leader should have a clear answer.

Be honest about what changes.

Automation can change responsibilities, expectations and roles. Pretending otherwise doesn’t build trust. Explain what’s changing, why it matters and what support people will receive. Invite the people doing the work to help design the new process—they know the exceptions a tidy workflow diagram can miss.

For this week, I’d offer three questions:

1. What task do we repeat that adds little value?
2. What better work could we do with that time?
3. What’s one small change we can test—and how will we know it helped?

Start there. Not with a sweeping rollout. Not with a promise that technology will fix everything. Just one practical improvement, built with the people it’s meant to serve.

The goal isn’t simply to move work faster. It’s to make room for work that matters—and lead in a way that shows people they matter, too.