Skip to main content
Steady at the Top
← All articles

How to run a CEO listening tour that changes decisions

A CEO listening tour should change what you believe and what you decide. Ask comparable questions across organizational levels, keep a contradiction log, and verify important accounts against the work. Close the loop by explaining what you learned and which decisions changed.

Psychological safety is a shared team belief that taking interpersonal risks, including reporting errors, is safe. Edmondson introduced the construct in her 1999 study: Psychological Safety and Learning Behavior in Work Teams. A listening tour can invite such reports, but the invitation does not establish that employees expect protection. Trust concerns reliance on a particular person. Psychological safety concerns the interpersonal consequences people expect when they speak within the group.

A private moment that makes the issue visible

Composite scenario, not a client case: You sit in the car after the final site visit, listening to a voice message from home asking when you will arrive. Everyone at the company has been polite. The executive team says the rollout is working, while supervisors describe handwritten workarounds. You have collected hours of conversation and still lack a way to compare them.

Use the research within its limits

Vroom and Jago’s 2007 account examines situational differences in leadership and decision participation: Vroom and Jago (2007): The Role of the Situation in Leadership. Use a listening tour to locate information that the current decision process lacks. A supervisor’s account of an abandoned request can answer a different question from an executive’s approval report. The proposed contradiction log helps compare those accounts. It is an editorial working tool, not a validated research instrument or a promise that listening alone improves delivery.

State the decision before discussing personalities

The tour needs a question set and a decision it can inform. Choose a live operating problem. Tell participants what you can protect, what you cannot promise, and how their information will be used.

Use the listening-tour contradiction review

  1. Ask about a recent event. Use: Walk me through the last customer commitment that failed. Ask for the sequence, the handoffs, and the information each person had. Ask what happened immediately before and after the missed commitment. Establish which part of the sequence the interviewee observed personally.

  2. Use comparable prompts. Ask every group what prevents the next successful delivery, what the senior team misunderstands, and which routine they would test changing first. Keep the central question consistent while allowing follow-up about the person’s actual task. A fixed script should not prevent clarification of an unfamiliar handoff.

  3. Keep contradictions intact. Log the differing accounts and their sources without immediately choosing a winner. Distinguish a factual discrepancy from different experiences of the same process. Mark each account as observed, reported, or inferred. Two people can accurately describe different stages while appearing to contradict one another.

  4. Verify one material contradiction. Trace a relevant order, approval, or escalation through records and the people involved. Share only the details necessary to establish what occurred. Select the contradiction that would change the recovery decision. Obtain permission and appropriate access before using a named case or private record.

  5. Report a decision consequence. Tell participants which assumption changed, what action follows, and what remains unresolved. Explain why a suggested change will not proceed when that is the decision. Explain a rejected suggestion as well as an adopted one. Participants should not have to infer whether an unanswered proposal was considered.

Ask questions that produce a traceable account

Start with a recent event connected to the recovery problem. “What gets in the way?” can open the conversation, but follow it with a request to reconstruct the last instance. Ask what the person received, what they needed to do, and where the work went next. Clarify which document or message would let someone check the account. Avoid turning an interview into a test of how fluently the participant can describe the company.

Use prompts that expose different boundaries. Ask executives what their report counts and supervisors what happens before a case enters that report. Ask customer-facing staff when they first learn that a promise cannot be kept. Ask the receiving function what information it must reconstruct. These are proposed questions, not assumptions about which group has the truthful story. Each participant may see a different segment of the same sequence.

Leave a place for an account that does not fit your emerging explanation. If most interviews point to slow approval, seek a case that moved quickly and still failed. Ask what differed. Do not demand a dissenting story for balance when the person has none. Your obligation is to make contrary evidence usable if it appears, rather than requiring the tour to produce either agreement or a particular quantity of disagreement.

Keep the contradiction log separate from the people list

Write the competing statements in neutral terms. One entry might read: “Executive report records approved exceptions; supervisors describe requests withdrawn before approval.” The question is what each measure includes. It is not yet whether one group is hiding failure. Put the relevant records, the decision affected, and the verification owner beside the entry. Limit names to what the verification requires.

Distinguish an inconsistency in timing from an inconsistency in responsibility. Two interviewees may agree that a request waited but disagree about who was supposed to answer. In that case, inspect the approval instruction and the communication received by each person. If the responsibility is unclear, the repair may be a decision-right change. If responsibility was clear but the request never arrived, examine the handoff. A general communication workshop would leave both questions unresolved.

