Lean ITSM: the biggest waste is the one nobody measures

Lean has a simple core idea: find the work that does not add value and remove it. Applied to manufacturing it gave us the famous seven wastes. Applied to IT service management it usually gets reduced to "fewer steps in the workflow," which is fine but misses the largest source of waste in most service desks.

That waste does not show up in a process diagram, because it lives in the gaps between systems.

The seven wastes, ITSM edition

The classic wastes translate cleanly into service management, and it is worth naming them because many teams will recognise themselves:

• Waiting. Tickets sitting in a queue for an approval that takes thirty seconds once someone finally looks.
• Motion. People moving between a portal, email, chat, and a knowledge base to handle one request.
• Overprocessing. Approval steps and mandatory fields that exist out of habit and add no safety.
• Defects. Tickets logged in the wrong category, missing information, bounced back and forth.
• Inventory. A backlog of stale tickets nobody will ever action, distorting every metric.
• Overproduction. Reports and dashboards no one reads, generated because the tool can.
• Transport. Handing a request from one team or system to the next, losing context each time.

A good lean exercise will attack all of these. Many of them turn out to be the same problem, though.

The waste nobody puts on the board

Waiting, motion, transport and defects mostly share one root cause: the request keeps moving between places. Every move is a chance to wait or to lose context.

Nobody measures this waste because it is invisible inside any single tool. The service platform looks efficient when you only look at the platform. The cost is paid in the space between it and Teams, Outlook and SharePoint, where work is carried across by hand. Call it the handover tax. In many organisations it is far bigger than the few seconds you save by deleting a workflow step.

Why classic ITSM creates this waste structurally

A traditional ITSM setup creates this waste by being a separate place, even when it is configured well. Once service management lives apart from where work happens, every request has to be carried in and out of it. You cannot configure the handover tax away, because it comes with that architecture.

You can lean out the workflow inside the tool all you like. The biggest waste is upstream of the tool, in the act of getting work to and from it.

Lean ITSM in practice: remove the distance

Lean ITSM comes down to removing distance more than trimming steps. The largest gains come from putting the platform where the work already is.

When service management runs inside Microsoft 365, many of the seven wastes shrink together. Motion drops because people do not move between tools, transport drops because the request is raised where it appeared, and defects drop because context is already attached instead of re-typed. Waiting drops because approvals happen in Teams, in the moment, and the handovers themselves go away.

A lean test you can run this week

You do not need a programme to see this. Pick ten recently resolved requests and trace each one honestly:

• How many separate tools did it pass through from first signal to resolution?
• How many times was the same information entered more than once?
• How much of the total elapsed time was spent waiting versus working?

Add up the moves and the re-entries. That number is your real waste, more than the count of workflow steps. Getting it close to zero is the work of lean ITSM, and one effective way is to stop making service management a place people have to travel to.

The bottom line

The seven wastes are a useful checklist, and most of them trace back to one root cause: work moving between separate systems. That movement is where the time and context go missing.

Put service management where the work already happens and waiting, motion, transport and defects drop together, because the handovers that caused them are gone.