On paper, and in practice
Take a piece of recurring work, such as a quote request, a supplier invoice or an inspection report.
Officially, it moves through four steps.
Illustrative example. Every process has its own version of this.
-
Received
Waiting for a missing detail
It arrives by email without one detail that nobody can work without. Someone asks for it. The answer comes back two days later, in a different thread.
Re: the details you asked for
A new thread, separate from the original request. -
Checked
Waiting for sign-off
It needs approval from the one person who can give it. They are out until Thursday, so it waits in their inbox, behind everything else.
Automatic reply: out of the office until Thursday
The one person who can approve it. -
Approved
Has it gone out?
The approval comes back by phone. The spreadsheet still says ‘checking’. Whether it has gone out depends on who you ask.
Status: checking
The spreadsheet everyone is meant to keep up to date. -
Sent
Until someone remembers
What happens next is not written down anywhere. It happens when someone remembers, often after the customer has had to chase.
Did anyone hear back on this?
A message to the team, some time later.
None of the four steps is the slow part. The work waits between them: for a missing detail, a sign-off, an answer, someone to remember.
So the useful place to start is the whole process, from the first request to the final output.