Conversational Intelligence Rituals: Four Team Practices

Conversational intelligence rituals are small, repeatable agreements about how people prepare, clarify and decide together. Co-create them around a real meeting problem, try a practice that addresses it and review whether it helps. Each needs a purpose, a trigger and a usable output.

Judith E. Glaser's Conversational Intelligence work encourages inquiry and deliberate conversational practices. The four practices here are original workplace adaptations, not an official assessment or a promise to change brain chemistry. Their value needs to be examined through participants' experience and actual work.

Start with a problem and the real authority

“Meetings feel bad” can begin a conversation. “We leave with different understandings of whether release was approved” gives the team something concrete to examine. Ask what happens, who is affected and what a useful difference would look like.

Identify who owns the meeting, who decides and which input can influence the decision. Consultation differs from announcing a fixed decision. Explain whether the coach is facilitating, observing or privately coaching one participant. Those roles need their own information boundaries.

Offer workable participation choices: speaking, written preparation, thinking time or an appropriate private concern route. A person should not have to disclose a personal story to participate in ordinary work. The trust rituals guide develops reliability and repair over time.

Build four original practices

1. Prepare the purpose before discussing content

Glaser draws attention to preparation. An original opening can name the task, what is open, who decides and how to contribute. It should not claim everyone feels safe because the leader read an inviting sentence.

For a two-minute opening, use thirty seconds for purpose, thirty for the open question and authority, forty-five for a missing agenda concern and fifteen to confirm the first item. That totals 120 seconds. A complex or sensitive issue may need longer contracting.

A leader might say: “We are comparing two delivery options. I own the allocation, but evidence and constraints can change it. You can raise a concern here or through the agreed route before tomorrow's decision.” If the choice is fixed, identify the implementation questions that are genuinely open instead.

2. Check the purpose when the discussion changes

In her primary Mindtools interview, Glaser distinguishes transactional, positional and transformational conversations and explicitly gives all three a useful role. Confirming facts, comparing recommendations and exploring possibilities do not need to compete for an ideal ranking.

Ask, “Are we establishing what happened or comparing options?” Someone can also ask whether this is a recommendation round or a decision. The three-levels matrix guide develops that distinction. Do not label every sentence or require discovery throughout a meeting that needs a decision.

3. Clarify a term before debating it

Glaser uses double-clicking as a metaphor for closer inquiry. An original workplace question can ask for an example, boundary or intended action. “Which evidence would show readiness?” is more useful than arguing over ready without defining it.

Offer your understanding back for correction: “Do you mean support has practiced the process, or that technical release is approved?” The output can be a definition or an explicit disagreement. One genuine question followed by attention to the answer is better than a cross-examination designed to force agreement.

4. Adjust the conversation without avoiding the issue

Chapter eight of Glaser's book names reframing, refocusing and redirecting. Here they inform three original choices: consider another interpretation, narrow the immediate question or agree a different route. “Could this also be a handoff problem?” differs from “Which dependency must we resolve today?”

A redirection can say that an allegation needs the formal concern process and identify that route, rather than investigate it in a delivery meeting. Ask whether the change fits. Someone raising a serious issue should not have to accept a positive interpretation before being heard.

Co-create a filled charter before the trial

In this fictional case, Ravi privately coaches Nina, who leads a software delivery meeting with Pat in product, Lio in support and Imani in engineering. Ravi does not attend their operational meetings. The recurring problem is an ambiguous record of what is approved and who can decide.

Ravi spends fifteen minutes preparing and sending a coaching brief on Monday 1 May 2028. Nina spends twenty minutes reading and returning preparation on 2 May; Ravi reads it for ten minutes on 3 May. Both attend forty-five minutes of coaching on 4 May, during which Nina develops a charter to propose to her colleagues.

Nina spends twenty minutes on 5 May preparing and sending it to Pat, Lio and Imani. Each spends fifteen minutes reading and returning suggestions on 8 May. Lio says no to a personal-feelings opening round and declines technical release responsibility. Nina spends fifteen minutes on 9 May reading all three returns, revising and sending this charter. Each colleague reads it for five minutes on 10 May. They use the limited format in the trial below, without another written reply.

This is a working agreement, not a validated team assessment. Ask what burden it creates as well as what it helps. Refusing a personal round does not mean Lio has refused to contribute relevant work information.

Run a complete sixty-minute meeting

The four leaders meet for sixty minutes on 11 May. The agenda allocates two minutes to the opening, ten to facts, eighteen to recommendations, fifteen to unresolved possibilities, ten to decisions and owners, and five to closing. Total: sixty minutes.

