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 for Fault Isolation.
Engineering
Fault Isolation
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.
Complexitydifferent
MediumLowMediumLow
Timedifferent
30-180 min30 min Setup, dann laufend90-180 min20-40 min initial, dann laufend
Participantsdifferent
1-61-3 maintaining, briefing for everyone4-123-15
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaRAID Log, Status Report SourceDecision Rights Matrix, AgreementROAM Board, Owner List
Tagsno overlap
TroubleshootingDiagnosisEngineering
RiskTrackingStakeholdersGovernance
DecisionGovernanceAlignmentResponsibility
RiskAgileTrackingAlignment
Add more methods