methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session45-90 minWorkshopDelegation Board

Session: Delegation Poker

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 3-10. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Delegation Board. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Clarify levels and areas

    10-15 min

    The facilitator explains the seven delegation levels with examples. Go through decision areas and verify understanding, clarify if needed. Hint: Level understanding is the most common error source. Consult and Advise are often confused. Clarify with concrete examples.

    FacilitatorDelegation Board
  2. 2

    Phase 2: Pick cards secretly

    15-20 min

    Each person picks one level per decision area in secret. Solo phase, no discussion. In multi-person groups, reveal all at the same time. Hint: Secret choices prevent anchoring to the lead position. If the first person reveals, others can be influenced, so reveal simultaneously.

    FacilitatorDecision Boundaries
  3. 3

    Phase 3: Discuss differences

    15-25 min

    Reveal cards per area. If all match, continue. If responses vary, discuss for 3-5 min: why this was estimated and what is needed for a higher delegation level. Hint: Variation is often the real value. Someone selecting Tell versus Delegate signals maturity or trust gaps.

    FacilitatorRole Agreements
  4. 4

    Phase 4: Reach agreement

    10-20 min

    Agree on one level per area. Record what is required for the next higher level (maturity signals, data, trust basis). Document it on the Delegation Board. Hint: Delegation is not static. For areas with different maturity per subtask, split the area.

    FacilitatorDelegation Board
  5. 5

    Phase 5: Cadence and review

    5-10 min

    Set review date (typically quarterly). Assign owner for the Delegation Board. Decide when the next poker runs (for example after six months or after a role change). Hint: The Delegation Board becomes wallpaper if nobody refers to it in conflicts. Visibility (Slack topic, wiki) is mandatory.

    OwnerDecision Boundaries
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerDelegation Board
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Delegation Poker

Goal

Artifact: Delegation Board

Working Question

Which delegation degree per decision area matches maturity and context, and which differences between lead and team do we need to negotiate?

Context

Decision areas collected in advance (for example Sprint Scope, Hiring, Tool Selection, Architecture, Pricing, Holiday Planning); explanation of the seven levels with examples; trigger (new lead, operating model change, recurring conflicts).

Setup

  • Format: Method session
  • Duration: 45-90 min
  • Mode: Workshop
  • Participants: One facilitator who explains the levels; one lead and team (three to ten); one scribe for the final Delegation Board.
  • Owner: One facilitator who explains the levels
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Delegation Board. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Cards with seven delegation levels from Management 3.0 (Tell, Sell, Consult, Agree, Advise, Inquire, Delegate); list of 8-15 decision areas; Delegation Board or Miro frame with a matrix; timer.

Preparation

Levels cards and examples visible. Matrix Decision area x level on the board. Rule: for each area, choose cards secretly, then reveal together, then discuss.

Agenda

  1. Phase 1: Clarify levels and areas (10-15 min) Owner: Facilitator Action: The facilitator explains the seven delegation levels with examples. Go through decision areas and verify understanding, clarify if needed. Hint: Level understanding is the most common error source. Consult and Advise are often confused. Clarify with concrete examples. Output: Delegation Board

  2. Phase 2: Pick cards secretly (15-20 min) Owner: Facilitator Action: Each person picks one level per decision area in secret. Solo phase, no discussion. In multi-person groups, reveal all at the same time. Hint: Secret choices prevent anchoring to the lead position. If the first person reveals, others can be influenced, so reveal simultaneously. Output: Decision Boundaries

  3. Phase 3: Discuss differences (15-25 min) Owner: Facilitator Action: Reveal cards per area. If all match, continue. If responses vary, discuss for 3-5 min: why this was estimated and what is needed for a higher delegation level. Hint: Variation is often the real value. Someone selecting Tell versus Delegate signals maturity or trust gaps. Output: Role Agreements

  4. Phase 4: Reach agreement (10-20 min) Owner: Facilitator Action: Agree on one level per area. Record what is required for the next higher level (maturity signals, data, trust basis). Document it on the Delegation Board. Hint: Delegation is not static. For areas with different maturity per subtask, split the area. Output: Delegation Board

  5. Phase 5: Cadence and review (5-10 min) Owner: Owner Action: Set review date (typically quarterly). Assign owner for the Delegation Board. Decide when the next poker runs (for example after six months or after a role change). Hint: The Delegation Board becomes wallpaper if nobody refers to it in conflicts. Visibility (Slack topic, wiki) is mandatory. Output: Decision Boundaries

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Delegation Board

Closeout

  • Update result artifact: Delegation Board
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Delegation Board: Delegation Poker

Working Question

Which delegation degree per decision area matches maturity and context, and which differences between lead and team do we need to negotiate?

Context

Decision areas collected in advance (for example Sprint Scope, Hiring, Tool Selection, Architecture, Pricing, Holiday Planning); explanation of the seven levels with examples; trigger (new lead, operating model change, recurring conflicts).

Participants

  • Owner: One facilitator who explains the levels
  • Participants: One facilitator who explains the levels; one lead and team (three to ten); one scribe for the final Delegation Board.

Input

Cards with seven delegation levels from Management 3.0 (Tell, Sell, Consult, Agree, Advise, Inquire, Delegate); list of 8-15 decision areas; Delegation Board or Miro frame with a matrix; timer.

Template

Delegation Poker Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Delegation Board:
  • Decision Boundaries:
  • Role Agreements:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Delegation Board is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Delegation Poker Working Template

View templateCompact working template for Delegation Poker with context, input, output artifacts, and next step.
canvas

delegation-poker-working-template.md

Compact working template for Delegation Poker with context, input, output artifacts, and next step.

Delegation Poker Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Delegation Board:
  • Decision Boundaries:
  • Role Agreements:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Delegation Board.
  • Own entry per session with date. Update with justification when maturity signs are reached. Three versions per year are usually enough.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet