Which workflow should you automate first?

The first-workflow trap

Teams choosing a first automation make one of two mistakes. The first is the trophy use case — flashy, demo-friendly, usually sponsored by whoever saw the vendor keynote, and ownerless the moment the demo ends. The second is nobler but worse: starting with the most painful process in the company. Processes are usually painful because they're tangled — messy data, undocumented exceptions, three departments with veto power. That's the hardest possible terrain for a first attempt.

Your first automation has a different job than either. It exists to prove the muscle: that your organization can pick a workflow, change it, measure the change, and decide. Sixty-two percent of organizations are already experimenting with AI agents, per McKinsey — experimentation is table stakes. The compounding advantage goes to whoever turns the first experiment into a repeatable playbook.

The rubric: five questions, scored 1–5

Score every candidate workflow on these, honestly:

• Frequency — does it happen daily or weekly? Volume means more reps, faster learning, and more hours at stake than anything quarterly.
• Pain — measured in hours and error rates, not in volume of complaints.
• Data readiness — are the inputs digital, accessible, and consistent? If the current process involves screenshotting PDFs, score it a 1 and move on.
• Blast radius — if the automation is wrong, is the result an internal correction or an external incident? First picks should fail safely, with a human review step.
• Ownership — is there a named person whose week gets better? Automation without an owner dies at the first handoff.

Eighteen or more out of 25 is a strong first candidate. Below that, it's not a no — it's a second-wave pick, after the playbook exists.

Five strong first candidates

Workflows that reliably score well across industries:

• Meeting notes → CRM hygiene: high frequency, low blast radius, and every seller's least favorite chore.
• Support ticket triage with drafted replies: bounded, measurable, human-reviewed — the pattern behind Klarna's AI assistant, which by the company's own reporting handled the workload of hundreds of agents.
• Weekly report assembly: the same numbers, gathered from the same systems, formatted the same way — automation's natural habitat.
• Invoice and PO exception matching: back-office, rule-heavy, and exactly where MIT found the most measurable GenAI returns.
• Sales-call summaries → coaching notes: compounding value for managers, zero customer-facing risk.

Notice what's not on the list: anything customer-facing without review, anything legal-adjacent, and anything whose data lives in seventeen spreadsheets. Internal copilots came first at JPMorgan and Morgan Stanley for the same reason.

Run it like a sprint, not a program

Thirty days is enough for a verdict. Week one: write the baseline and the guardrails. Weeks two and three: build in the open, with the people who do the work daily. Week four: measure against the baseline and make the call — scale it or kill it. Both outcomes are wins; a documented kill beats a zombie pilot that haunts three budget cycles.

The setup that makes the sprint work is organizational, not technical: a named squad, two to three protected hours a week from the people who own the workflow, and leadership sign-off on the decision date. (If that sounds familiar, it's the same readiness checklist as our Workflow Automation Sprint — that's not a coincidence.)