Gemba walks usually teach one skill: spotting waste. The waste log and the "what did you find today" conversation both point back to muda.
That's a third of the picture. Toyota names three separate enemies: waste, unevenness, overburden. Chase only one and the gains disappear within a year.
The three enemies of flow
Muda is waste: any activity that burns time or resources without adding something a customer would pay for. Seven types show up again and again: overproduction, inventory, defects, motion, processing, waiting, and transport.
Mura is unevenness: swings in demand, in schedules, in the method used from one shift to the next, and in the quality that comes out the other end. A warehouse that ships 200 orders on Monday and 40 on Wednesday has a mura problem, whether or not anyone on the floor uses that word.
Muri is overburden: pushing a person or a machine past what it can reasonably hold. Cut headcount on a line without fixing the demand swings behind it, and the people left behind absorb the difference, usually through overtime and shortcuts.
Why the order matters
Improvement programs go straight for muda first. Waste is visible, it's satisfying to remove, it photographs well for a report, and finding it doesn't require asking an uncomfortable question about workload.
The problem: waste removed without fixing the unevenness behind it comes right back. Level the demand first. Then make sure no person or machine is running past capacity. Only after that does waste hunting hold.
Skip that order and you get a familiar pattern. A team clears a stockpile of parts sitting in front of a machine. Two weeks later the stockpile is back, because the demand swing that made it necessary never went away.
Mura feeds Muri. Muri feeds Muda. Fix them backwards and the fix doesn't last.
What this looks like on a walk
A muda log tells you what broke. It rarely tells you why it keeps breaking.
When an issue repeats in the same spot, ask two questions before you tag it as waste and move on: does demand swing in this area from day to day, and is anyone here working past a sustainable pace to keep up. Half the "waste" you find traces back to one of the other two enemies.
Take that stockpile example again. Log it as inventory waste and you'll clear it once. Ask why the swing exists and you might fix it for good.
Where Gemba Walk AI fits
The Muda Tracker in Gemba Walk AI tags every issue by waste type as your team logs it, so patterns across walks show up. Twenty motion-waste flags in the same aisle over a month is a different finding than one flag on one bad day, and the tracker is what makes that visible.
Spotting whether mura or muri sits behind a given flag still takes a question from whoever's running the walk. The tracker's job is narrower: keep the pattern from disappearing into a stack of old reports before anyone gets around to asking that question.
Run your next walk looking for all three. Waste is only the most visible one.