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:Wardley Mapping ARID (Active Reviews for Intermediate Designs)Leverage Points Force Field Analysis

Criterion	Systems Thinking Wardley Mapping	Architecture ARID (Active Reviews for Intermediate Designs)	Systems Thinking Leverage Points	Decision Making Force Field Analysis
Purposedifferent	Wardley Mapping makes visible where an offering stands today and where it can evolve. The method connects user need, value chain, and evolution stages into a strategic basis for platform, build, or buy decisions.	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.	Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.	In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.
Complexitydifferent	Medium	Medium	High	Low
Timedifferent	1-3 h	2–4 h review as a planning range; preparation and evaluation additional	Half day	45-90 min
Participantsdifferent	2-10	Designers, developers as users, and facilitation	3-12	3-12
Formatdifferent	Workshop + async	Workshop + async	Workshop	Workshop
Outputdifferent	Wardley Map, Strategic Options, Evolution Notes	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Leverage Map, Action Strategy	Force Field Map, Change Levers, Risk Notes
Tagsno overlap	StrategySystems thinkingDynamics	ArchitectureEngineeringFeedbackValidationTasks	Systems thinkingChangeStrategy	ChangeDecisionStrategy

Add more methods