Method guideFacilitation

Responsibility Poker

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityLow

Time45-90 min

Participants3-10

FormatWorkshop

MaturityEmerging

Plan Responsibility Poker

Prerequisite

What needs to be finished first

Complete firstWorking basis

Select 6–10 recurring outcomes and describe scope with a real example. Invite affected roles, not only available individuals.

Use a concrete case and observable outcome.

Complete firstResult

Clarify card meanings with one example. Vote privately for each outcome and discuss only after simultaneous reveal.

Choose privately and reveal simultaneously.

Preparation

What needs to be ready before start

Materials

List of concrete outcomes or activities, cards for outcome ownership, execution, consultation, and information, matrix, and timer.

People / roles

Facilitator · all affected roles · sponsor or decider for unresolved mandates · documentation owner

Pre-read

Select 6–10 recurring outcomes and describe scope with a real example. Invite affected roles, not only available individuals.

Time needed

60–90 minutes for 6–10 concrete outcomes; review after the first work cycle.

Setup

Clarify card meanings with one example. Vote privately for each outcome and discuss only after simultaneous reveal.

Core question

The one question this method answers

Who owns each concrete result, and where are participation or escalation needed?

Flow

Phases with goal, actions, output and pitfall

Responsibility Poker uses hidden role cards or equivalent simultaneous choices so participants reveal how they see responsibility. Differences are discussed and recorded in a visible assignment.

Responsibility matrix

Fictional example

Fictional example for one concrete work case.

Responsibility matrix
Case	Outcome	Accountability	Execution	Consultation and information
Example caseWho owns each concrete result, and where are participation or escalation needed?	Release approval	Product Owner	Engineering Lead runs the checklist	Security is consulted; Support is informed

1. Outcome
Example case
Release approval
2. Accountability
Example case
Product Owner
3. Execution
Example case
Engineering Lead runs the checklist
4. Consultation and information
Example case
Security is consulted; Support is informed

The example is fictional and must be adapted to mandate and context.

Reference source · original teaching example

1
Outcomes
Choose work areas
Goal
List of concrete outcomes: List concrete activities or outcomes with clear boundaries instead of abstract roles.
Inputs for this step
- Select 6–10 recurring outcomes and describe scope with a real example. Invite affected roles, not only available individuals.
Actions
- List concrete activities or outcomes with clear boundaries instead of abstract roles.
Output
List of concrete outcomes
List of concrete outcomes
Quality check
Is each item a concrete outcome or bounded activity?
Pitfall
Abstract roles such as Delivery are assigned without naming an outcome. Return to “Choose work areas” and repeat this method step: List concrete activities or outcomes with clear boundaries instead of abstract roles.
Timing: 10–20 minutes
2
Cards
Clarify meanings
Goal
Shared card meanings: Explain cards for ownership, execution, advice, and information.
Inputs for this step
- List of concrete outcomes
Actions
- Explain cards for ownership, execution, advice, and information.
Output
Shared card meanings
Shared card meanings
Quality check
Does everyone distinguish outcome ownership, execution, consultation, and information in the same way?
Pitfall
Cards are read as rank levels although they represent different kinds of contribution. Return to “Clarify meanings” and repeat this method step: Explain cards for ownership, execution, advice, and information.
Timing: 10–20 minutes
3
Reveal
Show views
Goal
Independent responsibility views: Choose simultaneously face down; make assignment and uncertainty visible.
Inputs for this step
- Shared card meanings
Actions
- Choose simultaneously face down; make assignment and uncertainty visible.
Output
Independent responsibility views
Independent responsibility views
Quality check
Did everyone choose independently before status or hierarchy shaped the discussion?
Pitfall
The highest-ranking person reveals first and everyone else follows. Return to “Show views” and repeat this method step: Choose simultaneously face down; make assignment and uncertainty visible.
Timing: 10–20 minutes
4
Dialogue
Examine differences
Goal
Resolved differences: Discuss differences using examples, dependencies, and decision scope.
Inputs for this step
- Independent responsibility views
Actions
- Discuss differences using examples, dependencies, and decision scope.
Output
Resolved differences
Resolved differences
Quality check
Were the widest differences tested against a real handoff or decision case?
Pitfall
The group votes quickly without examining the practical conflict behind the cards. Return to “Examine differences” and repeat this method step: Discuss differences using examples, dependencies, and decision scope.
Timing: 10–20 minutes
5
Assignment
Record responsibility
Goal
Published responsibility matrix: Document the current assignment, gaps, and review date.
Inputs for this step
- Resolved differences
Actions
- Document the current assignment, gaps, and review date.
Output
Published responsibility matrix
Published responsibility matrix
Quality check
Does each outcome have one clear accountable role plus visible executing and contributing roles?
Pitfall
Several roles are simultaneously accountable, or nobody owns the gap. Return to “Record responsibility” and repeat this method step: Document the current assignment, gaps, and review date.
Timing: 10–20 minutes

Artifact

What comes out at the end

Sketch: what the artifact looks like

Responsibility Poker · Erwartungen abgleichenFür konkrete Aufgaben Verantwortung schätzen, Unterschiede sichtbar machen und tragfähige Rollenabsprachen festhalten

