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
How Might We
Innovation
How Might We
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Purposedifferent
With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction.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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.
Complexitydifferent
LowLowHigh
Timedifferent
30–45 min45-90 minHalber Tag
Participantsdifferent
1-103-105-20
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsDelegation Board, Decision Boundaries, Role AgreementsSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
FramingOpportunityIdeationQuestions
AutonomyRolesTeam
ResilienceOperationsIncident
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
Paper illustration for Responsibility Poker.
Facilitation
Responsibility Poker