Plenty of businesses know what to do and still fail at doing it reliably. Operations is the discipline of turning intentions into consistent output — and a huge share of real-world consulting value is operational, not strategic. The good news: operational problems are unusually tractable once you can see the process.

The transformation model

At its simplest, operations is inputs → process → outputs: resources go in, a series of steps transforms them, value comes out. Drawing this for any business — even a service or a software team — immediately exposes where value is added and where it's merely consumed. Most operational improvement starts by making the invisible process visible.

Process mapping

A process map is just the steps something actually goes through, in order, including the waiting and the handoffs. The revelation is almost always the same: the waiting between steps dwarfs the working. An order that takes "two weeks" usually involves a few hours of actual work and thirteen days of sitting in someone's inbox. You can't fix what you can't see — and once a team sees the map, the wasteful steps become obvious to everyone, not just the consultant.

Bottlenecks — the theory of constraints

Every process has one step that limits the whole thing's throughput — the bottleneck. The crucial, counter-intuitive lesson: improving anything that isn't the bottleneck does almost nothing. Speeding up a step before the constraint just piles up work in front of it; speeding up a step after it just leaves that step idle. Find the single slowest constraint, relieve it, and the whole system speeds up — then a new bottleneck appears and you repeat. Teams routinely optimise the wrong step because it's the easy or visible one; your value is pointing at the actual constraint.

Lean thinking — eliminate waste

Lean (from manufacturing, now everywhere) defines value as what the customer would pay for, and treats everything else as waste to remove: overproduction, waiting, unnecessary motion, defects and rework, excess inventory, over-processing. The mindset that travels best: relentlessly ask "does this step add value the customer cares about, or is it here for our convenience/habit?" An astonishing amount of work in any organisation exists only because no one ever questioned it.

Measuring what matters — KPIs and OKRs

A KPI (Key Performance Indicator) is a number that tells you whether something important is on track. OKRs (Objectives and Key Results) are a goal-setting method: a qualitative Objective ("become the easiest tool to onboard") with a few measurable Key Results ("cut time-to-first-value from 20 minutes to 5"). The discipline in both is choosing the few measures that genuinely reflect health and resisting vanity metrics that look good but don't drive decisions. A measure you won't act on is noise. And beware: people optimise exactly what you measure, so a badly chosen metric reliably produces badly distorted behaviour.

Getting things done — project basics

Any project juggles the iron triangle: scope, time, and cost (with quality in the middle). You can fix at most two; the third must flex. "We want everything, by Friday, with no extra budget" is a request to break physics, and naming that trade-off honestly is part of the job. Prioritisation tools help — a simple impact-versus-effort grid (do the high-impact, low-effort things first) cuts through most "what should we tackle?" debates faster than any elaborate system.

Test yourself