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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration for DACI
Decision Making
DACI
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture 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.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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.
Complexitysame
LowLowLowLow
Timedifferent
45-90 min1-2 h30-60 min1-2 h
Participantsdifferent
3-103-82-103-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsInception Canvas, Risks, Goal List, Open QuestionsDACI Matrix, Decision Owner, Decision LogArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
AutonomyRolesTeam
AlignmentArchitectureCanvas
DecisionRolesGovernanceAlignment
CanvasArchitectureAlignmentWorkshop
Add more methods