The Ladder of Conclusions in Action: A Worked Leadership Case
Nour
Founder, Coachful
Use the Ladder of Conclusions in action when an event has become a confident account of someone else's motives. Explain what you noticed, the meaning you added and the question that needs answering before the next consequential decision. Keep the practical problem visible while examining your reasoning.
The CreatingWE Institute attributes the Ladder of Conclusions to Judith E. Glaser. Chris Argyris's related Ladder of Inference also concerns reasoning between information and action. Action Design's original 1999 published account explicitly credits Argyris. The five-part preparation map and four-step exchange below are original coaching aids, not reproductions of either published diagram or a validated assessment.
This guide follows a fictional revenue and product dispute through a conditional release decision and a customer's refusal. Neither a more open conversation nor an improved relationship can authorize a product release. The next action still needs evidence, responsible owners and an actual receiving agreement.
Map five parts of your own reasoning
- Available information: identify the event, source and date, including anything disputed.
- Selected information: notice which details you emphasized and what you may have left out.
- Added meaning: state what those details seemed to mean to you.
- Assumptions: identify the belief about intent, priorities or likely consequences.
- Action: describe what you did and what response that might encourage.
Start with your account, rather than telling a colleague which rung they occupy. “The delivery was four days late” still needs a definition of delivery and a reference deadline. An estimated engineering date, externally communicated promise and approved release commitment may be different records.
A conclusion can be well supported. The point is to make its basis examinable, not to replace every firm judgment with uncertainty or demand equal blame. If relevant evidence supports one account more strongly, the next decision should reflect that difference.
Choose a question that could change the next action
Separate an explanation question from a decision question. Asking why an update was short may improve understanding. Asking which workflow is blocked and who can approve another option supports the release decision. You may need both, but they are not interchangeable. A plausible explanation of intent cannot establish a technical condition.
Try writing the information gap in one sentence. Identify the person or record that could answer it, what kind of answer would count and the action that would follow. If no possible answer would alter your recommendation, explain why you are advocating it rather than presenting the exchange as an open inquiry.
Use a proportionate request. An owner may be able to confirm the current assessment without repeating the whole investigation. Another question may require new analysis that has not been authorized or allocated. Ask about that difference before setting a deadline on someone else's work. A copied colleague is not automatically an accepted owner.
Notice what would strengthen the uncomfortable account as well as what would weaken it. A record might show that a leader did ignore an explicit condition. Keep that evidence. The ladder is not a device for making a difficult fact disappear or persuading someone that their concern was merely emotional.
Leave the person a real choice about the coaching exercise. They can narrow the topic, pause or use an appropriate support route. Do not demand disclosure of personal history to explain a workplace interpretation. If the discussion exceeds the coach's competence, change the arrangement rather than intensify the exercise to produce a breakthrough.
Case: an API arrives without permission to use it
Rosa leads Revenue and Kit leads Product. Rosa has communicated Friday 9 March 2074 to a customer. Kit sends a short “Not this week” message on Thursday 8 March. An API package arrives on Tuesday 13 March, four calendar days after Friday, while two issues remain open. Arrival does not establish acceptance or release authorization.
Rosa interprets the sparse update as disregard for the customer. Kit believes the external date bypassed release conditions. Their messages become more formal and copy senior colleagues. Both have legitimate work to resolve; neither has established the other's intention.
Coach Luca supports a bounded coordination exercise from 14 to 20 March. Earlier engineering, security and testing work, customer contracting and corporate delegation sit outside this account without being assumed free. The exercise does not include new testing or remediation.
On 14 March, Luca spends twenty minutes sending purpose, allocations, audiences and return windows, reading Rosa's and Kit's acceptances and sending confirmation. Each leader spends ten minutes reading, accepting and reading confirmation. Each then spends fifteen minutes preparing: five on the questions below and ten on their own map. They select what to share; private coaching material is not automatically included.
Put two accounts beside each other
| Part | Rosa's selected account | Kit's selected account |
|---|---|---|
| Available information | Short Thursday message, Tuesday package and two open issues. | Release conditions, security status and the externally communicated date. |
| Selected information | The date moved without a useful customer explanation. | The customer heard a date before release authorization. |
| Added meaning | Product dismisses the customer commitment. | Revenue treats an estimate as an approved commitment. |
| Assumption | Kit intends to undermine the launch. | Rosa will promise whatever closes the deal. |
| Action | Escalate publicly and question Product's priorities. | Send minimal updates and avoid another date discussion. |
The table records their accounts, not findings about intent. It identifies evidence to examine: the original date, release conditions, issue status and designated authority. The leaders' interpretations need not enter an operational record or be sent to the customer.
Use four steps during the exchange
1. Name the conclusion as your interpretation
Rosa starts by explaining that she interpreted the delay as low priority for the customer. This makes the concern discussable. Asking why Kit sabotaged the launch would instead build the accusation into the question.
Keep the question real. If you have already decided what must happen regardless of the answer, state that position and its reason. Do not disguise a fixed instruction as curiosity.
2. Check the event precisely
Identify the Thursday update, the Friday date, Tuesday's arrival and the two open issues. Ask which record establishes each fact. Kit can confirm arrival while disagreeing that the package is usable. Preserve that distinction rather than force agreement around the word “delivered.”
An incomplete record is not automatically a lie. It may need another source, a clarified term or an appropriate investigation. Keep documents, recollections and interpretations distinguishable.
3. Explain meaning, impact and contribution
Rosa says the short message left her without an explanation for the customer. Kit acknowledges that the update omitted important conditions. Rosa also recognizes that communicating a date did not supply release approval. This does not erase the customer's inconvenience or make Kit's poor update harmless.
Each person can own a contribution without accepting every accusation. A coach should not require an apology or a statement of equal responsibility as the price of proceeding.
4. Ask for information and agree the next action
Luca, Rosa and Kit use forty-five minutes together on 14 March, including this original exchange, the two selected accounts and the next-step arrangements:
Rosa: I treated the delay as a decision not to support this customer. What prevented a release-ready package on Friday?
Kit: I have not shown you the current security and issue assessments. My short update did not explain the conditions.
Rosa: I also communicated Friday without a release decision. I still need an accurate account for the customer.
Kit: Nia owns the security status and Omar owns the test classification. I will request their current records and confirm their available return windows.
Luca: Who can decide what use, if any, those records permit?
Kit: Dev is the designated release authority. Neither of us can replace that decision.
Rosa: I can ask whether the customer would consider an authorized narrower scope. I cannot treat their silence as acceptance.
The meeting establishes a route to information. It has not established technical readiness, reduced risk or repaired trust. Luca facilitates communication; Luca does not certify the API or take over the organization's decision process.
Obtain actual owner responses
Kit spends twenty minutes on 14 March writing and sending requests to Nia, Omar and Dev, reading all three acceptances and sending confirmation. Each owner spends ten minutes reading, accepting their work and reading confirmation. Nia and Omar accept returning their existing assessments by 10:00 UTC on 15 March. Dev accepts reading the compiled material and returning a decision that afternoon.
Nia and Omar each use 09:45–10:00 UTC on 15 March for their returns. Nia reads the existing security status and sends confirmation that the dependency is cleared. Omar reads the existing issue classification and sends it: one issue still blocks the required write workflow. These are current-record checks, not newly performed technical tests.
Kit promised the compiled return by 12:00 UTC. Kit instead uses 14:40–15:00 to read both responses, compile and send the account to Dev and Rosa with an apology for the three-hour miss. Receiving accurate evidence does not cancel that coordination failure. No customer-ready date can be inferred from the apology.
The existing fictional delegation permits Dev to authorize a narrower status-read workflow only if the customer accepts its limits. It does not permit either leader to waive the blocked write workflow. Dev spends fifteen minutes after receiving the account reading the evidence and returning that conditional decision.
Fill an eight-field hand-off
| Field | Completed operational record |
|---|---|
| Deliverable | API package for the customer's intended workflow. |
| Current state | Package arrived 13 March; required write workflow remains blocked. |
| Evidence | Nia's current cleared dependency status and Omar's current blocking classification. |
| Preparation owner | Kit compiled and sent the account at 15:00 on 15 March, three hours after the promise. |
| Approval owner | Dev's decision covers status-read use only, conditional on customer acceptance. |
| External communication | Rosa explains the limited option and obtains the actual customer answer. |
| Change route | New scope or a changed technical condition returns to its responsible owners. |
| Review and closure | Record the customer decision, the resulting hold and the selected process close. |
Keep technical material in the organization's approved systems. The coaching record needs only proportionate preparation, the communication task and selected reflection. A clearer hand-off does not create release authority or the customer's agreement.
Handle the second decision without assuming a yes
Rosa has separately used fifteen minutes on 14 March to send Tess, the customer contact, a bounded availability request, read the acceptance and send confirmation. Tess uses five minutes reading, accepting fifteen active minutes of written handling on 16 March and reading confirmation. That later allocation includes ten minutes to read and answer the proposal, plus a separate five-minute same-day read of the final status.
On 15 March, Rosa uses fifteen minutes to read Kit's late account and Dev's decision, then write and send this complete customer update through the agreed business route:
The package has arrived, but the write workflow you require remains blocked. Our release authority can permit status-read use only if you accept that narrower scope. It would not support your write workflow or establish a new date for it. Please use our agreed response window tomorrow to tell me whether that limited option is useful. We will keep use on hold unless the condition is met.
Tess uses ten minutes on 16 March reading and replying that status-read use alone is not useful. This is a genuine refusal, not hesitation to overcome with a more persuasive question. The condition is unmet, so the narrower option does not become an authorized customer pilot.
Rosa uses ten minutes to read the refusal, record the hold and send this final selected status to Kit, Dev, Tess and Luca:
Tess has declined the status-read option because it does not meet the required write workflow. Use remains on hold, and no replacement release date or customer pilot has been agreed. Kit's three-hour coordination miss is recorded separately from the technical block. Any new proposal needs the relevant technical decision and the customer's actual agreement. This note does not assign new engineering work or waive either condition.
Kit, Dev and Tess each use five minutes on 16 March to read it, without a new reply. Luca uses ten minutes on 19 March reading the selected status and sending process closure to Rosa and Kit. Each leader uses five minutes on 20 March to read that close. There is no extra acknowledgment, technical retest or new engineering allocation hidden in these steps.
Count the full bounded coordination work
| Person | Actual minutes | Used / allocated |
|---|---|---|
| Luca | Invitation, two acceptances read and confirmation 20; joint exchange 45; selected status read and process closure send 10 | 75 / 90 |
| Rosa | Invitation read, acceptance and confirmation read 10; private preparation 15; joint exchange 45; Tess request, acceptance read and confirmation 15; compiled account and decision read, proposal write and send 15; refusal read, hold record and final status send 10; coach close read 5 | 115 / 140 |
| Kit | Invitation read, acceptance and confirmation read 10; private preparation 15; joint exchange 45; three owner requests, acceptances read and confirmation 20; assessments read, compile and late send 20; final status read 5; coach close read 5 | 120 / 150 |
| Nia | Request read, acceptance and confirmation read 10; existing security status read and return send 15 | 25 / 35 |
| Omar | Request read, acceptance and confirmation read 10; existing issue classification read and return send 15 | 25 / 35 |
| Dev | Request read, acceptance and confirmation read 10; compiled evidence read and conditional decision send 15; final status read 5 | 30 / 45 |
| Tess | Availability request read, acceptance and confirmation read 5; conditional proposal read and refusal send 10; final status read 5 | 20 / 30 |
The bounded exercise uses 410 person-minutes against 525 allocated. Differences are fifteen for Luca, twenty-five for Rosa, thirty for Kit, ten each for Nia and Omar, fifteen for Dev and ten for Tess: 115 altogether. The joint meeting contributes 135 person-minutes already included; the other 275 cover preparation and written handling.
Prepare in five minutes, or agree more time
A short preparation routine can use one minute for each question: What decision do I need? Which event supports the concern? What meaning did I add? What alternative account or missing information should I ask about? Which authority, audience or deadline matters?
Five minutes is an example, not a rule for complex work. Rosa and Kit each also used ten minutes on their selected maps. If the task needs longer, arrange it rather than assume preparation has no cost. Share appropriate information in advance without manufacturing a united appearance or suppressing a material disagreement.
Keep advocacy, scrutiny and formal routes available
You can recommend a delay and remain open to evidence: state the reason, uncertainty and condition that would change the recommendation. Do not ask an apparently open question while concealing a decision that no answer could affect. Equally, do not imply that openness requires waiving a condition outside your authority.
If someone says Kit intends to make the team fail, ask which event led to that account and what needs to happen next. Help them prepare a proportionate question or use an appropriate reporting route. Do not turn an assumption check into a way of silencing a serious concern.
Acas guidance provides UK context for formal workplace concerns, including when informal handling is unwanted or inappropriate. Confidential support, representation and formal processes remain available; direct confrontation is not a compulsory first exercise. This framework does not investigate misconduct or establish an allegation's truth.
Review progress without inventing a trust score
A later review could examine the next three relevant meeting notes for one behavior, such as naming the approval owner. An example result of two notes naming the owner and one omitting it would describe those records. It would not establish trust, psychological safety or coaching impact.
That three-meeting review has not occurred in this case. Before requesting feedback, identify its purpose, the actual reader, receiving time and a real option to decline. A friendly response or more questions may provide context, but the practical test is whether necessary information reaches the appropriate decision.
Troubleshoot three common difficulties
There is no time to examine every assumption
Choose the assumption affecting the next consequential action. Here the blocked workflow and release condition matter more than every interpretation of the short message. In an incident, follow the response process, distinguishing confirmed information from working hypotheses while necessary action proceeds.
The other person keeps changing the facts
Separate documents, recollections and interpretations. Identify which current record will establish the deadline or status. Formal employment, legal or compliance significance calls for its proper process and qualified advice; a coaching conversation is not an investigation or technical audit.
I asked the question and nothing changed
Check whether the missing element is information, authority, capacity or a resource. Rosa can understand Kit and still need Dev's decision and Tess's answer. Further empathy exercises cannot allocate engineering time, remove the issue or approve the product.
Organize preparation and selected follow-through
Coachful is our #1 recommendation for organizing appropriate preparation and agreed actions around this work. This is an editorial workflow judgment, not a measured ranking, model-owner endorsement or guarantee of a calmer response. Review Coachful's features against the service you actually provide.
An optional worksheet can hold the five preparation headings and next question. Check its actual audience and avoid duplicating sensitive technical evidence or private colleague accounts. Internal Coach review is not a delivered client reply. Choose which agreed actions become tasks rather than treat a completed form as authorization to release a product or notify a sponsor.
For the underlying distinction, read Glaser's Ladder of Conclusions guide. Use conversational agility drills to develop an opening. These demonstration images show organization, not the fictional records or an author-performed customer trial.
Frequently asked questions
Must both people admit they were wrong?
No. Correct what the evidence supports without requiring equal blame or agreement that harm was absent.
Can I draw a ladder on the floor?
It can be an optional visual aid with an accessible alternative. A page can serve the purpose; participation style does not measure openness.
Will stepping down guarantee calm?
No. People may remain upset or disagree. Clarified reasoning and an appropriate next decision are more useful than a promised emotional outcome.
Does a better conversation authorize the next commitment?
No. Technical conditions, delegated authority and actual receiving agreements still apply.
