Outgrace, home
LeadershipHow-to guide

Running skip-level meetings that surface what managers hide

Skip-level meetings need a stated purpose, a fair sample and visible follow-through. Sourced research on the practice is thin, so this guide is editorial judgement.

A skip-level meeting is a conversation between a senior leader and someone two levels below, with the direct manager left out. Used well, it shows what the layer in between is passing up and what it is holding back. Used badly, it tells a team that the boss is checking on their manager, and the manager hears about it by Thursday. We found no sourced practice guide or research on the method in the material available to us, so this guide is editorial judgement from the desk. Where a point rests on something published, we say so.

Before you start

Three things must be true before the first invitation goes out. Each one reflects a judgement about what usually fails, not a measured finding.

  • The sponsor can state, in one sentence, what the round must reveal that the normal reporting line does not.
  • The direct managers know the programme exists, what will be reported back, and to whom.
  • A named owner, often a chief of staff or an HR business partner, is responsible for follow-through and has a date for the first read-out.

The purpose sentence does most of the work. How is morale? produces general answers and no action. Which two projects are slipping, and why has nobody said so in the monthly review? produces names, dates and a decision. If you cannot write the question, you are not ready to hold the meeting, and the people you invite will sense it within minutes.

Two points from MIT Sloan Management Review bear on this, taken from its page summaries. The first is that a leader's speed of action can hurt teams more than the actions themselves. The practical reading is to commit to a follow-up date you can keep. A quick, visible response to what you heard counts for more than a polished one that arrives after everyone has stopped caring. The second is that the review treats disclosure, meaning what people choose to tell you, as an imperfect signal of real change underneath. A remark from a junior employee is a lead to check. It is not a finding.

  1. Step 1

    Choose the question first

    Write the single question the round must answer before you invite anyone. Keep it narrow enough that a fair answer fits inside one conversation. What usually goes wrong is a question so broad that every meeting ends in a general complaint about workload, and the notes say nothing a leader can act on.

  2. Step 2

    Brief the manager first

    Speak to each direct manager before anyone is invited. Say which teams are involved, roughly how many people will be met, and what you will not do. You will not ask for private performance comments, and you will not pass names back without the person's agreement. What goes wrong is a manager learning about the round from a team member who was asked to attend.

  3. Step 3

    Choose a fair sample

    Draw the list from the organisation chart, not from the people who already speak up. Pick names across teams, locations and length of service, then let each manager suggest a few more. Keep each round to six or eight people so they speak freely. What goes wrong is a sample built from easy conversations, which tells you about the easy conversations and little else.

  4. Step 4

    Ask for facts, not verdicts

    Ask what happened the last time something went wrong, who made the call, and what the person would have needed to act sooner. Avoid questions that invite a yes or no about trust, such as whether they trust their manager. The answers describe a mood. They do not show where the work is failing.

  5. Step 5

    Write up within two days

    Write notes that week in three columns: what was said, what you checked, and what you could not verify. Strip names from anything that goes to the leadership team. What goes wrong is a write-up that reads like a list of grievances with no indication of which ones are true.

  6. Step 6

    Check the claims

    Take each concrete claim to the place where it can be tested. A missed deadline should appear in the project tracker. A pay complaint belongs with the people team. Set a period for testing and a rule for what you will do with a claim you cannot confirm. What goes wrong is acting on the most vivid story and then discovering it was only half right.

  7. Step 7

    Take the themes to the manager

    Return to the manager with themes, not quotes, and ask what they already know. Their answer is evidence too. If they knew for months and did nothing, that is a separate conversation, and it should happen directly and soon. What goes wrong is a leader who uses the round to deliver a verdict without giving the manager a fair chance to respond.

  8. Step 8

    Report back to the group

    Tell the people you met what you heard and what you will do, with dates. We looked at this and decided not to change it, because is a valid report. Silence after a round is the quickest way to make the next round useless, because people will reason that nothing happens.

Keep a simple log across rounds. Record the question asked, the number of people met, the themes raised, the checks made and the outcome. After three rounds you will see whether the programme surfaces anything new or repeats what the monthly review already says. If it repeats, change the question. If it surfaces something new, make sure the manager has heard about it first, through the channel they would expect.

The mistakes that undo the practice

The most common failure is a round with no visible output. People notice within two rounds, and participation falls to the same handful of confident voices. The second failure is using the meeting to check on a manager you already doubt. That turns a listening tool into an informal disciplinary one, and staff stop talking. The third is inviting the same people every quarter. Rotate the list, and ask openly in each round who has not been asked before. These are judgements about common patterns, not measured results.

How often should we run them?

A sensible starting point is one round a quarter, with a small group each time. Review the programme after the first two rounds, and change the cadence only if the notes show a reason. Shorter gaps tend to repeat the same complaints, and longer ones lose the thread. Our desk has no sourced figure for this, so treat the rhythm as a starting judgement.

Should the direct manager hear what was said?

Tell the manager the themes and the checks you are making, not who said what. If a remark points at a named person's conduct, it goes through HR under the normal process, and the manager should be told that it has gone there. Say so at the start of each round, so no one is surprised later.

What if someone raises a safety, legal or harassment matter?

Stop treating it as an open conversation. Route it at once to the people whose job it is, which means HR and, where it applies, legal counsel or the relevant regulator. Tell the employee honestly what will happen to what they have said, and do not promise confidentiality you cannot keep. If the topic needs a lawyer, take legal advice before the next round.

Do they work when some people are remote?

The desk found no sourced evidence on remote formats. In our judgement the rules are the same: a clear question, a fair sample and visible follow-through matter more than the room. Agree in advance how notes are stored and who can read them, since remote notes are easier to forward by accident.

This week, pick one question your leadership team cannot answer from the monthly pack. Brief the two managers closest to it. Book a round of six or eight people across two teams, and put the read-out date in the diary before the first conversation. If you cannot name the owner of the follow-through, do not start. A round that is cancelled does less harm than one that teaches people to stop talking.

Newsletter

The Briefing

One email a week: the leaders we profiled, the ideas worth stealing, and nothing else.

Weekly, free, one click to leave. Read our privacy policy.