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)Team Charter Expectation Mapping Alignment Mapping

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Facilitation Team Charter	Facilitation Expectation Mapping	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.	When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day.	When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.	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	Medium	Low	Medium
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	2-4 h	45-90 min	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	Team Charter, Working Norms, Role Notes	Expectation Map, Alignment Notes, Agreements	Alignment Map, Open Issues, Decision Questions
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	TeamAlignmentCollaboration	AlignmentStakeholdersTeam	AlignmentStakeholdersStrategyFacilitation

Add more methods