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 |  Delivery RAID Log |  Architecture Architecture Communication Canvas |  Architecture Architecture Inception 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-180 min | 30 min Setup, dann laufend | 60-120 min | 1-2 h |
Participantsdifferent | 1-6 | 1-3 maintaining, briefing for everyone | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | TroubleshootingDiagnosisEngineering | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | AlignmentArchitectureCanvas |