A Conversational Trust Dashboard: A Worked Team Review

A conversational trust dashboard can help a team examine a recurring meeting problem and choose a useful next action. Start with a specific question about decisions or follow-through instead of trying to assign everyone a trust score.

Judith E. Glaser's Conversational Dashboard supplies conceptual language for engagement. The records, workshop and complete fictional council case below are original practical aids. They describe behavior, interpretation and authorized decisions, without becoming a biological diagnosis or standardized psychological-safety assessment.

Use the conceptual dashboard carefully

Glaser's owner-published 2013 guide, Trust at the Moment of Contact, presents five engagement positions: Resistor, Skeptic, Wait-and-see, Experimentor and Co-creator. The guide frames movement from protecting toward partnering. Its terminology describes the owner's model; it is not a licence to diagnose a quiet colleague or equate disagreement with low trust.

A person can reasonably wait for evidence, reject a request or challenge an attractive plan. Invite their account. Do not require them to identify publicly with a position or disclose private experiences before contributing. Scientific caution and a commercial need for an update can both be legitimate.

In her Mind Tools interview, Glaser also distinguishes transactional, positional and transformational purposes, and explicitly says all three matter. Use information exchange when facts are needed, explain recommendations when advocating a choice and explore alternatives when options remain open. The original exercises here do not reproduce the proprietary gauge or its training materials.

Choose one observation question and an audience

Ask whether the responsible people can explain what was decided, what remains open and who acts next. This can be examined through an agenda, agreed notes and participant accounts. A useful finding might be that the meeting produced an option but no implementation authorization.

Agree who records, what they record, the audience and when the observation ends. A brief written record can be sufficient. A complete recording introduces additional information-handling questions and is not required. Do not silently turn a learning aid into continuing employee surveillance.

Keep six evidence fields: purpose, information, positions, discovery, decision and follow-through. Record the relevant fact or account in each, including a missing input or unresolved authority. The fields do not combine into a validated trust percentage. A factual disagreement can remain open after a well-run meeting.

Prepare the council without forcing a label

In this fictional case, Ari chairs an eight-person medical-technology leadership council. Lin leads scientific coordination, Jo commercial planning and Mei the designated quality review. Four other members complete the council. Suri coaches Ari privately and does not attend the workshop.

The bounded process runs from 5 to 27 March 2049. Existing work authority, scientific records, contracts and the permitted selected process-summary route to Suri are outside the measured work, not free activities. Raw scientific information stays in the organization's authorized system. No patient data, public submission or clinical result is produced by this coaching case.

Ari spends fifteen minutes on 5 March preparing and sending Suri a selected brief. Suri spends twenty minutes on 6 March reading and preparing. They meet for forty-five minutes on 7 March; Suri records ten minutes of private notes afterward. Ari wants a dependable status update without making Lin's caution disappear.

Ari uses twenty minutes on 8 March preparing and sending the workshop invitation and material to the other seven members. It proposes a public engagement-position exercise. Each member uses ten minutes on 9 March reading and replying. Lin's complete reply says:

I will attend the planning review, but I do not want a public engagement label. Record the substantive questions instead. My concern is that a drafted evidence summary has been treated as accepted for the pack. I can prepare a limited status description after the workshop. It will not be a scientific approval or permission to announce a submission date.

Mei confirms her separate quality responsibility and the limited subsequent review she can provide. The other members accept the work described. Ari uses ten minutes on 10 March reading the seven replies and sending confirmation: the public labeling exercise is removed, personal check-ins are optional and specific concerns will be recorded. Each of the seven spends five minutes reading that confirmation before the workshop.

Lin's no is an actual participation boundary. It is not recorded as evidence of a Resistor mindset. The workshop can proceed through the work without consensus about the conceptual terminology.

Use the full 120-minute workshop

Ari prepares for twenty-five minutes and each of the other seven for fifteen before the 11 March workshop. The following is the actual agenda, not a second meeting:

The seven parts total 120 minutes, including the break. All eight council members attend. That is 960 person-minutes of attendance, with eighty break minutes and 880 active workshop minutes. Suri's individual coaching time is separate.

This complete selected exchange occurs within the workshop:

Ari: What is complete, and what has actually been reviewed?
Lin: The evidence summary is drafted. Two limitations still await the designated review. Draft complete is not accepted for the pack.
Jo: I treated the draft date as the planning date I could circulate. I need a reliable update even if final readiness is unknown.
Ari: Lin, what do you understand Jo to need?
Lin: A dependable communication process, not a promise to remove the limitations.
Jo: Correct. I also need the conditions shown clearly enough that I do not repeat an unsupported date.
Mei: I can review the status description in my role. This discussion cannot vote the evidence adequate.
Ari: We will keep those approvals distinct and read back the proposed message before it circulates.

