Skip-Level Meeting Questions and How to Record the Answers

Elena runs operations for a 46-person team, split across five managers. Every spring she holds skip-levels with everyone two levels down. By June she has a notebook of half-sentences, three people's worries she can't quite remember, and a nagging sense that someone told her something important.

(Elena is a composite, not a real person. The notebook is very real.)

Her skip level meeting questions were fine. What went wrong was what happened to the answers, and that matters more in a skip-level than in any other meeting. Gallup reported in September 2026 that as of May 2026, only 1 in 5 U.S. employees strongly agreed they trust their organization's leadership. A skip-level is where that trust is built or spent, and it's spent fastest when people speak up and nothing changes.

This guide gives you 40 skip level meeting questions grouped by purpose, a 30-minute agenda, eight questions for employees to ask, and the part other lists leave out: how to record the answers so they turn into action without anyone regretting what they said. If you'd rather talk your takeaways into your phone than scribble them, try ParrotNotes free.

What a skip-level meeting is, and what it isn't

A skip-level meeting is a conversation between a manager and an employee who reports to one of that manager's direct reports. The senior manager "skips" a level to hear how the work looks from closer to it.

It isn't a performance review or an audit of the employee's manager. Yale's IT department, in its guidance on skip-level meetings, puts three rules plainly: hold them "at least once annually," tell your direct reports first ("share their intent with their direct reports"), and "aim for an 80/20 listen-to-talk ratio."

Once a year is a minimum; our guide to meeting cadence helps you pick a rhythm. The second rule matters most: a manager who hears about skip-levels from their own team will assume the worst.

A 30-minute skip-level meeting agenda

Half an hour is enough. Keep to this format so the employee knows when the meeting ends.

The first block is the one people skip, and it's what makes honest answers possible: people speak freely once they know what happens to their words.

40 skip-level meeting questions by purpose

Pick one or two groups per meeting, not all seven. Each ends with a listen for line: the signal worth noting afterwards. For your own direct reports, use our one-on-one meeting questions instead.

Opening: getting past the polite answer

1. What are you working on right now that you'd like more people to know about?
2. How did you end up in this role?
3. What part of your week do you look forward to?
4. What's changed in your work since we last spoke?
5. What would make this half hour worth your time?

Listen for: what they're proud of, often invisible from your level.

The work itself

6. Walk me through a normal Tuesday. Where does the time go?
7. Which task takes three steps that should take one?
8. What do customers (or other teams) ask you for that we make hard to give?
9. What tool or report do you use every day that nobody upstairs knows about?
10. Which piece of work would you stop doing if you could?
11. What's the best idea you've heard on the team that hasn't gone anywhere?

Listen for: the same friction named by more than one person.

Obstacles and decisions

12. Where does work pile up while it waits for someone else?
13. Which approval takes longer than it should?
14. When did you last need a decision and couldn't get one?
15. What's a decision you'd like to be trusted to make yourself?
16. Which meeting could become an email?
17. What did we change recently that made your work harder?

Listen for: decisions stuck above the team. Those are yours to fix.

How the team runs

18. How does the team find out about a change?
19. Who do people go to when they're stuck?
20. When the team disagrees, how does it get settled?
21. What does the team do well that other teams should copy?
22. What's one habit that would make the team's week easier?
23. How easy is it to say "I don't know" on this team?

Listen for: how information moves, not who's to blame.

Growth

24. Which part of the business would you like to understand better?
25. What skill would you learn if you had a free month?
26. Which project would stretch you that you haven't been offered?
27. Who outside the team would you like to learn from?
28. What's one thing the company could do to help you grow?

Listen for: an introduction or project you can broker without going around their manager.

Leadership and the company

29. What do you hear about the company's plans, and where from?
30. Which goal for this year makes the least sense from where you sit?
31. What would you want leadership to stop doing?
32. What's one thing leadership says that doesn't match what you see?
33. How do you find out whether the company is doing well?
34. What do new joiners find most confusing about how we work?

Listen for: gaps between message and experience. Gallup found employees who strongly trust leadership are 3.7 times as likely to be engaged; these answers show where trust leaks.

Closing

35. What should I have asked you that I didn't?
36. What's one thing I could do in the next month that would help?
37. Is there anything you said today you'd like me to keep to myself?
38. How would you like to hear back from me?
39. Would you want to do this again, and how often?
40. What do you want to ask me?

