Systems, SOPs & Processes

The Technician’s Trap

There’s a moment in the life of almost every service business owner where something breaks. Not the business - the owner.

The work is good. The clients are happy. Revenue is growing. But the person at the centre of it all is working harder than they ever did at their nine-to-five, making decisions they’ve already made a hundred times before, and wondering why it doesn’t feel like they own a business.

It feels like the business owns them.

Michael Gerber’s insight was simple but devastating. Most small business owners are not entrepreneurs. They’re technicians having an entrepreneurial seizure.

They were good at making the pies, so they assumed they’d be good at running a pie shop. But making pies and running a pie shop are completely different jobs.

Alex was a great marketer. He was not running a marketing business. He was just a marketer with clients.

What Is a System, Really?

The word “system” gets thrown around constantly in business circles. It’s become one of those words that means everything and nothing at the same time.

So let’s nail it down.

A system is a defined, repeatable way of producing a specific outcome. That’s it. Nothing more complicated than that.

When you make coffee in the morning, you follow a system - even if you’ve never written it down. Beans, grinder, water, machine, mug. You do it the same way every time because you’ve figured out the steps that produce the result you want.

If your friend comes over and asks “how do you make your coffee?”, you could walk them through it and they’d get a similar result.

A business system works exactly the same way, just at a higher stakes. It’s a defined sequence of steps that produces a predictable business outcome - onboarding a client, delivering a service, handling a refund, generating a lead.

If the answer is yes, you have a system. If the answer is no, you have a dependency - and that dependency is probably you.

The McDonald’s Test

Gerber famously used McDonald’s as an example. Not because McDonald’s makes great food, but because McDonald’s makes identical food in 40,000 locations staffed largely by teenagers.

That doesn’t happen through talent. It happens through systems so clear and so detailed that anyone can follow them and produce the same result.

You don’t need to become McDonald’s. But the principle is the same: if your business can only produce quality results when you personally are involved, you don’t have a business system. You have a talent dependency.

The Three Levels of Business Work

Before we talk about how to build systems, it helps to understand what kinds of work exist in a service business.

Gino Wickman, in Traction, talks about the importance of separating the visionary from the integrator. John Warrillow in Built to Sell talks about building a business that doesn’t depend on any single person. Gerber talks about working on the business, not in it.

They’re all pointing at the same truth from different angles. There are three fundamental levels of work in any business:

Level 1: Technical Work - This is doing the work. Writing the copy. Building the website. Designing the logo. Running the ad campaign.

It’s what most founders are brilliant at, and it’s the reason they started their business in the first place.

Level 2: Management Work - This is running the system. Making sure projects stay on track. Ensuring quality standards are met. Coordinating handoffs between team members.

Level 3: Strategic Work - This is designing the system. Deciding what services to offer. Building the processes that produce consistent results.

Defining how the business operates so that Level 1 and Level 2 work can happen without you.

Here’s the uncomfortable truth: most service business owners spend 80% of their time at Level 1, 15% at Level 2, and maybe 5% at Level 3.

The successful ones invert that ratio - or at least get it a lot closer to even.

What Is an SOP?

SOP stands for Standard Operating Procedure. It sounds corporate, bureaucratic, maybe even boring.

But don’t let the name fool you. An SOP is simply a written-down version of how you do something.

That’s it. No special format. No complicated template. Just: “Here’s how we do this thing, step by step, so that anyone can do it the way we want it done.”

An SOP captures what’s in your head and puts it somewhere anyone can access it. It turns institutional knowledge into institutional capability.

Instead of one person knowing how to do something, the business itself knows how to do it.

The Anatomy of a Good SOP

A useful SOP has five components. It doesn’t need to be fancy - it just needs to be clear:

1. The Trigger - What causes this process to start? (“A new client signs a contract.” “A lead fills out the contact form.” “It’s the first Monday of the month.”)

2. The Steps - What happens, in order? Each step should be specific enough that someone who’s never done it before can follow along.

3. The Owner - Who is responsible for each step? This could be a person, a role, a tool, or an AI agent.

4. The Output - What does this process produce when it’s done correctly? (“A completed client brief.” “A published blog post.” “An updated CRM record.”)

5. The Quality Check - How do you know it was done right? What does “good” look like?

Why Most People Don’t Build Systems

If systems are so important, why doesn’t everyone have them? The answer is simpler and more human than you’d expect.

