A skip-level meeting is not a shortcut past your manager

Why the meeting exists at all

A senior manager relies on a layer of reporting that is, by construction, filtered. Every manager between them and the work summarises, and every summary reflects the interests of the person writing it — not dishonestly, usually, but selectively. Skip-level conversations are an attempt to sample the underlying reality directly, and to notice problems that would otherwise be smoothed out on the way up.

That tells you what they want from it. They are looking for texture: what actually takes time, where the process gets in the way, whether people understand the direction, and whether there is anything they should be worried about. They aren’t, in the ordinary case, evaluating you against your manager, and they are certainly not there to be recruited into your side of a disagreement.

The two ways people waste one

The first is to treat it as a performance review with a bigger audience and spend the time listing accomplishments. It isn’t that this is offensive; it is that it supplies nothing the senior person cannot get from your manager, and it makes the conversation feel like an interview neither of you wanted. The second is the opposite: treating it as a chance to raise a complaint about your manager, which almost always rebounds.

The second one deserves a moment. A senior manager hearing criticism of a direct report has a natural and reasonable instinct to protect their own ability to manage through that person. In most cases the concern gets relayed, in some form, back down the line. That isn’t betrayal; it is how a management chain functions. There are exceptions — serious misconduct, safety, anything where formal routes exist — and those exceptions should go through those routes, deliberately, rather than being floated in an informal chat.

What to actually bring

The most useful material is specific, unemotional and structural. A step in a process that costs the team an unreasonable amount of time. A recurring source of rework caused by something outside your team. A place where the stated priority and the actual incentives point in different directions. These are all things a senior person can act on and would not otherwise hear.

Questions are as valuable as observations, and they cost you less. Asking what they are being measured on this year, or what they expect to change in the next eighteen months, gets you information that genuinely improves your decisions, and it is the sort of question senior people enjoy answering. It also demonstrates something about how you think, without any of the awkwardness of self-promotion.

Bring one thing you are working on and can explain clearly in two minutes, with the consequence stated rather than the mechanism. Not as a pitch — as an answer to what you have been up to, which will certainly be asked, and which people commonly answer badly by listing tasks in no particular order.

Tell your manager, before and after

This is the part that is skipped, and it is the part that matters. Mention beforehand that the meeting is happening and ask whether there is anything they would want raised. Afterwards, give a short account of what was discussed. Neither is an obligation to seek permission; it is a demonstration that you are not routing around them, which is precisely the fear a skip-level triggers in a manager who is at all insecure.

The cost of not doing this is disproportionate. A manager who hears secondhand that their report had a private meeting with their boss will construct an explanation, and it will not be a flattering one. The cost of doing it is two sentences. This is one of the clearest cases in working life where a small, slightly formal courtesy prevents a large and durable misunderstanding.

When the invitation means something else

Occasionally a skip-level is not routine. If they appear suddenly during a reorganisation, or only with selected people, or the questions are pointedly about a particular colleague, something else is happening — a restructure being scoped, a manager being assessed, a decision being pre-socialised. You will not usually be told, and pressing is unwise.

The sensible posture is the same in either case: be accurate, be fair about colleagues, and do not say anything you would be unhappy to have repeated, because in these conversations more gets repeated than people assume. And if your organisation runs no skip-levels at all, that is worth noticing too. It usually means the senior layer is working entirely from filtered information, which is a reliable predictor of decisions that seem inexplicable from where you sit.