1. The Two Reasons Most SOPs Never Get Used

On a recent episode of Virtual Equity, Nicole handed Lindsey four unscripted business scenarios. Losing employees, being buried in approval requests, missed deadlines, and mistakes piling up during a growth spurt. Four different problems, and the same missing piece underneath every one of them: a documented, repeatable way of doing the work.

Most content about SOPs treats that as a one sided fix. Leadership writes the process, employees follow it, end of story. In practice, that is exactly why so many SOPs get written once and then ignored. There are two separate reasons this breaks down, one that lives on the owner's side of the desk and one that lives on the employee's side, and both have to be solved for a process to actually stick.

2. The Owner's Trap: Waiting Until It Is Good Enough

The first trap belongs to the owner. It is the belief that a process is not worth writing down until it can be written well, with clear steps, screenshots, and a professional layout. Lindsey has built SOPs inside fast growing, understaffed small businesses for most of her career, and her honest answer is that she does not wait for any of that.

She shared a story from an earlier role where an owner kept losing recruiters every few weeks and could not understand why. There was no process for anything, so every new hire had to guess, ask, or get it wrong. When Lindsey suggested writing things down, the owner pushed back, convinced that documentation would slow the business down and tie it up in red tape. In reality, the absence of any process was exactly what kept costing him hires, month after month. Waiting for the perfect version never made the problem smaller. It just delayed the fix.

3. The Employee's Trap: Being Handed a Rulebook Nobody Asked Them About

The second trap belongs to the employee, and it is just as common, even if it gets talked about less. A process that gets handed down from above, fully formed, with no input from the people who actually do the work, tends to feel like a rulebook rather than a tool. It signals that leadership does not trust employees to make good decisions, which is the opposite of what most owners actually intend.

Nicole described the flip side of this from her own experience managing a heavy volume of work with an assistant while she was constantly on the road. The process they used was not handed to that assistant as a finished document. It was built together, through conversation, about how they communicated and how each type of request should move. Because the assistant had a hand in shaping it from the start, she rarely needed to ask a question that was not a genuine yes or no decision.

4. How to Write the First Draft in Minutes, Not Weeks

The fastest way to break the owner's trap is to remove every excuse for waiting. When Lindsey needs something documented quickly with a small team and no time to spare, her go to method is video. Whoever figures out how to do a task records themselves doing it, right then, on a phone or a screen. No script, no editing, just a labeled recording dropped into a shared drive.

If video is not your style, the backup method is just as unpolished. Open a plain document and type the steps as short instructions. Do this, then this, then this. She is upfront that she will write "in general, it is in this screen" rather than mark exactly where to click, and hand the rough draft to someone else to add detail later if the process needs it. Tools like Scribe, which generate a step by step guide automatically from your clicks, can also remove even that small amount of effort. None of these methods require special skill. They require two minutes and a willingness to skip the polished version entirely.

5. The Handoff: What Changes the Moment You Give the Document Away

Writing the first draft fast solves the owner's side of the problem. Handing it off solves the employee's side. The moment a rough SOP exists, the next move is giving ownership of it to whoever actually performs the task day to day, not keeping it as something only leadership is allowed to edit.

That single shift changes how a process gets experienced. Instead of a rule enforced from above, it becomes a working document the employee is trusted to improve. Nicole pointed out that when you have genuinely good employees, they often adopt and refine a process better than the person who originally created it, simply because they are the ones using it every day.

6. Why Ownership Is What Creates Buy In

This is the part most SOP advice skips entirely. A process someone helped shape gets followed differently than a process someone was simply told to follow. Ownership changes the relationship an employee has with the document, from compliance to investment.

Lindsey described this as a genuine opportunity for employees who are being coached toward more responsibility. Owning a process is a visible, low risk way to showcase expertise, and it gives someone a real stake in whether the department runs smoothly, rather than a rule to simply obey.

7. What This Looks Like Once It Is Working

Lindsey shared a simple, almost mundane example that captures how this plays out day to day. A process might say sign a document and hand it to a coworker. That works fine until three more people start handing that same coworker documents and things start getting lost on a crowded desk. In a top down system, that mistake becomes a lecture. In a system built on shared ownership, the person doing the work is the one who suggests the fix, in this case, a labeled tray on the desk, and the process gets updated because they noticed the gap and cared enough to solve it.

That is the visible difference between a process that was handed down and a process that is genuinely owned. One waits for someone above it to notice the problem. The other gets fixed by the person closest to it, immediately.

8. A Process Is Never Finished, From Either Side of the Desk

Both hosts were clear that writing an SOP once does not mean it is finished. Every process gets tested the moment real pressure hits it, whether that pressure comes from more customers, more employees, or a system change.

From the owner's side, that means expecting to revisit processes as the business grows, rather than treating a written SOP as a finished project. From the employee's side, that means the invitation to improve a process is ongoing, not a one time favor. Both perspectives point to the same outcome. A process built and maintained together adapts faster than one that only one person is allowed to touch.

9. What Skipping Both Steps Actually Costs You

Skip the owner's fix, and you stay the bottleneck. Every decision, every repeated question, every approval still runs through you, because nothing exists outside your own head. Skip the employee's fix, and you get a written process that nobody actually follows, because it was imposed rather than shaped with the people using it.

The scenarios Nicole gave Lindsey in this episode, employees quitting, an owner who cannot get away from their desk, deadlines slipping, mistakes piling up during growth, all traced back to one or both of these gaps. Fixing only the documentation half of the problem is not enough. The buy in half is what makes a process actually last.

10. Two Starting Points, One for Owners, One for Employees

If you are the owner, pick one task that generates the most repeat questions on your team right now. Record it or write it out in plain language today, without worrying about polish. Then hand the draft to whoever performs that task most often and tell them plainly that it is theirs to improve.

If you are the employee receiving that draft, treat it as an invitation, not a test. Note where it does not match how the work actually happens, update it, and bring changes back to the group instead of quietly working around the gaps. That is the exchange that makes a process worth keeping current on both sides of the desk.