Systems, processes, and SOPs: what they are and how they connect

Executive overview

Most founders use the words "system", "process", and "SOP" interchangeably — and build nothing that sticks. Each operates at a distinct level of detail, from single-task recipes up to the big-picture architecture of a business.

SOPs handle individual tasks, processes connect tasks into outcomes, and systems show why those outcomes matter.

Standard operating procedures (SOPs)

• An SOP is a recipe for one task: one person, one sitting, one outcome.
• Good scope examples: offboarding a client, recording a video, sending an invoice.
• Bad scope examples: training a new hire (months-long), retaining a client (multi-system).
• If an SOP requires many people or many sittings, it belongs at the process level.

Processes

• A process is a sequence of tasks assembled into a coherent flow toward a specific result.
• Each step in a process can have its own SOP, owner, and due date.
• Processes typically influence weekly key metrics.
• Processes are not rigid folders — they behave more like roads: they can be broad or narrow.
• Example: YouTube content creation (scripting → filming → editing → publishing).

Systems

• A system zooms out further: it captures how multiple processes fit together, who owns them, what software is involved, and how everything ties to the business's overarching goals.
• Systems typically influence monthly or annual metrics — the numbers leadership is accountable for.
• Example: lead generation system (YouTube content + email content + opt-in funnels + more).
• Systems can scale in scope: lead generation → IP creation → revenue generation → wealth generation.

The three levels in practice

• SOPs answer how to do an activity.
• Processes answer what is happening, who is doing it, and when.
• Systems answer why it matters and how it feeds the big picture.