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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain.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.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.
Complexitydifferent
MediumHighHighMedium
Timedifferent
Ongoing1-5 TagePreparation, scenario analysis, and findings review; effort depends on scope2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-204-12Architecture experts and stakeholders for scenarios and weightingDesigners, developers as users, and facilitation
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsLogic Model, Change Objectives, Intervention Components, Evaluation 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 alternativesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
CollaborationEngineeringIncident
ChangeSystems thinkingCapability
ArchitectureChangeAnalysisComparisonQuality
ArchitectureEngineeringFeedbackValidationTasks
Add more methods