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
Paper illustration of Double Diamond with its method-specific working model.
Innovation
Double Diamond
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
Wochen bis MonateAs needed30-60 min1-3 h
Participantsdifferent
3-124-153-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Problem Statement, Solution Options, Prototypes, Deliverables per PhaseIncident Log, Action Tracker, Stakeholder UpdatesStart Stop Continue Board, Improvement ActionsProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
ProcessDivergenceInnovation
IncidentOperationsReliability
RetrospectiveImprovementTeamReflection
ProcessOperationsImprovement
Add more methods