Prepare a short packet with the actual rule, two questions, one concrete uncertainty, and a declared note-sharing boundary. The employee and leader should work from the same questions. Leave actual answers and accepted follow-ups blank until they exist.
State the purpose and sharing boundary first
A skip-level meeting connects employees with their manager's manager across a management layer. GitLab's overview describes opportunities to ask questions and understand organizational objectives, while keeping duties such as priority and career management with the direct manager. This is one company's guidance, not a universal policy. GitLab's skip-level overview
Do not assume that the direct manager's absence makes feedback confidential. A separate GitLab engineering implementation explicitly says feedback will be shared with the manager. Your organization may have different instructions; establish them before discussing personal feedback. GitLab's engineering implementation
Put these fields at the top of your actual packet:
- Participants and management relationship: [TO CONFIRM].
- Purpose: understand the intake decision and identify the owner of the urgent-request question.
- Who may receive notes, whether names are included, and what may be attributed: [TO CONFIRM under actual policy].
- Where actual notes belong and who may access them: [TO CONFIRM].
- How a participant can raise a sharing concern or find the appropriate separate channel: [TO CONFIRM].
Resolve the sharing fields with the appropriate organizer before inviting disclosure. A blank field is not an anonymity promise. Keep actual personal feedback out of a demonstration or general review copy.
Prepare an employee view with evidence and questions
For this fictional example, a two-layer team has heard about a new cross-team intake rule. The official rule excerpt and its location are missing. Use [INSERT VERIFIED RULE EXCERPT AND SOURCE] rather than inventing exceptions or claiming you have read the policy.
The employee brings two original questions: “What organizational problem is the new route intended to address?” and “Who owns the decision about urgent-request exceptions, and where are the criteria published?” The concrete uncertainty is: “I cannot tell whether urgent requests use the same route.” That statement identifies a gap; it does not assert that exceptions are allowed.
The leader's preparation view repeats those exact questions. Beside each, provide space for a known explanation with its source, a question to check, and an actual reply. In this example, the explanation and reply fields stay blank because the rule evidence has not been supplied. The proposed follow-up is to check the published exception criteria. It is not approval to bypass intake or a promise to change the rule.
Run a 30-minute listening conversation
Use four minutes to restate the purpose and confirmed sharing boundary. Let the employee ask what a note might be used for before moving into feedback. If the boundary remains unclear, establish it rather than treating the template as permission to proceed.
Spend six minutes on organizational context. The leader can explain the decision using verified material, identify what is uncertain, and separate their interpretation from the written rule. With no supplied rule in this sample, the packet simply identifies the evidence needed.
Reserve fourteen minutes for the employee's questions and examples. The leader asks, “Which part of the instruction leaves you unsure?” and checks that their summary captures the question accurately. Today's work allocation remains a direct-manager matter; the sample does not instruct the employee to take an urgent request outside the established route.
Use the final six minutes to read back the unanswered question, proposed next step, and what may be shared. Add fields for actual accepted owner, agreed return date, and sharing summary. Leave them blank until the relevant person accepts. Four plus six plus fourteen plus six equals 30 minutes.
Copy this prompt for the preparation packet
Write a complete US English skip-level meeting packet with employee preparation and senior-leader facilitation views. Use a fictional team with an employee, direct manager and senior leader across two management layers. Do not invent a company policy or actual feedback.
Topic: a new cross-team intake rule. Rule excerpt/source: [INSERT VERIFIED RULE EXCERPT AND SOURCE]. The employee cannot tell whether urgent requests use the same route.
Preserve these exact questions in both views:
1. What organizational problem is the new route intended to address?
2. Who owns the decision about urgent-request exceptions, and where are the criteria published?
At the top, show participants, purpose, actual note-sharing policy, who may receive notes, attribution rules, approved record location/access, and a route for sharing concerns. Unsupplied policy fields must say TO CONFIRM. Do not promise confidentiality or anonymity.
Distinguish verified explanation/source, question to check, blank actual reply and proposed follow-up. The sample follow-up is to check published exception criteria; it is neither exception approval nor a rule-change promise. Leave accepted owner and return date blank until agreed. Do not replace direct-manager priority, performance or career responsibilities.
Allocate 4 minutes purpose/sharing boundary, 6 context, 14 employee questions/examples, 6 readback/follow-up/sharing. Provide complete facilitation questions and reusable blank reply fields. Exclude actual personal feedback from the demonstration. A proposed HTML view switch must preserve the same questions and sharing boundary, collect nothing, and require actual construction/testing. No recording, messaging or private-note storage claims.
Review the packet in NOS
NOS can save and render a prepared HTML copy of the sanitized questions and facilitation plan. Colleagues can check that both views preserve the issue and sharing boundary. Keep actual feedback and follow-up records in the organization's approved workflow; the review copy does not determine who can receive them.
Leave the conversation with the uncertainty accurately stated and any accepted follow-up owned, so the employee knows what answer is coming back and what may be shared.