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 for Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
Paper illustration of many question cards around one challenge
Facilitation
Question Burst
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.When a problem gets covered up too quickly with answers, Question Burst puts the better question at the center. The format opens the thinking space before the group commits to an interpretation.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
HighLowLow
Timedifferent
0.5-3 Tage15-30 min45-90 min
Participantsdifferent
5-152-84-12
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Rich Picture, Root Definitions, Conceptual Models, Change AgendaQuestion List, Reframed Challenge, Learning PromptsSailboat Board, Risks, Improvement Actions
Tagsno overlap
Soft systemsComplexitySensemakingSystems thinking
QuestionsReframingFacilitationSensemaking
RetrospectiveTeamImprovement
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of Team Cognitive Load Assessment with its method-specific working model.
Team Design
Team Cognitive Load Assessment
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective