Standard Operating Procedure Anyone Can Run

Turn a messy process into an SOP a new teammate can run without pinging the author. PROCESS Name: [PROCESS_NAME] Owner role: [ROLE] Trigger: [WHAT STARTS IT] Done looks like: [OUTPUT / STATE] Tools: [TOOLS] Frequency: [DAILY | WEEKLY | PER EVENT] Failure that already happened: [INCIDENT OR "none yet"] Rough notes from the person who does it today: [PASTE] WRITE THE SOP WITH THESE SECTIONS 1) Purpose — 3 sentences. Who is affected if this is skipped. 2) Roles — RACI in a small table (Responsible, Accountable, Consulted, Informed). 3) Before you start — access, files, and a 5-item preflight checklist. 4) Steps — numbered. Each step: action verb, where to click or which system, the exact field or command, and the expected result. Flag steps that need a judgment call and give the rule for that judgment. 5) Decision branches — if X, do Y. Put irreversible steps behind a confirmation. 6) Quality check — how the owner verifies the output before handing off. Include one example of "good" and one of "not good." 7) Exceptions — what to do when the happy path breaks, who to escalate to, and the SLA. 8) Change log line — version, date, author placeholder. Also produce a one-screen checklist version (no prose) for the person mid-task. Write for a competent new hire, not for the expert who already knows the shortcuts. Do not leave "use best judgment" without the criteria.