How COOs Balance Standardization and Local Flexibility in Operations

Put parameters around the elements of your process that affect safety, cost and customer experience in what you deliver. Allow drivers and technicians to decide the sequencing of stops or changes to arrival notifications to the customer or even explanations for minor delays. What you should not allow them to negotiate are inspection requirements or photo evidence, before-and-after pictures. Remember that flexibility works best when the people involved know what lines can't be crossed. I believe all techs should run through the list of 12 things to verify prior to closing the ticket as standard operating procedure no matter where the customer lives. Not only will you be delivering the same experience to customers in Dallas, Fort Worth or anywhere else, but you'll also be empowering your employees to route efficiently, conform to local traffic laws and manage any other details.

A rule that helped us scale without losing coherence was to standardize the first and last mile while letting the middle flex. The first mile covers intake, clear definitions, and shared goals. The last mile covers reporting, accountability, and learning from results. These points stay consistent because they build alignment and trust.

The middle is where local teams can adjust the order of work, communication style, and daily execution to fit their needs. This approach works because most operational drift starts when teams begin or report differently. Once those areas are consistent, local changes become easier to manage. We believe strong organizations keep shared standards while giving people room to use good judgment.

A parent who moved a child between two of our sites asked why settling-in worked differently at each, and the honest answer was that it shouldn't. Fifteen years running a group of nine day nurseries, and the list of what's fixed runs to 19 items — safeguarding, medication, ratios, how an accident gets recorded, the words used when a child is collected by someone new. Everything else is the manager's. Standardise anything you'd have to produce for an inspector, and let sites keep whatever a parent would notice — menus, routines, how much of the day is outside. Drift shows up in the paperwork first, so the deputy reads a sample of records from every site each month rather than visiting. Doesn't work with a new manager; they want a prescription for the first year, and I give it. One site does snack at ten and has never once explained why.

Determination of whether to standardize or provide local flexibility in a decision-making environment is impacted by the degree of financial materiality and level of risk exposure. Centralized core financial activities (i.e., general ledger accounting, payroll processing and major capital expenditures) require strict adherence to centralized workflow processes. All other minor operational expenses/purchases may be processed at each site with minimal administrative overhead since no corporate approvals need to be obtained prior to making such purchases.

Our simple rule, which eliminated the potential for our process to become stagnant, was “The Dollar-Threshold Guardrail.” Any operational expense/vendor agreement which exceeds $1,000 must have centralized corporate approval via standardized purchase orders. Any expense less than $1,000 may be approved by the site manager utilizing pre-budgeted discretionary funds. The dollar amount threshold allows for local leadership to have operational flexibility on day-to-day needs while maintaining absolute fiscal discipline and centralized control.

Standardize the identifiers, adapt the voice. My two jewelry brands sell overlapping pieces, and the same item carried one code in the supplier's file, another in the listing, and a third in my own spreadsheet. Price updates landed on some listings and not others, and customers read it as typos. I mapped every internal SKU to its supplier code—about 1,130 rows—and one automation now pushes changes from that single list. What stays local is anything a customer hears; the two brands are written in deliberately different voices, and I never unified that. Drift starts wherever two systems have to agree and nobody said which one is right.

A useful test is to ask whether a process exists to preserve standards or to preserve comfort. Many teams standardize because variation feels messy, not because it damages outcomes. The processes that deserve consistency are the ones that protect clarity across the full growth chain. Shared goals, measurement logic, approval discipline, and feedback loops should remain stable because they connect visibility to revenue with real accountability. Local adaptation should happen closer to the market signal.

One rule we follow is that every local exception must teach the wider system something. If a team wants to adapt a workflow, the change needs a clear hypothesis, a time frame, and a way to compare results against the common baseline. That keeps flexibility productive instead of political. It also builds a culture where people are trusted to use judgment, while still respecting the operating system that makes scale possible.

My test is whether a mistake would be invisible until it became expensive. If it would, it gets standardised. If it would be obvious immediately, it can flex.

Across client accounts, that means the things nobody sees are fixed: how conversions are defined, how access is granted and removed, where backups sit, the checklist before anything goes live. Our list of things that never change runs to 13 checks and covers only that kind of work. Every one of them is on the list because a version of it once went wrong quietly and was found weeks later.

Everything a client experiences is allowed to vary: strategy, tone, which channels get priority, how often we meet, what the reporting emphasises. Standardising those produces an agency that gives everybody the same plan, which is a good way to be efficient and wrong.

The rule that prevents drift is to standardise the measurement rather than the method. Everybody defines a lead the same way and reports it in the same format, and then how they get there is theirs. Once the numbers are comparable, you can see whether a local variation is producing a better outcome or just a different one, and the conversation stops being about permission and becomes about evidence.

The failure mode to watch is a process that exists because somebody senior once had a bad experience. Those never get reviewed.

When implementing processes that span multiple sites for operational support, we assess how much of an influence each process has on internal employees versus how much it will have on outside organizations. Processes that affect external organizations (e.g., terms for paying vendors, documents needed for health regulatory bodies, communication to the general public) need to be fully consistent in order to protect our corporate image. We allow internal, administrative timing to vary by the needs of the local staff.

We use "External Consistency - Internal Flexibility" as a guideline when determining what level of consistency to implement. For example, we require identical external procedures for submitting invoices at every location so there is no confusion within accounts payable departments. However, we leave it to the discretion of the local manager as to how they choose to run their internal weekly meetings.

Standardize anything that produces evidence; let the local site decide how the work gets done.

Corrective action has to look identical everywhere. Same form, same fields, same severity definitions, same closure criteria. If two sites classify findings differently, you can't compare them, and your corporate view of risk becomes fiction. Same for document control and records retention. Those are the interfaces where drift destroys your ability to see anything.

What I let vary is method. A site with different equipment, a different workforce, or a different regulatory environment will need a different work instruction, and forcing one version on everybody produces a document nobody follows. California facilities have reporting obligations that don't exist in other states, so the local procedure has to differ.

The big test, though, is if the difference is visible to a customer or an auditor as an inconsistency, standardize it. If it's just how the work happens locally, leave it alone and audit the outcome instead of the method.

What prevents drift is that the standardized parts get audited against each other. I compare corrective action closure times across sites, and outliers tell me where a system is decorative. Local flexibility doesn't cause drift. Unmeasured local flexibility does.

Process standardization occurs when we monitor and measure process outputs instead of controlling each step in the process. Corporate-wide administrative processes exist only to ensure that variance does not impact cost management or create liability issues (i.e., facility purchase thresholds, IT security levels). Site managers are otherwise provided with flexibility to manage their sites' operations as they see fit.

The principle we use to keep our sites from drifting away from the defined process is "flexible operation within predetermined guardrails" (site managers have the ability to adjust how they operate so long as they meet corporate-wide performance metric requirements, e.g., review all invoices sent by vendors within 5 business days; stay within budget on monthly utilities). Sites failing to achieve a given performance metric for 2 consecutive months will revert back to the corporate-defined process until performance stabilizes.

Q&A

How COOs Balance Standardization and Local Flexibility in Operations

Q&A

How COOs Balance Standardization and Local Flexibility in Operations

Lock Safety Rules, Free Route Choices

Anchor Endpoints, Let Middle Flex

Fix Inspector Records, Entrust Nursery Routines

Set Dollar Caps for Discretionary Purchases

Unify Product Codes, Preserve Brand Voices

Require Evidence for Every Exception

Align Metrics, Vary Client Tactics

Protect External Consistency, Permit Internal Choice

Audit Proof, Tailor Facility Practice

Measure Outcomes, Enforce Performance Guardrails

Related records

Standing brief