Building SOPs Your Team Actually Follows

Why Most SOPs Fail

Every business consultant will tell you to document your processes. Most SMB owners have tried. And most SOPs end up in a folder on Google Drive that nobody opens after the first week.

This is not because SOPs are a bad idea. It is because the way most companies create SOPs guarantees failure:

• Written by managers, not by doers. The person who writes the SOP has not actually done the task in months.
• Too long and detailed. A 15-page document for a task that takes 10 minutes.
• Created once, never updated. The process changed six months ago, but the SOP still describes the old way.
• No accountability. Nobody owns the SOP. Nobody checks if it is being followed.
• Stored in an inaccessible location. A PDF buried three folders deep in SharePoint.

The result: your team ignores the SOPs and does things however they remember. Which is exactly where you started.

Here is how to build SOPs that actually work.

The SOP Framework That Works

Principle 1: Write With the User, Not For Them

The person who performs the task every day should co-create the SOP. Your role as a manager is to help with, not dictate.

The co-creation process:

1. Sit with the person who does the task best
2. Ask them to walk through it step by step while you document
3. Ask “why” at each step — some steps exist for good reasons, others are just habit
4. Have a different person try to follow the draft SOP
5. Revise based on where they got stuck

This takes 1–2 hours per SOP. It produces documentation that is accurate, practical, and owned by the team.

Principle 2: One Page Maximum (for Written SOPs)

If your SOP is longer than one page, it is either too detailed or covers too many tasks. Split it.

The ideal SOP structure:

Section	Content	Length
Header	Title, version, owner, last updated date	2 lines
Purpose	Why this SOP exists (one sentence)	1 line
Scope	When to use this procedure	1-2 lines
Prerequisites	What you need before starting	3-5 bullet points
Steps	Numbered action steps	8-15 steps maximum
Decision points	If/then branches	2-3 maximum
Quality check	How to verify the output is correct	2-3 bullet points
Troubleshooting	Common problems and solutions	3-5 items

Principle 3: Use Verbs, Not Descriptions

Every step should start with an action verb. Not “the invoice should be reviewed” but “review the invoice for errors.”

Bad step: “The sales order needs to be entered into the system by the sales coordinator before it can be processed.”

Good step: “Enter the sales order in Omie: Sales > New Order > fill in client code, items, quantities, and payment terms.”

Principle 4: Include the “Why” for Critical Steps

For steps where skipping or doing it wrong has significant consequences, add a brief explanation.

Example: “Step 5: Verify the client’s credit limit before confirming the order. Why: Orders exceeding credit limits require manager approval. Shipping without approval creates collection risk.”

This turns compliance into understanding. People follow rules better when they know the reason.

The SOP Template

Here is our standard template. Copy and adapt it.

═══════════════════════════════════════════════
SOP: [Process Name]
Version: [X.X] | Owner: [Name] | Updated: [Date]
═══════════════════════════════════════════════

PURPOSE: [One sentence explaining why this procedure exists]

SCOPE: [When this procedure applies and when it does not]

PREREQUISITES:
□ [What you need before starting — access, tools, information]
□ [...]
□ [...]

STEPS:
1. [Action verb] [specific action] [in what system/location]
2. [Action verb] [specific action]
3. [Action verb] [specific action]
 → If [condition], go to Step 3a
 → If [other condition], continue to Step 4
 3a. [Action verb] [specific action]
4. [Action verb] [specific action]
...

QUALITY CHECK:
□ [How to verify the output is correct]
□ [What a correct result looks like]

TROUBLESHOOTING:
• [Common problem] → [Solution]
• [Common problem] → [Solution]
• [Common problem] → [Solution]

ESCALATION: If this procedure cannot be completed,
contact [Name/Role] at [contact method].
═══════════════════════════════════════════════

Video SOPs: The Game Changer

For many tasks, a 3-minute screen recording or phone video is worth more than a 3-page document. Video SOPs are particularly effective for:

• Software navigation — “Click here, then here, then enter this”
• Physical tasks — warehouse picking, equipment operation, quality inspection
• Complex setups — configuring a report, setting up a new client in the CRM
• Tasks with visual judgment — “This is what a correctly packed box looks like”

How to Create Video SOPs

Tools you need:

• Screen recording: Loom (free tier available), OBS Studio (free), or native OS recording
• Physical tasks: Any smartphone with a tripod or willing colleague
• Editing: Loom has built-in trimming. For more, CapCut (free) or Descript

Best practices:

1. Keep it under 5 minutes. If longer, split into multiple videos.
2. Narrate as you go. Explain what you are doing and why.
3. Show the common mistake and how to fix it.
4. Use zoom/callouts for small interface elements.
5. Pair with a written checklist. Video for learning, checklist for daily reference.

Where to Host Video SOPs

Platform	Best For	Cost
Loom	Screen recordings, quick videos	Free for 25 videos; R$60/user/month for business
Google Drive	Free storage with Google Workspace	Included with Workspace
Notion	Embedding videos alongside written SOPs	Free tier; R$40/user/month
Trainual	Dedicated SOP and training platform	R$250+/month; best for 20+ employees
Tango	Auto-generated step-by-step guides from screen recording	Free tier; R$40/user/month

