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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation 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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min30 min Setup, dann laufend90-180 min45-90 min
Participantsdifferent
3-101-3 maintaining, briefing for everyone4-123-12
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsRAID Log, Status Report SourceDecision Rights Matrix, AgreementExpectation Map, Alignment Notes, Agreements
Tagsno overlap
AutonomyRolesTeam
RiskTrackingStakeholdersGovernance
DecisionGovernanceAlignmentResponsibility
AlignmentStakeholdersTeam
Add more methods