Practical resource

Automation prioritization worksheet

Score candidate workflows on evidenced value, implementation effort, operational risk, data readiness, and adoption readiness. Treat the score as a conversation aid: a high total does not overrule an unacceptable safety, compliance, continuity, or ownership risk.

Illustrative electronics operator inspecting a circuit board on an assembly line
01

Understand

Score each dimension from 1 to 5

Dimension135
ValueRare, little active effort or delayRecurring, measurable burdenFrequent, material, decision-relevant burden
EffortMany systems and unknown rulesModerate integration and variationBounded workflow, supported interfaces
Operational riskFailure could stop or compromise critical workManaged fallback is possibleLow-risk information workflow
Data readinessIdentifiers and records unreliableUsable with cleanupOwned, available, representative data
Adoption readinessNo owner or time for changeSponsor and users identifiedOwner, users, training, and feedback committed
02

Understand

Calculate a discussion score

Use Value + Data readiness + Adoption readiness + (6 − Effort) + (6 − Operational risk). The maximum is 25. Keep every component visible; do not use the total to hide a risk score of 1. Record the evidence and confidence beside each score.

03

Apply

Candidate record

01

Workflow and business decision affected

02

Volume, active time, elapsed time, error or exception baseline

03

People and systems involved

04

Source data and identifier condition

05

Failure, fallback, security, and continuity concerns

06

Owner, users, and proposed pilot boundary

07

Unknowns the pilot must test

04

Review

Selection rule

Prefer a candidate that matters, has an owner, can be bounded, and tests important assumptions with acceptable risk. Defer candidates whose rules, data, or operating responsibilities are not ready; add a readiness action instead.

01

Start with one process

Which workflow currently costs your team the most time?

Bring one normal example and one exception. Use them to frame the systems, decisions, controls, and evidence a sensible next step needs.

Discuss your operation