Co-Creating Trust Rituals: A Conversational Intelligence Guide
Nour
Founder, Coachful
Co-create trust rituals by agreeing how people will explain uncertainty, clarify requests, keep commitments and repair a missed agreement. Start with a recurring situation where people need to rely on each other. Choose a small practice, define what it should produce and review whether it makes the work clearer.
Judith E. Glaser's Conversational Intelligence work encourages deliberate conversational practices and shared meaning. The charter and examples here are original adaptations. They help a team discuss reliability and participation without turning a meeting into a test of loyalty, personal disclosure or somebody's biology.
Define what people need to rely on
Ask a concrete question: “What do you need to know or receive from this working relationship to make your next decision?” Answers may concern timely information, an accurate status, a chance to question a proposal or a clear route for an unresolved issue.
Trust can differ by task and relationship. Someone may rely on a colleague's technical work while needing clearer notice of schedule changes. Discuss the specific agreement rather than demand that everyone declare complete trust in the team.
Identify the people who can make the relevant decisions. A coach can facilitate a discussion; they do not acquire authority to approve a product, change employment obligations or waive a professional requirement. Explain the purpose, participants and information boundaries before collecting examples.
The conversational rituals guide gives a broader meeting-design process. This guide focuses on commitments and what happens when they are difficult to keep.
Use three conversation purposes deliberately
Glaser describes transactional, positional and transformational conversations. In her primary interview, she explains that all three are useful. A team can confirm a fact, compare recommendations and explore a new option within one working discussion.
For a risk review, the factual part might establish which evidence is available. The recommendation part lets each owner explain their assessment. The discovery part can examine a smaller pilot or a different sequence when the first proposal does not meet the requirements.
State the purpose when it changes: “We have heard the recommendations. Is there an option that addresses both constraints?” Exploration does not remove specialist approval or require consensus where a named person must decide.
Build four practical trust rituals
1. Prepare the agreement before the agenda
Before a sensitive meeting, clarify the question, what is open to influence, who decides and how people can contribute. Invite relevant agenda concerns without requiring a personal vulnerability story.
An original two-minute opening could give thirty seconds each to purpose, authority, missing information and participation routes. For example: “We need to decide what is ready for review. The risk owner retains the approval. Please identify missing evidence or constraints; if a detail cannot be shared in this room, name the appropriate route.”
Ask whether that process fits. A participant may need the written proposal in advance, more time or a suitable private channel. A brief opening can establish an agreement, while actual conduct determines whether people can use it.
2. Clarify the meaning of a loaded word
Glaser uses double-clicking as a metaphor for looking inside an apparently familiar term. Ask for the action, evidence or example behind words such as ready, responsible, urgent or disciplined.
A useful exchange is: “When you say the review is complete, does that mean the documents were submitted, assessed or approved?” Offer your own understanding too, then invite correction.
The output should be a usable distinction. If people disagree about an approval requirement, record the difference and identify who can resolve it. A more agreeable phrase should not conceal a real condition that still has to be met.
3. Agree a conversational pause and return
Any participant can be offered a simple pause request: “I am losing track of the question. Can we stop and clarify what needs deciding?” The team agrees how to respond and how the work will resume.
A pause might mean quiet thinking, a short break, a written restatement or moving a sensitive issue to the proper route. Ask what helps rather than prescribe breathing, eye contact or a fixed period as a biological reset. People can choose an accessible alternative.
Include a return condition: the facilitator restates the issue, the person who was interrupted can finish if they want, and the team confirms the next step. If the discussion cannot proceed appropriately, agree an owner and date for the unresolved work.
4. Review commitments after the event
At an agreed point, ask what was promised, what happened, what changed and what needs repair. Include successful coordination and missed expectations. The aim is to improve an actual agreement, rather than produce an appreciative account regardless of experience.
A leader might say: “I said the assessment would be available Tuesday. It was not, and I did not update you. Here is the current position. What effect did the delay have, and what notice would be useful next time?”
The next agreement could specify an earlier status update, a smaller deliverable or a different owner. An apology does not require the other person to say the impact was minor or that trust is fully restored.
Create a risk-and-product working charter
Liv and Omar are fictional leaders in a financial-technology company. Liv owns a defined risk review; Omar coordinates product planning. Their meetings repeatedly confuse submission of evidence with permission to launch.
The following original charter is a draft for the actual authorised owners to adapt. It does not substitute for legal, regulatory, security or technical approval.
| Charter field | Proposed agreement |
|---|---|
| Shared purpose | Give each owner usable evidence and an accurate decision status |
| Product contribution | Omar supplies the scoped proposal, intended users, dependencies and requested date |
| Risk contribution | Liv identifies the review requirements, missing evidence and authorised decision route |
| Meaning of submitted | Materials received; no approval implied |
| Meaning of reviewed | Assessment completed within its stated scope; decision or outstanding conditions recorded |
| Meaning of approved | The relevant authorised owner has granted the specific permission under the actual process |
| Notice of delay | The responsible owner updates the agreed recipient before the promised date when possible |
| Clarification route | Either can ask which requirement, decision or evidence is being discussed |
| Disagreement | Record the specific difference and take it to the appropriate decision owner |
| Information | Restricted material remains in approved systems; wider notes contain only permitted references |
| Review | Trial the coordination agreement for three relevant reviews, then revise it |
A charter becomes useful when it changes a hand-off. Both leaders need a practical way to say that a commitment cannot be met, without turning a changed date into an unspoken approval.
Work through a complete clarification dialogue
Omar says the product is ready because the review pack was sent last week. Liv says it is not ready because evidence about one user group is missing. The facilitator asks them to identify the status rather than debate who is blocking progress.
Facilitator: What happened last week, and which decision did it complete?
Omar: We submitted the pack. I assumed the launch date was now confirmed.
Liv: Submission began the review. I had not approved that date.
Facilitator: What information would let the next decision happen?
Liv: The intended user group needs to be defined, and the authorised specialists need to assess the relevant evidence.
Omar: I can provide the user definition. I need a realistic review sequence before promising a customer date.
Facilitator: What will each of you confirm, and what remains outside this agreement?
They record a product action, an assessment dependency and a date for a status update. The launch remains subject to the actual approval process. Their useful result is a clearer request and sequence, rather than an asserted reduction in approval time.
Use a forty-five-minute working review
An original agenda uses five minutes to confirm the request and authority, ten to check evidence and status, ten to explain recommendations or constraints, fifteen to compare feasible next routes, and five to record owners and dates. Total: forty-five minutes.
Before closing, ask each owner to explain their commitment in their own words. Liv might promise to identify missing evidence, while Omar promises to supply the defined user scope. Neither should be recorded as promising a decision that depends on someone else.
If the discussion concerns an allegation or a requirement outside the group's authority, use the designated organisational process. The working review should not become an improvised investigation.
Check five common blind-spot areas
Glaser's published blind-spot discussion concerns assumed shared perspective, emotional context, taking another perspective, remembered interpretation and meaning received by the listener. Use these as five checks on the charter's operation.
For Liv and Omar, ask: Did both mean the same review status? What made the request difficult to answer? Which responsibility did the other person need understood? Which remembered words can be checked? What action did the recipient think was requested?
These questions support inquiry, not a label for a difficult colleague. The blind-spots matrix guide develops the five areas and a separate evidence record.
Agree three hybrid communication rules
First, include context in a written request: the decision, version, owner, deadline and kind of response needed. “Please identify missing evidence by Thursday; approval follows separately” is clearer than “Can you sign this off?” when sign-off is not the intended action.
Second, choose a channel by the task and people's needs. Clarify a confusing sentence in writing when that works. Offer a live or audio conversation where useful, with an accessible alternative and appropriate permissions. A compulsory voice call can exclude someone or leave an inadequate decision record.
Third, distinguish working connection from required disclosure. An optional relational check-in may help colleagues understand working preferences. It should not require private health, family or emotional detail, and it does not replace the information needed for a decision.
External document permissions remain their own controls. Sharing a link in a coaching workspace does not alter who can open the underlying business file.
Observe reliability without creating a trust score
Agree a small observation set, such as whether the request identified an owner, whether a status update arrived as promised and whether unresolved conditions remained visible. Ask participants what the record misses.
In an illustrative trial, three status updates are promised. Two arrive on the agreed date; the third owner notifies the recipient beforehand and agrees a revised date. Report those events separately. The record shows how commitments were handled; it does not calculate a percentage of interpersonal trust.
Participant feedback can add context. A brief response may mean the process is clear, the person is busy or the question is unsuitable. Ask rather than infer distrust from message length, app activity or a rating. Obtain appropriate permission before recording or using identifiable meeting material.
Make the next decision from the review
After three reviews, Liv and Omar find that their status labels are useful. They also discover that a specialist approval queue, outside either person's control, is the main scheduling constraint. They keep the charter and ask the responsible owner about prioritisation and capacity.
The next task is to obtain an authorised scheduling decision, not intensify the trust ritual. A better hand-off can reveal a real resource problem rather than solve it. Record that distinction when reviewing the coaching work.
When introducing the charter to new leaders, explain its purpose and invite adaptation. Review actual behaviour and outcomes without treating enthusiastic participation as evidence of trust or readiness for promotion.
Prepare and review the charter in Coachful
Use a suitable resource or optional worksheet for preparation. Explain who can read submitted responses and keep sensitive risk or product evidence in the organisation's approved system. Record agreed coaching follow-through through the normal client-plan workflow.
A custom coaching flow can offer a short reflection when its audience, display and reminders are configured appropriately. Keep private journal takeaways separate from shared responses. Before a recap is shared, check its applicable approval, session-type and delivery settings against the agreed audience.
Frequently asked questions
Is a trust ritual a validated assessment?
The practices and charter here are original coaching aids. A formal instrument has its own evidence, permissions and administration requirements.
Must a pause last fifteen minutes?
Choose a useful response with the participants and agree how the work resumes. A fixed duration does not establish anybody's physiological state.
Can listening replace challenge?
Listening helps clarify what is being challenged. People can understand another perspective while still questioning evidence, declining a proposal or using a formal concern route.
Sources and further reading
Judith E. Glaser, primary Expert Interview with Rachel Salaman, Mindtools. Conversation purposes, shared understanding and clarification practices.
Glaser, “Conversational Blind Spots,” January 2015; The CreatingWE Institute, “Uncovering Blind Spots through Conversational Rituals.” Framework attribution and practice context, not independent evidence of hormonal or financial effects.
Explore Coachful's features to organise preparation, shared review and agreed follow-through.
