Module 09 Activity
Scenario
Take this out of the classroom: a real workplace process, assessed honestly against the manual version.
What you produce
An automation case: a workflow chosen on volume and checkability, the real approval chain, an exception rate from historical records, and a stated boundary.
Steps
- Score three candidate workflows on volume, minutes each, and whether the output can be checked. Choose one and write down why you rejected the others.
- Map the approval chain as it actually exists: who approves what, at which amounts, how long it takes, and how many approvers each case needs.
- Write the triage rules and apply them by hand to a month of real historical records. Report the exception rate.
- Give every exception a named destination.
- Compare manual against automated including the review time the automation creates and both error rates.
- State what share you would automate, where you would stop, and what you would need to see to move that boundary.
Evidence to hand in
- Three candidates scored, with the rejections.
- The approval chain as it exists, with latencies and approver counts.
- The exception rate over real records, with destinations.
- The comparison including review time and both error rates.
- The stated boundary and the condition for moving it.
Review checklist
- The chosen workflow clears volume and checkability.
- Latency is in days where that is the truth, and multi-approver cases are recorded as such.
- Triage was applied to real historical records, not invented examples.
- The comparison states the error rate even if it went up.
- The boundary is written down with a reason and a condition.
