Delegation Poker: Making Power Visible
A practical leadership tool for clarifying decision rights, accountability and the uncomfortable question every organization eventually has to answer: who actually gets to decide?
Delegation Poker sounds playful. Almost too playful.
But the problem it addresses is not playful at all.
Many companies do not have a delegation problem. They have an honesty problem.
They say teams are empowered. They say decisions should be made closer to the work. They say leadership wants ownership.
Then the first uncomfortable decision comes along and suddenly everything moves back to the top.
That is where Delegation Poker can help.
Not because it magically creates better leadership. It does not. And not because a deck of cards can fix trust issues. It cannot.
Delegation Poker is useful because it makes one thing visible that many organizations prefer to keep vague:
Who is actually allowed to decide?
It is not about giving power away.
It is about making power visible.
The real issue: fuzzy authority
Most organizations have job titles, reporting lines, steering committees, approval workflows and strategy decks.
And still, when a real decision needs to be made, people hesitate.
A product team thinks it owns the roadmap. Sales thinks customer commitments should drive priorities. Finance wants to approve anything with budget impact. Legal gets involved late and stops the train. The executive team says it wants empowered teams, but reverses decisions when the result feels uncomfortable.
This is not rare. It is normal.
The problem is that formal authority and practical authority are often two different things.
On paper, a team may “own” a topic. In reality, every meaningful decision still needs senior approval. Or the opposite happens: a team makes a decision and later finds out that leadership expected to be consulted.
That is how trust gets damaged.
Teams feel micromanaged. Leaders feel bypassed. Decisions slow down. People start managing politics instead of outcomes.
Delegation Poker does not solve all of this. But it exposes where the confusion sits.
That is already useful leadership work.
What Delegation Poker actually is
Delegation Poker is a Management 3.0 practice based on the Seven Levels of Delegation. It helps teams and leaders clarify who is responsible for what and to what degree.
The core idea is simple:
Delegation is not binary.
It is not just:
“The boss decides.”
Or:
“The team decides.”
There are useful levels in between. You do not need to memorize them. The point is to see that decision authority has shades.
LevelMeaningIn plain language1. TellThe leader decides and informs others.“I decide. You need to know.”2. SellThe leader decides and explains the reasoning.“I decide. I explain why.”3. ConsultThe leader asks for input, then decides.“I listen. Then I decide.”4. AgreeLeader and team decide together.“We decide together.”5. AdviseThe team decides after receiving advice.“You decide. I offer input.”6. InquireThe team decides and explains afterwards.“You decide. I ask how you got there.”7. DelegateThe team decides fully.“You decide. No approval needed.”
The cards are not the point.
The conversation after the cards are shown is the point.
If one person picks level 2 and another picks level 6, the exercise is working. The disagreement was already there. Now it is visible.
Before that moment, both people may have assumed they were aligned.
They were not.
Why this matters for leadership
Good leadership is not about making every decision yourself.
It is also not about pushing every decision downward and calling it empowerment.
Good leadership means placing decisions where three things come together:
The right information
The right competence
The right accountability
That third point matters most.
Accountability is where many empowerment conversations become vague.
It is easy to say:
“The team should decide.”
It is harder to answer:
Who carries the risk if the decision fails?
Who explains the decision to the board?
Who owns the budget impact?
Who handles the customer escalation?
Who documents the reasoning?
Who can reverse the decision?
These are not side questions. They are the real questions.
Delegation without accountability is not empowerment. It is abdication.
Control without clarity is not leadership. It is friction.
Delegation Poker helps leaders and teams discuss the space in between.
Empowerment is not the goal
Better decisions are the goal.
That distinction matters.
Empowerment sounds good in a town hall. But in the daily life of an organization, empowerment only matters if it helps people make better, faster, better-owned decisions.
That requires more than freedom.
It requires context.
It requires competence.
It requires boundaries.
It requires trust.
And it requires clarity about consequences.
Without those things, “empowerment” becomes a slogan people stop believing.
What research supports - and what it does not
Let’s be precise.
Delegation Poker itself is best understood as a practical facilitation tool, not as a standalone leadership theory with a large body of direct empirical research behind it.
That does not make it weak. It just means we should not oversell it.
The research does not “prove” Delegation Poker as a method. What it does support are the leadership mechanics around it: participation, role clarity, autonomy, trust, competence and accountability.
Research on delegation and consultation suggests that managers are more willing to delegate when they perceive people as competent and aligned with their goals. Research on empowering leadership also points to positive effects on performance, organizational citizenship behavior and creativity, while emphasizing factors such as trust and psychological empowerment. At the same time, reviews of empowering leadership warn that its effects are context-dependent and not always simple or linear.
In plain English:
More freedom can help when people have the skill, information and support to use it well.
More freedom without boundaries creates confusion.
More control without explanation creates resentment.
That is why Delegation Poker can be useful. It gives people a simple language for discussing decision rights without turning the conversation into a power struggle.
A deck of cards cannot fix weak leadership. It cannot create trust where there is none. It cannot make an unprepared team ready overnight. It cannot turn unclear strategy into clear decisions.
But it can reveal whether people are operating with the same assumptions.
Often, they are not.
A practical example
Imagine a company discussing this decision:
Who decides which features go into the next product release?
Product picks level 6:
“We speak with customers, support, engineering and sales every week. We have the best information. We should decide and explain afterwards.”
Sales picks level 3:
“Major customers are waiting for specific commitments. We need to be consulted before priorities are locked.”
The executive team picks level 4:
“Some roadmap decisions affect revenue expectations and board conversations. We cannot be surprised later.”
Engineering picks level 5:
“Product can decide, but delivery risk and technical complexity must be considered before anything is promised.”
This is not a personality conflict.
It is a decision-rights conflict.
Everyone is looking at the same decision from a different risk angle.
A reasonable outcome could be:
Product decides normal roadmap priorities at level 5. Sales and engineering advise before commitment. Executive approval is only required when the decision affects strategic accounts, external revenue commitments or delivery dates already communicated to customers.
That is not bureaucracy.
That is a working agreement.
And it is much better than discovering the disagreement after the decision has already been made.
The biggest misunderstanding
The lazy version of Delegation Poker is:
“Let’s empower the team.”
The useful version is:
“Which decisions are we actually willing to let the team make, even when we disagree with the outcome?”
That is the real test.
Many leaders are comfortable delegating decisions as long as the decision is the one they would have made anyway.
That is not delegation.
That is supervised agreement.
Real delegation includes the possibility that someone else makes a different call.
Not a reckless call.
Not an uninformed call.
But a different call.
This is where leaders often discover their own limits.
They want speed, but also control. They want ownership, but also veto power. They want teams to act independently, but also keep leadership comfortable.
Delegation Poker makes that contradiction harder to hide.
Where Delegation Poker fails
Delegation Poker fails when it becomes theater.
If leadership already knows the answer and only uses the session to create the appearance of participation, people will see through it.
It also fails when teams treat delegation as freedom without consequences.
Level 7 does not mean:
“We decide and nobody can ask questions.”
It means:
“We decide and we are prepared to explain, own and improve the decision.”
The method also fails when the decision areas are too vague.
“Strategy” is too broad.
“Technology” is too broad.
“People topics” is too broad.
Use real decisions:
Who approves hiring for a new role?
Who decides vendor selection below a certain budget?
Who owns product roadmap priority?
Who can change delivery dates promised to customers?
Who decides architecture principles?
Who approves exceptions to security rules?
Who can stop a project?
Who can spend from an approved budget?
Delegation Poker works best when the decision is concrete enough that people can imagine the consequences. This also matches the original recommendation to apply the seven levels to important decision areas rather than tiny individual tasks.
How to use it without turning it into a workshop circus
Start small.
Pick five to eight decisions that recently caused friction.
Do not begin with a company-wide delegation program. That usually turns into a heavy exercise with too many people and too little honesty.
Start with one leadership team, one product area, one function or one cross-functional group.
For each decision, ask:
What is being decided?
Who has the best information?
Who carries the risk?
Who needs to be consulted?
Who must be informed?
What is the budget or risk limit?
When does the delegation level change?
That last question is important.
A team may decide freely up to a certain budget. A manager may decide after consultation if customers are affected. A leader may retain decision authority when legal, compliance or reputation risks are involved.
This is not about trust versus mistrust.
It is about making the rules clear before emotions run high.
A simple delegation board could look like this:
Decision areaDelegation levelBoundaryTool choice inside the team6Allowed if annual cost stays below €10,000Product roadmap priority5Sales and engineering advise before commitmentStrategic customer promises3Leadership decides after input from sales and productArchitecture standards5Security must be consulted for critical systemsHiring a new role4Manager and leadership agree togetherBudget reallocation6Allowed within approved quarterly budget
A clear one-page delegation board is often more useful than a twenty-page governance document nobody reads.
What leaders should watch for
Delegation Poker reveals more than decision rights.
It reveals leadership culture.
If leaders always choose low delegation levels, the organization may have a control problem.
If teams always choose high delegation levels, they may underestimate risk.
If every decision lands at level 4, the company may be confusing collaboration with consensus.
Consensus feels safe. It can also become slow, political and expensive.
Not every decision needs everyone in the room.
One useful executive question is:
Is this decision hard to reverse?
If a decision is easy to reverse, move it closer to the people with the best information.
If it is expensive, public, legally sensitive or hard to undo, keep stronger leadership involvement.
This is a better rule than simply saying:
“We need more empowerment.”
Empowerment is not the goal.
Better decisions are the goal.
Getting Started
Run one focused session.
For a first pass, 60 to 90 minutes is often enough if the group works with a small number of concrete decisions.
Bring the people who actually matter for the decisions. Not everyone who has an opinion. Not everyone who might be interested.
Bring the people who decide, advise, own risk or live with the outcome.
Use real decisions. Avoid theory.
For each decision:
Clarify the decision in one sentence.
Let everyone choose a delegation level silently.
Reveal the levels at the same time.
Let the highest and lowest voters explain their reasoning.
Agree on one level.
Write down the boundary conditions.
Review it after a few weeks.
That last step matters.
Delegation is not a one-time announcement. It is a working agreement. It should change as competence, trust, risk and business conditions change.
Final Thoughts
I have rarely seen companies slow down because one team made one imperfect decision.
I have seen many companies slow down because nobody knew which decisions teams were truly allowed to make.
That is the quiet cost of fuzzy authority.
People escalate too much. Or they wait too long. Or they act without alignment and pay for it later.
Delegation Poker gives leaders a simple way to clean that up.
It is not a silver bullet. It does not replace trust, competence, judgment or courage.
But it does one thing very well:
It turns vague authority into a conversation people can actually have.
And sometimes that conversation is exactly what leadership has been avoiding.
Useful sources behind this article
Delegation Poker is a Management 3.0 practice based on the Seven Levels of Delegation. This article references the method for explanation and commentary. For the original practice, materials and licensing information, see Management 3.0.
Management 3.0: Delegation Poker & Delegation Board
https://management30.com/practice/delegation-poker/Jurgen Appelo: The 7 Levels of Delegation
https://medium.com/@jurgenappelo/the-7-levels-of-delegation-672ec2a48103Gary Yukl & Ping Ping Fu: Determinants of Delegation and Consultation by Managers, Journal of Organizational Behavior, 20(2), 219–232, 1999
https://www.jstor.org/stable/3100422Allan Lee, Sara Willis & Amy Wei Tian: Empowering Leadership: A Meta-Analytic Examination of Incremental Contribution, Mediation, and Moderation, Journal of Organizational Behavior, 39(3), 306–325, 2018
https://research.manchester.ac.uk/en/publications/empowering-leadership-a-meta-analytic-examination-of-incremental-Minyoung Cheong, Francis J. Yammarino, Shelley D. Dionne, Seth M. Spain & Chou-Yu Tsai: A Review of the Effectiveness of Empowering Leadership, The Leadership Quarterly, 30(1), 34–58, 2019
https://www.researchgate.net/publication/327535755_A_Review_of_the_Effectiveness_of_Empowering_Leadership