Operational Consulting
Operational consulting: structure, process, and decision rights
Operational consulting here is about how work actually moves through the business — the process as it runs, who is allowed to decide what, where work crosses between teams, and what keeps it reviewed once the engagement ends. The output is documented and handed over. Each scope is written and quoted before work starts.
What the scope covers
The process as it runs
A process described in a meeting and a process that runs day to day are rarely the same thing. The map is built from what the people doing the work describe, then checked against records in the systems you already use — timestamps, status fields, and the places work visibly waits.
Decision rights
Who can approve a discount, commit a delivery date, or change a scope. Written down, because the absence of that answer is what turns a two-day decision into a two-week one. The table names the decision, the owner, the inputs, and the escalation point.
Handoffs between teams
Sales to delivery, delivery to finance, marketing to sales. Each handoff has a trigger and a definition of complete; where those are missing, work is re-opened, re-explained, or quietly re-done. The scope names the trigger and what has to be true for the handoff to count.
The operating cadence
The standing reviews that hold the changes in place — what each reviews, who owns it, and what gets decided. A cadence without decisions is a status meeting with a new name.
The guide on why operational handoffs break covers what each boundary between teams has to define.
What a scope delivers
01 · Current state
A map of how work actually moves
The process as it runs rather than as it is described: where work enters, who touches it, where it waits, and where it comes back for rework. Built from conversations and from evidence in the systems you already use.
Deliverable: A current-state process map with the friction points marked.
02 · Structure
Structure and decision rights
Who decides what, at which level, and with which inputs. Written as a decision-rights table rather than an org chart, because the chart rarely says who is allowed to say yes.
Deliverable: A decision-rights table and role boundaries.
03 · Changes
A prioritised change list
The changes worth making, ordered by what they unblock and what they depend on, with the ones that are not worth the disruption stated as such.
Deliverable: A sequenced change list with owners.
04 · Cadence
The operating cadence
The standing meetings that keep the changes in place: what each one reviews, who owns it, and what gets decided rather than merely discussed.
Deliverable: A cadence calendar with an agenda per meeting.
How the work runs
01 · Discovery
Discovery
Interviews across functions, plus a read of the systems and documents that already exist. What people say the process is gets compared with what the records show.
02 · Map
Map
The process drawn end to end, including the informal steps that never appear on a slide.
03 · Design
Design
The target structure and flow agreed on paper, with decision rights and handoffs named.
04 · Prioritise
Prioritise
Changes sequenced so the first ones unblock the rest, and the ones that only move furniture are dropped.
05 · Implement
Implement alongside your team
Changes introduced with the people affected, including the awkward cases nobody documented.
06 · Handoff
Handoff
The maps, the decision rights, the change list, and the cadence handed over with an owner for each.
When operational consulting fits
A fit when
- Work depends on specific people rather than on a documented process.
- Decisions escalate further than they need to because no one is sure who owns them.
- Teams hand work to each other and it comes back for rework.
- The leadership team meets often and decides little.
Not the right scope when
- You need an operating leader in the role rather than a scoped redesign.
- The constraint is a system that genuinely cannot do the work — that is the integration scope.
- The organisation is mid-restructure and the reporting lines are not settled yet.
- You want a strategy document with no process change behind it.
Related operations scopes
Scope operational consulting
Describe where the work gets stuck
A first conversation is about the specific handoff, decision, or process that is causing friction. From that we can say whether this scope fits, and what it would include.
Operational consulting: common questions
What does operational consulting cover here?
Structure, decision rights, cross-team handoffs, process improvement, and the operating cadence. It is the work of making the business runnable without a person holding it together: what the process is, who decides, where work crosses between teams, and how progress gets reviewed.
How is this different from a fractional COO?
A fractional COO holds the operating role and carries accountability over time. This is a scoped engagement that designs and documents the operating model, then hands it over. Where the underlying need is ongoing operating leadership rather than a defined change, the fractional conversation comes first.
Do you need to interview everyone?
No. Discovery covers the roles that touch the process in question, plus whoever owns the outcome. Interviews are part of it, but the map is checked against system records and existing documents rather than built only from recollection.
What does it cost?
A scoped quote, given in writing before work starts. The figure depends on how many processes and functions are involved and whether documentation has to be created from nothing. No hourly rate or package price is published for this scope.
Will you tell us to change our tools?
Only where the tool is demonstrably the constraint. Most friction sits in the process and in unclear decision rights, and a new tool installed on top of those reproduces the same friction. Where a system change is genuinely the answer, it is stated as a recommendation with its cost and dependency, not bundled into the scope.
What happens after handoff?
The map, decision rights, change list, and cadence belong to you. Ongoing support is available as a separate monthly scope with an agreed cadence; it is not implied by this engagement and not priced into it.
Keep reading
Related resources
Metrics
How Many Sales Opportunities Do You Need? Pipeline Sizing Explained
Work backward from a revenue target to the deals, opportunities, and activity you actually need, with the arithmetic, the definitions, and the assumptions spelled out.
Read resourceProcess
How to Build a Repeatable B2B Sales Process
Define the stages every deal moves through, the exit criteria at each one, who owns it, and what to measure — with a worked example.
Read resourceOperations Leadership
What a Fractional COO Does and When to Hire One
What a fractional chief operating officer owns, the signals operations have outgrown the founder, and how the role differs from a consultant or a full-time hire.
Read resourceStart the Conversation
Bring us the opportunity, challenge, or next step. We'll start by understanding where you are, where you want to go, and what it will take to get there.