How to build systems so good, your business runs itself
Ross Harkness · 11:26 · systems ≠ automations; ownership is the missing piece · watch
From someone who systematized 6/7/8-figure founders’ ops. Core distinction up front: AI, automations, even SOPs are not systems — they can be parts of one.
What a system actually is
A system = things working together to achieve an outcome, with four components:
- Input (e.g. lead booked a call)
- Processes (reminder sequences, the call, the script)
- Output (a sale)
- Feedback loop (data: calls booked → showed → bought → feed improvements back)
Without all four you’re driving blindfolded — nothing tells you what matters or what to fix.
The failure mode he kept seeing
He ran a ghostwriting agency drowning in rewrites and missed deadlines, built all the systems… and still did everything, micromanaged everything. Diagnosis: he built the systems but still owned them. Everything routed back to him — like building your own freedom machine and never switching it on. Missing component: assigned ownership.
Mapping exercise (Canva whiteboard or anywhere)
- List major functions — every business has core four: marketing (generate leads), sales (leads→customers), operations (deliver product/service), finance (cash flow & profitability). Bigger ones add HR/IT.
- List every task in the business; write each task’s goal. Watch for misaligned goals — content isn’t for followers, it’s for leads.
- Cluster tasks under the function whose goal matches.
- Order tasks logically within each function (reminder emails precede the sales call).
The fix: named ownership
- Every process and every system gets exactly one person responsible — name beside it on the map, yours included. What’s under your name = your delegation shopping list.
- Managers own whole systems; team members own processes within them.
- Everyone/Somebody/Anybody/Nobody parable makes the rule obvious: shared responsibility = nobody does it (or you do).
- One person CAN hold multiple responsibilities; but one thing never has two owners.
- Nuance: owning ≠ only-doing. Person A can cover emails while copywriter B is away, but B stays accountable for it getting done, the data, and improving the process — like owning a business ≠ doing everything in it.
Making it stick
- SOPs preserve standards without supervision: document step-by-step per task; direct the team to consult the SOP first, manager second; fold every answered question back into the SOP permanently. (He offers a client SOP-generating AI tool via description link.)
- The snowball method: list your remaining owned tasks smallest→largest; delegate in that order. Each small handoff frees time to tackle the next bigger one — compounding.
- On every handoff: update the map, then walk the person through the map + their role + the SOP. Showing people why their node matters (“the next step can’t run without yours”) produces meaning → effort. Don’t underestimate that effect.
Definition of done: every daily-run task has an owner who isn’t you. 20 daily tasks? Get 20 off your plate — the business runs itself.