Operational Effectiveness Assessment
A clear read of how work actually flows from request to done - and where effort leaks between the steps.
Our operational effectiveness assessment tells you how work actually flows from request to done - not how the process map says it should. We look at six things: the flow of work end to end, the split between value demand and failure demand, cycle time against touch time, where decisions wait, how information moves across boundaries, and how fast the place learns. Then we give you the few places where effort leaks between the steps - what's already flowing well, what's stalling it, and what to work first.
Flow is easy to assume and hard to see from a dashboard, so we study the work where it happens - real jobs, from the moment they arrive to the moment they're done. That's what makes the findings usable, and where any improvement starts.
43% of executives name productivity their top priority for 2026 (McKinsey, State of Organizations 2026). The hard part is seeing where the day actually goes - which is what studying the flow of work gives you.
When an operational effectiveness assessment helps
An assessment earns its place when the same drag keeps showing up in the work and you need to see where it comes from:
The situation | How it helps |
|---|---|
Work takes far longer than the hands-on time in it | Shows where jobs sit waiting between steps, so you shorten the queue, not rush the people. |
The team is flat out, but throughput isn't moving | Measures how much of the load is failure demand - work that only exists because something didn't land first time. |
Everything needs a sign-off before it can move | Reads where decisions wait and who has to be in the room, so authority sits closer to the work. |
Jobs stall every time they cross a team boundary | Traces the handoffs and what gets lost in each one, so the flow holds across the seams. |
You're scaling, and the way work runs won't stretch | Gives you a clear read of how the operation flows now, before more volume makes the leaks expensive. |
Improvements are made, then the old way creeps back | Reads how the place learns - whether a fix sticks or quietly unwinds - and what would make the next one hold. |
What we look at
We study one thing above all: how work moves from the moment a request arrives to the moment it's done. We read that through six angles - the lenses we use to find where effort leaks between the steps rather than inside them:
- Flow of work end to end - how a job travels from request to done, and where it stops moving.
- Value demand and failure demand - how much incoming work is the job itself, versus work created because something didn't land first time.
- Cycle time and handoffs - the elapsed time a job takes against the touch time actually worked on it.
- Decision latency and autonomy - how long work waits for a call, and whether the person doing it can make one.
- Information flow across boundaries - whether what a step needs arrives with the work, or gets chased after it.
- Improvement metabolism - how quickly the operation spots a problem, fixes it, and makes the fix hold.
The six angles stay constant; how we read them, we shape around you - your work types, volumes, teams, systems and where delivery actually happens - so the picture fits your operation, not a template.
Why these six angles
We read flow rather than function because flow is where the time goes and where you can actually shift it. Most of the wait in a job isn't in the work - it's between the steps, in the queues and handoffs no single team owns. The six angles are how we find that space, because a job that spends a fortnight in the system and an afternoon being worked on is telling you something the org chart never will.
Value demand and failure demand is the master signal. Value demand is the work you exist to do; failure demand is work that only landed because a prior step didn't deliver - the chaser, the rework, the call to fix what should have worked. In service operations it is often a large share of the load, and it's usually invisible because it looks exactly like busy. Naming the split, on real incoming work, is where the biggest gains hide.
Cycle time against touch time reads the flow itself. Decision latency and point-of-work autonomy read why it waits - work sitting for a sign-off it didn't need. Information flow reads what each step arrives with, or has to chase. And improvement metabolism reads whether the operation can mend itself, because a place that learns fast leaks less over time. These six are our lens, refined across many operations, and deliberately about how work moves, not how it's drawn.
How it works
You can't read this off a process map or a dashboard - both show the work as designed, not as it runs. So we study the work where it happens, through more than one lens, so the findings hold up:
- We measure it - a demand analysis on real incoming work, separating value demand from failure demand, and a flow walk timing jobs end to end - elapsed time against touch time. We show you the spread across job types and teams, not just the average. The variation is usually where the story is.
- We watch, at the point of delivery - time spent where the work is actually done, following real jobs through the handoffs and queues, so we see what happens between the steps, not only within them.
- We listen - interviews across a cross-section - the leaders and the operational teams doing the work. We look at real, recent jobs: what actually happened, and where the flow stalled or doubled back.
- We make sense of it - drawing on years of operational-development work, we read the gap between the process as drawn and the work as run, and bring you where effort leaks between the steps.
The thinking behind the method
No single method captures a flow on its own, so we use several and cross-check them. A demand analysis tells you what work is arriving and why, but not how it then travels. A flow walk times the journey, but a dashboard average hides how differently one job type moves from another. Watching at the point of delivery shows what people actually do with a job, rather than what the system says happens to it. Used together, they triangulate: a finding has to show up in more than one before we treat it as real.
We separate value demand from failure demand on real incoming work rather than assuming the split, because failure demand hides in plain sight - it looks like a busy, productive team, when much of the load is work the system created for itself. Counting it on live requests is the difference between guessing at the leak and seeing it. The artefact we build from the flow walk is a map of exactly that: where effort leaks between the steps.
We interview the operational teams alongside the leaders, on purpose. The people running the work can see the queues and workarounds that never reach a report, and the gap between the view from the top and the view from the front line is frequently the most useful thing we find. And we show you the spread, not the average, because a flow isn't one number: the same operation can move one job type in hours and another for weeks.
What you get
A working session, not a report filed and forgotten. We walk you through:
- A clear picture of how work flows now - end to end, in practice.
- The parts already flowing well - not just where it stalls.
- The few places effort leaks between the steps, and why.
- The handful of changes that would free up the most flow.
Where two things are both true and in tension - "we want work to move faster" and "nothing ships until it's been signed off" - we show you both. That's usually where the useful conversation starts.
How we hand it back - and what happens next
The assessment ends in a working session, not a document dropped in your inbox. We take you through what we found in person, with the flow walk and the demand split in front of you, so it lands as something you understand and can use.
Some of the most useful findings come as pairs - two things both true and pulling against each other, like wanting speed while requiring a sign-off for every step. We name those tensions rather than smoothing them into one tidy message, because the tension is usually the thing worth working on.
From there it's your call. Sometimes the map is enough and you carry the improvement forward yourselves. Sometimes you want us alongside for the work that follows - a focused fix, or a fuller operational improvement programme. And if what you need turns out to be lighter than you feared, we'll say so.
Focused now, or continuous over time
This is a focused, one-off deep read of how your work flows right now. If what you want is the whole organisation tracked continuously - flow as one thread among eight - that's States of Vitality, our organisational-health platform. Different job: depth now, versus the wider picture over time.
Common questions
How is this different from a time-and-motion or efficiency study?
A time-and-motion study speeds up the steps; this reads whether the steps should be happening at all. We separate value demand from failure demand, and time the elapsed journey against the touch time, so you see the wait between steps - the queues and handoffs - not just the pace of the work inside them. That's where most of the time actually goes.
Who do you involve?
The leaders and the operational teams doing the work. We time real jobs and interview across levels, teams and job types, because the people running the flow can see the queues and workarounds that never reach a report - and the gap between the view from the top and the view from the front line is where the value is.
How long does it take?
It's usually weeks rather than months, but it depends on the size of your operation, how many work types you run, and how complex the flow is. We build each assessment around you, and agree the timeline when we scope it.
How much does it cost?
There's no standard price - we build each assessment around you, so the cost reflects the size of your operation, the scope, and the depth you need. We scope it with you and give you a clear figure before you commit.
Is it confidential?
Yes. Interviews are confidential, and we report in flows, patterns and groups - by job type, step and team - never in a way that identifies an individual or singles out a person's numbers.
Is this a Lean or process-improvement project?
No - the assessment reads where effort leaks first, before anyone changes a step. The improvement work is what may follow, and it lands better for starting from a clear read of how the work actually flows rather than a guess at where to cut.
Thinking about an operational effectiveness assessment?
Tell us what's prompting it and what you want to understand, and we'll say whether it's the right move.