The Workflow Audit Manual

Ask a leadership team "what should we automate?" and you'll get the loudest ideas, not the best ones. The workflows worth automating rarely announce themselves — they're absorbed into people's routines so completely that nobody thinks of them as work. They're just Tuesday.

A workflow audit is the antidote: a structured, one-week sweep that surfaces what your company actually does by hand, prices it honestly, and ranks it. Done right, it replaces the quarterly "AI ideas" debate with a shortlist you can defend.

01Where manual work hides

• ▸The inbox rituals. Any email that gets forwarded to the same person with the same one-line note every time is a workflow wearing a costume. Watch for "FYI — can you handle?" patterns; each one is an intake process nobody designed.
• ▸The bridge spreadsheets. Every spreadsheet whose columns mirror two different systems is a human API — someone re-keying data between tools that don't talk. These are the highest-yield finds: bounded, repetitive, and universally resented.
• ▸The pre-meeting scrambles. Reports assembled by hand every Monday morning, status decks rebuilt from four sources, numbers copied from dashboards into slides. Recurring meetings are fed by recurring manual work.
• ▸The veteran's queue. Work that routes to one specific person "because they know how." That routing rule is undocumented process knowledge — and an outage waiting for their vacation.
• ▸The after-hours tell. Whatever people do at 6pm to catch up — the follow-ups, the data entry, the logging — is work the business needs but never staffed. It shows up in burnout before it shows up in budgets.

02The interview method

The audit's engine is a 25-minute interview per team, and the questions matter more than the sample size. Skip "what should we automate?" entirely — people answer with science fiction. Ask instead about last week:

• ▸"Walk me through yesterday." Chronological, specific, boring on purpose. The manual work appears as connective tissue between the things people consider their real job.
• ▸"What do you copy-paste?" The single highest-yield question in the audit. Copy-paste is the universal symptom of a missing integration.
• ▸"What do you dread on Mondays?" Dread marks recurring work with no owner and no tooling. It's also adoption fuel — the person who dreads a task will champion its automation.
• ▸"What would break if you were out for two weeks?" Surfaces the key-person dependencies — the workflows that exist only as habits inside one head.
• ▸"What questions do people keep asking you?" Recurring questions are retrieval workflows. If three teams keep asking ops for the same status, that's a dashboard or an assistant, not a Slack ping.

03Scoring what you find

Every candidate goes on one row with five scores, each 1–5: frequency (how often it runs), time (how long each run takes), pain (how much the team hates it), error cost (what a mistake costs downstream), and feasibility (are the inputs digital and reachable). Multiply frequency × time for the raw hours; let pain and error cost break ties; let feasibility veto.

The ranking that falls out is usually surprising. The workflow everyone complains about loudest often scores mid-table — visible pain isn't the same as expensive pain. And somewhere in the top three there's almost always a workflow nobody mentioned in the kickoff meeting, because its owner stopped thinking of it as work years ago.

04From audit to shortlist

The deliverable is not a heat map. It's a one-page shortlist: the top three workflows, each with its trigger, its systems, its hours ledger, its error modes, and its finish-line sentence ("done when a user can ___"). That page is simultaneously your automation roadmap and — run through a scoping session — your first three build requests.

Resist the urge to rank thirty items. Below the top handful, precision is fake: the scores are estimates, and the act of shipping the first automation will teach you more about the list than another week of analysis.