View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Waste Analysis |  Domain Modeling Domain Context Map |  Systems Thinking Evaporating Cloud |  Product Strategy Lean Canvas |
|---|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 45-120 min | 1-3 h | 60-120 min | 45-90 min |
Participantsdifferent | 2-8 | 3-10 | 2-8 | 1-6 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Domain Context Map, Boundary Notes, Ownership Map | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Lean Canvas, Core Assumptions, Experiment Backlog |
Tagsno overlap | WasteLeanProcess improvement | Domain-Driven DesignContextBoundaries | Theory of ConstraintsAssumptionsSystems thinking | StartupLeanAssumptionsBusiness model |