Skip-level meeting agenda

TL;DR: A skip-level meeting is a diagnostic conversation between a senior leader and the direct reports of their direct reports. Most skip-level meetings underdeliver not because the intention is wrong, but because the structure is. This guide gives you a modular agenda that fixes that, from intent-setting through follow-through. You'll also find scripts for handling sensitive feedback. Granola transcribes device audio in real time, letting you jot high-level keywords while the AI notepad fills in the context.

Most skip-level meetings underdeliver not because the intention is wrong, but because the structure is. A senior leader schedules time with a junior employee, arrives with no clear agenda, does most of the talking, and walks away with a polished, rehearsed picture of how things are going. That's not organizational intelligence. That's theater.

This guide gives you a modular agenda built on established people-management practice, drawing on active listening research, psychological safety frameworks from Google's Project Aristotle and Amy Edmondson's work at Harvard Business School, and conflict-resolution methodology from the Harvard Program on Negotiation. The framework prioritizes listening, builds genuine trust, and produces insights you can act on without exposing the people who shared them.

Skip-level agenda: quick-start guide

What is a skip-level meeting?

A skip-level meeting is a direct conversation between a senior leader and the direct reports of their direct reports, bypassing one layer of management in the org chart. The middle manager does not attend.

The purpose is diagnostic, not evaluative. You are not assessing the employee's performance, policing their manager, or gathering ammunition for a personnel decision. You are trying to understand the lived experience of people doing the actual work: what's blocking them, where communication breaks down, and what organizational patterns are invisible from the top floor. This distinction matters because employees often walk into the meeting assuming it's evaluative.

Why skip-levels matter

As organizations grow, information often gets filtered through management layers before reaching senior leaders. Skip-levels are the mechanism for recovering unfiltered signal before it costs you a major product decision, a retention crisis, or a cultural drift you didn't see coming.

A common guideline in active listening practice is for leaders to aim for the other person to do roughly 80 percent of the talking in feedback-oriented conversations. That ratio transforms what would otherwise be a status update into a genuine diagnostic session.

Some leaders argue that skip-levels are unnecessary when middle managers are doing their jobs well. That's a reasonable position, but it misses what skip-levels actually diagnose: systemic communication gaps that middle managers themselves may not see because they are inside the system.

When to schedule them

Frequency depends on organization size:

• At 20 to 50 employees: Informal, monthly or bi-monthly one-on-ones can work well. These conversations help leaders stay connected without heavy process overhead.
• At 50 to 100 employees: Structured quarterly conversations of 20 to 30 minutes can focus on organizational health rather than project status.
• At 100 or more employees: Meeting each person at least once per year, with flexibility for small-group sessions when schedules require it. Consider sending a written explanation to the broader team before scheduling individual conversations. Explain what skip-levels are, why you are running them, and what will and won't be shared afterward.

Opening and setting intent

The opening minutes shape whether the conversation produces honest feedback or carefully rehearsed answers. Employees who walk in anxious will give you the version of reality they think you want to hear.

Establish psychological safety

Open with a clear statement that the meeting is for your learning, not a performance review, and invite the employee to drive the agenda. A common guideline in active listening practice is an 80/20 ratio: the employee should do roughly 80 percent of the talking in feedback-oriented conversations. Then stop talking. The employee needs a moment to recalibrate from the evaluative frame they walked in with.

The most important heuristic here is the 80/20 ratio. If you find yourself speaking for extended periods during the diagnostic phase, you've likely drifted off course.

Explain confidentiality boundaries

Confidentiality in skip-levels requires a clear framework. Give the employee a specific, honest explanation of how you will handle what they share. The working principle is to focus on systemic themes rather than individual attribution and to aggregate insights from multiple sessions before any feedback reaches middle managers.

Set expectations for follow-up

Feedback without a visible response is worse than no feedback at all. Before you move into the diagnostic phase, tell the employee specifically when and how you will follow up on themes from the conversation. One approach: "Within two weeks, I'll share a brief note on the one or two things I'm actively working on based on what I'm hearing across these sessions." That commitment changes the meaning of the conversation entirely.

How the team is doing

These questions surface dynamics the middle manager may be too close to see.

Workload and capacity

• "What's consuming the most time on the team right now that isn't the most valuable use of that time?"
• "Are there deadlines on the team's plate that feel unrealistic from where you sit?"
• "What would you stop doing if you could, to make room for more important work?"

Listen for patterns across sessions. When multiple people describe the same overhead process as a time drain, that signals a systemic issue rather than individual preference.

Morale and engagement

• "What part of the work has felt most energizing recently?"
• "What's been the most frustrating?"
• "How does the team feel about the direction the company is heading?"

Consider asking in that order: start with the positive to build rapport, then move toward friction.

What's working and what's not

Process and workflow effectiveness

Two scenarios come up frequently in skip-levels, and both require careful handling.

Scenario A: The manager is perceived as a micromanager. Use neutral inquiry to gather a specific example, then frame systemically: acknowledge there may be an expectation mismatch around autonomy and propose exploring delegation boundaries for the whole team. This approach, informed by conflict resolution methodology at Harvard PON, keeps you from adjudicating between employee and manager in the moment.

Scenario B: The manager is perceived as unresponsive. Acknowledge the frustration, gather specific facts about timeline and what was needed, then frame your response systemically. The principle is the same: gather objective patterns across multiple sessions and address them structurally rather than in the moment.

Tools and resources

• "Does the team have the software and documentation it needs to execute on its priorities?"
• "What tool or resource, if you had it today, would make the biggest difference?"
• "Is there anything the team is working around that a proper solution would fix?"

These questions often surface inexpensive wins: a missing integration, a documentation gap, or a process step that nobody owns.

Communication and alignment

• "When you're making a decision on your own, how clear are you on what the company's priorities are?"
• "Where do you feel like you're working without enough context?"
• "What's something the leadership team should know that you're not sure has reached us yet?"

That last question gives the employee explicit permission to share information they may have been holding back because they assumed it wasn't welcome.

Career growth and development

The questions below draw on career development frameworks; adapt them to your context and the employee's trajectory.

Showing genuine interest in an employee's trajectory builds trust that improves the entire conversation.

Learning opportunities

• "What skills are you most focused on developing right now?"
• "Are there stretch projects or areas of responsibility you'd like to take on?"
• "Is there anyone in the organization you'd benefit from spending more time with?"

These questions signal genuine investment and give you actionable information: a specific mentorship connection or project assignment you can follow through on within days.

Skill gaps and support needs

• "Where do you feel least supported in your current role?"
• "Are there areas where you'd benefit from more training or coaching?"
• "What's the biggest gap between where you are and where you want to be?"

Give the answer to that last question space. It can surface honest insights about an employee's trajectory.

Career path clarity

• "How clear are you on what progression looks like for your role?"
• "Do you feel like your work is visible to the people who would influence your growth here?"
• "Is there anything about your career trajectory you'd like to think through with me today?"

You are demonstrating that you see the employee as a whole person with a professional future, not just a unit of output.

How you'll act on what you heard

Action is what separates a skip-level program from a wellness initiative that produces no change.

Share themes without attribution

When you deliver feedback to your direct reports based on skip-level sessions, the anonymization process you described to employees must hold. Aggregate insights across multiple sessions before surfacing a pattern. Frame feedback as systemic: "Several people across the team described an expectation mismatch around autonomy in decision-making" rather than anything attributable to a specific conversation. This protects the employees who were candid with you and keeps the middle manager from becoming defensive in a way that shuts down future feedback.

Commit to specific next steps

Choose one or two systemic issues from the themes you've gathered. Write them down. Assign a clear owner and a timeline. "I'm going to address the delegation clarity issue by working with the management team on explicit autonomy frameworks over the next three weeks" is a commitment. "I'm going to look into the feedback I received" is not.

Close the feedback loop

Go back to the employee within two to three weeks. A brief message works. Tell them what you heard across the sessions in aggregate, what you're doing about it, and what you're still working on. When you return with "I heard the onboarding documentation gap and we're fixing it," you change their expectation of what these conversations can produce.

How Granola helps you stay present

Manual note-taking during a skip-level means choosing between being present and capturing detail. You miss the moment where the employee's tone shifted, or the pause before they answered a question about their manager. Those signals are often where the real insight lives.

