View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Fault IsolationArchitecture Inception CanvasStakeholder MappingArchitecture Communication Canvas
| Criterion | ![]() Engineering Fault Isolation | ![]() Architecture Architecture Inception Canvas | ![]() Facilitation Stakeholder Mapping | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-180 min | 1-2 h | 60–90 min | 60-120 min |
Participantsdifferent | 1-6 | 3-8 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Inception Canvas, Risks, Goal List, Open Questions | Stakeholder Map, Engagement Plan, Risk Notes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | TroubleshootingDiagnosisEngineering | AlignmentArchitectureCanvas | StakeholdersAlignmentFacilitationChange | ArchitectureCommunicationStakeholdersCanvas |



