Give Your Operator a Mandate, Not a To-Do List

Give Your Operator a Mandate, Not a To-Do List

A senior operator moves fast when you give them named decisions, usable spending authority, and a result they own. Give that same person a task list plus approval for every consequential move, and you have bought expensive hesitation. The problem is usually not the operator. It is the mandate.

THE REAL CONSTRAINT

Why does senior operating help stall after the hire?

It stalls because the owner has hired judgment but retained every meaningful decision. In the engagements we run, the fractional arrangements that produce results in the first ninety days share one document: a written mandate naming what the operator decides alone, what they spend without asking, and what outcome they answer for.

That document is not a job description. A job description lists activities. A mandate establishes authority, boundaries, and accountability. The distinction is the difference between asking someone to improve operations and authorizing them to change the operating system when the evidence says it is necessary.

A pattern we keep seeing is that micro-approval kills exactly the judgment you hired. The operator starts proposing instead of deciding. The founder becomes the queue. Momentum disappears into reasonable questions that should never have traveled upward.

Vista's Real-Constraint Lens is useful here. When a capable operator has been hired and the business still does not move, the constraint is commonly the mandate, not the person. More meetings, more status reports, and a better to-do list do not repair a missing transfer of decision rights.

THE FIVE PARTS

What belongs in a working operator mandate?

A working mandate has five parts: decision domains, spending authority, outcome KPIs, reporting cadence, and revocation terms. Each part removes a different kind of ambiguity. Together, they make it possible to tell whether the operator had room to act and whether the action improved the result.

Mandate part	What it settles	Example phrasing
Decision domains	Which recurring calls the operator makes independently	"You decide the operating changes within the agreed priorities."
Spending authority	What resources can be committed without a new approval	"You may spend from the agreed operating budget within your domains."
Outcome KPIs	What result the operator owns	"You are accountable for the agreed operating outcomes and their leading signals."
Reporting cadence	How the founder stays informed without becoming a bottleneck	"You report progress, risks, and decisions at the scheduled operating review."
Revocation terms	How authority changes when conditions materially change	"Authority changes only through an explicit update to this mandate."

The examples are intentionally plain. A mandate should be specific enough to guide a tense Tuesday afternoon, not so legalistic that everyone needs a meeting to understand what it means. Add the actual domains, budget boundaries, and outcomes that fit your business, but keep the language executable.

DECISION DOMAINS

Which decisions should the operator own alone?

Name recurring domains where speed and cross-functional judgment matter. Good domains are operational priorities, process changes, capacity allocation within an agreed plan, and the sequence of improvement work. The wording should separate decisions the operator owns from decisions the founder deliberately retains.

Avoid catch-all phrases such as "run the business." They create a flattering but fragile arrangement because both parties will fill the phrase with different assumptions. A mandate gains force from naming concrete categories, then naming the few reserved matters that genuinely require owner approval.

The test is simple: when a live issue arises, can the operator tell from the document whether it is theirs to decide? If the answer is no, they will either seek permission or take a bet on your tolerance. Neither is a reliable operating model.

There is also a subtle benefit to written domains. They protect the founder from casual re-entry. Without them, a founder can re-litigate a decision whenever anxiety rises, even after delegating it. With them, the conversation becomes whether the decision falls inside the domain or whether the mandate itself needs to change.

MONEY AND MEASURES

Why must spending authority and KPIs travel together?

Because an operator cannot be accountable for an outcome while lacking the ordinary means to influence it. Spending authority is not a blank check. It is a pre-agreed range that lets the operator make routine tradeoffs without converting every move into a founder approval request.

Tie the range to the decision domains and the operating plan. If the operator owns a process improvement but cannot authorize the modest resources needed to implement it, the founder still owns the real decision. If they can spend freely outside their domain, the mandate is loose in the wrong place.

Then define outcome KPIs, not a catalog of tasks. Tasks tell you whether someone stayed busy. Outcomes expose whether their choices made the system better. In the engagements we run, the mandate is also the accountability instrument: clear domains make misses attributable.

Use a small set of measures the operator can actually influence, paired with leading signals that reveal whether the work is moving before the final result is visible. Do not solve uncertainty by adding a dashboard full of distant metrics. The purpose is a clear operating conversation: this was yours to decide, this was the intended result, and here is what happened.

The authority-accountability rule. Never ask an operator to own an outcome without granting the decision rights and operating budget needed to influence it.

