Conversational Intelligence Blind Spots: A Practical Matrix
Nour
Founder, Coachful
A conversational intelligence blind spots matrix helps a leader compare intended meaning with what another person understood. Start with a specific exchange, separate remembered words from interpretation and invite correction. Then choose a relevant action, an authorized owner and a review point.
Judith E. Glaser discussed five conversational blind spots. This guide briefly attributes those concerns and develops an original evidence-and-action record around an automotive launch misunderstanding. It is a preparation aid, not a score of intelligence, trustworthiness or brain chemistry, and not an official licensed assessment.
Understand the attribution and its limits
Glaser's January 2015 article “Conversational Blind Spots,” reproduced by The CreatingWE Institute, discusses assumed shared viewpoints, emotional context, access to another perspective, memory of one's interpretations and the meaning a listener receives. These concerns can prompt inquiry; they do not establish what a particular colleague thinks or feels.
The article includes practitioner accounts and biological explanations. A meeting observation cannot establish a colleague's cortisol, oxytocin or neural activity. Here the evidence consists of words, requested corrections, decisions and work records. The examples and matrix are original teaching material, separate from proprietary graphics, questionnaires and training exercises. Formal instruments require their owner's current permissions and administration arrangements.
Glaser's book Conversational Intelligence: How Great Leaders Build Trust and Get Extraordinary Results has a Routledge first-edition record with copyright 2014. That identifies background reading; it does not turn this worksheet into a validated instrument.
Explore five concerns without diagnosing the speaker
| Concern | What to examine | Original preparation question |
|---|---|---|
| Assumed shared viewpoint | Others may understand the situation differently. | What output does each person think we agreed? |
| Emotional context | Concern or confidence may affect interpretation. | What conditions make an answer workable here? |
| Another perspective | A strong position can obscure another person's constraints. | What responsibility am I not seeing? |
| Words and commentary | Remembered meaning may differ from what was said. | Which words can we check, and what did I add? |
| Received meaning | Intention alone does not establish understanding. | What action did my request suggest to you? |
For example, “ready next month” can mean a technical demonstration, a customer commitment or permission to spend. Agreement with that phrase need not mean agreement with all three. Ask for the expected output, evidence and date, then explain your meaning too. Clarification is mutual work, not a test of whether colleagues can guess the leader's intention.
A quiet response may reflect thinking time, uncertainty, disagreement, access needs or a wish not to answer publicly. Ask about the setting, audience and available route rather than labeling silence as fear. Likewise, imagining a colleague's concern is a hypothesis until they describe it.
Keep approximate recollections visibly approximate. “She requested a revised estimate” is different from “She said I managed the project badly.” The second may be commentary added by the listener. If there is no exact record, do not put quotation marks around an interpretation and treat it as proof of intent.
The separate blind-spots practice guide offers another application after a misunderstanding. Choose one manageable exchange rather than assigning a label to every interaction.
Begin with an actual decision problem
In this original fictional case, Mara leads an automotive supplier preparing a battery-management product. In an earlier review she said that everyone needed to be aligned on a launch next month. Commercial and engineering then prepared different plans. Mara also interrupted a testing explanation. That earlier meeting and the engineering work already completed are outside the measured account below; their time is unknown, not free.
Arun is Mara's coach. Enid owns the engineering account, Chen leads commercial planning and Dara holds the company's release-approval authority. The coach does not have that authority. Mara initially interprets the additional testing request as resistance to strategy, while Enid has only described a possible demonstration.
On Monday 6 November 2028 Arun spends fifteen minutes preparing and sending a finite coaching/review plan. Mara uses twenty minutes on 7 November, five reading and accepting and fifteen preparing and sending her selected recollection. Arun reads it and prepares for ten minutes on 8 November.
Their forty-five-minute conversation on 9 November includes this original exchange, based on Mara's approximate recollection rather than a recording of the earlier meeting:
Arun: What did alignment mean in that meeting?
Mara: I meant everyone could commit to customer availability.
Arun: What did engineering say they could commit to?
Mara: A demonstration. I treated that as the same thing.
Arun: What would help you check their position before choosing a response?
Mara: I need to ask which tests remain and what each launch option would permit us to say.
Mara's account is a starting point. The coach does not decide that Enid was misunderstood, that the product is safe or that customer release should proceed. Those questions require the appropriate people and records.
Send a request that permits a substantive correction
On 10 November Mara spends twenty minutes checking the existing meeting notes and preparing and sending this complete clarification request to Enid, Chen and Dara through their authorized operational channel:
I used launch to mean customer availability. The notes refer to a demonstration, so I may have merged different commitments. Please identify the output you understood, the evidence required and the person who can approve it. I also interrupted the testing explanation. I am sorry; please correct what I missed without treating my preferred date as an agreed release. I propose a thirty-minute review on 15 November to separate facts, recommendations and remaining options. Tell me if that format is unsuitable. No external announcement or customer commitment is authorized by this request.
No private coaching notes or confidential test files go to Arun. The request is a selected operational message, not a transfer of the coaching record. It includes both an apology and work to resolve, without demanding reassurance that the relationship is repaired.
Enid spends twenty minutes on 13 November reading the request, preparing the factual account and sending it to the other three. She rejects the customer-availability date and says no to a coach observing the technical review. Chen spends fifteen reading and replying with his commercial position. Dara spends fifteen reading the request and those accounts and returning the applicable approval conditions.
Mara uses fifteen minutes on 14 November to read all three replies, accept the observation limit and prepare and send the operational agenda. Enid, Chen and Dara each spend five reading, accepting and preparing. Arun is not invited and does not receive the technical records.
Fill an evidence, question and action matrix
Mara's original filled preparation record is below. It organizes what she needs to check; it does not classify the other participants as deficient.
| Area | Evidence or uncertainty | Next question or action |
|---|---|---|
| Shared viewpoint | Mara meant customer availability; the notes describe a demonstration. | Ask each owner to name the deliverable and its limits. |
| Speaking conditions | The preferred date preceded the request for concerns; Enid objects to external observation. | Use the authorized internal review and respect the declined observer. |
| Other perspective | Testing requirements and commercial pressure both need explanation. | Hear each account before comparing recommendations. |
| Words and interpretation | Mara treated a demonstration as a commitment to release. | Correct the record without attributing resistance or consent. |
| Received meaning | Engineering and commercial are drafting different possible messages. | Name the wording, approval owner and unresolved capacity question. |
Add the decision requested, relevant participants, permitted information, next action and review date. An empty evidence field should remain empty until checked. A matrix becomes less useful when completing every box matters more than preserving uncertainty.
Choose the conversation type for the work
In her primary Mindtools interview, recorded in 2017 and posted in 2024, Glaser distinguishes transactional, positional and transformational conversations. She explicitly recognizes useful roles for all three: confirming information, exploring recommendations and discovering possibilities. These are not ranks of employee worth, and discovery need not govern every exchange.
On 15 November Mara, Enid, Chen and Dara meet for thirty minutes. The agenda uses five minutes for the interruption repair, ten for facts, five for recommendations, five for alternatives and five to record the decision and open work.
Mara names her interruption and asks what she missed. Enid says the pressure made the earlier review difficult and remains unhappy about it. Mara listens without requiring forgiveness. They agree to hear release requirements before comparing dates. This puts the four original repair actions into practice: name the action, invite the other account, agree the process and return to the unresolved work.
Enid describes a possible controlled demonstration, while customer release requires additional testing and Dara's sign-off. Chen explains why a commercial date matters. His concern is not dismissed as poor listening. Dara distinguishes what can be discussed internally from what can be announced. They consider different demonstration scope without authorizing it as customer availability.
Understanding each explanation does not require accepting every request. The technical release remains held and the next decision concerns testing capacity. No new tests, demonstration or customer release are performed during this review.
The three-levels matrix guide develops how to change conversational purpose explicitly. Say what genuinely remains open and who decides before asking for discovery. A useful conversation can end with a clearer disagreement.
Test the written record before treating agreement as complete
After the meeting Mara spends ten minutes preparing and sending an internal V1 note. It wrongly merges demonstration readiness with launch readiness. Enid spends ten minutes on 16 November reading and rejecting it against three checks: distinguish the two events, name the approval owner and retain the unresolved testing-capacity question.
Mara uses ten minutes that day to read the correction, revise and send V2 to all three. The complete note is:
Our discussion distinguished a possible controlled demonstration from customer availability. It did not approve a customer release. Dara remains the release-approval owner, subject to the required testing and governance process. Enid will provide the technical account for the separate capacity decision; no new testing work is authorized by this note. Chen's commercial timing concern remains open. External wording requires the applicable approval before use. This is an internal planning record, not a customer promise or evidence that the product is ready.
On 17 November Enid spends five minutes reading and sending limited acceptance of the corrected record. Chen spends five reading and replying that he will not promote externally before the required approval. Dara spends ten reading and approving the internal planning wording while retaining the customer-release hold. None of these replies validates a product or authorizes the missing testing resources.
Mara uses twenty minutes on 20 November to read all three replies, prepare and send their operational close and a separate selected summary to Arun. Enid, Chen and Dara each read the close for five minutes on 21 November; no further acknowledgment is requested or sent.
Arun spends ten minutes on 21 November reading Mara's selected summary and preparing. They meet for thirty minutes on 22 November to review what helped and how Mara will approach the still-open capacity decision. Mara declines using a question-to-statement ratio as a personal target: she wants accurate definitions and decisions, not a conversation score.
Arun spends ten minutes preparing and sending this finite closing return after their meeting:
Your corrected record separates demonstration planning from customer availability and keeps Dara's release authority visible. The testing-capacity decision and Enid's concern about the earlier pressure remain open. The received corrections support a more accurate account, not a finding that trust is restored or the product is ready. Keep the selected operational actions in the company process. This coaching review is complete; it requires no further reply or new observation exercise.
Mara reads it for five minutes on 23 November and sends no acknowledgment. She has a corrected account and a next decision, not proof that all five blind spots disappeared.
Prepare the next decision without reopening every disagreement
The next testing-capacity discussion needs a different brief from the misunderstanding review. A proposed preparation template for that future discussion could contain the following fields. It is not an additional document Mara has sent or work already performed in this case.
| Field | Proposed content to verify |
|---|---|
| Decision | What testing capacity, if any, can the authorized budget and technical owners commit? |
| Evidence | Remaining test work, resource availability, dependencies and the applicable release criteria. |
| Options | Retain the hold, change demonstration scope or revise timing, each subject to the appropriate approval. |
| Constraints | No customer-availability promise before required evidence and sign-off; no assumption that colleagues can absorb extra work. |
| Receiving work | Who prepares each input, who reads it, the time they accept and the deadline for a substantive return. |
A finance owner could understand Enid's testing dependency and still reject the proposed spend. Chen could accept the release criteria while disagreeing about commercial timing. Ask for the relevant reasons and options; neither position needs to be reclassified as a conversational defect.
Bring forward corrections already accepted so people do not have to defend the same distinction repeatedly. At the same time, leave room for new evidence to change the plan. The point of the matrix is to make the next decision more accurate and workable, not to produce permanent agreement with the leader's first proposal.
Include preparation, correction and receiving work
| Person | Measured minutes | Used / allocated |
|---|---|---|
| Arun | 6 November prepare and send plan 15; 8 November read and prepare 10; 9 November coaching 45; 21 November read summary and prepare 10; 22 November review 30; prepare and send close 10 | 120 / 145 |
| Mara | 7 November read, accept, prepare and send 20; 9 November coaching 45; 10 November source check and send request 20; 14 November read replies and send agenda 15; 15 November operational meeting 30; prepare and send V1 10; 16 November read correction and send V2 10; 20 November read replies and send operational close/selected summary 20; 22 November review 30; 23 November read close 5 | 205 / 240 |
| Enid | 13 November read and send technical account 20; 14 November read agenda and prepare 5; 15 November meeting 30; 16 November read and reject V1 10; 17 November read V2 and reply 5; 21 November read close 5 | 75 / 95 |
| Chen | 13 November read and send commercial account 15; 14 November read agenda and prepare 5; 15 November meeting 30; 17 November read V2 and reply 5; 21 November read close 5 | 60 / 80 |
| Dara | 13 November read accounts and send conditions 15; 14 November read agenda and prepare 5; 15 November meeting 30; 17 November read V2 and send limited approval 10; 21 November read close 5 | 65 / 85 |
Known work totals 525 person-minutes against 645 allocated, a difference of 120: Arun twenty-five, Mara thirty-five and each operational colleague twenty. The meetings already contribute 270 person-minutes; other handling contributes 255. Earlier testing, the original meeting and unrelated business work remain outside this bounded account, not free. The difference is not whole-practice headroom or an efficiency gain.
Interrupt pressure and observe proportionately
Glaser calls escalating attempts to impose a message “tell, sell, yell.” Inspect the instruction, persuasion, pressure and response instead of treating repetition as clarity. A longer slide deck would not answer Mara's missing release question. An authorized direct instruction can still be appropriate; match the communication to the task and leave a workable route for relevant information.
Agree the purpose and audience of any meeting observation. Note whether a decision was stated, a concern was addressed and the closing account matched the discussion. Invite corrections. Enid's refusal of the coach's attendance is respected here; the coach works from Mara's selected account rather than pretending to have observed the technical meeting.
Counts of questions or interruptions may prompt inquiry, but there is no universal ideal ratio. An emergency briefing and design workshop have different purposes, and a question can contain an accusation. Informal ratings or message activity do not establish individual trustworthiness.
Permission and appropriate handling matter for notes and recordings. Repeated intimidation, discrimination or misconduct may require an organizational concern or investigation process in addition to coaching. An apology must not pressure someone to withdraw a legitimate complaint. The Acas challenging-conversations guide provides workplace preparation context; it does not replace the organization's applicable formal processes.
Use four checks during a crisis
Separate confirmed facts from uncertainty. Identify authorized decision and action owners. Give people a route to raise new information. State when the next update will occur, including who prepares it and who needs to receive it.
A cybersecurity incident, safety event or regulatory investigation belongs within designated response arrangements. A coach may help a leader prepare an accurate briefing within competence; specialists determine operational action and disclosure. Other functions can contribute without receiving unnecessary sensitive information. Openness about what is known can coexist with limits on audience and timing.
Prepare selected reflection in Coachful
Coachful is our #1 recommendation for organizing this chosen worksheet, preparation and agreed follow-through. That editorial recommendation concerns the workflow, not a trust score or neuroscientific assessment. The demo images illustrate organization rather than Mara's engineering records.
Use a short optional worksheet for the event, remembered words, interpretation, question to check and chosen action. Explain who can read the submitted response. Keep confidential technical records in the company's approved system and share only the selected material appropriate to coaching.
A private Coach review save is not a return the client has received. Deliver the selected feedback through the agreed route and account for the client's reading, as Arun does. Keep private journal takeaways separate from submitted work. Any recap needs the applicable approval, session-type and delivery settings checked against the information agreement.
Record the client's agreed action without granting the coach authority over the operational decision. Use Coachful's features to support that distinction. If disagreement persists, review resources, priorities and authority rather than repeat the same listening exercise indefinitely.
Frequently asked questions
Is this an official Glaser assessment?
No. It is an original preparation aid informed by her published concerns. Formal instruments have their own permissions, training and administration requirements.
Can I identify a blind spot from silence?
Ask what is happening and offer a suitable route. Silence can reflect thought, uncertainty, disagreement, access needs or a wish not to participate in that setting.
Does better conversation guarantee agreement?
No. It can expose a genuine disagreement and help authorized people decide with clearer information. A product-release hold may remain appropriate.
How do I know the repair was received?
Distinguish sending, actual reading and any requested reply. Use only the receiving evidence available. Limited approval of a corrected note does not establish restored trust or acceptance of a wider plan.
