Absent but Implicit Listening in Coaching: Worked Guide
Nour
Founder, Coachful

Absent but implicit listening in coaching means hearing a difficult account while remaining curious about what gives the experience its significance. A complaint may matter because an agreement was broken, an important responsibility was threatened or a preferred way of relating was missing. The coach does not get to decide which meaning is hidden underneath it.
This guide explains the narrative idea, four original inquiry movements and a complete fictional CTO case. The case includes a rejected coach interpretation, a factual correction, an actual customer response and a review that leaves disappointment visible. It treats meaning as something to explore with the client, not an optimistic answer to extract.
Coachful is our #1 recommendation for organizing the client's optional reflection, selected action and returned coaching feedback in this process. This is an editorial workflow recommendation, not an independent market ranking or evidence that software provides narrative therapy or improves executive performance.
Understand the contrast without inventing its meaning
Michael White's narrative work is an important source for the absent but implicit. In their 2009 conceptual paper on therapeutic enquiry, Maggie Carey, Sarah Walther and Shona Russell describe experience gaining meaning against a contrasting background, including accounts of life outside a dominant problem story. Their article concerns narrative therapy and presents a practice map. It is not an executive coaching outcome trial.
For a workplace example, someone may describe a decision as a betrayal. That word could relate to an explicit promise, a valued relationship, the right to be consulted or a practical consequence for other people. Listening for a contrasting expectation opens a question. It does not establish which expectation is present or whether the person's factual interpretation is correct.
Jill Freedman's 2012 primary practice paper, Explorations of the absent but implicit, describes learning that assuming a problem's direct opposite could miss what mattered. She emphasizes exploratory, tentative inquiry rather than the practitioner's confident interpretation. That caution is useful here: dissatisfaction does not automatically mean a wish for happiness, and anger does not necessarily mean a wish for harmony.
The idea is interpretive. It does not work like a test that detects an objectively hidden value. The person may identify several concerns, reject the proposed language or find no useful meaning to explore at that moment. A practical need such as enough time to check a document need not be elevated into a lifelong identity statement.
Keep listening to the expressed problem. The relevant contrast may illuminate the concern, but it does not cancel the event or its effects. A client can identify a commitment to accurate information while still needing a misleading statement corrected. A values conversation is not a substitute for that correction.
Choose the response the client actually wants
Ask what would be useful before moving toward meaning. The person may want uninterrupted space, help checking facts, preparation for a decision or a chance to examine why the event matters. Those are different requests. A coach who insists on finding a positive commitment can become another person who does not hear the actual concern.
Distinguish acknowledgment from endorsement. “You saw a firm date after expecting delivery review” recognizes the account being brought. It does not establish that no review happened or that another employee acted dishonestly. You can take the client's concern seriously while helping them check those claims.
White's 2005 Workshop Notes, in its section on therapeutic posture, gives the person consulting the practitioner primary authorship of their account and meaning. The practitioner can still influence a conversation through questions and reflections. Translated cautiously into coaching, this supports active curiosity with the client's correction taking priority over the coach's preferred explanation.
That stance does not require a coach to accept every factual assertion or ignore harm. A client can be mistaken about who made a decision, and the consequences can still be serious. Ask permission to inspect the relevant evidence rather than equating a disputed fact with an invalid feeling.
Use four inquiry movements as an original practice aid
These four movements organize the coaching discussion below. They are an original aid, not a reproduction of Carey and colleagues' clinical map, a diagnostic instrument or a required sequence. Return to the event, pause or stop when that fits the client's request.
1. Establish the event and the present concern
Invite a specific example. What did the client see or hear, what did they infer and what is still unknown? Ask what effect matters now. A broad conclusion such as “they never listen” may contain an important history, but a recent event helps identify what the current decision actually needs.
Use tentative summaries that the client can correct. Check whether you have merged an observation with a motive. “A date appeared on the slide” and “they wanted to undermine my role” are different statements. The second might feel compelling without yet being established.
Do not demand a detailed personal history or sensitive business material to make the account legitimate. Use the minimum information appropriate to the coaching purpose. If the event raises a formal employment, legal or safety issue, identify the relevant route rather than treating interpretation as the whole problem.
2. Explore the difference that would have mattered
Ask what the person wanted to be possible or what agreement they expected to hold. Keep the answer open. They may want consultation, a clear uncertainty statement, a manageable workload or a chance to decline. Those possibilities imply different next steps.
A coach can offer a tentative phrase when useful, but should make rejection easy and then change course. If the client rejects “respect,” do not keep asking until they agree that respect is the hidden issue. Ask what their own wording makes clearer than yours.
Sometimes the answer is modest: “I needed one accurate number before sending the report.” That can be enough. Do not turn every practical frustration into a search for a noble value, an identity transformation or forgiveness.
3. Develop meaning without fixing an identity
If the client wants to continue, ask why the difference matters in this situation. They may connect it with responsibility for customers, previous experience or a way they prefer to work. An example from their own actions can give the account substance, but recalling one is optional.
Let the client choose the scope of that history. They can stay with a recent work example instead of discussing childhood, family or trauma. A past occasion may show one way they acted, not prove an unchanging trait or that the same response suits today.
Also leave room for conflict between commitments. Someone may care about honesty and keeping a relationship, or protecting a team and meeting a customer need. Clarifying that tension can be more useful than deciding that one value is their authentic self and the other is false.
4. Choose a proportionate response and a review
Compare what the client can do, what requires another person's answer and what evidence is needed before acting. A client-owned commitment does not authorize another person's work or remove practical constraints. The next step might be checking a record, correcting their own statement, requesting a decision or seeking specialist advice.
Describe the output and receiving route. Who needs to read or decide, and what will their reply establish? A sent question is not an accepted proposal. A prepared clarification is not a correction the affected person has received.
At review, ask what the facts, meaning and chosen response now look like. Keep the earlier account visible when it changes. Look for a more accurate distinction or an informed decision, not simply a warmer emotional tone. Our action and identity guide explores a related narrative distinction.

