The 5-minute stability check

Before investing in automation, AI, or process changes, run through this checklist. Each "no" reveals a stability risk that changes won't fix—and may amplify.

Ownership clarity

  • Can you name who owns every decision point? — Not who touches it, but who's accountable when it breaks
  • When exceptions hit, is there a named owner? — Not a queue. A person.
  • Do escalation paths exist in writing? — Not just "ask your manager"
  • Is handoff ownership explicit? — When work moves between teams, who owns the gap?

Decision rules

  • Are decision rules documented? — If someone new took over tomorrow, could they make the same calls?
  • Do rules apply consistently? — Or does it "depend on who's working"?
  • Are edge cases written down? — Not just the happy path
  • Can you explain approval criteria? — Without saying "it depends"

Exception handling

  • Are exceptions rare or routine? — If exceptions happen daily, they're not exceptions
  • Is there a defined path for each exception type? — Not "figure it out"
  • Do exceptions get documented? — Or just handled and forgotten?
  • Can someone other than "the expert" handle exceptions? — Single-person dependencies are stability risks

Automation readiness

  • Does the current workflow behave predictably? — Same inputs produce same outputs
  • Would the workflow survive if your best person left? — Tribal knowledge isn't stability
  • Do people trust the current process? — Or do they work around it?
  • Are failure modes known and monitored? — Or discovered by customer complaints?

How to interpret your results

All yes: Your workflow may be stable enough for safe automation. Proceed carefully, with monitoring.

Mostly yes: You have specific risks to address before automating. Fix those first.

Many no's: Automation will likely amplify existing problems. Diagnose stability before investing in tools.

What this checklist doesn't tell you

This checklist identifies signals of instability. It doesn't diagnose root causes, map failure modes, or tell you what to fix first.

That's what the Workflow Stability Assessment produces: a written verdict with ownership mapping, failure patterns, and a sequenced stabilization plan.

When to use this vs. request an assessment

  • Use this checklist when you're still exploring and want a quick self-check
  • Request an assessment when you need objective diagnosis, documented findings, and action sequencing

The checklist costs you 5 minutes. The assessment produces decision-ready outputs.