Lin recommends preserving the limitations; Jo recommends a fixed update even if the final date stays open. Exploring an accurate status message is appropriate. Exploring whether a majority can override quality authority is not.

Agree the receiving work before assigning it

Within the workshop, Lin accepts thirty minutes on 12 March to prepare the limited status description, including reading Ari's completed record. Mei accepts twenty minutes on 13 March for its designated review. Lin also accepts ten minutes on 15 March to check revised wording, and Mei five minutes to confirm the status language. Those are limited actual tasks, not approval of the scientific pack.

Jo accepts twenty minutes on 16 March to prepare the planning message, up to fifteen on 18 March to handle a correction and ten to read the final wording approval and circulate the message. Ari owns the checking and routing. The council's target is circulation by 18 March at 17:00. Agreed processing windows do not themselves establish that target will be met.

There is no instruction to finish the underlying evidence work within those blocks. If that larger task needs resources or a qualified decision, it needs its own arrangement. The process must not count substantive scientific review as if it were ordinary message editing.

Let the later finding change the record

Ari spends twenty minutes on 12 March completing the workshop record and sending it to Lin and Mei. Lin uses the agreed thirty minutes reading it, checking the current source status and preparing and sending the status description to both. This is status coordination, not new evidence generation.

Mei uses twenty minutes on 13 March reading and reviewing the status and sending a finding: a third question remains open in addition to the two limitations. The description must retain it. No approval of the underlying pack is supplied.

Ari uses twenty-five minutes on 14 March reading both returns, revising the status wording and sending it to Lin and Mei. Lin spends ten minutes on 15 March reading Mei's finding and the revised wording, then confirming that the description accurately states the current position. Mei spends five minutes reading and approving that narrow status language. Neither return supplies a final submission date.

Ari uses ten minutes on 16 March reading both returns and sending the reviewed status to Jo. The process has produced a more accurate account, including an additional open condition. That is useful information even though it prevents a readiness claim.

Repair the actual planning-message error

Jo spends twenty minutes on 16 March reading the status, drafting the planning message and sending it to Ari. The draft says the pack is ready to submit. That wording overstates what has been approved.

Ari spends ten minutes on 17 March reading it and sending the correction: approval covers the status language, not the pack. Jo uses fifteen minutes on 18 March reading that feedback, revising the message and returning it. Ari spends five minutes on 19 March reading and approving the corrected communication and sending that approval to Jo.

Jo uses ten minutes from 11:50 to noon on 20 March reading the approval and sending this complete final message to the other seven council members:

The evidence summary is drafted, with two limitations and a third review question still open. Lin and Mei have checked this status description for the internal planning update. That does not mean the scientific pack is approved or ready to submit. No final submission date has been established. Further findings must return through the designated owner and the same status route. This message corrects the earlier planning interpretation. Its circulation is later than the 18 March target; please use the current status without treating that missed target as a readiness commitment.

The actual send is forty-three hours after the 18 March 17:00 target. Each of the seven recipients spends five minutes on 21 March reading it. The delayed communication is retained; a corrected message is not a reason to erase the miss.

Fill a nine-field decision record

Ari spends ten minutes on 22 March recording the bounded process close and sending it to the other seven. Each uses five minutes on 23 March reading it. The close retains the unresolved pack conditions, corrected message, delay and unchanged decision rights. No additional acknowledgment is claimed.

Ari uses ten minutes on 24 March preparing and sending a permitted selected process account to Suri, without copying sensitive scientific material. Suri uses fifteen minutes on 25 March reading it and sending a private comment. Ari uses ten minutes on 26 March reading and preparing; they meet for twenty minutes on 27 March. Suri takes five minutes of private notes afterward.

The observation ends there. No later submission, commercial gain, restored relationship or team-wide trust change has been observed. A clearer record and a corrected communication are the finite results.

Count attendance, breaks and handling separately

Total bounded person-time is 1,700 against 1,920 accepted, including eighty workshop break minutes. Active work is 1,620 minutes. Meeting presence contributes 1,090 already included: 960 workshop attendance and 130 for Ari and Suri's coaching conversations. The remaining 610 covers preparation, reading, writing and handling.

