Assessment

Automation & Orchestration Candidate Assessment

An interactive, structured assessment that helps teams evaluate processes for automation, agentization, or orchestration. Capture scored criteria, qualitative context, and pilot-design notes. Stored responses enable traceable recommendations and follow-up experiment planning.

Interactive Tool

Automation & Orchestration Candidate Assessment

Use this assessment to evaluate a candidate process for automation, agentization, or orchestration. Score each criterion honestly — the combined picture helps you decide whether to pilot, reprioritize, or avoid automation. The form saves your responses so teams can track decisions and design pilots that preserve learning and safety.

Scoring guide: 1 = poor/low/long/hard; 5 = strong/high/short/easy. Higher composite scores generally indicate better suitability for automation, but note special cases (high downstream impact or regulatory sensitivity) that may require human-in-the-loop design regardless of score.

Short name that identifies the process or workflow being assessed.
Person or role responsible for outcomes and decisions.
Describe what the process does, who it serves, and the primary business outcome it supports.
1 = Highly variable; 5 = Highly repeatable. Higher is better for automation.
1.0 10.0
1 = Low complexity (simple, rule-based); 5 = High complexity (expert judgment). Lower is generally better for full automation. Consider hybrid or human-in-the-loop for high scores.
1.0 10.0
1 = Data missing or low quality; 5 = Complete, timely, high-quality data. Automation needs reliable signals.
1.0 10.0
1 = Very frequent exceptions; 5 = Rare exceptions. Frequent exceptions reduce automation suitability unless handled with clear escalation paths.
1.0 10.0
1 = Low impact; 5 = High impact (safety, compliance, major customer harm). High-impact items often need human checks or staged automation.
1.0 10.0
1 = Very difficult to monitor; 5 = Easy to monitor and alert. Good monitoring preserves learning and safety.
1.0 10.0
1 = Long horizon (2+ years); 5 = Short horizon (under 3 months). Shorter ROI horizons favor piloting.
1.0 10.0
Yes indicates special governance, human-in-the-loop, or additional validation will be needed even if technical suitability looks strong.
Note any scripts, RPA, rules engines, agents, or partial automations already in place and their outcomes.
Who needs to be involved for design, monitoring, and escalation? Include operations, compliance, product, and customer-facing owners.
Capture context that numeric scores may miss: rare but severe failure modes, data drift risks, vendor constraints, known biases, etc.
Use the scored criteria and qualitative context to choose an initial outcome. You can revise later after a pilot or additional analysis.
Example: error rate < X%, time saved Y minutes per case, no regression in compliance metrics, monitoring alerts triggered < Z per week.
Describe what you will monitor, alert thresholds, who gets notified, and the rollback/stop criteria. Include frequency of review and learning capture.
Suggested pilot length (weeks), staffing, and rough effort estimate.
Capture agreed next steps, owners, and review date.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.