SOPs & Process

What Works

• Write SOPs right after doing the task — while it's fresh
• Use a 3-part format: Trigger | Steps | Done Criteria
• Store them where the work happens (Notion, Google Docs, shared drive — anywhere your team actually opens)
• Review quarterly — stale SOPs are worse than none

Watch Out For

• Overly long SOPs aren't read — 1 page max per process
• Don't write SOPs for things you do once a year — write them for weekly/daily work
• Version control matters: date every update and archive old versions

Frequently Asked Questions

What is an SOP?

A Standard Operating Procedure (SOP) is a documented way of completing a task consistently. For operators, the goal is: anyone on your team can do this right without asking you.

How long should an SOP be?

One page or less for most tasks. If it's longer, it's either two processes or it needs a checklist format instead of paragraphs.

What format should I use for SOPs?

Trigger → Steps → Done Criteria. Add screenshots or a short video for visual tasks. Text-only is fine for most things. Stored wherever your team already works.