Granola is an AI notepad designed for exactly this context. You jot a short phrase, like "onboarding friction" or "autonomy gap," and Granola fills in the surrounding transcript context after the meeting.

Your rough notes guide what gets surfaced. The AI doesn't decide what mattered. You do.

Granola captures device audio directly and transcribes in real time. You can choose to notify participants using Granola's in-chat notification feature, which posts an automatic message when transcription begins, or enable the video watermark, which displays a visible indicator on your video throughout the call. Both options let participants know the conversation is being captured.

Privacy-first note-taking

The audio Granola captures is transcribed and then deleted. Audio is not retained after the session ends. Only the transcript and your enhanced notes persist. Granola is SOC 2 Type 2 certified and GDPR compliant, with third-party AI providers contractually prohibited from training on your data.

Pattern recognition across conversations

The value of skip-levels compounds when you can query across them. Granola's team folders and cross-meeting chat let you create a shared "Skip-Levels" folder and query it with natural language. You can ask "What are the recurring complaints about our product discovery process?" and Granola searches every note in the folder, returning a synthesized summary with source-linked citations pointing to the specific conversations where each theme appeared.

Granola's pre-meeting briefs also prepare you before each session, surfacing relevant context from prior conversations with that person so you walk into the skip-level with continuity rather than starting from scratch every quarter. The cross-meeting intelligence this builds over time turns a collection of individual conversations into a searchable organizational intelligence system.

The free Basic plan gives you AI meeting notes, chat within and across meetings, shared folders, and customizable templates. The Business plan at $14 per user per month adds unlimited history, advanced integrations with HubSpot, Notion, Slack, and Zapier, and full API access.

Try Granola for free: download the Mac or Windows app, connect your calendar, and use it in your next skip-level to see how it fits your workflow.

FAQs

How long should a skip-level be?

Keep skip-level meetings to 30 to 45 minutes, which gives you enough time to work through all five agenda phases without overrunning the employee's schedule. Shorter sessions work for quarterly check-ins with established relationships.

Should I take notes during the conversation?

Typing detailed notes disrupts eye contact and active listening, which are your primary tools for building the trust the conversation depends on. Use a tool like Granola to capture the transcript while you jot occasional, high-level keywords that guide how the AI enhances your notes afterward.

How do I handle feedback about a middle manager without damaging that relationship?

Aggregate the feedback across multiple sessions before sharing anything and frame it as a systemic pattern rather than a personal complaint. A manager who hears "I've observed an autonomy gap across the team and I'd like us to work on delegation clarity" can engage constructively in a way they cannot when they feel individually accused.

How do I get employees to open up if they're guarded?

Send a written explanation to the team before scheduling any individual meetings, explaining the purpose and what will and won't be shared. During the conversation, open with a direct statement that this is not a performance review, ask the employee to set the agenda, and wait in silence after that prompt rather than filling the space yourself.

Can I run skip-levels remotely?

Yes, and the format works well for distributed teams. Keep video on for both parties, signal active listening verbally since you can't nod as visibly, and be deliberate about following up in writing after the session so the conversation doesn't feel transactional.

Key terms glossary

Skip-level meeting: A structured conversation between a senior leader and the direct reports of their direct reports, used to diagnose organizational health rather than assess individual performance.

Psychological safety: The shared belief within a team that it is safe to take interpersonal risks, including sharing honest feedback with leadership. Foundational to the research of Amy Edmondson at Harvard Business School.

80/20 listen-to-talk ratio: A widely-used heuristic in active listening practice that guides the senior leader to speak no more than 20 percent of the time in feedback-oriented conversations, allowing the employee to drive 80 percent of the dialogue.

Device audio capture: The method by which Granola accesses your computer's microphone and system audio directly to transcribe meetings in real time, deleting the audio immediately after the session ends.

Folder-level query: A Granola feature that lets you ask natural language questions across a shared collection of meeting notes, returning synthesized answers with source-linked citations from specific conversations.

Organizational memory: The accumulated skip-level insights, decisions, and feedback patterns that persist beyond individual team members' tenure, often stored in searchable meeting notes.