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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
LowLowLowMedium
Timedifferent
45-90 min30 min Setup, dann laufend1-2 h60-120 min
Participantsdifferent
3-101-3 maintaining, briefing for everyone3-82-8
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsRAID Log, Status Report SourceInception Canvas, Risks, Goal List, Open QuestionsCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
AutonomyRolesTeam
RiskTrackingStakeholdersGovernance
AlignmentArchitectureCanvas
ArchitectureCommunicationStakeholdersCanvas
Add more methods