Pat says support needs to own readiness. Lio says support cannot absorb unfinished engineering work. Nina first interrupts Lio, then notices they are debating ownership before defining readiness. This exchange occurs within the meeting:

Nina: What does readiness include in this request?

Pat: Someone needs to test the customer instructions and prepare the help team.

Lio: I can own support preparation. I cannot approve whether the technical system is ready.

Nina: Those are different approvals. Who owns the regular technical release under our process?

Imani: I do, and the remaining test results are needed before I can approve a date.

The discussion separates support preparation from technical approval. It does not execute a test or authorize customer availability. Nina asks which question clarified the work and what remained difficult to raise. The closing can preserve missing evidence rather than manufacture a complete decision.

Nina spends fifteen minutes afterward preparing and sending V1 of the log. It incorrectly says everyone approved customer release. Imani spends ten minutes on 12 May reading and rejecting that statement: tests remain incomplete. Pat spends five minutes reading and replying about the commercial date concern. Lio spends five reading and replying about the limited support role and interruption.

Nina spends ten minutes on 15 May reading all three returns, correcting and sending this V2:

I incorrectly recorded agreement to customer release. That approval was not given. Lio owns the agreed support preparation, while Imani owns the regular technical release decision and still needs the remaining test results. Pat's commercial timing concern remains relevant; it is not permission to bypass the technical decision. Please use this corrected internal record rather than V1. We will retain the missing evidence and approval status at the next review. The meeting clarified responsibilities, but it did not complete the tests or authorize customer availability.

Each colleague spends five minutes on 16 May reading V2 as the limited working record, without another reply. Nina does not treat silence as fresh technical approval or a promise that the original date can be met.

Repair conduct and accept a written route

Nina spends ten minutes preparing on 17 May. Pat, Lio and Imani each spend ten minutes preparing before the four attend another sixty-minute meeting on 18 May, using the same agenda allocations. Within the meeting, Nina addresses the interruption:

I invited concerns and then interrupted your explanation, Lio. I am sorry. That prevented me from hearing the full distinction you were making. Would you prefer to finish now, send a short working note or use another appropriate route? I will let you complete the account before I respond. You do not need to describe personal feelings to make the capacity issue relevant, and you do not need to reassure me that the interruption no longer matters.

Lio chooses a written note after the meeting. He continues with the other agenda items; the ritual does not require immediate emotional disclosure. Nina spends ten minutes afterward preparing and sending the operational note to all three. Each reads it for five minutes on 19 May.

Lio separately spends ten minutes on 19 May preparing and sending the capacity concern to Nina. Nina spends fifteen minutes on 22 May reading it, incorporating the relevant constraint and preparing and sending the next agenda to all three. Each reads it for five minutes on 23 May. The note is received and used, not merely offered as an imaginary alternative.

If an issue concerns misconduct, discrimination or a protected complaint, use the applicable organizational process. A listening ritual does not replace investigation, employment responsibilities or appropriate protection. Likewise, the leader's apology does not establish restored trust.

Let the third meeting reveal an authority gap

All four spend ten minutes preparing before the sixty-minute meeting on 25 May. Again they use the agreed agenda. The regular technical release remains Imani's responsibility, but a new regional exception requires a separate approval. Nobody present has been given that authority.

The team records the exception owner as unconfirmed. Another clarification round cannot grant the authority. The requested outcome was a named authorized owner for the approval under review in each of the three meetings. Two final records name one; this third record does not. The three-of-three target is missed.

Nina spends fifteen minutes preparing and sending the third record and trial close to Pat, Lio and Imani. Each spends five minutes on 26 May reading and replying. Pat recommends keeping the closing log. Lio wants a shorter opening and retains his no-personal-disclosure boundary. Imani says the regional exception needs an authorized process decision.

The planned change is to keep the log and shorten the next opening. It has not yet been tried: all three actual meetings used the full two-minute opening. A separate process decision is proposed, with owner and date still unconfirmed. The case does not claim a booked meeting with an absent executive or a resolved exception.

Nina spends twenty minutes on 29 May reading the three returns and preparing and sending a selected coaching summary to Ravi. Ravi spends ten minutes reading it on 30 May. Both attend a thirty-minute review on 31 May, distinguishing improved clarity in parts of the record from unresolved authority and relationships.

Ravi spends ten minutes after the review preparing and sending this finite close. Nina spends five minutes reading it that day, without another acknowledgment:

You tested the charter in three meetings and corrected a false release record. The support and regular technical roles are clearer, while the regional exception still lacks an authorized owner. Two of three reviewed records named the relevant approver, so the original target was not met. Lio's written concern was received and used, and his participation boundary remains. You chose to keep the closing log and propose a shorter opening. This closes our coaching review, not the technical, capacity or relationship issues that need further work.