Keep impressions about credibility out of the factual field. “Seems defensive” does not explain whether a timestamp is wrong. Ask for the specific discrepancy and evidence that could settle it. If accounts cannot be reconciled, record the unresolved point without choosing the person closest to the CEO as the default authority. A contradiction log should preserve the question long enough for the work to answer it.

Verify without exposing the source unnecessarily

Before following up, decide what information must be shared and with whom. You may be able to ask about an abandoned-request process without identifying the employee who described it. If a named case is necessary, use the appropriate review route. Do not offer absolute confidentiality while planning to repeat identifiable details in an executive meeting. Explain limits accurately before people decide what to share.

Separate investigation of a process from review of a serious allegation. Ask the responsible specialist how to handle an account involving possible misconduct or protected information. A listening tour is not a substitute for the organization’s formal process. Preserve the material through that process and continue the tour’s operational questions without inviting other participants to speculate about individuals. Keep the purpose of each conversation clear.

For an ordinary handoff discrepancy, propose tracing a permitted sample with the people who handled it. Ask each person to describe what they knew then, not what is obvious now. Compare records with the original interview account. Give the contributor an opportunity to correct your summary. The aim is a usable reconstruction that can change a decision, rather than a polished quotation that supports the story you planned to tell.

Close the loop with a decision, a limit, or a next check

At the end of the tour, organize findings by the decision they inform. Explain which assumption changed and what action follows. If you chose a narrower test, identify why the evidence supports that step. If a suggestion cannot proceed, state the constraint you can share. Avoid describing every comment as valuable while leaving participants unable to identify any consequence of the time they gave you.

Use a hypothetical closing note to test clarity: “The tour identified requests that never enter the approval count. We will examine that intake boundary before changing the approval target.” This makes a limited commitment. It does not announce that all reporting is unreliable or that the interviewees proved the cause of every delay. Keep your conclusion proportional to the verified cases and name the work still open.

Ask whether the proposed correction reached the people who described the problem. A revised executive dashboard may not help the supervisor whose request still lacks a recipient. Invite a concrete follow-up about that gap. Do not require employees to judge whether the entire tour succeeded. They can tell you whether the particular obstacle remains and which subsequent case illustrates it.

The useful output is a better account of the work and a visible decision consequence. Meeting totals, attendance, and appreciative comments can describe participation. They cannot establish that a critical contradiction was resolved. Keep the log small enough that every material entry receives an owner and a disposition. A shorter tour that changes a consequential choice can serve the recovery better than an expanding schedule without a verification plan.

Put the boundary into words

I am looking for where our account of the business differs from the work. Tell me about the last example. I will verify material facts and report what changes. I cannot promise that every suggestion becomes a decision.

Work through a bounded example

Hypothetical application: Executives report that exceptions are rare because their dashboard counts approved requests. Frontline employees describe requests abandoned before approval. The tour reveals a measurement boundary. The CEO tests an intake record before concluding that employees are resisting the standard process.

Check the failure mode before scaling

Do not use a listening tour as covert performance surveillance. Avoid naming a junior employee as the source of a challenge in a senior meeting. An invitation to speak does not itself establish that the channel is safe.

If an interview reveals an immediate safety, legal, or customer exposure, use the approved escalation route rather than waiting for the tour’s closing report. Tell the participant what information must reach the responsible specialist and avoid promises you cannot keep. Record the containment action separately from conclusions about the wider process. A serious account needs verification and appropriate handling, not circulation as an illustrative quotation.

Review the work, then revise the arrangement

Review the contradiction log and the decisions it affected. A tour with many meetings and no changed assumptions needs a narrower question or stronger verification.

The APA’s 2018 role-ambiguity entry describes unclear expectations attached to a position: APA Dictionary of Psychology: role ambiguity. When two interviewees disagree about who should approve an exception, establish the actual decision right before calling either account evasive. Uncertainty about responsibility differs from disagreement about a recorded event. Your log should allow both types of finding, because they require different follow-up.

Connect this decision to the next one

Use the returning-founder playbook to connect tour findings to the recovery mandate. Prepare the separate departing-CEO handover for information unavailable in site interviews. Address urgency through the cash-pressure leadership discussion. If comparable questions produce little usable information, inspect the employee-silence warning signs before adding more meetings.

Sources

Steady at the Top