Operations · 4 min read
What the frontline taught me about automation
I didn't arrive at process automation through a framework. I arrived through five years of tickets — first as inDrive's first agent in Morocco, then as a senior agent, a supervisor, and now leading automation projects.
That order matters. By the time I was designing workflows, I had lived inside the ones that were broken.
Lessons that stuck
- The frontline already knows the answer. Agents can tell you exactly which steps are pointless. The job of an automation lead is mostly to listen, then make it real.
- A great SOP is a prototype. Every workflow I documented as a senior agent was a draft of something a machine could eventually carry. Writing it down for the next person was the first version of automating it.
- Standardization is kindness. When everyone answers the same case the same good way, customers get consistency and agents stop guessing. COPC gave me the discipline; the floor gave me the reasons.
- Data tells you where, people tell you why. KPIs point at the leak. Conversations explain it. You need both, in that order.
The pattern
Find the task people dread. Understand why it exists. Remove the parts a machine can carry. Give the freed-up time back to the customer relationship — the part no machine should touch.
Repeat. That's the loop I've run from agent to project manager, and it hasn't changed — only the scale has.