Operator Glossary

Terms we use across the practice, defined the way we mean them. Not the dictionary definitions; the operator definitions. Alphabetical.

Backlog. Work that has entered the system but not yet been completed, sitting at one or more stages. A growing backlog is the earliest sign that incoming work has outrun capacity. Tracked weekly; ignored, it becomes the reason a quarter slips.

Binding constraint. The single bottleneck that currently caps the output of the whole system. Fixing anything that is not the binding constraint produces no net improvement — the constraint still caps you. The entire Audit phase exists to find it. Almost nobody is constrained by what they think they are.

Boring fundamentals rule. Most operating gains, over the life of a business, come from a small number of unglamorous variables done consistently for years — clean handoffs, documented workflows, a weekly review, owned numbers. The interesting variables (new tools, clever tactics, exotic frameworks) account for single-digit-percent gains and are rounding error if the fundamentals aren't in place. The rule: spend ninety percent of attention on the fundamentals, ten percent on the interesting.

Cadence. The fixed rhythm at which reviews and check-ins happen — weekly, monthly, quarterly. Not a vibe; a contract written into the plan. The cadence is the system. A plan with no cadence is a document.

Change control. A defined step that scope or process changes must pass through before work starts, owned by a named person. The most-skipped element of most operations and one of the highest-leverage. A change-control step that gets written into the plan and bypassed is not change control; it is a doc nobody reads.

Cycle. A defined operating period with a single primary objective — usually thirty days. The cycle is the unit we actually plan against; the week is just a building block inside it.

Cycle time. How long a unit of work takes from entry to completion. The most useful single throughput signal a process gives you. Tracked across weeks, cycle-time drift is the earliest indicator that the process has fallen behind volume.

Exception. Any item that falls out of the standard path and has to be handled manually. A low, stable exception rate is healthy. A rising exception rate means the standard path no longer fits the work — the earliest sign of process drift.

Handoff. The point where work passes from one owner to the next. The most common place work silently stalls, because handoffs without an explicit "done" check and a named owner drop the ball under load. Most margin leaks live in an unowned handoff.

Instrumentation. The measurement layer that makes a business legible to its owner — the numbers, where they come from, and who pulls them. A business without instrumentation is run on vibes, and vibes have a short half-life.

Load balance. A comparison of incoming work (last 7 days) against capacity (trailing 28-day average). When incoming is higher, you are accumulating backlog. When capacity is higher, you are clearing it. Useful for timing pushes and catching overload before it becomes a crisis.

1% protocol. Internal shorthand for the principle that you cannot fix everything at once, and trying to is the most common reason engagements stall. Identify the single highest-leverage change for the coming week; ignore the other four candidates until that one ships and proves itself. Compounded across 52 weeks, 1% changes outperform attempts to fix everything in March.

Operating review. The quarterly review of the engagement. A re-run of the original Audit against current data, plus a defined KPI check. The point is to force the question "is this engagement still earning its keep" every 90 days rather than letting it drift.

Process debt. The slow accumulation of undocumented workarounds against operating load. Invisible week to week, obvious at the monthly view. Pays itself back in the form of margin erosion, dropped handoffs, and the loss of months of operating arc. The most common driver of long plateaus in operators who think they have a strategy problem.

Process drift. The slow gap between what a workflow says you should be doing and what you are actually doing. Missed steps get improvised. Improvisations become habits. By week ten, the process in the document and the process in your operation are different processes. Caught early with the weekly review; ignored, it ends cycles.

Queue depth. How much work is waiting at the slowest stage. The variable that determines whether the plan is conservative enough. A deep queue three days running signals capacity has to absorb both new work and backlog.

Throughput. Total work completed across a day, week, or cycle. The most common output metric. Tracks against the prescribed plan week by week; deviation flags either a capacity problem or an adherence problem.

Weekly review. The weekly 30-minute appointment with yourself to roll up the week's numbers, ask one honest question, and make one change. The smallest viable feedback loop; arguably the highest-ROI 30 minutes in any operator's week.

Wind-down protocol. The fixed end-of-week sequence run as a system rather than a vibe — the review, the one change logged, the next week's priorities set, the inbox closed. The unglamorous mechanical cousin of "staying on top of things." Skipped because it sounds boring; effective because it works.