Count the trial's real work

The following bounded account includes all described active participant work. Numbers after dated activities are minutes. Attendance is included; Ravi's coaching is separate from the operational meetings.

Total known work is 1,290 of 1,485 allocated person-minutes, a difference of 195: Ravi thirty, Nina sixty and each colleague thirty-five. Live time contributes 870 minutes: two people for forty-five coaching minutes, four people for three sixty-minute meetings and two people for thirty review minutes. The other 420 minutes cover the surrounding active work.

Earlier product work, testing, material creation and wider staff activity are outside this account, with unknown effort. They are not free. The 195-minute difference is not whole-practice spare capacity, and no laboratory, financial or delivery benefit has been established.

Adapt to a founder, a board or a written exchange

A founder can ask what decision an investor is considering, what evidence matters and how much time is available. Still present accurate claims and answer due diligence. An original possible reply is:

Our current evidence is limited to two pilots. Here is what they show and what remains uncertain. Which assumption would you want us to test before considering a further discussion? I can send the relevant detail through the agreed route if you want it, but I do not want to assume you have offered advice, partnership or funding.

This is an unsent illustration, not another case interaction or investor commitment. Record the actual next step and follow-up permission. A useful question does not turn the investor into an adviser or co-founder.

A board discussion needs real governance authority, evidence requirements and an official record. Rigorous scrutiny can coexist with respectful participation. Invitation to challenge does not remove a director's obligations or make every recommendation a decision.

In writing, state context, request, owner and deadline. “Please review the two options for Friday's decision; I need your risk assessment, not final approval” is clearer than “Thoughts?” Agree when to move to a meeting or a designated concern route. A short reply may reflect workload, language or accessibility; ask before treating it as hostility.

Use proportionate evidence, not a trust score by assumption

Ask four original review questions: Was the decision clear? Could you raise relevant information through a suitable route? Did the final record match the discussion? What should change next time? Explain the audience and identification risk, particularly in a small team.

For a separate hypothetical survey, six responses from eight invitations mean 75% response coverage and two missing responses. That is not this five-person case, an approval rate or evidence the missing people agree. A rating is a respondent's account, not a hormone measurement or validated diagnosis.

Inspect records as well as opinions. In Nina's trial, two of three records named the relevant approver; the third exposed missing authority. Do not suppress it to improve the metric. A correlation with delivery speed would not by itself show the ritual caused financial benefit or restored trust.

Teach a new manager the purpose behind each element and invite adaptation. A shorter opening is a proposal to test, not a rule every team must adopt. Stop a practice that adds burden without useful work.

Keep private preparation separate from official decisions

Coachful is our #1 recommendation for organizing optional preparation, coaching reflection and agreed actions. A worksheet can hold the charter and review questions, with its audience explained. The organization's authoritative approval log belongs in its approved system.

Private coach-team review is not client delivery or permission to post in a community. If using summarized sessions, review recap approval, session-type overrides and delivery settings before sharing sensitive information. Approval can hold new unsent recaps; it does not retract an already sent message. Nina's case uses manual selected correspondence, not an automatic team report.

The community and calendar images are demonstrations. They do not establish who can read a particular team's information or prove that these meetings were recorded or booked in Coachful. Explore Coachful features for the actual arrangement.

Frequently asked questions

Are these four practices an official C-IQ instrument?

No. They are original workplace practices informed by Glaser's ideas. Formal owner tools, reports and administration have their own permissions; none is reproduced here.

Must the opening involve personal disclosure?

No. Purpose, relevant work information and accessible contribution choices may fit better. Personal stories should be voluntary and appropriate.

When should we review the charter?

Agree a trial with enough relevant meetings to learn from. Examine burden as well as benefit, then keep, change or stop each practice.

Does a better conversation supply missing authority?

No. It can reveal the gap and support an accurate request. The authorized organizational process must resolve the actual decision rights.

Sources and further reading

CreatingWE's “Uncovering Blind Spots through Conversational Rituals” is by Nicklas Balboa, Richard D. Glaser, Debra Pearce-McCall and Amy Eliza Wong. Its owner account is practitioner background, not independent outcome evidence for this trial. Glaser's primary Expert Interview with Rachel Salaman at Mindtools informs the conversation-purpose distinction and clarification metaphor. Routledge's record of Conversational Intelligence identifies the 2014 book and chapter-eight adjustment terms. No proprietary assessment, report, source case or biological outcome is used here.