Write the runbook before the run
Create a browser automation runbook with stop triggers, intervention owners, and rollback evidence.
A pricing portal agent changes customer discount tiers. The workflow saves time but has a high-severity failure mode: wrong discount applied to a live account. FMEA runbook: failure mode, effect, detection, stop trigger, owner, rollback evidence The common trap is writing only happy-path operating steps. That leaves incident response to Slack improvisation when the agent behaves unexpectedly. Failure mode Agent selects the wrong discount tier or updates the wrong customer record. Name the specific wrong action, not just 'automation failed.' Effect Revenue leakage, customer trust impact, manual correction, and audit exposure. Severity determines how low the stop threshold should be.…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in