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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.
Complexitydifferent
MediumLowHighLow
Timedifferent
1-2 h1-2 h1-6 Wochen1-2 h
Participantsdifferent
3-123-84-103-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsInception Canvas, Risks, Goal List, Open Questions8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
Systems thinkingTradeoffsLeadership
AlignmentArchitectureCanvas
QualityProblem solvingRoot cause
CanvasArchitectureAlignmentWorkshop
Add more methods