3.X.2 SOPs & Templates

Make It Easy to Do It Right

Turn knowledge into action. Empower teams to execute flawlessly.

What You’re Actually Doing Here

This section is about turning defined processes into usable tools: SOPs, checklists, templates, and guides.

These are the assets your team needs to execute reliably, without waiting on tribal knowledge or hallway conversations.

You’re now:

Writing clear SOPs for each core process
Building templates and guides for consistency
Making it easy for anyone to execute well
Training new team members through real use cases

A good SOP isn’t paperwork. It’s an instruction manual for winning the same way every time.

1. Create Clear SOPs

Goal: Give teams a step-by-step guide for executing core processes.

Each SOP should include:

Overview – What this process does and why it matters.
Who It’s For – The roles or teams responsible for executing this SOP.
Criticality Class – Importance level (e.g. high volume, customer-impacting, compliance-sensitive).
Preconditions – What must exist before starting — logins, prior steps, data availability.
Data Required to Complete – Key inputs needed (e.g. order number, customer info, system access).
Step-by-Step Instructions – The exact sequence of actions to complete the task — clear and concise.
Known Variations / Exception Handling – Expected deviations, options, or common “what if” paths.
Validation Steps – How to confirm the process completed successfully — including final system state.
Links to Tools, Templates, or Checklists – Direct access to any supporting docs, files, or forms used in the process.
Owner / Contact for Questions – The go-to person or team if something’s unclear or broken.
Last Updated Timestamp – Track when this SOP was last reviewed or revised.

Tools: Notion, Process Street, Google Docs

Use your Transaction Specification as a model SOP.

2. Build Operational Templates

Goal: Create reusable templates for common actions or artifacts.

Examples:

Campaign brief template (Marketing)
Financial close checklist (Finance)
Onboarding flow (People Ops)
Sales proposal doc (Sales)

Store in a central library, with:

Clear naming conventions
Cross-linking to SOPs
Usage instructions

3. Test for Clarity & Resilience

Goal: Ensure SOPs work for someone other than the author.

Have another team execute the SOP with no help
Gather feedback for clarity gaps
Pilot in a live project
Improve based on what breaks

If it doesn’t work for a new hire, it doesn’t work.

4. Train the Team on Usage

Goal: Make SOPs and templates a living part of execution.

Training Tactics:

Include in onboarding
Use in 1:1 coaching and retros
Record Loom walkthroughs
Review during functional meetings
Reinforce through task templates

Don’t just store them. Teach them. Use them. Improve them.

5. Embed in the Daily Workflow

Goal: SOPs must be easy to find and used in real-time.

Embed SOP links into:

Project templates
CRM / task management tools
Onboarding flows
Dashboards and wiki pages

Tag outdated docs and schedule review cycles.

SOPs are operational currency. Keep them current or mark them as expired.

Bottom Line:

Defined processes build structure. But SOPs and templates bring that structure to life in the hands of your team.

Give them the tools to win consistently. Then watch quality, speed, and trust increase across the org.