liveBook · Manning

Eight wastes

As explained in Build High Value Software Systems

The eight Lean categories of waste—transport, inventory, motion, waiting, overproduction, overprocessing, defects, and unused skills—remembered by the mnemonic TIMWOODS.

The eight wastes, remembered as TIMWOODS, are recurring patterns where effort fails to translate into outcomes. In software, they apply to information, decisions, and attention as well as work such as pull requests, tests, and reviews. section 2.4 section 2.7

TIMWOODS names eight categories:

Use the categories as a diagnostic lens, not a checklist. One pull request may contain several wastes; the point is to spot system-created friction, not blame individuals. Work can look productive while effort quietly accumulates without improving outcomes. section 2.4 section 2.7

Look at the work as it happens

A pull request, ticket, refactor, test, review, or operational task may combine value-creating changes, necessary safeguards, and avoidable friction. Examine the work in context before deciding what is waste. section 2.4

Figure 2.4 TIMWOODS for software developers.

A visual map pairs TIMWOODS categories with examples from day-to-day software development. section 2.4

How Build High Value Software Systems covers it

How deep it goes
Names all eight categories and frames their role, but does not detail each category in the available treatment.
Examples
Uses pull requests, tickets, refactors, tests, reviews, operational tasks, and an Order History request as software-work contexts.
What you can do after
Evaluate/understand where effort disconnects from outcomes and recognize waste as system friction rather than personal failure.
How it connects
Connects waste to value, outcomes, Gemba, and Kaizen.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.