Skip to content

VOOCS · Element 5 of 5

Systems: scale it.

What runs without a hero?

By Russ ReederUpdated October 2026

Systems is the fifth element of VOOCS, the execution framework Russ Reeder built. It answers: what runs without a hero? The test is the VOOCS diagnostic: if the person running this quit tomorrow, would it still work? If not, you do not have a system. You have a hero. The verb is scale it, because scale is what a system does once it works. (The March 2026 Forbes essay called this element Scale; it is Systems now.)

What breaks without systems

Russ Reeder's test for Systems, the fifth element of VOOCS, is whether the work survives the person who does it today. Without shared systems, every handoff depends on someone who remembers how it is supposed to work, and the company slows down whenever that person is out of the room.

Coordination breaks where definitions differ. When one team's "qualified lead" is another team's "marketing inquiry," handoffs fail. When "done" means different things to different departments, every cross-functional effort becomes a translation exercise.

Well-intentioned decentralization becomes chaos without a shared backbone. If coordination keeps breaking, you have a systems problem, and the fix is to align definitions first.

What to build

  • Definitions PlaybookThe minimum backbone the company runs on: shared definitions, metrics and processes, written down, with autonomy preserved everywhere else. The question is not whether to standardize. It is what the minimum is that teams must share to work together: usually what counts as a qualified lead, what "done" means, and how the core numbers are calculated.

How you know systems is working

In my experience, you know Systems is working when the knowledge lives in the system, not in someone's head. Teams hand work to each other without a translation step, because a qualified lead means the same thing on both sides. The business holds after any one person leaves the room. Heroes don't scale. Systems do.

What's the minimum we must standardize so teams can work together?

Where systems fits in VOOCS

VOOCS runs in order: Vision, Outcomes, Ownership, Cadence, Systems. The mantra is the same five verbs: define it, measure it, own it, close it, scale it. Start with the element where the pain is, fix it, then move to the next.

  1. 01VisionWhat are we doing, and what are we saying no to?
  2. 02OutcomesWhat does done look like, and how will we know?
  3. 03OwnershipWho owns it? One name, not a team.
  4. 04CadenceWhat rhythm forces closure?
  5. 05SystemsWhat runs without a hero?