| Overproduction | Producing sooner or more than needed | - Conducting more research than is necessary, like 15 interviews when 8 would have sufficed
- Asking questions in research when the answers are already well known
- Generating excessive data or documentation that isn’t analyzed or used
|
| Waiting | Delays while expecting information, people, or goods | - Delays waiting for participant recruitment, stakeholder feedback, approvals, or decisions
- Delays waiting for concepts or prototypes to be research-ready
|
| Transportation | Unnecessary moves of data, documents, or people | - Unnecessary hand-offs
- Emailing reports back and forth
- Moving data between tools without added value
|
| Overprocessing | Providing more than what is required or valued | - Requiring multiple rounds of reviews or approvals of test plans and materials prior to research
- Creating pixel-perfect prototypes for usability testing, when lower fidelity would work just as well
- Creating long polished presentations when only an executive summary is needed
- Adding unnecessary analysis
|
| Inventory | Storing too much and carrying cost of maintaining stock | - Stockpiling un-analyzed data
- Maintaining a backlog of research findings beyond what can be synthesized or shared
- Holding onto archives of video footage beyond what is needed, used, or current
- Keeping all draft versions of a document, even after the work is finalized
|
| Motion | Too much movement or activity | - Inefficient or manual workflows, such manual data entry
- Creating new documents from scratch rather than using a template or leveraging existing work
- Duplicating efforts across teams
- Using too many different tools for the same job
|
| Defects | Error that results in failing to meet customer expectations | - Errors in research (flawed methodologies, biased sampling, incorrect data, unclear reporting) that require rework or lead to inaccurate or unreliable findings
|
|