Work through a complete fictional CTO case
All people, software and commercial circumstances in this case are fictional. Mina is CTO of an analytics company; its connector is not a Coachful feature. Rowan is her coach. Joel handles the customer account, Elia owns delivery and Sana has commercial decision authority. Tari is the customer's contact.
On 24 June 2035, Mina brings a slide saying the connector will be available on 30 June. She saw it after a customer discussion. She is angry and says engineering was never consulted. Rowan first asks whether she wants to be heard or prepare a response. She chooses the response.
Rowan tentatively suggests that recognition of Mina's status may be the issue. Mina corrects that interpretation: “I do not need to approve every slide or be thanked for everything. I want customers to know what we have actually committed to. I also do not want a planning estimate turned into overtime for a team that never accepted it.”
Rowan acknowledges the correction rather than redescribing it as a wish for respect. Mina chooses the phrase “a commitment people can understand and actually accept.” When invited to explore its history, she declines a personal-history discussion. She prefers a recent work example in which a pilot date was kept separate from a full release. Rowan accepts that limit.
That earlier example does not prove a solution here. Mina identifies what she still needs to know: where 30 June came from, whether release approval exists, what the customer understood and what the commercial record says. She chooses source checking before accusing another team of excluding engineering.
Obtain the facts without assuming other people's availability
Mina asks Joel and Elia for a joint discussion. Joel cannot attend the proposed time. He offers a ten-minute asynchronous check of the slide and source message instead. Elia accepts fifteen minutes to check the current technical status. Mina accepts those bounded routes rather than recording the unheld joint meeting as an agreement.
On 25 June, Joel finds Mina's own 12 May email. It gives 30 June as a planning target, explicitly conditional on a privacy review. The slide retained the date and omitted that condition. Elia confirms that the review is still pending and no release approval or replacement firm date exists.
Sana checks the commercial record and proposed clarification. The written order does not name this connector, but she does not use that fact to dismiss what the customer may have understood from the presentation. Questions about legal obligations would require the appropriate adviser; Rowan does not determine them through coaching.
Mina now corrects her own earlier claim to Joel and Elia: “I said engineering had never been consulted. That was wrong: I supplied the conditional May estimate. The problem I need to address is that its conditions disappeared and the slide presented availability as confirmed.” Both read and acknowledge that correction. Neither is required to agree that the initial accusation caused no harm.
The concern has become more accurate without becoming pleasant. Mina still wants the customer-facing statement corrected and the team's workload protected. Her own contribution is now part of that account.
Keep a completed listening-and-decision record
| Field | Mina's completed record |
|---|---|
| Observed event | The customer slide states connector availability on 30 June. |
| Earlier interpretation | Engineering was never consulted. Source checking disproved that broad claim. |
| Client's meaning | A commitment people can understand and actually accept. Mina rejected the coach's status-recognition interpretation. |
| Own contribution | Mina's 12 May email supplied a conditional target. She corrects her inaccurate accusation to Joel and Elia. |
| Known facts and remaining limits | The slide omitted the privacy-review condition. Elia confirms the review is pending and no release date is approved. The written order does not name the connector; that does not settle every legal or customer-understanding question. |
| Chosen response and authority | Mina drafts an accurate clarification. Sana authorizes its commercial wording; Joel sends it to Tari. No new date, expansion or developer workload is authorized by Mina's reflection. |
| Sharing boundary | The operational clarification and Mina's factual correction go to their relevant recipients. The private coaching discussion and her interpretation of what matters are not forwarded as a team report. |
| Review | Check what Tari actually received and decided, whether Mina's statement was corrected and what remains unresolved. Do not count a positive phrase as proof of improved culture. |
This record distinguishes facts, interpretations, meaning and authority. It is original case documentation, not a psychological assessment or a claim that each complaint should yield these eight fields.
Complete the actual clarification and receiving decision
On 26 June, Sana authorizes the following original message and Joel sends it through the established customer account route:
Subject: Correction to the connector availability slide
Hi Tari, we need to correct the availability statement in our presentation. The 30 June date came from a planning target that was conditional on a privacy review. The slide omitted that condition and presented the date too firmly.
The review is still pending. We do not have an approved release date, and you should not plan your 6 July workshop on the connector being available. We are sorry that the slide gave a different impression.
This clarification does not change your current service or authorize an expansion. Please tell me whether you want to pause the expansion discussion or ask a factual question about the current position. We will not substitute another firm date without the necessary decision.
Kind regards, Joel
Tari reads it and replies: “I had understood 30 June as firm, and that has disrupted my workshop planning. We will pause the expansion. Please keep the current service unchanged. I do not want further connector calls until we ask.”
Joel acknowledges those instructions. Sana accepts the pause and the decision not to initiate another connector call. This is the completed receiving outcome: an accurate clarification, an acknowledged disruption and a customer decision against expansion for now. It is not restored trust, a successful release or evidence that the workshop problem has been solved.
At the 27 June coaching review, Mina says she remains angry about the omitted condition and uncomfortable about her own accusation. She also sees that seeking a broad recognition statement would not have answered the operational question she actually cared about. She retains the customer response in the review account without predicting whether Tari will return later.

