Systems thinking: the engine

Two agency owners each bill $500,000 per year.

Owner A works 70-hour weeks. Every client question goes through her. Every project requires her review. When she takes a vacation, things fall apart. She is exhausted and cannot grow.

Owner B works 30-hour weeks. She has documented every process. Her team handles 90% of client work without her. She spends her time on strategy and new business. She could double revenue without doubling her hours.

Same revenue. Completely different businesses.

The pattern: Most founders build businesses that depend on them. They are the smartest person in every room, the bottleneck in every process. This feels important but is actually a trap.

The opportunity: Systems thinking means designing your business as a machine that produces outcomes — not as a collection of tasks that require your constant attention.

Every business function can be described in three parts.

Inputs

What goes into the process:

• Raw materials or data
• Customer requests or leads
• Information from other departments
• Time and attention from staff

Process

What happens to the inputs:

• Steps performed in sequence
• Decisions made according to rules
• Transformations applied to materials or information

Output

What comes out:

• Finished products or services
• Completed tasks or deliverables
• Information for the next process

Why this model matters

When output is bad, the instinct is to blame people. But usually the problem is the process.

If ten different people make the same mistake, the process is broken. Fix the process, and the output improves — regardless of who is operating it.

This is the core insight of systems thinking: design for the average person, not the genius.

An SOP is a documented set of steps that produces a consistent result. It is the instruction manual for how work gets done.

What makes a good SOP

A good SOP is:

• Specific enough that someone new could follow it
• Simple enough to fit on one or two pages
• Updated when the process changes

Bad SOPs are vague ("ensure quality"), too long (20 pages nobody reads), or outdated (reflect how things were done two years ago).

How to create SOPs

1. Do the task while recording your screen or taking notes
2. Write each step as a simple instruction
3. Have someone else follow the instructions
4. Fix any steps where they got confused
5. Store it where people can find it

The best SOPs are created by capturing the actual work, not by imagining how it should be done.

The Loom Protocol

For tasks that are hard to write down, record a video of yourself doing it. A five-minute video often works better than a ten-page document.

"Never explain a task twice. Record it once and make that the training."

Scalability means the ability to handle more volume without proportionally more resources.

Non-scalable operations

If getting 10 more customers requires hiring 10 more people, you have a linear cost structure. Growth means more complexity, more management, more problems.

Scalable operations

If getting 10 more customers requires only slightly more resources — or none at all — you can grow profitably.

Scalability comes from:

• Automation replacing manual steps
• SOPs enabling faster training
• Systems that handle increased load
• Processes that work without founder involvement

The scalability question

Before making any operational decision, ask: "If we had 10x the volume, would this break?"

If yes, design a different approach now. It is easier to build scalable processes from the start than to redesign under pressure.

Every critical process needs a backup. Otherwise, a single failure can stop everything.

Single points of failure

Identify where one problem could break the business:

• The only person who knows the password
• The only supplier for a key component
• The only computer with important files

These are vulnerabilities waiting to happen.

Building redundancy

• Document knowledge so it is not trapped in one person's head
• Cross-train team members on critical tasks
• Keep backup equipment or supplier relationships ready
• Store files in multiple locations

Redundancy costs money and effort. Invest it in the most critical parts — the things that would hurt most if they failed.

A simple test for systems health: What would break if you disappeared for two weeks?

How to run the audit

1. List every task you do regularly
2. For each task, ask: "If I am not here, does someone know how to do this? Is it documented?"
3. The tasks with no backup are your vulnerabilities
4. Prioritize documenting or delegating those tasks

What the audit reveals

Most founders are surprised how much depends on them personally. The Ghost Audit makes this visible.

The goal is not to disappear — it is to have the option. A business that requires your constant presence is a prison, not an asset.

Systems thinking has limits. Not everything can be systematized.

Creative work

Highly creative tasks — strategy, design, innovation — resist standardization. You can systematize the environment and process around creative work, but not the creative act itself.

Early-stage chaos

When a business is new and changing rapidly, detailed SOPs become outdated before they are finished. In this phase, flexibility matters more than documentation.

Over-systematization

Too many rules can make people stop thinking. Rigid systems without judgment lead to poor customer experiences and inability to handle exceptions.

The goal is the right amount of structure — enough for consistency, not so much that it creates bureaucracy.