Reference
Operations has its own jargon, and it shouldn’t be a barrier to getting help. Here are the terms used across this site — defined plainly, with no assumed knowledge.
A shared operating vocabulary is not a nicety. It is one of the cheapest improvements a leadership team can make. Most operating problems start as language problems — the same word meaning three different things to three people in the same room, so a decision that should take a minute takes a meeting, and accountability quietly dissolves. When everyone agrees what a metric is, who owns it, and what counts as good, a surprising number of recurring arguments simply stop.
These definitions exist for that reason. They are written to be used, not admired. Each is plain enough for someone in their first week to understand and precise enough that two people can hold a process to the same standard without relitigating the terms every time they meet. The same care that goes into a definition here is the care that goes into a real operating model: say exactly what you mean, once, in a place everyone can find.
Use the list below as a working reference. When a term turns up in a proposal, an operating review, or one of the case studies and the meaning is not obvious, look it up and adopt the definition as the shared one for your team. Where a concept deserves a fuller treatment, a link points to it. The short essays that follow go a level deeper on the ideas that matter most — the ones that decide whether an operation holds under scale.
Operating cadence: the heartbeat of a run business
Cadence is the regular rhythm in which leadership looks at the few metrics that matter, decides what to do, and closes the last cycle’s actions. Usually it is weekly. Without it, a company reviews its operation only when something breaks — which means it reviews too late, every time. A good cadence is short and disciplined, and it produces decisions rather than updates. It is also what makes measurement worth the effort: a metric that moves is only useful if there is a standing forum where someone is expected to act on it. Install the rhythm first, and most other operating improvements have somewhere to land.
Governance: the machinery that lets leadership steer
Governance is often mistaken for a status meeting. It is the opposite. Real operational governance is a system of thresholds, owners and escalation, so that when a number leaves its healthy range it is already clear who acts and what they are allowed to do. It turns reporting into action. Each metric that matters carries a defined range, a named owner, and a rule for what happens when it drifts. The payoff is a leadership team that spends its time deciding rather than discovering, and an operation that holds its standard without constant supervision. Governance is how a business steers itself instead of waiting to be steered.
Business Excellence versus one-off improvement
Improving a process once is straightforward. Keeping it good while a company doubles is the hard part, and it is what Business Excellence means. Quality control catches defects at a checkpoint; excellence redesigns the process so the class of defect stops recurring as volume rises and attention moves elsewhere. A business can pass every inspection and still degrade, because inspection alone never changes what produces the work. Excellence is the standard, the honest measurement against it, and the governance that holds the gain — the system that makes good outcomes survive new hires, busy quarters, and the moments when nobody is watching closely.
Lean Six Sigma as engineering tools
Lean and Six Sigma solve different problems, which is why they work best together. Lean strips out waste and waiting — the steps that add nothing and the queues where work sits idle. Six Sigma reduces variation, so the same input reliably produces the same output. A fast process that varies wildly is untrustworthy; a consistent process full of waste is slow. Together they make work both quick and dependable. The point is not to run a training programme or collect a belt. It is to prove an improvement with data rather than assert it — to measure the real process, change one thing, and show the gain held.
First pass yield: where hidden cost lives
First pass yield is the share of work that meets the standard the first time, with no rework. It is a truer measure than a final pass rate, which can look excellent while hiding enormous cost — because it counts work that passed only after being fixed once or twice. Every unit that fails first pass consumes capacity twice. That makes first pass yield one of the most useful numbers an operation can track: it ties quality directly to cost. And lifting it is almost always a design problem, not an effort problem. The work was usually set up to fail before anyone touched it.
Decision rights: ending the founder bottleneck
Decision rights define who may decide what, and at what threshold. When they are unclear, choices default upward — usually to the founder — and the company slows to the speed of one inbox. It is the most common reason a business cannot move without one person. The fix is rarely delegation in the abstract. It is writing down, for the decisions that actually recur, who owns each one, what limits apply, and when something must escalate. Done well, decisions move closer to the work, the founder is freed to lead rather than approve, and the team gains real authority instead of the appearance of it.
The full glossary
Every term used across the site, defined plainly and sorted alphabetically. Where a concept has a fuller treatment elsewhere, follow the link.
- Business Excellence
The system that keeps every process good as a company scales — a defined standard, honest measurement against it, and the governance that holds the gain. More than one-off process improvement.
- CAPA (Corrective & Preventive Action)
The disciplined response to a defect: fix the instance (corrective), then change the process so the whole class of defect stops recurring (preventive). The preventive half is what makes quality hold.
- Cycle time
How long a unit of work takes to move from start to finish — a campaign, an approval, an order. Long cycle times tie up cash and hide errors; compressing them is often the fastest operational win.
- Decision rights
Who is allowed to decide what, and at what threshold. Clear decision rights stop choices defaulting upward to the founder — the single most common cause of a business that can’t move without one person.
- Defect / failure mode
A defect is any output that breaches the standard. A failure mode is the way it happened. Systemic failure modes recur because the process invites them; designing them out is how you move quality.
- First Pass Yield (FPY)
The share of work that meets the standard the first time, without rework. A truer quality measure than a final pass rate, because it exposes the hidden cost of fixing things that should have been right.
- Fractional COO
An experienced chief operating officer who works with a company part-time instead of full-time — senior operating leadership, sized and priced for a company not yet ready for the full-time seat.
Read more- Governance (operations)
Not a status meeting — a system of thresholds, owners and escalation, so that when a metric moves it is clear who acts and what they may do. The machinery that lets a business steer itself.
Read more- Leading vs lagging indicators
A lagging indicator (last quarter’s revenue) reports a problem after it has cost you. A leading indicator moves earlier, while the problem is still cheap to fix. Good scorecards favour the leading kind.
- Lean Six Sigma
Two disciplines used together as engineering tools: Lean removes waste and waiting from a process; Six Sigma reduces variation and defects. Used to prove an improvement with data, not assert it.
- Makegoods
What an agency owes a client when delivery falls short of what was sold. At scale, undetected shortfalls become a steady, invisible loss — which is why staged QA to catch them early matters so much.
Read more- Operating cadence
The regular rhythm — usually weekly — in which leadership looks at the few metrics that matter, decides what to do, assigns it, and closes the previous cycle’s actions. The heartbeat of a run business.
- Operating diagnostic
A short, fixed-fee assessment that maps how an operation really runs — where decisions stall, where quality is exposed, and what to fix first. The usual low-commitment first step of an engagement.
Read more- Operating model
How a company is organised to do its work: who owns what, how decisions are made, how work flows, and how quality is held. Most scaling failures are operating-model failures, not effort failures.
- Process transformation
Re-engineering how work flows — measuring the real process, removing steps that only compensate for earlier failures, and proving the gain with data — rather than imposing a methodology on top of the mess.
Read more- Quality score
A measured, comparable percentage of work that meets an agreed standard. Useful only when it is honest and consistent — the last few points (95% to 99%) are a systems problem, not an effort problem.
- Root Cause Analysis (RCA)
Tracing a defect past the person who made it to the flaw in the process that allowed it. Good operations fix the system the RCA reveals, not the individual the incident names.
- Single source of truth
One definition per metric, in one place, produced the same way every time — so reporting reconciles and the leadership team steers by numbers it trusts instead of arguing with them.
- Standard work / SOP
The documented, agreed way a process is run, so a good outcome is repeatable rather than dependent on who happens to do it. The thing a transformation locks the gain into.
- Throughput
How much finished work an operation produces in a given time. Often capped not by team size but by how work moves through the system — which is why redesigning flow can multiply it.
Questions about the vocabulary
How to read these terms, and why the distinctions behind them matter in practice.
Most operating problems hide behind loose language. When the same word means three things to three people, decisions stall and accountability blurs. A shared vocabulary is the cheapest improvement available to a leadership team: agree what a metric is, who owns it, and what counts as good, and half the recurring arguments disappear. These definitions are written for that purpose. They are plain enough for a newcomer to use in the first week, and precise enough that two people can hold a process to the same standard without relitigating the terms each time they meet.
Quality control catches defects. Business Excellence stops the class of defect from recurring as a company scales. Control is a checkpoint; excellence is a system — a defined standard, honest measurement against it, and the governance that holds the gain when volume rises and attention moves on. The distinction matters in practice. A business can pass every inspection and still degrade, because inspection alone does not change the process that produces the work. Excellence redesigns the process so good outcomes survive growth, new hires, and the quarters when nobody is watching closely.
They solve different problems. Lean removes waste and waiting from a process — the steps that add no value and the queues where work sits idle. Six Sigma reduces variation and defects, so the same input produces the same output every time. Used alone, each is partial: a fast process that varies wildly is unreliable, and a consistent process full of waste is slow. Used together, they make a process both quick and dependable. On this site they are treated as engineering tools for proving a gain with data, not as a training programme or a belt to collect.
First pass yield is the share of work that meets the standard the first time, with no rework. A final pass rate can look excellent while hiding enormous cost, because it counts work that passed only after being fixed once, twice, or more. First pass yield exposes that hidden rework. It is one of the most useful numbers an operation can track, because it ties quality to cost directly: every unit that fails first pass consumes capacity twice. Lifting it is usually a process-design problem, not an effort problem — the work was set up to fail before anyone touched it.
Decision rights define who may decide what, and at what threshold. When they are unclear, choices default upward — usually to the founder — and the business slows to the speed of one inbox. This is the single most common cause of a company that cannot move without one person. Fixing it is rarely about delegation in the abstract. It is about writing down, for the decisions that actually recur, who owns them, what limits apply, and when something must escalate. Done well, decisions move closer to the work, the founder is freed to lead, and the team gains real authority rather than the appearance of it.
An operating cadence is the regular rhythm — usually weekly — in which leadership looks at the few metrics that matter, decides what to do, assigns it to an owner, and closes the previous cycle’s actions. It is the heartbeat of a run business. Without it, reviews happen when something breaks, which means they happen too late. A good cadence is short, disciplined, and produces decisions rather than updates. It is also the mechanism that makes leading indicators useful: a metric that moves is only valuable if there is a standing forum where someone is expected to act on it.
Governance here is not a status meeting. It is a system of thresholds, owners and escalation, so that when a metric moves it is already clear who acts and what they are allowed to do. It is the machinery that lets a business steer itself rather than wait for a leader to notice and intervene. Good operational governance turns reporting into action. Each metric that matters has a defined healthy range, a named owner, and a rule for what happens when it leaves that range. The result is a leadership team that spends its time deciding, not discovering — and an operation that holds its standard without constant supervision.
Use them as a working reference, not a textbook. When a term appears in a proposal, a review, or one of the case studies and the meaning is not obvious, look it up here and adopt the definition as the shared one for your team. The entries are deliberately short so they can settle an argument quickly. Where a term has a fuller treatment elsewhere on the site — the operating model, governance, the makegoods framework — a link points to it. The aim is a single, consistent vocabulary that a leadership team and an operating partner can both rely on without translation.
Recognise the problem behind the words? That’s what a first conversation is for.