What needs to be finished first
The team has a practiced norm of speaking openly without self-reflection turning into blame.
There are written Working Agreements that can serve as a reference point for ownership.
What needs to be ready before start
Visual ladder with eight rungs from unawareness to ownership; markers or digital pens for placement; reflection template for the person (stage before the situation, stage after, trigger); note space for next steps.
A coach or facilitator who guides through the model; the team or individual who places themselves; in a team setting, a lead person who records shared agreements after reflection.
Concrete example scenario (conflict, missed goal, delivery slip) to practice the ladder on; definition of the eight stages with examples; note that stages are behavioral descriptions, not labels for people.
60-90 min for one scenario in a team
Hang the ladder visibly or draw it on the board. Short forms of the stages: Unaware, Blame Others, Make Excuses, Wait and Hope, Acknowledge Reality, Own It, Find Solutions, Make It Happen. Introduce the scenario briefly, then move into silent work.
The one question this method answers
Which stage of the ladder does the behavior in this concrete situation sit on, and which conditions would enable a step upward?
Marker: Sektion
| Step | Duration | Action | Hint |
|---|---|---|---|
1Section 1: Model and scenario | 15 min | Explain the eight stages, one example sentence per stage. Introduce the scenario: a concrete situation from the last sprint or quarter with a measurable consequence. | Examples from the lead person's own behavior increase safety. Staying abstract signals that reflection is only for others. |
2Section 2: Silent self-positioning | 10 min | Each person notes privately which stage they were on in the scenario. Add two sentences about the trigger for that stage. | Do not share in plenary, otherwise consensus drift sets in. Force written commitment before verbal exchange. |
3Section 3: Pair exchange | 15 min | Form pairs, spend 5 min on your own position, then 2 min of questions. No evaluation, only questions for understanding. | If a pair slips into justification, the facilitator interrupts and reminds the group of the question-first stance. Evaluation blocks honesty. |
4Section 4: Identify conditions | 20 min | Plenary: what enables a higher stage (information access, decision authority, clear expectations)? What blocks it (culture, punishment for mistakes, missing mandate)? | If blockers are always located elsewhere, that itself is a lower stage. The facilitator mirrors this calmly. |
5Section 5: Agreements | 15 min | Formulate one concrete agreement per person: which behavior from when with which owner. Optional additional team agreement. | Agreements without time frame and observability are wish statements. Each agreement needs at least one follow-up in the next retro. |
What comes out at the end
Reflection note per person with scenario, identified stage, conditions for a stage shift, and concrete agreement; optional team charter entry with shared Working Agreements; linked to retro backlog for follow-up review.
Add date and trigger to the header for each reflection event. Maintain agreements separately as a living Working Agreements list, archive individual reflections. When reviews repeat, document stage history per person only with consent.
Compact working template for Accountability Ladder with context, input, output artifacts, and next step.
A model that classifies reactions from blame to ownership on a ladder.
When and for what do we use this method?
Which data, observations, decisions, or materials are available?
Short notes along the runsheet.
Owner, date, and success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Scenario: Release 2.4 was delayed by 9 days. Three team members reflect on their share.
@anna (Tech Lead): Stage Acknowledge Reality. I saw the QA bottlenecks but waited to see whether they would resolve themselves. Trigger: assumption that the QA lead would escalate on their own.
@ben (PM): Stage Wait and Hope. I waited three weeks for the vendor commitment without a Plan B. Trigger: avoiding the uncomfortable conversation.
@lisa (Engineer): Stage Own It. I escalated after day 3 and initiated pair programming with QA, which saved the last 4 days.
Conditions: Escalation path was unclear. QA engagement model was not documented. Vendor risk had no Plan B.
Agreements:
Recognize symptoms and steer against them
People are sorted into stages like grades, and psychological safety collapses.
Clarify that stages describe behavior in a situation, not people. Always reflect from the first-person perspective, never about others.
The lead person places team members without involving them.
Self-positioning is mandatory, positioning others is forbidden. The lead starts with their own stage to set the norm.
Reflection stays at the label without asking what enables or blocks the behavior.
Run Section 4 strictly. Note at least one condition per stage shift that the team can influence.
The discussion drifts into abstract culture topics and concrete actions disappear.
The facilitator asks for a concrete action from the last 14 days. If none can be named, no relevant situation has been reflected yet.
The workshop ends with aha moments and is forgotten in two weeks.
One written, observable agreement per person with a re-review date. Without a date, the agreement is considered not made.
People lower their voice, withdraw, and respond with self-deprecation.
Pause, normalize the model in first person, openly share your own low stages. Abort the workshop if the shame level stays high.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.