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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.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.
Complexitysame
LowLowLowLow
Timedifferent
45-90 min30 min Setup, dann laufend1-2 h45-90 min
Participantsdifferent
3-101-3 maintaining, briefing for everyone3-83-12
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsRAID Log, Status Report SourceInception Canvas, Risks, Goal List, Open QuestionsExpectation Map, Alignment Notes, Agreements
Tagsno overlap
AutonomyRolesTeam
RiskTrackingStakeholdersGovernance
AlignmentArchitectureCanvas
AlignmentStakeholdersTeam
Add more methods