The correction: undocumented process isn't flexibility, it's chaos that only feels free until someone leaves. The fix is a written change-log so the process can evolve on purpose, not drift by accident.
SOP: Changing a live process
Run this whenever someone wants to alter an existing SOP.
Stage 1 — Propose
— ☐ Write what changes and the problem it solves. (Owner: proposer)
— ☐ Name who the change affects downstream. (Owner: proposer)
Stage 2 — Approve
— ☐ The SOP's owner accepts or rejects within two days. (Owner: SOP owner)
— ☐ On accept, update the doc and stamp the date and reason. (Owner: SOP owner)
Stage 3 — Broadcast
— ☐ Notify everyone who runs it; old version archived, not deleted. (Owner: SOP owner)
Owner: SOP owner. Trigger: anyone proposes a process change. Done-when: the SOP is updated, dated, and the change is announced.
Save this. Run it every time.
The Ops Playbook
@TheOpsPlaybook
MYTH: "Process makes the team rigid."
This post was published in the Telegram channel The Ops Playbook (@TheOpsPlaybook). All its posts are on the channel page.
Open on Telegram