STAY INFORMED WITHOUT INTERFERING

What reporting cadence keeps the founder out of the queue?

Choose a regular, short operating review with a predictable agenda: outcomes, leading signals, decisions made, risks, and requests that fall outside the mandate. This preserves visibility without turning every normal decision into a meeting. The operator should report what matters, not perform constant reassurance.

The cadence matters because silence creates founder anxiety, and anxiety often reappears as micro-approval. A visible rhythm gives the owner confidence that important tradeoffs will surface. It also gives the operator a sanctioned place to ask for a boundary change rather than improvising one.

Separate information from permission. An operator can inform you about a decision after making it when it falls within the mandate. They seek a decision only when it crosses a reserved boundary. If every update sounds like a request for approval, you have recreated the bottleneck in a nicer format.

Put material surprises into the reporting rule as well. The operator should not hide a meaningful risk simply because it falls within their domain. Authority is not independence from context. It is the ability to act inside agreed boundaries while bringing the owner the information needed for truly owner-level choices.

REVOCATION WITHOUT DRAMA

How should authority change when the business changes?

Write revocation terms before there is a disagreement. State that authority changes through an explicit update to the mandate, what conditions trigger a review, and who makes the final call. This prevents authority from shrinking through side conversations and prevents an operator from treating an outdated mandate as permanent permission.

Revocation is not evidence that the relationship failed. A business can change priorities, face a new constraint, or learn that a domain needs a different boundary. The issue is whether the change is deliberate and legible. Quietly overriding decisions while leaving the old mandate in place creates confusion and weakens accountability.

Review the mandate at an agreed checkpoint and whenever the operating context materially changes. The review should ask three things: Are the domains still right? Is the budget enough for the outcomes? Are the outcomes still the outcomes the business needs? Those questions are cleaner than arguing about whether the operator is being sufficiently "proactive."

A CLEAN START

How do you install the mandate without slowing the first month?

Draft it together before the operator begins meaningful work. The founder should name the outcomes and reserved decisions. The operator should pressure-test the domains, the budget, and the reporting rhythm against the realities they expect to encounter. Where either person says "we will know it when we see it," add language.

Use the first operating review to test the document against actual decisions. Do not wait for a failure. If a decision surfaced that neither person could place, the mandate has already identified a gap. Tighten the wording and keep moving.

The objective is not to eliminate judgment from the relationship. It is to put judgment in the right place. The owner should spend attention on choices only they can make, while the senior operator makes the operating choices you hired them to make. If you need help structuring that handoff, book an advisory conversation around the constraint that is actually slowing the company.

For a fuller comparison of roles, read fractional COO versus full-time COO and alternatives to hiring a full-time COO or CFO. The title matters less than whether the mandate creates useful authority on day one.

COMMON QUESTIONS

Frequently asked questions

Is a mandate only for a fractional operator?

No. A mandate is useful for any senior operator whose value depends on independent judgment. Fractional roles make the need more visible because time is limited, but a full-time executive can be slowed by the same approval pattern. The document clarifies authority regardless of employment arrangement.

How specific should decision domains be?

They should be specific enough that a live decision can be placed without guesswork, yet broad enough to avoid rewriting the document for normal variations. Name recurring categories and reserved matters. If the operator repeatedly asks whether something is theirs, the domain language needs another pass.

Does discretionary spending remove financial controls?

No. It moves routine controls into an agreed boundary before the decision is needed. The mandate can specify a budget, eligible uses, and reporting expectations. Financial oversight remains intact, while ordinary operating moves no longer wait for a separate approval at the moment they matter.

What if the operator makes a bad decision inside the mandate?

Then evaluate the decision against the outcome, the information available, and the agreed authority. Clear domains make the miss attributable and therefore coachable. Do not respond by silently removing all authority. Decide whether the issue was judgment, context, or a mandate boundary that needs revision.

Can KPIs be changed after the operator starts?

Yes, when business priorities materially change, but change them explicitly and alongside the relevant decision rights. Holding someone to obsolete outcomes is as damaging as shifting authority without notice. The mandate should include a review path so both sides can make a clean, shared update.

What is the most common mandate failure?

The common failure is calling an activity list a mandate. "Improve operations" and "keep me posted" do not establish authority, resources, or accountability. A real mandate names decisions, spending, outcomes, reporting, and revocation. Anything less leaves the founder as the hidden operating bottleneck.