Form

Responsibility matrix with outcome, accountable role, executing roles, contributing roles, unresolved mandate questions, and review date.

Versioning / ownership

Version the published responsibility matrix with date, owner, source state, and review date. Preserve earlier observations and append changes with their reason.

Tool alternatives

Responsibility cards for Accountable, Responsible, Consulted, and Informed
Matrix with concrete outcomes as rows and role assignments
Versioned repository for mandate questions and review

responsibility-poker-working-template.md

Plan the question, inputs, complete run, and review with clear ownership.

Responsibility Poker: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 60–90 minutes for 6–10 concrete outcomes; review after the first work cycle.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: List of concrete outcomes or activities, cards for outcome ownership, execution, consultation, and information, matrix, and timer.
Roles: Facilitator · all affected roles · sponsor or decider for unresolved mandates · documentation owner
Advance information: Select 6–10 recurring outcomes and describe scope with a real example. Invite affected roles, not only available individuals.
Overall time needed: 60–90 minutes for 6–10 concrete outcomes; review after the first work cycle.
Setup: Clarify card meanings with one example. Vote privately for each outcome and discuss only after simultaneous reveal.

Prepare for the work steps

Outcomes: Choose work areas

Select 6–10 recurring outcomes and describe scope with a real example. Invite affected roles, not only available individuals.

Cards: Clarify meanings

List of concrete outcomes

Reveal: Show views

Shared card meanings

Dialogue: Examine differences

Independent responsibility views

Assignment: Record responsibility

Resolved differences

Responsibility matrix

Case	Outcome	Accountability	Execution	Consultation and information
Example case

Example case: Who owns each concrete result, and where are participation or escalation needed?

Use one specifically bounded case per row.

Reference source · original teaching example

Outcomes: Choose work areas

Expected artifact: List of concrete outcomes

List of concrete outcomes

Entry:

...

Is each item a concrete outcome or bounded activity?

Cards: Clarify meanings

Expected artifact: Shared card meanings

Shared card meanings

Entry:

...

Does everyone distinguish outcome ownership, execution, consultation, and information in the same way?

Reveal: Show views

Expected artifact: Independent responsibility views

Independent responsibility views

Entry:

...

Did everyone choose independently before status or hierarchy shaped the discussion?

Dialogue: Examine differences

Expected artifact: Resolved differences

Resolved differences

Entry:

...

Were the widest differences tested against a real handoff or decision case?

Assignment: Record responsibility

Expected artifact: Published responsibility matrix

Published responsibility matrix

Entry:

...

Does each outcome have one clear accountable role plus visible executing and contributing roles?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/responsibility-poker/run-sheet

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

responsibility-poker-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Responsibility matrix

Guiding question: Who owns each concrete result, and where are participation or escalation needed?

Outcome	Accountability	Execution	Consultation and information
Release approval	Product Owner	Engineering Lead runs the checklist	Security is consulted; Support is informed

The example is fictional and must be adapted to mandate and context.

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Choose work areasAbstract roles such as Delivery are assigned without naming an outcome.View in phase
Clarify meaningsCards are read as rank levels although they represent different kinds of contribution.View in phase
Show viewsThe highest-ranking person reveals first and everyone else follows.View in phase
Examine differencesThe group votes quickly without examining the practical conflict behind the cards.View in phase
Record responsibilitySeveral roles are simultaneously accountable, or nobody owns the gap.View in phase

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Pause or return to the previous step when this check is not satisfied: Is each item a concrete outcome or bounded activity?

Pause or return to the previous step when this check is not satisfied: Does everyone distinguish outcome ownership, execution, consultation, and information in the same way?

Pause or return to the previous step when this check is not satisfied: Did everyone choose independently before status or hierarchy shaped the discussion?

Pause or return to the previous step when this check is not satisfied: Were the widest differences tested against a real handoff or decision case?

Pause or return to the previous step when this check is not satisfied: Does each outcome have one clear accountable role plus visible executing and contributing roles?

Where to go next?

Facilitation

Delegation Poker

Also clarifies the appropriate level of delegation for open gaps.

Agile

Working Agreements

Anchors the published responsibility matrix as a binding team rule.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods

Responsibility matrix

1. Outcome

2. Accountability

3. Execution

4. Consultation and information

Choose work areas

Clarify meanings

Show views

Examine differences

Record responsibility

responsibility-poker-working-template.md

Responsibility Poker: Worksheet

Question

Desired outcome

Scope

Preparation for this scope

Method setup

Prepare for the work steps

Outcomes: Choose work areas

Cards: Clarify meanings

Reveal: Show views

Dialogue: Examine differences

Assignment: Record responsibility

Responsibility matrix

Outcomes: Choose work areas

Cards: Clarify meanings

Reveal: Show views

Dialogue: Examine differences

Assignment: Record responsibility

Open questions and next steps

responsibility-poker-beispiel.md

Fictional teaching example: Responsibility matrix

Choose work areas

Clarify meanings

Show views

Examine differences

Record responsibility

Where to go next?

Finished the method guide?