Explain the purpose before scheduling
A skip-level conversation fails before it starts if people believe it is a performance review or an investigation. State the purpose in the invitation: to hear how work is going, what gets in the way, and what the executive should understand. Say who will see the notes and in what form.
Offer a small group format and a one-to-one option. Some people will not speak in front of their manager’s peers, even when the manager is absent. A mix of formats produces richer signal than a single standing meeting with whoever happens to attend.
Set the boundary explicitly: the session is not the place to raise an individual grievance that requires a formal process. Give participants the correct channel for complaints, safety concerns, and ethics reports. The assistant should have those contacts ready before the first session.
Pick a consistent question set
Use the same four or five questions across sessions so themes can be compared. Good questions ask what is working, what is slowing the team down, what the executive misunderstands, and what would make the next quarter easier. Avoid questions that invite a status report.
Leave room for an open question at the end. The most useful observation often arrives after the formal questions, when the participant has decided the conversation is safe. Do not fill the silence with a summary.
Ask about the participant’s own work before asking about the organization. People are more precise about what they experience than about what they infer. A specific example is more useful than a general impression, and it is easier to protect when the notes are written.
Capture themes, not attributions
Write notes at the level of a theme, not a person. “Three people in the claims team described the handoff to underwriting as unclear” is usable. “Maria said underwriting is a mess” is not, and it exposes the speaker if the note travels.
Record the frequency and the specificity of a theme. A concern raised once may be an individual experience; the same concern raised independently in several sessions is a pattern worth the executive’s attention. Do not inflate frequency by counting the same person twice.
Keep direct quotes only when they are essential and the speaker has agreed. A paraphrase is usually safer and often clearer. If a quote could identify the speaker through a unique detail, remove the detail or do not use the quote.
Separate signal from one-off complaints
Create three buckets: patterns that need a decision, issues that need a local fix, and context the executive should know but need not act on. The buckets force the note-taker to make a judgment rather than dumping everything on the executive.
Test a pattern against other evidence. Does it appear in engagement data, attrition, missed deadlines, or customer escalations? A single vivid story can be true and still not be representative.
The executive needs to know which is which.
Be willing to report that nothing systemic emerged. A listening program that always produces a dramatic finding is probably leading the witnesses. “The team is tired after the migration but the handoffs are working” is a legitimate and useful result.
Write a note the executive can act on
Use a one-page format: the sessions held, the themes, the evidence, the recommended action, and the owner. Put the recommendation next to the theme so the executive does not have to connect them. If no action is recommended, say why.
Distinguish what the executive can change from what belongs to a manager. A skip-level note that asks the executive to solve every local problem undermines the managers and overloads the calendar. Route local issues to the accountable leader with a date to report back.
Include a short “what I did not hear” section. If no one raised a topic the executive expected to be top of mind, that absence is information. It may mean the topic is well handled, or that people do not trust the channel enough to raise it.
Close the loop with participants
Tell participants what changed as a result of the sessions, even when the answer is “not yet.” A listening program that never reports back teaches people that speaking up has no effect. Keep the update general enough to protect sources and specific enough to be credible.
Where an issue was routed to a manager, confirm that the manager received it and has a plan. Do not disclose the participant’s identity. If the manager needs more detail, the assistant can broker a conversation with consent.
Thank participants and explain how to raise something between sessions. The skip-level is a channel, not an event. A short follow-up note with the next session date and the escalation path keeps the channel open.
Watch for retaliation and trust risk
The greatest risk in a skip-level program is that a participant becomes identifiable and suffers for it. Review notes for small-team deductive disclosure: in a team of four, a distinctive complaint can identify the speaker even without a name.
If someone reports retaliation or a protected concern, stop the listening process and route it to the appropriate function immediately. The assistant should not investigate. Document the referral and the date, and follow the organization’s policy on confidentiality.
Review the program with HR and legal before the first cycle and whenever the format changes. The questions, the retention period, and the sharing rules should be documented. Trust is easier to preserve than to rebuild, and the notes are the most likely place for it to leak.
Background sources consulted for this workflow: How CEOs Manage Time; Employment Law and Compliance; Stress Effects on the Body.