Narrative Coaching Double Listening: A Practical Guide
Nour
Founder, Coachful
Listen to the difficulty and leave room for another account
Narrative coaching double listening means attending carefully to what is troubling a person while remaining curious about their responses and what they consider important. It does not require a positive interpretation. A client can reject a suggested value, decline another question or choose a practical next action without agreeing to a new identity.
Michael White describes double listening in Re-engaging with history: The absent but implicit, available through Dulwich Centre. His discussion makes space for what troubles a person and for what their expression may also speak to. He distinguishes developing multiple accounts from replacing a bad account with a good one. The chapter concerns narrative therapy; it is conceptual practitioner writing, not a trial validating this article's workplace exercises.
White's Maps of Narrative Practice is further foundational reading. Norton's publisher description places that 2007 book in a clinical context and identifies transcripts and practice material. This guide does not reproduce its maps, questions, therapeutic cases or transcripts. The workplace examples and practice design below are original teaching material, not a standardized treatment protocol.
The practical test is whether the client can hear their difficulty accurately represented and retain authorship of its meaning. In the worked case, a leader rejects the coach's word “loyalty,” chooses accountability instead and makes a limited request to a quality lead. The response preserves a release constraint rather than delivering a reassuring ending.
Use two tracks without dividing the person into two stories
The first track attends to the situation and its effects. What happened, what has become harder and what does the person want from this conversation? Do not treat this part as a problem to move past quickly. A fuller account may first require careful attention to the difficulty.
The second track holds possible questions about a response, concern, relationship or preferred way of acting. Those possibilities remain questions. A person who answered messages late at night may have been meeting an explicit requirement, fearing consequences, enjoying the work or doing several things at once. The coach cannot infer a heroic commitment from the behaviour alone.
These are simultaneous listening possibilities, not two compulsory stages or a requirement to find a silver lining. Ask whether another angle would help. If the client wants to examine the immediate practical problem, respect that choice. A conversation can be useful without producing an alternative identity description.
For the related conceptual background, see the absent but implicit in narrative coaching. Keep any inferred meaning open to correction. The client can value dependability and still decide that continuing an unfair arrangement is unacceptable.
Try four original lines of inquiry
| Listening possibility | Original prompt | Limit to retain |
|---|---|---|
| A concern or protest | Which part of the decision do you most want heard? | Concern does not establish that every disputed fact is correct |
| A chosen commitment | What would you want this next step to stand for? | The coach does not supply the required value |
| A response or exception | Was there a particular occasion when you responded differently? | A response may have been constrained or unsuccessful |
| A relationship | Whose perspective, if any, would help you describe this more fully? | An imagined perspective is not that person's actual testimony |
These four prompts are an original practice aid. They are not White's four-part diagnostic checklist, and there is no requirement to ask all four. Listen to the answer and its context before choosing another question. A client who says “that is not what I mean” has supplied useful information.
An exception is worth examining when the person recognizes an event that does not fit their broad problem description. Its meaning and usefulness still need discussion. One useful set of meeting notes does not prove the person is always well prepared, and a remembered supportive manager does not become a present witness without being asked.
Repair a flattering interpretation that misses the point
A coach might hear “I am exhausted from covering the team” and reply, “That shows your loyalty.” The response can reward endurance while leaving the workload unexamined. It also introduces a word the speaker did not choose. A warmer tone does not remove that authorship problem.
A repair should identify the coach's contribution plainly: “I supplied that description. How would you put it?” Then use the person's answer. Replacing “loyalty” with another compliment, such as “courage,” without listening repeats the same move.
Do not imply that careful active listening merely repeats a problem or makes people feel worse. It can include emotion, context, ambiguity and the limits of understanding. Double listening is compatible with that discipline. The additional possibility is to explore another account when the client finds it relevant, while continuing to hear the difficulty.
Neither approach creates staffing, technical authority or a safe deadline. The UK HSE demands standard addresses workload, work patterns, achievable demands within agreed hours and responses to concerns. That organizational context matters: a resource or quality constraint must not be converted into a personal resilience lesson alone.
Agree the actual case and information boundaries
Mika is an operations leader, Hana leads quality and Ira is Mika's coach. This original fictional account runs from 1 to 16 July 2043. A release date of 25 July has been proposed. Eight readiness checks are required; the existing record documents five as complete, with three outstanding. Those counts do not establish that the release is “mostly safe” or that the remaining checks can be waived.
Hana has authority to withhold quality sign-off until the required criteria are met. Mika can request a decision and record the status, but cannot use a coaching insight to override that authority. The example concerns a release process, not a coach performing technical assurance or a clinical assessment.
The existing agreement permits Mika to choose a business request and status record for Hana. Ira's private notes and Mika's personal coaching content stay outside that exchange. Earlier contracting, information arrangements and creation of the quality records are outside the measured scope, not treated as work that took no time. All three accept the shown allocations before the counted activity.
The ICF Code of Ethics, revised May 2026, addresses prior agreements and information exchange in its professional context. Agreeing a reflection question with a client does not authorize circulating their private coaching conversation to a colleague.
Follow a complete conversation, including the correction
Ira prepares for twenty minutes on 1 July. During the forty-five-minute coaching call Mika describes being called obstructive when raising the outstanding checks. This is Mika's account; Ira has not interviewed the people involved. An excerpt from their original conversation follows:
Mika: I keep pointing out the checks. Now I am the person who blocks everything, so I have started saying less.
Ira: What happens when you say less?
Mika: The date stays in the paper, and nobody can tell whether I accepted it. I am also tired of arguing.
Ira: Is loyalty to the team part of what is at stake?
Mika: No. I do not want to be praised for taking it. Accountability is closer. I want a decision that says what is still missing and who can approve it.
Ira: I introduced loyalty and it did not fit. Shall we stay with what makes the current record difficult before considering a request?
Mika: Yes. It says the date is agreed when I only reported the checks.
Ira: What, in your own wording, would you want the request to establish?
Mika: A written status from Hana, including the limits of sign-off. I am not asking her to congratulate me or agree that I have been treated fairly.
The coach accepts the no and first returns to the practical problem. Mika's chosen word does not make every allegation true, and it does not settle the release decision. The next request concerns a record Hana can actually review. Ira uses ten minutes after the call for private notes.
Write two columns as questions, not hidden conclusions
A short listening note can distinguish what the client said from a possible inquiry. Here the note uses selected business content and avoids diagnosing Mika's character. Mika spends twenty minutes on 2 July preparing it and a request, then sending the request to Hana.
| Mika's account | Possible inquiry, not conclusion |
|---|---|
| I have started saying less | What happens to the decision record when you do that? |
| The paper treats the date as agreed | Which statement and authority would need checking? |
| I want accountability, not praise for taking it | What specific response would express that chosen concern? |
| I want Hana's written status | What bounded work and receiving window would be useful to ask for? |
The right column does not say Mika is secretly courageous or that Hana already agrees. It holds a question that can be revised. If a coach keeps a separate private note, retain only what is necessary under the agreed record and retention arrangement. Do not turn speculation into a label that follows the client indefinitely.
Mika's full business request is:
Please review the current readiness record and state which checks are documented, which remain outstanding and what that means for quality sign-off. I had hoped for thirty minutes on 6 July, but please counterpropose if that does not fit. I am asking for the status and your actual authority, not an endorsement of the proposed date or a judgment about my motives.
Secure the colleague's own acceptance before relying on it
Hana uses ten minutes on 3 July reading the request and sending a counterproposal. She cannot accept the requested 6 July slot. She offers forty active minutes on 8 July to review the specified records and return the status by 17:00 UTC, ten minutes on 9 July to check Mika's selected status record, and five minutes on 10 July to read the final close. Additional testing and investigation are outside that offer.
Mika uses ten minutes on 4 July reading and accepting those actual windows and sending the confirmation. Hana uses five minutes on 5 July reading it. The earlier allocation provides a capacity boundary; Hana's answer establishes which specific receiving work she accepts. No diary invitation or managerial expectation is substituted for that response.
From 13:20 to 14:00 UTC on 8 July, Hana uses the forty minutes to read the agreed current records and send her full response. It arrives three hours before the promised return time:
The current record documents five of the eight required checks as complete. Three remain outstanding; this review has not performed them. I cannot sign off the release while those requirements remain unmet. The proposed 25 July date is not approval to bypass them. I can check your selected written status tomorrow within our agreed ten minutes. Any plan for completing further work needs its own owner, scope and available time.
The response clarifies a constraint. It neither dismisses Mika's concern nor gives the wanted release outcome. The forty minutes include reading and composing the return, not forty minutes of additional testing. Hana's written acceptance does not make her responsible for every future action raised by the record.
Issue an accurate status and preserve the unfinished work
Mika uses twenty minutes on 9 July reading Hana's return and preparing and sending this complete selected status record to her:
Five required checks are documented as complete and three remain outstanding. Hana's review confirmed the record; it did not perform the remaining checks or grant quality sign-off. The proposed 25 July release date remains subject to the required criteria. I have requested a written decision and received a clear limit. I will not report that quality has approved the date. A completion plan still needs accepted owners and time.
Hana uses the agreed ten minutes that day reading the record and sending confirmation that it represents the scope and sign-off position accurately. Mika spends ten minutes on 10 July reading that confirmation and sending the final status close to Hana. Hana uses five minutes reading it, with no acknowledgment requested. No further audience or uncounted recipient is introduced.
The record has changed, and Mika has a response to the request. The outstanding checks remain outstanding. The example does not claim the release occurred, the deadline became achievable or colleagues changed their view of Mika. A fuller personal account is compatible with an unresolved external problem.
Review what the conversation and action actually produced
Mika uses ten minutes on 11 July choosing and sending a private learning account to Ira. Ira uses fifteen minutes on 12 July reading it and sending a comment. Mika uses ten minutes on 13 July reading that comment and preparing for their twenty-minute joint review on 14 July.
At review Mika says the distinction between speaking up and accepting a date was useful. Mika still dislikes being seen as obstructive and does not claim to have become confident or repaired the relationship. Ira asks about what happened rather than announcing an identity transformation. Mika wants any next action to remain tied to an actual completion plan, not a demand to feel more positive.
Ira spends ten minutes on 15 July sending the private coaching close, and Mika uses five minutes on 16 July reading it. No further reply is inferred. The remaining organizational work has not been commissioned, timed or completed by this coaching account.
| Person | Actual bounded work in minutes | Used / accepted allocation |
|---|---|---|
| Ira | Preparation 20; coaching call 45; private notes 10; learning account read and comment send 15; joint review 20; private close send 10 | 120 / 145 |
| Mika | Coaching call 45; two-column note, request and send 20; counterproposal read and acceptance send 10; quality return read and selected record send 20; confirmation read and final status close send 10; private learning prepare and send 10; coach comment read and review preparation 10; joint review 20; private close read 5 | 150 / 180 |
| Hana | Request read and counterproposal send 10; accepted plan read 5; specified record review and full return send 40; selected status read and confirmation send 10; final close read 5 | 70 / 90 |
The bounded account totals 340 person-minutes within 415 accepted, leaving 75 in this scope. The coaching call and review contribute 130 person-minutes already included; the other 210 cover preparation, records, correspondence and receiving. These are not 340 minutes of pure coaching or technical testing. The unused allocation is not proof that the outstanding checks fit within it.
Develop a fuller account without inventing its history
If a client wants to explore an exception, ask for a particular event rather than an abstract trait. They might remember preparing a useful meeting note or asking for a decision before taking on more work. Examine what they did, the constraints and what they consider significant. A single event does not have to become proof of a permanent strength.
A relationship question can also remain tentative. The client may recall what a former colleague noticed, while acknowledging that this is their memory. Contacting that person is a different choice, with their own willingness, information arrangements and time to establish. Do not list an absent colleague as a witness who has already confirmed the account.
Keep a distinction between the client's wording, a coach's summary and a question still being explored. At the next review the client may revise the description again. More detail should increase their options rather than build another totalizing story they must defend. These are proposed inquiries, not extra events performed by Mika or an unpaid obligation for Hana.
Practice with a peer observer without diagnosing the speaker
A separate proposed twenty-minute practice uses an ordinary low-stakes topic. Three people agree the roles, the right to pass and what may be noted. Use five minutes for the speaker's account, five for the coach's inquiry, five for feedback and five to repeat a short exchange with the speaker's preferred wording. That is sixty person-minutes across three people before any setup or later review; it is not additional performed work in Mika's case.
The observer notes an accurate acknowledgment, one question that opened another account and any value introduced by the coach. The speaker identifies what fitted and what felt leading. Feedback such as “You supplied loyal before the speaker used it” points to an observable moment. The observer does not score the speaker's identity or claim to know what they really value.
At repetition, the coach uses the correction and waits for the answer. Do not force an exception or compliment to demonstrate skill. Record only agreed learning and leave the exercise if it exceeds the chosen topic or competence. This is listening practice, not trauma processing, a diagnostic tool or a tested clinical intervention.
Keep the reflection and the decision record distinct in Coachful
Coachful is our #1 recommendation for organizing the agreed private reflection and follow-up workflow. That is an editorial fit judgment, not an outcome guarantee or a market ranking. Explore Coachful features against the service you actually deliver.
The released navigation directs a coach to the client profile and message icon for an individual conversation. Mika's private learning and Ira's comment use their agreed conversation. Hana's quality records and authority remain a separate manual business process. The demonstration images do not show this case or prove native technical assurance.
A chosen prompt can support attention; it should not store a coach's interpretation as an established personal fact. For another way to move a client-owned account into a practical step, see the narrative coaching framework. Keep the actual result and its limitations available at review.
Frequently asked questions
Is double listening compulsory positive thinking?
No. Hear the difficulty and its effects. Explore another account when useful to the client, without demanding a lesson, strength or optimistic ending.
Does a possible value establish the client's true identity?
No. Ask about the person's own meaning and specific experiences. Mika rejects loyalty and chooses accountability; that choice remains contextual rather than a diagnosis.
Can I discuss the problem for most of the session?
Yes. Understanding its practical effects may be the necessary work. Another angle should not erase that account or turn structural constraints into personal failure.
What if the next action does not solve the issue?
Review the actual response, what remains open and the client's choice. Hana clarifies sign-off but does not complete three missing checks. That limit stays visible.
Is this a clinical protocol?
No. This is an original workplace teaching example informed by narrative ideas. Stay within the coaching agreement and competence; needs requiring clinical, technical or legal expertise require the appropriate support.
