Document processes with verification checkpoints

Document repeatable processes with verification checkpoints

Critical repeatable processes (deployments, migrations, incident response) where precise step order and verification prevent outages and tribal knowledge loss.

• · process name and audience
• · trigger event (what kicks off the process)
• · all prerequisites (access, tools, knowledge)
• · decision points and rollback conditions

• · numbered procedure with time estimates
• · prerequisites checklist
• · decision trees for edge cases
• · verification checkpoints (you should see X)
• · rollback steps for failure recovery

• · Process is repeatable (not one-time)
• · Clarity on who will follow it (expertise level)

• · Omitting obvious steps → new team members lost at 2 AM
• · Missing decision points → failures cascade undetected
• · No verification checkpoints → stale docs cause outages
• · Unclear prerequisites → access/permissions block execution

• · Anti-patterns with specific failure scenarios (what's obvious to you is opaque to new hire)
• · Explicit prerequisites table with system names, access levels, and request paths
• · Numbered steps with verification checkpoints (not just outcome descriptions)
• · Rollback steps explicitly included