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 a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.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
MediumLowHighLow
Timedifferent
1-2 h30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope45-90 min
Participantsdifferent
3-123-12Evaluation team, architects, and relevant stakeholders4-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsStart Stop Continue Board, Improvement ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsSailboat Board, Risks, Improvement Actions
Tagsno overlap
Systems thinkingTradeoffsLeadership
RetrospectiveImprovementTeamReflection
ArchitectureQualityRiskTradeoffsStakeholders
RetrospectiveTeamImprovement
Add more methods