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 the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.
Complexitydifferent
MediumLowLowHigh
Timedifferent
1-3 h1-2 h30-60 min2-6 h
Participantsdifferent
5-303-102-83-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Consensus Clusters, Theme Titles, Priority AreasArchitecture Canvas, Goals, Constraints, Quality AttributesFishbone Diagram, Cause Categories, Investigation BacklogFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
FacilitationConsensusWorkshopAlignment
CanvasArchitectureAlignmentWorkshop
Root causeQualityOperations
RiskQualityOperationsRoot cause
Add more methods