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 for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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.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
MediumHighLowLow
Timedifferent
1-2 h2-6 h1-2 h1-2 h
Participantsdifferent
3-123-103-83-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsFMEA Table, Risk Priority, Mitigation ActionsInception Canvas, Risks, Goal List, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
Systems thinkingTradeoffsLeadership
RiskQualityOperationsRoot cause
AlignmentArchitectureCanvas
CanvasArchitectureAlignmentWorkshop
Add more methods