Glossary

The complete vocabulary of SYSTEMology.

A-players

Top-tier team members who thrive on clarity and high standards. SYSTEMology argues A-players actively prefer a systems-centred business because well-documented expectations let them stand out, whereas average performers are more comfortable when expectations are vague.

Attention (CCF stage)

The first stage of the Critical Client Flow — the systems by which prospective clients first become aware of your business (advertising, content, referrals, foot traffic). The dashboard metric is typically a count of impressions, visitors, or reach.

Business Dependency Score

SYSTEMology’s diagnostic tool for measuring how dependent a business is on its owner. A free assessment at systemology.com/tools/dependency-score.

Business systemisation

The practice of turning the way work gets done in a business into documented, repeatable systems — so the business runs on processes rather than on the personal knowledge of a few people. The four stages are Survival, Stationary, Scalable, and Saleable.

CCF Dashboard

A simple measurement document — typically a spreadsheet — that tracks one key metric for each stage of the Critical Client Flow (Attention, Enquiry, Sales, Money, Onboarding, Delivery, Repeat/referral). It’s the baseline used to start optimisation.

Complete business reliability

SYSTEMology’s end goal: a business where every critical outcome is delivered consistently regardless of who is on shift, on leave, or no longer with the company. Person-independent, system-dependent.

Critical Client Flow (CCF)

The 7–12 systems that move a customer from first awareness through to repeat purchase or referral. The CCF is documented first because it’s the smallest set of systems that, once captured, makes the business able to function without owner involvement. Download template: www.SYSTEMology.com/resources.

Delivery (CCF stage)

The fifth stage of the Critical Client Flow — the systems for delivering the product or service after the customer has paid. Often the largest cluster of systems in a service business.

Department head

A person responsible for overseeing one of the business’s departments (e.g. Finance, Sales, Operations). In SYSTEMology, department heads are usually the first people consulted when identifying critical systems for that department.

Departments, Responsibilities & Team Chart (DRTC)

A SYSTEMology template that maps every department, every key responsibility within it, and the team member who owns each one. Used in Stage 2 (Assign) to identify Knowledgeable Workers and surface single-person dependencies. Download template: www.SYSTEMology.com/resources.

Enquiry (CCF stage)

The second stage of the Critical Client Flow — the systems that turn attention into a qualified prospect (forms, calls, proposals, lead capture).

Four stages of business systemisation

SYSTEMology’s progression model: Survival (founder is the business), Stationary (predictable but owner-dependent), Scalable (systems run, owner is optional), Saleable (a third party could buy it and it would keep working). Most owners try to leap from Survival to Saleable; the model says you have to walk through each stage.

Knowledgeable worker

A team member who knows how to complete a particular task to a high standard. The KW isn’t asked to write the system — they’re recorded doing the work, and a Systems Champion turns the recording into documentation. The two-person job principle.

Leader

The visionary half of a business. Typically the founder. Strong on inspiration, strategic direction, fast decisions, and problem-framing — but often weak on follow-through and operational detail. Must be paired with a Manager.

Manager

The operational half of a business. Detail-oriented, completion-driven, expert at running the day-to-day. The Manager is the natural counterweight to the Leader and is the role most often missing in a Stage 1 (Survival) business.

Minimum Viable Systems (MVS)

The ~42 systems across six departments (Finance, HR, Sales, Marketing, Operations, Management) that move a business from Stationary to Scalable. The CCF gives you the first 7–12; the MVS rounds out the rest. The point is “just enough systems,” not exhaustive coverage.

Money (CCF stage)

The fourth stage of the Critical Client Flow — the systems for getting paid. The dashboard metric is usually average sale price.

Onboarding (CCF stage)

The fifth-into-sixth stage of the Critical Client Flow — the systems for transitioning a paying customer from “purchased” to “set up and ready to be served.” Often combined with Delivery on the dashboard.

Onboarding system (team)

The system for welcoming new team members into the business. SYSTEMology recommends this as one of the two HR systems (alongside the Recruitment system) that you should re-engineer rather than just capture as-is, because it sets the standard for “this is how we do things here.”

Problem personnel

Team members who actively resist systemisation — typically because they fear being replaceable, because they’ve been hiding workload, or because they’re long-tenured and dug in. SYSTEMology argues these need to be addressed in advance, not when the friction surfaces.

