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:ARID (Active Reviews for Intermediate Designs)Force Field Analysis McKinsey 7S Alignment Mapping

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Decision Making Force Field Analysis	Business Strategy McKinsey 7S	Facilitation Alignment Mapping
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.	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.	McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.	When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent	Medium	Low	Medium	Medium
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	45-90 min	2-4 h	1-2 h
Participantsdifferent	Designers, developers as users, and facilitation	3-12	3-12	4-12
Formatdifferent	Workshop + async	Workshop	Workshop	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Force Field Map, Change Levers, Risk Notes	7S Assessment, Alignment Gaps, Change Actions	Alignment Map, Open Issues, Decision Questions
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	ChangeDecisionStrategy	OrganizationStrategyAlignmentChange	AlignmentStakeholdersStrategyFacilitation

Add more methods