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 Pareto Analysis
Decision Making
Pareto Analysis
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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.
Complexitydifferent
LowLowMediumHigh
Timedifferent
30-60 min30 min Setup, dann laufend1-3 Tage2-6 h
Participantsdifferent
1-61-3 maintaining, briefing for everyone1-43-10
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Pareto Chart, Top Causes, Focus ListRAID Log, Status Report SourceArchitecture Views, Cross-view Notes, RationaleFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
PrioritizationQualityFocusRoot cause
RiskTrackingStakeholdersGovernance
DocumentationStakeholdersArchitecture
RiskQualityOperationsRoot cause
Add more methods