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 Risk Storming.
Architecture
Risk Storming
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Purposedifferent
Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.
Complexitysame
LowLow
Timedifferent
60-90 min45-90 min
Participantssame
4-124-12
Formatsame
WorkshopWorkshop
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogStarfish Board, Practice Changes, Experiments
Tagsno overlap
RiskArchitectureWorkshopValidation
RetrospectiveImprovementExperimentsTeam
Add more methods

Often compared together

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

Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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