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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.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.
Complexitysame
HighHighHighHigh
Timedifferent
1-4 h1-6 WochenPreparation, scenario analysis, and findings review; effort depends on scope2-6 h
Participantsdifferent
3-84-10Architecture experts and stakeholders for scenarios and weighting3-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Challenge Findings, Risk Register, Mitigation Plan8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
RiskDecisionSensemaking
QualityProblem solvingRoot cause
ArchitectureChangeAnalysisComparisonQuality
RiskQualityOperationsRoot cause
Add more methods