View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Fault Isolation |  Facilitation Stakeholder Mapping |  Architecture Software Architecture Canvas |  Facilitation Consensus Workshop |
|---|---|---|---|---|
Purposedifferent | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-180 min | 60–90 min | 1-2 h | 1-3 h |
Participantsdifferent | 1-6 | 2-8 | 3-10 | 5-30 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Stakeholder Map, Engagement Plan, Risk Notes | Architecture Canvas, Goals, Constraints, Quality Attributes | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | TroubleshootingDiagnosisEngineering | StakeholdersAlignmentFacilitationChange | CanvasArchitectureAlignmentWorkshop | FacilitationConsensusWorkshopAlignment |