Use this whenYou want to see where work actually waits, repeats, or gets lost before deciding where AI belongs.

Why it exists

A process diagram shows what is supposed to happen. Watching someone do the job shows where they wait, re-enter information, chase a decision, or work around the system. Companies that move information and decisions all day are factories too, with human and digital workers. Few of them have walked the floor.

The framework

  1. Step 1Choose a unitWhat is the one thing you will follow?
  2. Step 2Walk the stationsWho touches or transforms it?
  3. Step 3Spot the wasteWhere does it wait, repeat, or get lost?
  4. Step 4Change a handoffWhich handoff is worth changing first?
  1. Choose a unit

    What is the one thing you will follow?

    Pick one piece of information or one decision, such as a request, an approval, or a change. Follow it from the person who spots the need to the person who can resolve it.

  2. Walk the stations

    Who touches or transforms it?

    Every person, system, and inbox it passes through is a station. Watch the work where it happens, rather than asking people to describe it.

  3. Spot the waste

    Where does it wait, repeat, or get lost?

    Look for time spent waiting, data typed in again, work sent back, and effort that does nothing for the result. Inboxes and queues are inventory, and inventory is waste.

  4. Change a handoff

    Which handoff is worth changing first?

    Pick the handoff where the most waste collects, and make the smallest change that improves it. Then hand it to the data, process, people lenses.

How to use it

  1. Pick one unit of information and name where it starts and where it ends.
  2. Follow it with the people who handle it. Note every station.
  3. Mark the waste: waiting, re-keying, rework, over-processing, and anything piled up in a queue or an inbox.
  4. Ask at each station whether there is a real decision to make, or whether someone is only looking for information.
  5. Choose one handoff to change, and take it into data, process, people.

Where the waste hides

  • Waiting: the work is done, and nobody knows it is their turn.
  • Re-keying: the same information is typed into a second system.
  • Rework: a step sends it back because something upstream was missing.
  • Over-processing: a step adds effort nobody downstream uses.
  • Queues and inboxes: unfinished work piles up where nobody counts it.

What it looks like

Picture a construction team following one change request. It starts with someone on site who spots a problem. It passes through an email thread, a spreadsheet, a meeting, and a system where it gets recorded. Mapped this way, the team may find the context gets lost at the second handoff, and the meeting exists only because nobody can see the cost and schedule together. The fix may not involve AI at all. That is a good outcome.

Where it breaks down

A map is only as honest as the people who helped draw it. Watching the work is slower than interviewing, and some people will tidy up what they do when watched. Following one unit shows one path, so check that it is typical. And lean was built for plants, so don’t force the metaphor where it stops helping.

Try it with AI

I want to follow one piece of information through my business like a part through a plant.

Ask me one question at a time. First, what unit of information or decision should we follow, and where does it start and end? Then help me list each station (every person, system, and inbox it passes through) and mark the waste: waiting, re-keying, rework, over-processing, and queues or inboxes holding unfinished work.

At the end, name the one handoff worth changing first, and say whether that change needs AI at all.

Related