Operations Analysis

Everyone Is Busy and Nothing Is Moving

D
Author
DOMS Global LLP
Published
July 29, 2026
Read Time
6 min read
Everyone Is Busy and Nothing Is Moving

You walk through the office and everyone is working. Genuinely working — heads down, calls happening, messages flying. Nobody is idle.

And yet the thing you asked about two weeks ago is still not finished, and when you ask why, you get an answer that is completely reasonable and completely unsatisfying: they were waiting on someone.

The gap nobody owns

Here is what is happening, and it is not about effort.

Work in your business passes between people. A quote needs approval. A design needs sign-off. An order needs stock confirmed. Every one of those moments is a handover, and a handover is where work stops being anybody's problem.

While a task sits with a person, they own it. The moment they pass it on, they stop tracking it and the receiver has not started. It sits in the gap. Nobody is late, because nobody currently holds it.

Work does not usually get slow inside tasks. It gets slow between them, in the space where nobody has it.

Why asking makes people defensive

When you ask why something took three weeks, everyone can account for their part. The designer did their bit in a day. Operations turned it round in two. Nobody is lying.

The three weeks lives in the four days here and the six days there when it was in nobody's hands. Since no individual can see the whole path, the question sounds like an accusation of laziness — and they were not lazy, so they push back.

You are both right, and you are talking about different things.

Find it by timing the gaps, not the tasks

Take one job that felt slow. Draw the actual path it travelled — every person who touched it. Then write two timestamps against each step: when they received it, and when they passed it on.

The picture is usually stark. The work itself takes a fraction of the elapsed time. Most of the calendar is waiting.

Once you can see that, the conversation changes completely, because you are no longer asking people to work harder. You are asking how to stop things sitting still.

The fixes are unglamorous and they work

  • Name the receiver. Not "send it to operations" — to a person. Teams cannot be accountable; people can.
  • Say what complete looks like. Half the delay at a handover is the receiver waiting for information they need and did not get.
  • Make waiting visible. Anything untouched for a defined period surfaces automatically. Nobody has to remember to chase.
  • Cut one approval. Look at the approvals in the path and ask which one has ever changed an outcome. Usually at least one has not, and it is costing days every time.

What actually changes

The first thing you will notice is not speed. It is the tone. When the delay is visibly structural, people stop defending themselves and start pointing out where the process traps work — because it has been frustrating them far more than it has been frustrating you.

They have been living inside it. They just could not see the whole shape either.

If this is your business

You do not have a motivation problem or a talent problem. You have work sitting in gaps that nobody owns, and the people around you are trying hard inside a structure that keeps stopping them.

Fixing that is not a management crackdown. It is drawing the path, timing the waiting, and closing the gaps one at a time — and it usually takes weeks, not quarters.

Frequently asked questions

Why does work take so long when everyone is busy?

Because work usually slows between tasks rather than inside them. Every handover creates a gap where the sender has stopped tracking and the receiver has not started, so the task sits with nobody. No individual is late, because nobody currently holds it.

How do you find bottlenecks in a business process?

Take one job that felt slow, draw the actual path it travelled through every person who touched it, then record when each person received it and when they passed it on. The work itself usually takes a fraction of the elapsed time; most of the calendar is waiting.

Why do people get defensive when asked why work is slow?

Because each person can account for their own part accurately — and they are not lying. The delay lives in the days when the work was in nobody’s hands, which no individual can see. The question sounds like an accusation of laziness, so it gets resisted.

How do you speed up handovers between teams?

Name a person rather than a team as the receiver, define what "complete" looks like so the receiver is not waiting on missing information, make anything untouched for a set period surface automatically, and remove at least one approval that has never changed an outcome.

operational efficiencyworkflow bottlenecksteam productivityprocess improvementhandovers

Recognise any of this
in your business?

Most of what we write about started as a problem someone brought to us. If something here sounded familiar, a conversation costs nothing and usually makes the constraint obvious.