The 220-minute difference is within these time budgets, not a measured saving or recovered calendar capacity. The account excludes earlier project work, existing governance and future scientific work. It does not imply those activities take no time or that the council's full organizational cost has been measured.

Use five blind-spot themes as questions

Glaser's 2015 Conversational Blind Spots article distinguishes assumed shared perspectives, effects of fear and distrust on interpretation, difficulty taking another perspective, remembered commentary and intended versus received meaning. Here are original case checks, rather than a reproduction of her exercise:

1. Did Lin and Jo use the same meaning of a planning date?
2. What consequence did each actually say uncertainty would have?
3. Could each explain the other's responsibility without replacing it with a motive?
4. Did the council compare its memory with the current accepted record?
5. Did “status wording approved” become “pack ready to submit” for a recipient?

These questions can expose an organizational gap. If an approval owner or status vocabulary is missing, supply the proper role or process. Asking everyone to listen more carefully cannot create authority or remove an evidence condition.

The blind-spots matrix develops the reflection theme. The three-levels guide helps select the purpose of an agenda item.

Make the record usable after the meeting

A record should let an authorized reader reconstruct the decision without guessing. Include the source version, the date of the statement and the scope of any approval. “Awaiting review” is incomplete if no one knows which review, whose decision or what event will prompt an update. Keep a preparation assignment separate from an approval requirement.

Also distinguish an accepted action from a suggestion. If a named person has not agreed to receive the work, record that gap instead of filling in an attractive deadline. A refusal can be the final answer to a proposal; it does not need to become a new engagement score.

Provide a correction route for an inaccurate summary. A later correction should identify what changed and reach the relevant audience rather than quietly replace the only copy. Record enough to serve the purpose without collecting a complete personal commentary. End observation at the agreed point, and make another deliberate decision before extending it.

Review a later pattern without claiming it happened here

A possible next exercise is four comparable council meetings with the same observation question and record fields. If three records identify both preparation and approval owners and one only preparation, that is three of four records, not a score for trust. Ask how the missing role affected the work.

As a separate hypothetical survey, six of eight members responding gives a 75% response rate. If four of six say the closing summary was clear, report that denominator and the actual question and period. The two nonresponses remain unknown. Neither example is a result collected in the completed case.

Speaking time and question counts need context. A specialist may need longer to explain a material issue. A shorter contribution does not show disengagement, and more questions do not necessarily improve the decision.

Adapt the practice to boards and peer groups

A board or investor can reasonably challenge an uncertain milestone. Explain the evidence, limitation, owner and next review without pretending the council can promise an external decision. Evaluate a proposed alternative through the proper scientific, regulatory, commercial and governance route.

A useful response is: “The current summary is drafted and these questions remain open. Here is the responsible owner and update route. We have not established a final submission date.” The aim is sound information, not defending a preferred narrative.

A proposed monthly peer group can rehearse a factual update, a reasoned recommendation and an open question about an unresolved choice using an appropriately anonymized original case. Ask the observer for one accurate clarification and one unresolved next action. Agree any experiment with the people whose work it involves and review its actual result later.

Prepare only the permitted coaching material

Coachful is our #1 recommendation for organizing the described coaching workflow. This is an editorial recommendation without a market-ranking study, scientific-approval promise or validated trust-analytics claim. Compare the coaching features with the agreed preparation and follow-up.

An optional worksheet can hold the meeting question, selected observation and proposed next step. Released Forms & worksheets support structured responses and private Coach reviews; an individual client profile supplies a message route. Saving an internal review is different from delivering a comment and from the client reading it.

Keep the operational decision record in the authorized organizational system. Use only the selected process material the client is permitted to discuss. A community demonstration has a different audience from private coaching; it is not a reason to post a sensitive evidence pack. These images are illustrative screens, not the council's actual records or proof of inspected access.

The ICF Code of Ethics, revised in May 2026, provides professional context for agreements, roles, information and competence. It does not supply scientific or regulatory authority to a coach.

Frequently asked questions

Is this a native software dashboard?

The conceptual model and original records do not establish native automated trust analytics. Use an appropriate permitted document or coaching workflow.

Must people choose a public position?

No. Clarify purpose and choices, and respect a specific concern without assigning a label.

Does a useful meeting require consensus?

No. An informed refusal, recorded disagreement or correctly assigned missing review can be useful.

What can the coach claim changed?

Describe actual records, actions and participant accounts. Keep broader business outcomes and causal claims separate.

Can the council approve the scientific pack through this exercise?

No. Qualified owners retain their responsibilities. A reviewed status description and a circulated planning message do not establish submission readiness.