The Operating Model Glossary: 28 Terms Founders Hear From Consultants and Investors, Explained in Plain English

Consultants and investors speak a dialect of their own, and this operating model glossary translates it into the plain language of a 20 to 60 person services firm. Your operating model is how the business actually delivers what it sells, covering who decides what, how work flows, how often leaders meet and how performance is measured, and every term below describes one part of that machinery, with an example you will probably recognise from your own week.

How to use this operating model glossary

The terms are grouped by the question they answer, so that you can read a section before a board meeting rather than the whole list, and each entry gives a definition followed by an example from a fictional but familiar firm: a digital agency or IT consultancy of around 40 people, still led by its founder, which is growing faster than its habits.

Structure and decisions: who decides what

Operating model. Gartner IT Glossary calls it "the blueprint for how value will be created and delivered to target customers," the thing that brings the business model to life by executing it, while The Hackett Group Glossary adds that it explains roles and responsibilities, decision rights, performance measures, capabilities and the flow of information. Example: your business model says you sell managed services, and your operating model is how a ticket actually gets resolved, by whom, and who notices when it does not.

Business model. The broader logic of who you serve, what you sell and how you make money, of which Wikipedia describes the operating model as a subset focused on delivery. Example: deciding to move from projects to retainers is a business model change, whereas reorganising the team to service those retainers is an operating model change.

Decision rights. The agreed answer to who may make which decision, on their own or in a group. The UNITE Glossary notes that they are distinct from structure, since two organisations with the same org chart can perform very differently depending on whether authority sits at the front line or at the top. Example: your delivery lead has the title, yet every discount above a small amount still waits for the founder.

Governance. The formal arrangements through which decisions are made, checked and recorded. In the framework from Bain & Company (via The Uncertainty Project), governance often refers to decision rights tied to cross-functional decision-making, which in practice means which leaders belong to which decision-making body. Example: a monthly pricing panel of sales, delivery and finance replaces a hallway conversation with the founder.

RACI. A matrix naming who is Responsible, Accountable, Consulted and Informed for each task. Wikipedia's responsibility assignment matrix entry explains that Responsible people plan and complete the work, while the Accountable person is individually and ultimately responsible for its success or failure. Example: three engineers are Responsible for a migration, but the account manager is Accountable to the client.

Single point of accountability. The principle that each outcome has exactly one owner, which CIO.com reinforces in noting that several people can share Responsible status but only one truly owns and signs off the work. Example: when the client onboarding slips and three people each assume another owned it, there was no single point of accountability.

Span of control. The number of people who report directly to one manager. Example: when a founder has a dozen direct reports, every one of them gets a fraction of attention, which is usually the first structural strain a growing firm feels.

Delegated authority. A written statement of what a role may approve without asking, usually by type and size of decision. Example: your operations manager may approve contractor spend within an agreed limit, so that the founder sees only the exceptions.

Escalation path. The route a problem takes when it exceeds someone's authority, and the point at which it should stop. Example: a client complaint goes from engineer to service lead to director, and reaches the founder only when the relationship itself is at risk.

Rule of thumb: if a decision regularly waits for the founder even though someone else holds the title, the decision rights have not been delegated, whatever the org chart says.

Rhythm: how the business runs week to week

Operating cadence. The fixed rhythm of meetings and reviews through which the business is run, from weekly leadership meetings to quarterly planning. Example: a weekly leadership meeting with a set agenda replaces the founder chasing updates one by one.

Scorecard. A short set of numbers each leader owns and reports weekly, so that trends are visible before they become crises. Example: utilisation, overdue tickets and pipeline coverage on one page, each with a named owner.

KPI. A key performance indicator, meaning a measure chosen because it tells you whether the business is on track. Example: tracking project margin rather than headline revenue, because revenue can grow while every project loses money.

Leading and lagging indicators. Leading indicators predict what is coming, whereas lagging indicators report what has already happened. Example: a thin pipeline this month is leading, and next quarter's empty bench is lagging.