Account for the conversation and its actual follow-through
Mina uses 135 active minutes: 10 preparation, 30 initial coaching, 15 requesting and handling the fact checks, 20 checking sources and completing her record, 20 drafting the clarification, 10 reading and handling its authorization, 10 sending her own correction and reading acknowledgments, 15 final coaching and 5 receiving and replying to Rowan's written comment. Her cap of 150 leaves fifteen.
Rowan uses 70 minutes: 30 initial and 15 final coaching, 15 preparation and notes, and 10 writing and sending the returned comment and reading Mina's reply. His cap of 75 leaves five. Joel uses 25: 10 source checking, 10 sending the clarification and handling Tari's response and his acknowledgment, and 5 reading and acknowledging Mina's factual correction. His cap of 30 leaves five.
Elia uses 20 minutes: 15 technical-status checking and 5 reading and acknowledging Mina's correction, within a cap of 25. Sana uses 20: 15 commercial-record and message review and 5 accepting the closure position. Her cap is twenty. Tari uses ten across reading the clarification, writing the actual response and reading Joel's acknowledgment. Her cap is ten.
The named total is 280 person-minutes. Waiting for asynchronous replies is not active effort; handling them is. The account includes all named receiving and correction work. It excludes the company's wider development and the customer's workshop preparation, neither of which is completed or costed by this coaching example.
Rowan's actual returned comment in the private client conversation is: “Your correction kept the concern about dependable commitments while changing the inaccurate account of consultation. Keep Tari's pause and the unapproved release visible. You do not need a positive ending to preserve the distinction you chose.” Mina reads it and replies: “I will retain both my correction and the customer response. I am not treating this as permission to set another date.” This written exchange is separate from the fifteen-minute final coaching conversation.
Use a team application only with an appropriate mandate
A client may want to bring a clarified concern to a team. Ask what should be shared and why. A private meaning statement is not automatically a suitable team disclosure. In Mina's case, the practical clarification does not require Joel or Elia to hear every interpretation discussed with Rowan.
If the organization later wants a working agreement about target and committed dates, obtain the relevant owners and authority. People may value dependable commitments while disagreeing about uncertainty, timing or the cost of review. Explore those real differences rather than assuming a shared value has produced a shared operating rule.
Offer a written or individual route when public disagreement with a senior person would be difficult. Do not ask staff to reveal personal values or private histories to demonstrate cooperation. The related absent-but-implicit practice guide develops another original inquiry example; neither guide authorizes an organizational intervention on its own.
Keep coaching, therapy and formal concerns distinct
The source ideas developed in narrative therapy. Here they support voluntary reflection and practical decision preparation within coaching competence. Do not use the clinical papers' questions about despair, trauma or family relationships as a ready-made workplace protocol, or present this guide as treatment for trauma or moral injury.
If the client's needs exceed the service, discuss appropriate professional support. An allegation of misconduct may require a protected reporting route or qualified legal advice. Persistent or severe distress affecting daily life may call for suitable health support. Do not make a values interpretation the condition for accessing those routes.
The current ICF Code of Ethics addresses agreements, competence, role clarity and changing value in the engagement for ICF professionals. It does not establish that an interpretive coaching exercise resolves an unsafe system or every legal duty.
Prepare and review the reflection in Coachful
- Offer a short, optional preparation worksheet. Use original prompts about the event, the difference the client wanted and the decision they want to discuss. Ask them to omit unnecessary names and confidential customer details. A person can choose conversation instead of writing.
- Explain the actual response audience. A submitted worksheet and an unshared journal page have different handling. Clients can explicitly share some journal pages; do not promise that all journal material is categorically unreadable to a coach. Keep the selected route understandable.
- Review meaning with the client. Keep observations and interpretations distinct. Record a rejected coach phrase as rejected, rather than leave it in a summary as the client's value. Do not automatically turn every sentence into a task.
- Choose only the agreed owned action. The client can request a fact check or prepare a clarification. Another person's answer remains a dependency, not a completed client action. Review the actual receiving decision at the next conversation.
- Deliver any promised comment separately. Worksheet Coach review is private to the authorized coach team, not a sent client response. In the case, Rowan uses the private client conversation for the actual comment, and Mina's read-and-reply time is included.
See Coachful's features for supporting client reflection and follow-through. The workspace organizes the agreed work; it does not infer a person's hidden values or verify an external release approval.
Frequently asked questions
Does every complaint reveal a positive value?
No. Ask what gives the concern significance and accept the client's answer, including a practical need, conflicting concerns or no useful interpretation yet. Do not impose the direct opposite of the problem.
Can the client reject the coach's interpretation?
Yes. Make correction easy and actually change course. Repeating the same assumption in gentler wording still centers the coach's account.
Should I use it when someone only wants to speak freely?
First agree what would help. Listening without a meaning inquiry may be the appropriate response. Permission to discuss an event is not permission for a personal-history exploration.
Does finding a commitment mean the client is factually right?
No. Meaning and evidence are different. Mina's concern remains significant while her claim that engineering was never consulted proves inaccurate.
How do I know the conversation helped?
Look for an accurate client-owned distinction, an informed choice or a useful completed response. Do not use a positive tone, a values label or a changed story alone as proof of performance or cultural change.
Is this a therapy method I can offer without training?
This article describes a bounded coaching adaptation and source limits. It does not provide a clinical qualification or permission to deliver treatment beyond your competence and professional responsibilities.







