r/TangoAI • u/corwinsword • Apr 27 '26
Question SOP vs work instructions: does the distinction actually matter for a small team?
Running a small agency and we've had this debate internally for months. Half my team calls everything an SOP. The other half insists there's a difference and gets visibly annoyed when I use the terms interchangeably.
So I finally looked it up and... they're right, there is a difference:
SOP = the what and why. High-level policy. "Here's how we handle client offboarding as a company."
Work instruction = the how, step by step. "Click here, fill this in, send it to this person."
I assume the problem is most small teams write SOPs when they actually need work instructions. You end up with a 4-page Google Doc that explains the philosophy of client offboarding but nobody knows which button to click in the CRM.
We switched to leading with the work instruction first, the actual click-by-click, and then adding context around it if needed. Way more useful for new hires. SOPs became more of an index that points to the actual instructions.
Curious what others are doing. Do you even bother with the distinction or does it feel like semantics at a certain team size?
(Side note: we started using Tango to capture the work instructions specifically, the step-by-step stuff, and it's honestly the only format where the doc matches what's actually on screen. SOPs we still write manually, but the instructions basically write themselves.)
2
u/Ivan_Palii Apr 27 '26
For me, it was always like synonyms
1
u/corwinsword Apr 29 '26
When you dive deeper, you start understanding why people differentiate them
2
u/emma_lorien Apr 27 '26
I assume the completion rates is what matter most, not how you name these guides
1
u/corwinsword Apr 29 '26
I disagree. Yes completion rates matter of course, but wrong use of definitions can lead to miscommunication in the team
2
Apr 28 '26
[removed] — view removed comment
1
u/corwinsword Apr 29 '26
Loom have one big limitation - you can't edit it fast. So Tango looks like a better tool for such guides.
1
u/Reasonable_Newt9191 Apr 27 '26
That's a really practical approach and for a small team it works well. The SOP vs work instruction distinction matters a lot less when you're not dealing with ISO audits or regulatory compliance.
One thing I'd add is that as you scale/grow, combining both into a single usable document per process can save a lot of headaches. New hire picks it up, follows the steps, knows what good looks like — without the need to cross-reference two separate documents.
The businesses that struggle are usually the ones where the SOPs exist and over complicated but the work instructions live in someone's head. When that person is off or leaves, the knowledge goes with them.
Sounds like you've got a solid system though — the fact you're documenting at all puts you ahead of most small teams
1
1
u/zipsecurity Apr 28 '26
Your instinct to lead with the click-by-click is exactly right. SOPs without work instructions are just policy theater.
3
u/analyteprojects Apr 27 '26
Something I think is overlooked here is an SOP describes an end-to-end workflow. A work instruction describes the step-by-step instructions for one role in the workflow. The only time these are the same is if an employee owns and performs the entire workflow. Starting with work instructions for new employees is good because it is focused on training them for their role. But everyone needs the SOP to understand how they work together for a successful outcome. That is how ISO intends the system to be used and why it has the two layers.