Motion waste is unnecessary physical or cognitive movement during work. In software, it is attention spent searching for information, rebuilding context, or navigating systems instead of solving problems. Transport moves information between places; motion moves attention. section 2.4.3
Small interruptions—checking logs, asking who owns something, switching tools—add up and fragment focus. When artifacts omit intent, people must infer what happened, why, and with what result. This is a system design problem, not an individual productivity failure. section 2.4.3
Look for recurring effort that reveals motion waste:
- What questions do engineers repeatedly answer manually? section 2.4.3
- Where does expertise exist only in people's heads, and how much time goes to navigating instead of solving? section 2.4.3
Listing 2.3 Motion waste
log.info("Processing request");
log.info("Request complete");
These log messages record that a request started and completed, but omit its context and outcome. Finding meaning requires inference or asking someone who remembers. section 2.4.3
Treat motion as one diagnostic lens among the eight TIMWOODS wastes, not as a fixed label for every task. In AI-assisted code comparisons, it can appear as extra effort to reconstruct intent; weigh it alongside other waste and genuine reductions in effort. section 2.4 section 3.5
