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 Responsibility Poker.
Facilitation
Responsibility Poker
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences.When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitysame
LowLowLowLow
Timedifferent
45-90 min45-90 min45-90 min30-60 min
Participantsdifferent
3-104-123-103-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Responsibility Map, Role Agreements, Open QuestionsStarfish Board, Practice Changes, ExperimentsDelegation Board, Decision Boundaries, Role AgreementsStart Stop Continue Board, Improvement Actions
Tags1 shared
RolesResponsibilityTeamFacilitation
RetrospectiveImprovementExperimentsTeam
AutonomyRolesTeam
RetrospectiveImprovementTeamReflection
Add more methods