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:Context Map ARID (Active Reviews for Intermediate Designs)Balanced Scorecard Getting Things Done

Criterion	Domain Modeling Context Map	Architecture ARID (Active Reviews for Intermediate Designs)	Business Strategy Balanced Scorecard	Operations Getting Things Done
Purposedifferent	When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.	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.	Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures.	With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.
Complexitydifferent	Medium	Medium	High	Medium
Timedifferent	1-3 h	2–4 h review as a planning range; preparation and evaluation additional	Halber Tag bis mehrere Wochen	1-2 h Setup, laufend
Participantsdifferent	2-8	Designers, developers as users, and facilitation	4-12	1
Formatdifferent	Workshop + async	Workshop + async	Workshop + async	Async
Outputdifferent	Context Map, Integration Patterns, Boundary Notes	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Balanced Scorecard, Strategic Measures, Initiative Map	Action Lists, Project List, Review Routine
Tagsno overlap	Domain-Driven DesignBoundariesStrategy	ArchitectureEngineeringFeedbackValidationTasks	StrategyMetricsExecution	ProductivityPlanningTasksExecution

Add more methods