methodatlas
Compare

View methods side by side.

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

Criterion
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Purposedifferent
When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.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.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.
Complexitydifferent
LowMediumHighMedium
Timedifferent
45-90 min1-3 h1-5 Tage1-3 h
Participantsdifferent
3-103-104-123-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsDomain Context Map, Boundary Notes, Ownership MapLogic Model, Change Objectives, Intervention Components, Evaluation PlanSystem Map, Dependencies, Leverage Points
Tagsno overlap
AutonomyRolesTeam
Domain-Driven DesignContextBoundaries
ChangeSystems thinkingCapability
Systems thinkingMappingBoundariesChange
Add more methods