Operating rhythm owner. The person responsible for running the cadence itself, usually a COO or operations director rather than the founder. Example: the agenda goes out, actions are tracked and meetings end on time, because someone owns that rather than everyone assuming it.

Delivery and money: how the work pays

Utilisation. The share of a person's available time spent on billable client work. Example: a senior developer who spends half the week answering internal questions has low utilisation, which is a structural problem rather than a laziness one.

Bench. Billable people who are currently not on client work. Example: one lumpy quarter, where a large project ends before the next one starts, creates a bench that eats margin quietly.

Realisation. How much of the time you could bill you actually do bill and collect, after write-offs and discounts. Example: hours logged against a fixed-price project that overran are worked but not realised.

Gross margin. Revenue minus the direct cost of delivering it, chiefly the people doing the work. Example: two projects of the same size can carry very different gross margins because one was estimated well and the other was not.

Change control. The agreed process for pricing and approving work outside the original scope, and the defence against scope creep. Example: the client asks for an extra integration, and it goes through a written change request instead of a friendly yes on a call.

Run rate. Current performance projected forward over a year, usually revenue or cost. Example: a strong recent month annualised gives a flattering run rate, which is why investors ask how recurring it really is.

Recurring revenue. Income contracted to repeat, such as support agreements or retainers, as opposed to one-off project fees. Example: an MSP's monthly managed services contracts are recurring, while its hardware refresh projects are not.

Pipeline coverage. How much qualified opportunity you have relative to the revenue you need to win. Example: if the founder is the only person who can say what is really in the pipeline, coverage cannot be trusted.

Investment and exit: what investors are checking

Key person risk. The exposure the business carries if one individual leaves, falls ill or stops performing. Example: the one architect who understands your largest client's estate is a key person risk, and so, very often, is the founder.

Founder dependency. The specific key person risk created when clients, decisions or knowledge route through the founder. Example: the founder-as-routing-layer pattern, where nothing moves until the founder has seen it.

Value creation plan. The investor's plan for how the business will become more valuable during their ownership, covering growth, margin and operational change. Example: building your own value creation plan lets you shape the agenda rather than receive it.

100 day plan. The set of changes expected in the first months after investment, usually reporting, governance and leadership hires. Example: a monthly board pack and a finance lead appear soon after completion.

Due diligence. The buyer's or investor's investigation of the business before committing, covering finance, legal, commercial and operational matters. Example: the reference call you dread is part of it, and so is the question of who runs delivery when you are on holiday.

Investable. Describes a business whose results are stable, repeatable and not dependent on any one person, so that an outsider can underwrite them with confidence. Example: two firms with similar profits look very different to an investor if only one of them can show its numbers hold without the founder.

The word investable describes how the business runs, not how much it earns.

Common questions about operating model terms

What is the difference between an operating model and an org chart?

An org chart shows who reports to whom, whereas an operating model also covers decision rights, processes, cadence and performance measures. Two services firms can share an identical org chart yet run very differently, because in one the delivery lead genuinely decides and in the other every meaningful decision still waits for the founder, which an org chart cannot show.

Does a 30 person firm really need a RACI?

A 30 person services firm rarely needs a RACI for everything, but a RACI for the handful of processes that keep going wrong, such as onboarding, pricing approvals and escalations, is worth the hour it takes. The value of a RACI lies in forcing a single Accountable name onto each outcome, which is exactly where growing firms tend to blur.

Where Vitori fits

Knowing the vocabulary helps you follow the conversation, but it does not change how your business runs, and plenty of founders will do the work themselves or with another adviser, which is a perfectly sound choice. Vitori works inside leadership teams to design and embed operating models, using its Operational Scale Framework to assess Growth, Delivery and Operations and then implementing the changes until they hold. If that would help, you can get in touch with Vitori to talk through where your firm sits, with the aim of a business that runs, and scales, without the founder in every decision.

Published by

Vitori

Advisory, delivered

Chat to us →

← All insights