methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
Paper illustration of a four-column Kanban board with limited ongoing work, a visible blocker and a review loop.
Engineering
Kanban
Purposedifferent
With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable.
Complexitydifferent
LowMediumHighMedium
Timedifferent
Ongoing30-90 min90-180 minOngoing
Participantsdifferent
1-201-63-82-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Visual Board, Status Indicators, Exception CuesDecision Tree, Option Map, Assumption ListCoD Table, Prioritization SequenceKanban board, WIP policies, Flow metrics
Tagsno overlap
SignalsOperationsVisual management
DecisionTreeOptions
PrioritizationDeliveryEconomicsDecision
FlowVisual managementDelivery
Add more methods