Reason 1: It Feels Slower

Writing an SOP for something you can just do yourself in 20 minutes feels like a waste of time. Why spend an hour documenting a process when you could just knock it out?

This is the technician’s math - and it’s always wrong at scale.

That 20-minute task happens every week. Over a year, that’s 17 hours. Over three years, 52 hours. And every one of those hours is your hours - the most expensive hours in the business.

The one hour you spend writing the SOP pays for itself within a month.

Reason 2: It Feels Rigid

Creative professionals especially resist systematisation. “Every project is different.” “Clients have unique needs.” “You can’t template this kind of work.”

These are all true - and they’re all missing the point.

You’re not templating the creative decisions. You’re templating everything around the creative decisions. The intake process, the brief format, the review cadence, the delivery checklist, the revision process.

All of that can and should be systematised. The actual creative work sits inside a structure that makes it easier, not harder.

Reason 3: It Feels Unnecessary Right Now

When you only have three clients, you can keep everything in your head. The chaos is manageable.

But systems aren’t built for the business you have today - they’re built for the business you want to have in two years.

By the time the chaos is unmanageable, you’re too deep in it to stop and build the systems you should have built months ago.

This is what Warrillow hammers on in Built to Sell. If you want a business someone could buy - or one that could run without you - you need to build the systems before you need them.

The Process Spectrum

Not every process needs the same level of documentation.

One of the biggest mistakes people make when they first start building systems is trying to document everything at the same level of detail. That’s a recipe for burnout and abandoned SOPs.

Think of your processes on a spectrum:

Checklists are for simple, low-risk tasks that just need a quick reminder. Publishing a social media post. Running a backup. Sending a weekly report.

Process Maps are for moderate-complexity work where you need to know who does what and in what order, but the individual steps are straightforward. Client onboarding. Monthly invoicing. Content calendar planning.

Full SOPs are for your core delivery processes - the ones that directly affect client outcomes and revenue. These need detailed steps, defined owners, quality checks, and version control.

Automated processes are SOPs that have evolved to the point where technology handles them entirely - or almost entirely, with human-in-the-loop checkpoints where needed.

The key insight: you don’t start by writing full SOPs for everything.

You start by writing checklists for the things that trip you up most often, then graduate the important ones to process maps, then to full SOPs, then eventually to automation.

It’s a natural progression, not a one-time project.

Where to Start: The Five Core Processes

If you’re a service business owner looking at this and thinking “I have a hundred things that need documenting,” take a breath.

You don’t need a hundred SOPs. You need five.

Every service business, regardless of industry, has five core processes that drive everything else.

Wickman calls these “core processes” in Traction. Warrillow would call them “the things that make your business sellable.” Gerber would call them “the systems that run the business.”

1. Lead Generation - How do you attract potential clients? Whether it’s content marketing, referrals, outbound outreach, or partnerships - document what you do and how you do it.

2. Sales & Conversion - What happens when a lead raises their hand? The discovery call, the proposal, the negotiation, the close. Every step, every template, every follow-up cadence.

3. Client Onboarding - From signed contract to first deliverable. The welcome email, the kickoff call, the intake questionnaire, the project setup. This is where first impressions are made.

4. Service Delivery - The actual work. How do you produce the thing you sell? This is usually the biggest and most complex process, and it’s often the last one people document because “every project is different.”

Document the structure. The creative work goes inside it.

5. Review & Improve - How do you know if things are working? How do you collect feedback, measure quality, and improve over time? This is the process that makes all the other processes better.

Building Your First SOP

The biggest barrier to writing SOPs is overthinking.

People want the perfect template, the perfect tool, the perfect format. Meanwhile, their processes remain trapped inside their heads, accessible to no one.

Here’s how to build your first SOP in under an hour. No fancy software required. A Google Doc works fine.

Step 1: Pick One Process

Choose the process that either happens most frequently or causes the most friction.

Don’t try to document everything at once - that’s a guaranteed way to document nothing.

Step 2: Do It One More Time, Slowly

The next time you do this process, slow down and write down every step as you do it.

Don’t edit, don’t organize, don’t worry about formatting. Just capture what you’re actually doing, in the order you’re doing it.

Step 3: Clean It Up

Go back through your steps and add three things to each one: who does it, what the output is, and how long it should take.

This transforms a list of steps into something someone else can actually follow.

