Why your team hates SOPs and how to fix it

Executive overview

Most teams associate SOPs with bureaucracy, micromanagement, and creative stifling. The problem isn't SOPs themselves — it's how they're introduced and who owns them.

SOPs are just work recipes. The resistance comes from filling cultural gaps with assumptions rather than answers.

SOPs only kill creativity when they're imposed on the wrong work by the wrong people.

Give ownership to the people doing the work

• Teams reject SOPs written by owners or consultants — they feel like the Mona Lisa handed with a paintbrush
• Outsourced SOPs produce intimidation, rejection, and ignored documentation
• Have workers write their own SOPs; they become guides for future selves and colleagues
• Give editing access openly — in seven years, no horror story of teams editing SOPs too much

Pick a tool built for collaboration

• SOPs locked behind permissions and passwords will not be updated
• If changing an outdated step requires 30 hoops, no one will change it
• Use a centralized, accessible tool with revision history — not a dedicated locked system
• The barrier to edit should be zero

Only create SOPs where they actually help

• A recipe for a cup of water isn't helpful — neither is an SOP for work people already do instinctively
• The goal: make mindless work truly mindless, not make creative work robotic
• Creative processes have too many permutations to systemize well — and systemizing them rarely changes outcomes
• The real targets are the "bits of boring" surrounding creative work: pre-work checklists, file uploads, setup steps
• A pre-filming checklist frees mental energy for the actual creative act
• SOPs protect creativity by removing the cognitive load of remembering routine steps