Updated October 20, 2026

Ask an owner where the time goes and they will name a step. Order entry. Quoting. Month-end. Almost always something a person sits down and does.

Then you watch the work move through the building, and the step turns out to be the short part. The order arrived Monday. It got entered Thursday. The typing took an hour; the job took three days.

The short answer

An operational efficiency consultant should start with the gaps between your steps, not the steps themselves. Most lost hours sit in waiting, handoffs, rework, and work that feeds nobody. Speeding up a step inside a bad flow produces almost nothing, because the step was never the constraint.

Why “efficiency” sends people to the wrong place

The word itself does the damage. Efficiency sounds like doing the same things faster, so that is what gets bought: a quicker tool, a better template, a person who is quicker at the task. The first lever again — add speed, add capacity, add someone.

But a step only matters if it is the constraint. In most small operations it is not. The constraint is the gap on either side of it, and gaps are invisible in a way steps are not — nobody is sitting at a desk being slow during a gap. Nobody is doing anything at all. That is exactly why it does not show up when you ask people what takes them so long.

The scale of it is not subtle. Asana’s Anatomy of Work Index found that roughly 60% of the working day goes to what it calls work about work — chasing status, duplicating effort, looking for information, coordinating — rather than the job someone was hired to do. One summary of the findings put it as “60% of the Workday Lost to ‘Work About Work.’”

If that is even roughly right for your business, then optimizing the 40% is the smaller half of the problem.

The four places the hours actually go

When we walk a process, we are not timing the steps. We are looking for these four, in this order.

1. Waiting

Work sitting between people. Nobody is touching it and the clock is running. Measure elapsed time, not work time — when the thing arrived versus when it was done. The difference is usually larger than anyone in the building expects, and it is the number that your customer actually experiences.

2. Handoffs

Every transfer between people is a chance to re-explain, re-enter, or drop it. Count how many pairs of hands a single piece of work passes through. If three people touch it and two of them retype something, you do not have a speed problem. You have a structure problem, and no tool fixes it.

3. Rework

Doing it twice because the first pass was wrong or incomplete. Rework is expensive in a way that hides from everyone, because it gets logged as the same task done again rather than as a defect. Ask what percentage of these come back, and ask what is usually missing when they do. The answer names the fix.

4. Work that feeds nobody

Output with no reader and no next step. The report, the summary, the field someone fills in because the form has it. This is the cheapest category to fix and the one nobody looks at, because it takes somebody saying out loud that a piece of work should stop existing.

Diagram of the four places operational hours are lost: waiting, handoffs, rework, and work that feeds nobody, each with a concrete example

Notice that only one of the four is fixed by going faster. The other three are fixed by changing the shape of the work, or by deleting it — which is why the first question is always whether the work should exist at all.

What this looked like in our own operation

We take orders from 27 retail stores. Each one sends its own spreadsheet, its own format, roughly 100 line items. Every SKU used to be re-typed by hand, about an hour per order.

An hour per order is a step. It is the number everybody quotes, and it is real. But the honest number was worse, because orders landed in an inbox and waited for somebody to have a clear block of time. The work took an hour. The order took days.

The obvious fix was to make the typing faster. The fix that worked was to remove the typing and the waiting together, and — this is the part that mattered — to change nothing on the stores’ side. We could have asked 27 businesses to submit orders in one standard format. That is the efficient-sounding answer, and it would have failed, because every one of those stores would have had to change how they work to solve a problem that was ours. Instead the system absorbs their formats exactly as they already send them.

It did not work the first time. The early version could not reliably tell two stores apart, because a store’s identity is not its name — it is the name plus its customer ID. Same chain, different locations, identical spelling. Until every line carried both, the output looked right and was wrong, which is the most expensive failure available: it creates rework in a process you just told everyone was fixed.

Twenty-seven hours a week became about ten minutes, with two manual steps left. The full build is written up here.

The cleaner example is category four. A distributor we know spent four months automating a weekly report. It worked perfectly. Nobody had opened that report in about a year. Four months of good engineering aimed at output with no reader — and every efficiency framework in the world would have scored that project as a success, because the step got faster.

How to judge the person you’re about to hire

Search for an operational efficiency consultant and nearly every result is a firm explaining how consultants improve efficiency. Almost none of them tell you how to decide whether you need one, or how to tell a good one from an expensive one. So here is the test.

In the first conversation, a good one asks about elapsed time, how many people touch the work, and what comes back wrong. A weak one asks what tools you are running and what your budget is. Tools are a late question. If they come up first, the answer was decided before anyone looked at your business — which is the same failure as quoting a build before counting the hours.

The other signal is whether they will tell you to stop doing something. Deleting work is the highest-return move available and the one nobody sells, because it is not a project. A consultant who never recommends elimination is a consultant whose incentives are pointed away from your cheapest win.

What to do Monday morning

Take the one process you would name if someone asked what is eating your week. Then, before hiring anybody:

  • Find the last ten of them. Write down when each one arrived and when it was finished. That gap is your real number.
  • Count the pairs of hands it passes through, and mark every point where information gets re-entered.
  • Ask who reads the output. If the answer takes more than a few seconds, you may have found category four.

An hour of that will tell you more than most discovery calls, and it will tell you whether the thing you were about to pay to speed up was the constraint at all.

Have us find the gaps for you

A Lever Audit walks your actual work end to end — elapsed time, handoffs, rework, and output nobody reads — and hands back a prioritized map of what to eliminate, what to keep human, what to document, and what is worth building, each with its numbers attached.

It takes a couple of conversations and enough access to see how work moves. It is $500, credited toward implementation if you decide to build something.

Book a Lever Audit

FAQ

What does an operational efficiency consultant actually do?

A good one maps how work actually moves — not how the org chart says it moves — and finds where it waits, gets handed off, comes back wrong, or produces something nobody uses. The recommendations come out of that map. If someone proposes a solution before they have walked a real job end to end, they are selling a template.

How do I know if we need one, or if we can do this ourselves?

Run the Monday-morning exercise above. If the elapsed time surprises you, there is real money in the gaps and it is worth bringing in help. If elapsed time is close to work time and the work is genuinely busy, you may just need more capacity — and no consultant can improve your way out of that.

Is operational efficiency the same as automation?

No, and conflating them is how money gets wasted. Automation makes a step run without a person. Efficiency work asks whether the step should exist, who it passes through, and why it waits. Automating a process with four handoffs just gives you a faster version of a bad shape.

How long does this kind of work take to pay off?

Elimination pays immediately — stopping work costs nothing and returns the hours that week. Removing a handoff usually takes days. Rebuilding a flow takes weeks to months. That ordering is also the right sequence: take the free wins before funding the expensive ones.

Our process isn't written down anywhere. Is that a problem?

It is normal, and it is usually the first piece of work. Rules living in one person’s head are both why the process cannot be improved and why the business cannot run without that person. Writing them down is valuable even if you change nothing else.