Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Systems Mapping ARID (Active Reviews for Intermediate Designs)Evaporating Cloud Intervention Mapping

Criterion	Systems Thinking Systems Mapping	Architecture ARID (Active Reviews for Intermediate Designs)	Systems Thinking Evaporating Cloud	Systems Thinking Intervention Mapping
Purposedifferent	Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.	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.	The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.	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.
Complexitydifferent	Medium	Medium	Medium	High
Timedifferent	1-3 h	2–4 h review as a planning range; preparation and evaluation additional	60-120 min	1-5 Tage
Participantsdifferent	3-12	Designers, developers as users, and facilitation	2-8	4-12
Formatdifferent	Workshop + async	Workshop + async	Workshop	Workshop + async
Outputdifferent	System Map, Dependencies, Leverage Points	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments	Logic Model, Change Objectives, Intervention Components, Evaluation Plan
Tagsno overlap	Systems thinkingMappingBoundariesChange	ArchitectureEngineeringFeedbackValidationTasks	Theory of ConstraintsAssumptionsSystems thinking	ChangeSystems thinkingCapability

Add more methods