Step 4: Test It

Hand the SOP to someone else. Watch them try to follow it. Don’t help unless they’re truly stuck.

Every question they ask represents a gap in your documentation. Write down each question and update the SOP.

Step 5: Iterate

An SOP is never done. It’s a living document.

Every time it’s used, it gets a little better. Every edge case you discover gets added. Every unnecessary step gets removed.

Over time, your SOP goes from “rough first draft” to “polished machine.”

The SOP Lifecycle

SOPs aren’t static documents you write once and forget.

The best businesses treat their SOPs like software - they version them, test them, and iterate on them continuously.

Create - Write the first version. Get it out of your head and onto paper. It doesn’t need to be perfect.

Deploy - Put the SOP where your team (or your future AI agents) can access it. A shared drive, a project management tool, a knowledge base - wherever your team goes for answers.

Execute - Use the SOP in real work. This is where theory meets reality. Some steps will work great. Others will reveal gaps you didn’t anticipate.

Review - On a regular cadence - monthly is ideal - look at which SOPs are being used, which ones are causing problems, and which ones need updating. This is where the data speaks.

Improve - Update the SOP based on what you learned. Add the missing steps. Remove the unnecessary ones. Clarify the confusing bits.

Version - Track your changes. Version 1.0 becomes 1.1 becomes 2.0. This way, if something breaks after an update, you can roll back. It also gives you a history of how your processes have evolved.

Then the cycle repeats.

This is what Gerber means when he talks about working on the business. The business is a system. The system improves through iteration.

Your job as the owner is to drive that iteration.

The Five Mistakes That Kill Most SOPs

After watching hundreds of service business owners try to build systems, certain patterns emerge.

These are the mistakes that cause people to give up on SOPs entirely - not because SOPs don’t work, but because these mistakes make it feel like they don’t.

Mistake 1: Writing SOPs for an Ideal World

People write SOPs describing how things should work instead of how things actually work. The SOP looks beautiful on paper and falls apart in practice because it was never grounded in reality.

Start with what you’re actually doing. Improve from there.

Mistake 2: Documenting Everything at Once

The “let’s systematise the whole business this weekend” approach. It never works. You burn out, abandon the project, and conclude that “SOPs don’t work for my business.”

They do. You just tried to eat the whole elephant in one sitting.

Mistake 3: Making SOPs Too Detailed

An SOP that reads like a legal contract won’t get used.

People need enough detail to do the work correctly, not so much detail that they spend more time reading the SOP than doing the task.

If a step is obvious to a competent adult, you don’t need to document it.

Mistake 4: Never Reviewing or Updating

An SOP written six months ago and never touched since is probably wrong. Your business has changed. Your tools have changed. Your clients have changed.

SOPs that don’t evolve become obstacles instead of assets.

Set a monthly review. It takes 30 minutes. It’s the highest-leverage half hour in your month.

Mistake 5: Not Assigning Ownership

If nobody owns the SOP, nobody updates it.

Every SOP needs a single owner - the person responsible for keeping it accurate and current. In a small business, that’s usually the founder. As you grow, ownership can be distributed.

But someone’s name has to be on it.

From Processes to Systems Thinking

Individual SOPs are powerful.

But the real transformation happens when you stop thinking about individual processes and start thinking about how they connect to each other.

This is what separates a business that has a few SOPs from a business that runs on systems.

Gerber calls this “the franchise prototype” - building your business as if you were going to franchise it.

Warrillow calls it “building a business that can thrive without you.” Wickman calls it “documenting your core processes and getting everyone to follow them.”

They’re all describing the same shift: from a business that depends on individuals to a business that depends on systems.

From a business where knowledge lives in people’s heads to a business where knowledge lives in the system itself.

What Comes Next

If you’ve read this far, you understand the fundamentals.

You know what a system is and why it matters. You know what an SOP is and how to build one. You understand the lifecycle, the spectrum, the common mistakes, and the leap from individual processes to systems thinking.

This is the prerequisite knowledge for the Blur Framework.

The Blur Framework takes everything you’ve just learned and organises it into a layered operating system designed specifically for service businesses.

It gives you not just the building blocks - which are what we covered here - but the architecture for how those blocks fit together.

Four layers. Three external artifacts. A clear separation between doing the work and designing the system that does it. And a monthly cadence that keeps everything evolving.