Delegation Poker
Delegation Poker is a card game in which a team and its manager set who decides in each decision area. Each player holds seven cards. They run from level 1 to level 7. At level 1 the manager announces a decision. At level 7 the team decides without the manager needing to know about it. For each area the players choose a card in secret and turn their cards over together. The players who laid the highest and the lowest card explain their choice. The group plays again until it agrees on a level. The delegation board shows the result with one row per area and one column per level. Jurgen Appelo defined the seven levels and the board in Management 3.0 (2011).
Goal
Delegation Poker divides decision authority between a manager and a team. It lists a team's decision areas: tool choice, working hours, purchases and release planning. For each area it sets one of Jurgen Appelo's seven levels of authority. At levels 1 to 3 the manager decides. At level 4 the manager and the team decide together. At levels 5 to 7 the team decides.
A team that does not know how far its authority goes loses time. It asks the manager to take decisions that the manager would have left to the team. It takes other decisions that the manager later overturns.
The technique delivers the delegation board. The board settles a recurring question: should this decision go to the manager? It also sets a starting point. The team and the manager move each area to a higher level as the team gains competence.
Usage
When to use it
- New team or new manager: set the limits of authority before the first disagreement.
- Move to self-organisation: write down what the team now decides alone and what stays with the manager.
- Repeated friction between the team and its managers: take the contested areas one by one with both parties at the table.
- Blocked decision raised in a retrospective: add the area to the board and play its level.
- Requirements governance not yet defined: set who decides a priority, a scope change or an acceptance criterion.
- Work with a supplier or another team: write down what each party decides without the other.
- Hierarchical culture: the simultaneous reveal lets an employee show a different level from their boss without contradicting the boss out loud.
- Team spread over several sites: a shared spreadsheet holds the board and the players turn their cards over on one signal in a video call.
When not to use it
- Dividing the work of an activity: use the RACI matrix to set who carries it out and who answers for the result.
- Access rights to an application: define them with the roles and permissions matrix.
Description
The seven levels of authority
Each level describes what the manager does. On the Management 3.0 cards the person who delegates speaks in the first person.
| Level | Card | What the manager does | Who decides |
|---|---|---|---|
| 1 | Tell | Makes the decision and announces it. For Appelo this level delegates nothing yet. | The manager |
| 2 | Sell | Makes the decision and then tries to convince the team that it is sound. | The manager |
| 3 | Consult | Gathers and weighs the team's views before deciding. | The manager |
| 4 | Agree | Seeks a consensus with the team. The manager's voice counts as much as the others. | Together |
| 5 | Advise | Gives an opinion. The team decides what to do with it. | The team |
| 6 | Inquire | Lets the team decide and afterwards asks for its reasons or asks to be kept informed. | The team |
| 7 | Delegate | Leaves the matter to the team and does not need to know its decisions. | The team |
Appelo builds these levels on Hersey and Blanchard's theory of situational leadership. In his view that theory does not distinguish the manager who informs the team of a decision already taken from the manager who consults the team before deciding. Levels 2 and 3 separate the two. The theory also has no style for full delegation. Appelo adds level 7 because he sees it as the goal of delegation.
According to Appelo, the level of an area depends on the competence of the people and on the impact of the decision on the organisation. Coding conventions and salaries do not sit at the same level. Tool choice can sit at level 6 for a seasoned team and at level 3 for a team that is still learning.
Choosing the decision areas
The game deals with decision areas rather than tasks. An area groups recurring decisions of the same kind. Appelo applies the same level to the whole area. A level set task by task leaves everyone unsure how far their authority goes. "Install the new test server" is a task. "Choose the test infrastructure" is an area.
The manager plays with the team. The facilitator is therefore a coach or a Scrum Master. Before the session the facilitator gathers the decision areas. Management 3.0 cites cases that range from project design to hiring a new team member. Sarika Kharbanda reports a session where the team's coach held this role. The Scrum team had first drafted the list and then submitted it to the managers. Each area becomes a short scenario: "A tester asks for a second screen. Who decides to buy it?"
Preparing the managers
A manager who fears losing control can block the game before the first card. In Kharbanda's case the coach first met the managers without the team. She showed them what delegation changed for them. The team and the managers then played together. After the session the managers understood that the exercise did not take control away from them.
Without the manager who holds the authority, the agreed level binds no one.
Playing a round
The players form groups of three to seven people. Each player receives the seven cards. A round covers one area. One player reads the scenario aloud or describes a real case from their own work. Each player silently chooses the card that says how far they would delegate this decision. When everyone has chosen, the players turn their cards over at the same time. The player with the highest card and the player with the lowest card explain their choice.
If the cards still diverge, the group plays the same area again: secret choice, cards turned over together and an explanation from the two extremes. It stops when it agrees on a level. The facilitator then places the sticky note for the area in the column of that level. The group moves on to the next area.
The simultaneous reveal protects minority views. A level announced aloud steers the people who speak after it. A level announced by the manager steers them most. Cards turned over together show the spread before any argument. The two extremes speak first because the gap between them carries the information: one of them knows a risk or a skill that the other does not.
Keeping score
Management 3.0 suggests keeping score. Each player scores the value of their card. The rule of the highest minority is the exception: a player alone on the highest card scores nothing. If three or four players lay a 7, they are not alone on the card and each scores 7 points. The rule encourages players to delegate as far as possible without going too far. Some groups also deny points to the lowest minority. This variant targets the boss who wants to control everything or the team member who refuses any authority.
Management 3.0 leaves each team to play in its own way. Many teams play without keeping score. The discussion produces the board. The points only make it livelier.
The delegation board
The delegation board is a grid with one row per decision area and one column per level. Management 3.0 accepts a physical board, a spreadsheet or any visible surface. On the wall the board is an information radiator: anyone who wonders who decides reads the answer there.
Appelo presented this board in 2011 under the name authority board. He wrote that the manager maintains this board. A task board is maintained by the team. In the played version the group places the notes where the cards agree. The manager still stands behind each level and answers for it. If the manager later overturns an agreed level, the team no longer knows where its authority ends.
Moving the board forward
The agreed level is a starting point. Appelo sees delegation as an investment: an inexperienced team costs time, energy and money before it pays back. Circumstances sometimes force a start at the Tell or Sell level. The manager then raises the team's authority step by step. On the board the notes move to the right. This movement takes far longer than on a task board.
Appelo describes the micromanagement trap. The manager waits for the team to be competent before handing it an area. A team that exercises no authority does not acquire that competence. Problems multiply. The manager then delegates even less. The right level lets the team grow without the manager losing hold of the situation. Appelo aims for distributed control and sets it against a situation that is out of control.
Management 3.0 asks teams to review the areas and their levels regularly. Daily meetings and retrospectives bring up the areas where authority remains unclear. The team adds them to the board.
Related techniques
| Technique | Question | Unit | Content of a cell |
|---|---|---|---|
| RACI matrix | Who carries out the activity, who answers for it, who is consulted before, who is informed after? | An activity or a deliverable | R, A, C or I |
| Roles and permissions matrix | What can a role do with a function of the solution? | A system function | Create, read, update, delete, approve |
| Delegation Poker | How far does the team decide? | A decision area | A level from 1 to 7 |
Appelo presents the seven levels as an answer to the limits of the RACI matrix in an agile setting. In his view RACI assumes by default that the responsible person (R) who does the work is not the accountable person (A) who answers for the result. In an agile team the person who does the work also answers for it. The Consulted and Informed roles describe the process. Delegating means handing that process to the team. RACI works task by task while authority must stay the same across a whole area. Appelo still takes from RACI the distinction between informing and consulting. Situational leadership lacked it.
These objections concern the delegation of authority. The RACI matrix remains the tool that divides the work of an activity. A team uses the two tools together. The board sets how far the team decides on its test tools. The matrix says who carries out each test activity.
The roles and permissions matrix concerns a system. The delegation board concerns a team and its decisions. The word "authority" links them: it means an access right in the matrix and a right to decide on the board.
A team that keeps a team charter can carry the board over into it under the heading for decisions. The charter adds the rule by which the group settles a question (consent, majority or a ruling by a designated person).
AI considerations
To draw up the list of areas a language model reads the team's documents: team charter, purchasing rules and retrospective minutes. It proposes decision areas. It spots tasks disguised as areas ("Install the screens") and rewords them ("Choose the workstation equipment").
To prepare the scenarios it turns each area into a short case. After the session it writes up the arguments of the two extremes and keeps the board in a spreadsheet.
The choice of level stays with the players. The level reflects the trust that the manager grants and the competence that the team recognises in itself. A model has access to neither. A level that the tool proposes before the cards are turned over anchors the players. The arguments exchanged sometimes judge the competence of named people. They fall under the Federal Act on Data Protection (FADP). The analyst anonymises them before passing them to an AI service hosted by a third party.
Examples
A development team at a health insurer in Lausanne played five areas with its manager and its product owner.
The note for the events budget carries its limit. The team decides alone on this budget within a ceiling of CHF 1'500 a year that the manager sets. Hardware purchases and tool choice both concern equipment. They do not sit at the same level. A purchase commits the unit's budget. The choice of a tool stays within the team's own work.
Visualisations
The completed board is the deliverable. The table of the seven levels is its legend. The round with its cards face up shows how the group decides where an area's note goes on the board.
Cost
| Phase | Level | Justification |
|---|---|---|
| Preparation | Low | List the decision areas and write them as scenarios. Meet the managers first if the fear of losing control dominates. The cards print for free. |
| Execution | Medium | One round per area. The group plays it again until it agrees. The manager and the whole team take part. |
| Documentation | Low | The board is the documentation. The team updates it at each review. |
Tooling
Each player receives a set of seven cards numbered from 1 to 7. Management 3.0 sells a deck in English. Registered users can download free printable cards in French, German and sixteen other languages. Management 3.0 forbids their resale. Seven cards numbered by hand do the same job.
For the board a flipchart sheet and sticky notes are enough for a team on site. A spreadsheet replaces the wall: Management 3.0 offers an .xlsx template to copy into Google Sheets. A distributed team plays on a digital whiteboard (Miro offers a template) or in a video call. In the call each player types their level in the chat and sends it on the facilitator's signal.
Sources
Jurgen Appelo defined the seven levels of authority and the board in Management 3.0 in 2011. Management 3.0 distributes the card game and maintains its rules.
- Jurgen Appelo, Management 3.0: Leading Agile Developers, Developing Agile Leaders, Addison-Wesley, 2011: the seven levels of authority and the authority board.
- Jurgen Appelo, Leading Agile Developers: The Seven Levels of Authority (Part 2), InformIT, 3 February 2011: the chapter of the book as an article. The objections to the RACI matrix, the link with situational leadership, the seven levels, the authority board, the micromanagement trap and delegation as an investment.
- Jurgen Appelo, Managing for Happiness, Wiley, 2016, chapter 3 "Delegation Boards and Delegation Poker": Appelo presents the board and the game there.
- Management 3.0, Delegation Poker & Delegation Board: the three principles, the course of a round, the points, the delegation board and the cards.
- Sarika Kharbanda, How to make the Delegation Board work for your team, Management 3.0, 5 April 2017: the case of a Scrum team, its list of areas, the preliminary session with the managers and the round played again until agreement.