Problems list

A running list of system gaps and breakdowns, held in your project management software, reviewed at a regular meeting (usually monthly). Larger problems become the queue for new system development; smaller ones get patched in the moment.

Recruitment system

The four-phase system for hiring: (1) write and post the job ad, (2) shortlist + trial task + CV, (3) one-on-one interview, (4) hire. Like Onboarding, this is one of the two HR systems SYSTEMology recommends re-engineering rather than capturing as-is.

Repeat/referral (CCF stage)

The seventh stage of the Critical Client Flow — the systems for bringing customers back or generating referrals. The dashboard metric is usually retention rate, NPS, or number of referrals per customer.

Saleable (4th stage)

The fourth and final stage of business systemisation. A third party could buy the business, run it without you, and have it keep working. Even owners who never plan to sell aim for this stage because it’s the only state where the business is genuinely independent of the founder.

Sales (CCF stage)

The third stage of the Critical Client Flow — the systems that convert a qualified enquiry into a paying customer. The dashboard metric is conversion rate or number of sales made.

Scalable (3rd stage)

The third stage of business systemisation. Core systems are documented, the team follows them, and the business can grow without each new unit of growth requiring a proportional unit of owner time.

Seven stages of SYSTEMology

The methodology’s framework, applied in order: Define, Assign, Extract, Organise, Integrate, Scale, Optimise. Each stage builds on the previous; skipping ahead is the most common cause of failed systemisation efforts.

Single-person dependency

The condition where a critical business outcome can only be delivered by one specific person. The DRTC exposes these. The vacation test confirms them. The whole point of SYSTEMology is to remove them.

Standard Operating Procedure (SOP)

The traditional name for a documented work process. SYSTEMology generally uses “system” rather than SOP because the SFCS approach (recording the work, then transcribing) produces something more usable than the long, prose-heavy SOP documents most businesses end up with.

Stationary (2nd stage)

The second stage of business systemisation. The business is profitable and predictable, but its operations live in the founder’s head. Most small businesses that “made it” plateau here for years.

Survival (1st stage)

The first stage of business systemisation. The owner is the business — every customer outcome depends on them being there. Cash flow is irregular; time is the bottleneck.

System For Creating Systems (SFCS)

SYSTEMology’s meta-system for capturing how work gets done. The Knowledgeable Worker is recorded performing the task (screen recording, video, or audio); the Systems Champion turns the recording into documentation. The two-person split is the unlock — it removes the blank-page problem and the writing burden from the person who actually knows the work.

Systems champion

The person who owns the day-to-day momentum of systemisation. Detail-oriented, organised, and energised by clarity. Typically not the founder. The Systems Champion drives interviews, captures the work, produces documentation, and chases follow-through.

Systems-centred business

A business where the default question for any task is “is there a system for this?” and where the system, not the individual, is the source of truth. The opposite of a personality-driven business.

Systems management software

The single source of truth for documented systems — separate from project management software. SYSTEMology recommends one tool for “how to do the work” and another for “what work is being done right now.”

Systems-thinking culture

An environment where the team naturally looks for systems-based solutions when problems arise, rather than personal heroics or ad-hoc fixes. Built through repetition, recognition, and consistent meeting rhythms.

SYSTEMologist

A certified practitioner of the SYSTEMology methodology. Trained to walk a business through the seven stages as an external implementer or coach. See the SYSTEMologist Certification Academy.

Top-down approach

The recommended sequence for introducing systemisation to a team: partners first (with the business benefits), then department heads (with both perspectives), then frontline team members (with team-member benefits). Reduces resistance and prevents the rumour mill from getting ahead of you.

Trial task

A small piece of paid work given to shortlisted candidates during recruitment. Reveals more than a CV ever could about how someone thinks and how they handle real input. Standard practice in SYSTEMology’s Recruitment system.

Two-person job (creating systems)

The principle that creating systems requires two people: the Knowledgeable Worker (who knows how to do the task) and the Systems Champion (who documents it). Asking one person to both perform and document is the most common reason systemisation efforts stall.

Vacation test

The diagnostic for whether a business is genuinely systemised: send a key team member (or the owner) on a one-month vacation. Whatever breaks while they’re gone is what still depends on a person rather than a system. The opposite of theoretical — you can only fail it after the fact.