Operational Excellence & OPEX Control
Take cost out without taking capability out. Most OPEX programmes cut the visible line and pay for it in the next quarter’s failures.
Cost programmes usually go after the visible line — headcount, a vendor rate, a travel budget — because those are the numbers a review meeting can see. The cost that actually accumulates is quieter than that. It is duplicated supervision nobody consolidated. It is the same fault paid for twice because the first repair was never verified. It is consumption reconciled against an invoice rather than against run-hours. It is an SOP describing a process the site stopped following three years ago, still being signed off monthly.
None of that shows up as a line item, so none of it survives a budget exercise. It shows up as a margin that will not improve however hard the operation works, and as a team that treats fire-fighting as normal because it always has been.
The other half of the problem is that improvements do not stick. An intervention lands, the numbers move, and eight months later the operation has quietly returned to where it started — because nobody owned the control after the consultant left, and no artefact existed to show it had lapsed.
How I work it
Map the process as it is actually run, not as documented. Reconcile cost to activity. Find the work being paid for twice and the supervision being paid for three times.
One accountable name against every control, a turnaround clock somebody answers for, SOPs rewritten to match the real work, and a review pack that fits on one page.
An adherence scorecard your own team runs monthly, a governance review in somebody’s calendar, and second-line managers capable of holding it.
Tools and frameworks
Placed against the stage each one serves, and against the artefact it leaves behind. A framework that produces no artefact is a word.
| Framework or instrument | Analyse | Act | Adhere | Artefact it produces |
|---|---|---|---|---|
| Process and workflow mapping, as-is | ● | ○ | – | As-is map with the duplicated steps marked |
| Root cause analysis — 5-why, fishbone | ● | ○ | ○ | RCA sheet per recurring loss, corrective owner named |
| Cost-to-activity reconciliation | ● | ● | ○ | Variance sheet; the outliers are the shortlist |
| Responsibility matrix over the control set | ○ | ● | ● | The matrix below, agreed and dated |
| SOP and HOTO redesign, versioned | – | ● | ● | SOP set with revision numbers and a handover that closes |
| Adherence scorecard and review cadence | – | ○ | ● | Monthly scorecard run by your team, not by me |
The responsibility matrix
The artefact the Act stage produces. “As found” is what a typical intake looks like — not a description of your operation.
| As found — typical intake | As governed — on exit | |||
|---|---|---|---|---|
| Control activity | Accountable | Evidence | Accountable | Evidence |
| Cost variance investigation | Nobody named | Monthly MIS, unexplained | Function head | Variance note per line above tolerance |
| Repeat-failure root cause | Nobody named | Ticket closed, cause blank | Operations head | RCA sheet on every third repeat |
| SOP currency and revision | Quality, nominally | Signed, unread | Process owner | Revision number and training register |
| Supervision layer justification | Historic | None | COO | Span-of-control sheet, reviewed annually |
| Monthly governance review | Held, not minuted | Slides | COO | Decisions log with owners and dates |
A scoped, paid diagnostic across cost, process, accountability and adherence — ending in a leakage register and a prioritised control list.
Your team runs the scorecard; I chair the review that checks it and challenge what has slipped.
What good looks like
The state a completed engagement leaves behind — the definition of done we agree at the start. Not a result already achieved.
| Area | What good looks like | How you would know |
|---|---|---|
| Cost | Every cost line above tolerance has an explanation written by the person accountable for it, not by finance. | Variance notes |
| Process | The documented process and the observed process are the same process. | Walk-through record |
| Repeat failures | The same failure does not reach a third occurrence without a documented cause and a corrective owner. | RCA sheets |
| Accountability | Every control has exactly one accountable name, and that person knows it. | Responsibility matrix |
| Adherence | The controls survive the quarter after I leave, because the review that checks them is scheduled. | Monthly review pack |
Every cost line above tolerance has an explanation written by the person accountable for it, not by finance.
The documented process and the observed process are the same process.
The same failure does not reach a third occurrence without a documented cause and a corrective owner.
Every control has exactly one accountable name, and that person knows it.
The controls survive the quarter after I leave, because the review that checks them is scheduled.
Thirty minutes, and you will know whether this is worth pursuing
A structured conversation about where your operation is losing money, not a sales call. Mon–Sat, 09:00–18:00 IST, on Google Meet, in English or Hindi. Nothing is required from you in advance.
Book an Operational DiagnosticThe diagnostic I run in the first week of an engagement: what to freeze, what to measure, and what to fix first — in that order, because doing them in any other order is how cost programmes get reversed.
↓ Download · PDF, 4 pp