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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
MediumHighHighLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional2-4 h2-6 h15-30 min
Participantsdifferent
Designers, developers as users, and facilitation3-83-102-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsFuture Reality Tree, Negative Branches, Assumption List, Improved InjectionsEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
Theory of ConstraintsSystems thinkingChange
CausalityIncidentRoot causeTimeline
Root causeIncidentLeanProblem solving
Add more methods