Listen for: question 37. Whatever they name stays in your head and out of every note.

Questions to leave out

Some questions feel natural and do damage:

• "What do you think of your manager?" It turns the meeting into an investigation. A real concern will come up unasked, and then it needs a proper HR process.
• "Are you happy here?" A yes-or-no question people answer defensively.
• "Is anyone thinking of leaving?" Nobody answers it honestly, and everyone repeats it.
• Status questions. Status belongs in reports; a skip-level is for what reports can't hold.

Skip-level meeting questions for employees to ask

If you're the employee, the meeting is also yours. Bring two or three of these:

1. What are you most focused on this quarter, and how does our team fit in?
2. What does good work from our team look like from where you sit?
3. What's a decision coming up that will affect us?
4. What do you wish more people at my level knew?
5. What skills do you see the company needing in the next year or two?
6. How did you get from a role like mine to yours?
7. Is there a project outside my team I could help with?
8. What's the best way to raise an idea with you?

Bring one small idea of your own, with how you'd do it. It's what they'll remember.

How to record the answers without breaking trust

You can't act on what you don't remember, but an employee who watches you write every word starts choosing words carefully. The fix: a clear recording rule, a short debrief, and a log of themes rather than names.

Ask before you record, and make "no" easy

Recording the conversation itself is fine only with the employee's explicit OK, asked in advance, not as you press the button. Try:

"I'd like to listen properly instead of taking notes. Would you be OK with me recording this so I get your points right? It stays in my notes, it's never shared, and no is completely fine. If you'd rather not, I'll jot down my own takeaways afterwards."

If they hesitate at all, don't record. Never record a complaint, an HR matter, or a conversation about someone's performance. Recording laws vary by state and country, and your company may have its own policy; our guide to one-party consent states covers the U.S. rules. This isn't legal advice.

The four-minute debrief

Without a yes, record yourself instead. Straight after the meeting, talk through five points:

1. Who and when: name, team, date. This stays in your private note only.
2. Three things I heard: in their words where you can remember them.
3. What they asked me for: anything you offered or promised.
4. Themes: which of their points you've heard before.
5. What I won't repeat: anything they asked you to keep private (question 37), noted only as "keep private".

With ParrotNotes, you tap record, talk for four minutes with the phone in your pocket, and get a transcript, an AI summary, and your promises as action items. No meeting bot, and nothing in the room while they're talking.

The theme log: themes, not names

After a round of skip-levels, the individual notes stay private. What you share and act on is a theme log:

A theme needs at least three people before it goes in the log; with fewer, a paraphrase can point to one person.

Here's Elena's next round (still a composite). She held 11 skip-levels in two weeks and dictated a debrief after each. Two people agreed to be recorded; nine didn't, as she'd expected.

On Friday she used AI semantic search on Pro to look for "approval" across her notes and found it in six debriefs. The $500 sign-off limit went to $2,000 the next month, and in the following round three people mentioned it unprompted as proof skip-levels work.

Ready to try the four-minute debrief after your next skip-level? Download ParrotNotes free. The free plan includes 100 minutes of recording a month and an AI summary on every recording, enough for a full round of debriefs. Pro adds AI semantic search across your notes, so "approval" finds every mention.

Close the loop within a week

Saying nothing afterwards is the fastest way to end honest skip-levels. Within a week, share the themes with your direct reports, as Yale suggests ("remember confidentiality": themes and counts, never who said what). Then send everyone who took part a short note:

"Thanks for the skip-level. Across 11 conversations, three themes came up: [theme], [theme], [theme]. Here's what's happening: [action, owner, date]. One we can't change yet: [theme], because [reason]. Next round in [month]."

Put the actions in your team's action items template so they get tracked like any other commitment.

Make the answers count

Good skip level meeting questions are half the job. The other half is the answers:

• Tell your managers first, and keep to a 30-minute agenda.
• Pick one or two question groups, and let the employee ask theirs.
• Record the meeting only with an explicit yes; otherwise, debrief yourself in four minutes.
• Log themes, not names, and close the loop within a week.

Elena's notebook is now a list of themes with owners and dates. Try ParrotNotes free and dictate your first debrief after your next skip-level.