The Workflow Audit: Finding the Work That Should Not Exist

Every large organization carries a hidden tax: work that exists only because the systems around it cannot speak to each other. Reconciliations between two systems of record. Manual data entry that exists because an API was never built. Approval chains that exist because no one has revisited them in a decade.

Automation done well does not just speed this work up. It eliminates it. The first step is a workflow audit.

Start with three filters. Frequency — how often does this work happen? Friction — how many systems, people, and handoffs does it touch? Fragility — how often does it fail or require rework?

Work that scores high on all three is automation gold. Work that scores high on frequency but low on the others is often best left alone. Work that scores high on fragility is usually a sign of a deeper architectural problem that automation will only paper over.

The instinct is to automate everything that qualifies. The discipline is to ask, for each item, whether it should exist at all. The most valuable outcome of a workflow audit is often not new automation. It is the retirement of work that no longer needs to be done.

What remains, automate properly — with monitoring, fallback paths, and clear ownership. Automation without these is a future incident report.