Building the SOP Library

Priority Matrix: What to Document First

Not everything needs an SOP. Start with tasks that are:

Priority	Criteria	Examples
P1 (This month)	High frequency + high risk of error	Order processing, invoicing, client onboarding
P2 (Next month)	High frequency + low-to-medium risk	Email responses, report generation, filing
P3 (Quarter 2)	Low frequency + high impact when done wrong	Month-end close, employee termination, system recovery
P4 (As needed)	Low frequency + low risk	Office supply ordering, room booking

Typical SOP Library for a R$10M–R$30M SMB

Department	Number of SOPs	Key Procedures
Sales	5-8	Lead qualification, proposal creation, contract signing, CRM entry, handoff to operations
Operations	8-12	Order processing, quality control, delivery scheduling, returns handling, inventory counting
Finance	6-10	Invoice issuance, payment processing, collections, monthly close, expense reporting, bank reconciliation
HR	5-8	Hiring process, onboarding checklist, leave requests, performance review, offboarding
IT	3-5	New user setup, password reset, backup verification, system access management

Total: 27-43 SOPs. Build over 6 months, not 6 days.

Integrating SOPs into Onboarding

SOPs become most valuable when they are the backbone of your onboarding process. New hires should not learn by shadowing for two weeks — they should learn by following documented procedures with supervision.

The SOP-Based Onboarding Framework

Week 1: Core SOPs

• Assign the 5–8 SOPs most relevant to the role
• New hire reads/watches each SOP
• New hire performs each task with supervision
• Supervisor validates completion

Week 2: Independent Execution

• New hire performs tasks independently using SOPs as reference
• Supervisor reviews outputs (not the process — the outputs)
• Identify gaps and provide targeted coaching

Week 3-4: Full Autonomy

• New hire operates fully with SOP reference available
• Supervisor spot-checks quality
• New hire provides feedback on SOPs (often catching outdated or unclear steps)

Result: Onboarding time drops from 4–8 weeks (typical for undocumented SMBs) to 2–3 weeks. Quality is consistent from day one.

The Review and Update Cadence

SOPs are living documents. An outdated SOP is worse than no SOP because it creates false confidence and trains people on the wrong process.

Quarterly Review Process

1. SOP owner reviews — Is this still accurate? Have tools or processes changed?
2. User feedback check — Ask 2–3 people who use the SOP if anything needs updating
3. Version update — If changes are made, update version number and date
4. Communication — Notify all users of significant changes
5. Archive old version — Keep previous versions accessible but clearly marked as outdated

Trigger-Based Updates

Update immediately when:

• A software system changes (new ERP version, new tool)
• A process step is added or removed
• A quality problem is traced back to an SOP gap
• A new hire identifies an unclear or missing step
• Regulations change (especially fiscal/compliance procedures)

SOP Governance

Element	Recommendation
Ownership	Every SOP has one named owner (person, not department)
Review frequency	Quarterly minimum
Approval	Department manager signs off on changes
Access	All users can view; only owner can edit
Format	Standardized template across all departments
Storage	Single location (Notion, Google Drive, Trainual) — never multiple copies

Tools Comparison

Tool	Best For	SOP Features	Monthly Cost
Notion	Tech-comfortable teams	Pages, databases, embeds, templates	Free–R$40/user
Google Docs	Simple, accessible	Comments, version history, sharing	Free with Workspace
Trainual	Dedicated SOP platform	Assignments, tracking, quizzes, roles	R$250+/month
Slite	Knowledge base with search	Templates, verification, analytics	R$35/user/month
Process Street	Checklist-based SOPs	Recurring checklists, automations	R$120+/month

Our recommendation for most Brazilian SMBs: Start with Notion or Google Docs. Move to Trainual when you exceed 25 employees and need formal tracking and accountability.

Measuring SOP Effectiveness

How do you know if your SOPs are working?

Metric	How to Measure	Target
Onboarding time	Days until new hire is independently productive	30% reduction vs. pre-SOP
Error rate	Defects, rework, or corrections per process	50% reduction within 6 months
Process consistency	Variation in output quality across different people	Quality variance under 10%
SOP usage	Page views, video plays (if using Notion or Trainual)	Weekly usage by assigned users
SOP freshness	% of SOPs updated within last 90 days	Above 80%

Connecting SOPs to Operational Excellence

SOPs are not the end goal — they are a tool in your operational excellence toolkit. They connect directly to:

• Process mapping — Your maps define what needs SOPs. Your SOPs detail how to execute each step.
• ERP implementation — SOPs must reflect your system workflows. Update SOPs when you change systems.
• Training and development — SOPs are your curriculum. They define what competence looks like.
• Quality management — SOPs set the standard. Deviations from SOPs are quality issues to investigate.

The companies that do this well — document, train, review, improve — consistently outperform those that rely on tribal knowledge and hope.

---

Want to assess your operational documentation maturity? Take our free diagnostic — it evaluates your process documentation alongside financial health, team capabilities, and growth readiness.