How to stop being the bottleneck using SOPs

Executive overview

When every question from your team lands on you, you become the bottleneck. The fix is a Standard Operating Procedure (SOP) — a written process your team checks first, so you stop fielding the same questions repeatedly.

Write the SOP once. Each interruption that slips through becomes an investment: answer it, update the SOP, and that question stops coming back.

The SOP shifts authority from your brain to a shared process — and that's what creates a self-managing team.

Building your first SOP

• Open a doc in whatever tool your team already uses (Notion, Google Docs, spreadsheet)
• Name it descriptively — e.g. "How to cover for an unexpected team member out of office"
• Write the steps you already know; don't overthink the first draft
• When a question comes in, respond with "did you check the SOP?" to redirect the habit

Turning interruptions into SOP improvements

• A weak SOP still saves time if you treat every interruption as a gap to fill
• When someone asks a question, answer it — then ask them to update the SOP with that answer
• One-time cost of the conversation saves all future identical conversations
• Each update makes you incrementally less of a bottleneck

Giving your team permission to decide

• Many interruptions aren't caused by lack of knowledge — they're caused by lack of confidence
• Set a reversibility rule: if a decision is easily reversible, make it and report after
• Set a dollar threshold: if the cost of a wrong call is under a set amount, just decide
• Both rules let team members act without waiting for you, even if they're unsure
• You choose the threshold based on your current trust level with the team