How to Decide What Business Work Should Be Automated
Automation should remove repeated friction from a stable process rather than hide a broken process behind software.
Working record
| Check | What to do | Evidence to retain |
|---|---|---|
| Map the current workflow | Describe the trigger, inputs, sequence, handoffs and exceptions. Check the current process before specifying a replacement. | One real source record, process steps and an exception case. |
| Identify repeatable steps | Separate stable rules from tasks that require judgement or approval. Start automation with the steps whose inputs and outputs are known. | The identify repeatable steps record, its source and the person responsible for resolving missing evidence. |
| Define exceptions | List missing inputs, duplicates, failed connections and approval cases. Name the person responsible for resolving each exception. | The define exceptions record, its source and the person responsible for resolving missing evidence. |
| Measure after automation | Review successful runs, unresolved failures and manual recovery effort. Compare the result with the original workload. | The measure after automation record, its source and the person responsible for resolving missing evidence. |
Review the decision
Automation should remove repeated friction from a stable process rather than hide a broken process behind software. Keep map the current workflow, identify repeatable steps, define exceptions attached to the conclusion so the next owner can challenge the assumptions. Resolve missing evidence before treating this record as approval.
Continue the decision
When a Spreadsheet Should Become a System · How to Build a Lead Qualification Process.
Calculation and source notes
Keep the displayed formula, input units and model scope with the result. Corrections or questions can be sent through the request section on this page.
Content updated: October 11, 2026