Five common mistakes that make SOPs ignored and outdated

Executive overview

SOPs fail not because teams don't write them, but because of how they're written. Bad format, wrong authors, and locked editing guarantee that no one uses or maintains them.

Build SOPs for retrieval speed, not creation convenience. The SOP is created once but used dozens of times.

The core mistake is optimising for ease of creation instead of ease of use.

Mistake 1: Video-only SOPs

• A single long video has no skimmable structure, no timestamps, no searchability.
• Updating one changed step means re-filming the whole thing — so it never gets updated.
• Video works inside a single step; it fails as the entire SOP.

Mistake 2: Wrong authors

• Top-down SOPs written by owners or managers trigger resistance, not adoption.
• The people who do the work must write the SOPs they will use.
• Others can review and improve, but the author must be the practitioner.

Mistake 3: Locked, non-editable documents

• If suggesting a fix requires permission or multiple intermediaries, feedback stops.
• Every team member should have at minimum commenting access, ideally suggestion access.
• View-only access signals you don't want the process to improve.

Mistake 4: Dense, unskimmable formatting

• Long paragraphs and giant images force reading instead of scanning.
• Use numbered steps with headers that state the result, not the action.
• A good step header lets the reader know — without opening it — whether they need to dig deeper.
• Bold key terms; use sections, toggles, and searchable keywords.
• Poor example: "Pull up everything you need" — vague, no clear completion signal.
• Good example: "Verify upcoming holidays reflect from Gusto in Google Calendar" — unambiguous result.

Mistake 5: Writing SOPs before you hire

• Writing comprehensive SOPs as a hiring prerequisite is a false assumption.
• The order of operations matters; the video referenced covers why this is not required upfront.