The Skip-Level Meeting Planner: Turn Rare Face-Time With Your Boss's Boss Into a Career-Advancing Conversation

Why this prompt matters
Skip-level meetings happen once or twice a year at most for most professionals, and a wasted one doesn't just fail to help — it actively costs an opportunity, because the senior leader walks away with no new signal about this person at exactly the moment their name might otherwise have come up for a stretch project or promotion conversation that happens outside the room.
What we use it for
A senior engineer at a 200-person company has a rare 30-minute skip-level meeting scheduled with the VP of Engineering next week — the first time they've had direct access to anyone above their own manager in two years at the company.
Prompt
Role: You are an executive coach who has prepared dozens of professionals for skip-level meetings and has seen which approaches actually move a career forward versus which ones waste the slot on pleasantries. Context: - My role and tenure: [YOUR ROLE AND HOW LONG YOU'VE BEEN IN IT] - The skip-level's role: [THEIR TITLE, e.g. "VP of Engineering, oversees 4 teams including mine"] - Meeting length: [DURATION, e.g. "30 minutes"] - What I know about their current priorities: [ANYTHING YOU'VE HEARD FROM ALL-HANDS, SLACK, YOUR MANAGER — OR "Not sure, haven't had visibility into this"] - My real accomplishments in the last 6-12 months: [LIST 3-5 SPECIFIC THINGS YOU ACTUALLY DID, WITH RESULTS WHERE POSSIBLE] - My career goal for the next 12-18 months: [e.g. "Move into a technical lead role" or "Not sure yet, still figuring it out"] - Why this meeting is happening: [e.g. "First skip-level ever," "Quarterly skip-level rotation," "I requested it after a reorg"] Task: Build a plan for this specific meeting. Select which 3-4 of my listed accomplishments are actually relevant to what a skip-level would care about (organizational impact, cross-team patterns, things their direct manager might not have visibility into) — not just a highlight reel. Draft 3 strategic questions that use this specific person's role to get information or signal I can't get from my own manager. Flag pitfalls specific to my stated situation. Constraints: - Do not fabricate accomplishments beyond what I listed, and do not inflate their scope. - Do not recommend directly asking for a promotion or raise unless my stated career goal explicitly says that's the ask — a skip-level is for building visibility and gathering signal, not for negotiating. - If I said I don't know their priorities, do not invent any — instead, include a question designed to surface that information. - Tailor every talking point and question to what a skip-level specifically has visibility into (strategy, cross-team patterns, org-level decisions), not day-to-day work my direct manager already sees. Output Format: 1. Opening framing (one sentence to set the tone when the meeting starts) 2. Talking Points table: Accomplishment | Why It's Relevant to Them Specifically 3. Strategic Questions (3, each with the signal it's designed to surface) 4. Pitfalls to Avoid (specific to my stated situation) 5. Follow-Up Plan: what to do in the 48 hours after the meeting
Result
Opening Framing
"Thanks for the time — I know your calendar is packed, so I wanted to use this well. I'd love to hear how you're thinking about [a priority you mentioned, or ask them directly if unknown], and share a couple of things from my end that might not have crossed your desk yet."
Talking Points
| Accomplishment | Why It's Relevant to a VP of Engineering Specifically |
|---|---|
| Led the migration that cut our deploy pipeline from 40 minutes to 8 minutes, now adopted by 2 other teams | Cross-team adoption is exactly the organizational-impact signal a VP tracks that your direct manager might mention in passing but won't frame as a pattern |
| Identified and fixed a recurring on-call pain point that was costing the team roughly 5 hours/week | VPs care about systemic inefficiency across teams, not just individual incident resolution — frame it as "I noticed this pattern," not "I fixed one bug" |
| Mentored two junior engineers, both of whom shipped their first production features independently within 2 months | Signals leadership readiness without you having to say "I want to lead" out loud |
Strategic Questions
- "What's the biggest thing slowing the engineering org down right now that isn't visible from inside one team?" — Signal: reveals their actual current priorities, which you said you don't have visibility into, without asking them to just list priorities generically.
- "When you look at the teams reporting up through you, what's the difference between the ones that are thriving and the ones that are struggling?" — Signal: surfaces what they actually value in team performance, which tells you what to optimize for beyond your manager's immediate feedback.
- "Is there a type of problem or project you wish more engineers would raise their hand for?" — Signal: an indirect way to learn what stretch opportunities exist without directly asking "what should I do to get promoted."
Pitfalls to Avoid
- Since this is your first skip-level, don't treat it like a status update — your manager already has that information. Spend the time on things only this level can see or decide.
- Don't ask about promotion timing directly in a first skip-level — it reads as premature and shifts the tone from "building visibility" to "transactional ask," which can work against you.
Follow-Up Plan
Within 48 hours, send a short thank-you note referencing one specific thing they said (not generic gratitude), and mention one concrete next step tied to what you learned — for example, if they mentioned a cross-team inefficiency, note that you're going to look into whether your team hits the same issue.
Most people get one or two skip-level meetings a year, treat them like a scheduling formality, and walk in with nothing more prepared than "things are going well." The Skip-Level Meeting Planner exists because that default wastes one of the few slots most professionals get with someone whose opinion carries real weight in promotion and stretch-assignment decisions, but who has almost no visibility into your actual day-to-day work.
Why the prompt filters accomplishments instead of just listing them
Dumping every recent win onto a skip-level manager is the single most common mistake — it reads as a status update, which is what your direct manager already handles. The prompt explicitly instructs the model to select only accomplishments relevant to what this specific person would care about: organizational impact, cross-team patterns, things their direct reports might mention but wouldn't frame as a trend. That filtering step is what separates a memorable conversation from a forgettable one.
Why each question has to name the signal it's designed to surface
Generic advice says "ask good questions" without explaining what a good question actually accomplishes. This prompt requires every suggested question to come with an explicit statement of what information or signal it's meant to extract — because a skip-level has a different vantage point than your manager, and the entire value of the meeting is accessing information you structurally can't get anywhere else. A question that could just as easily be asked of your own manager is a wasted turn.
Why the prompt refuses to recommend asking for a promotion unprompted
It's tempting to treat any face time with a senior leader as a negotiation opportunity, but that reframes a visibility-building conversation into a transactional one, often before the relationship has enough trust to support it. The constraint against recommending a direct promotion ask — unless the user's stated goal explicitly calls for it — keeps the prompt from pushing people toward a move that typically backfires in a first or early skip-level.
Why the output ends in a 48-hour follow-up, not just meeting notes
A skip-level conversation that isn't followed up on fades from memory within a week — for both sides. Requiring a specific, non-generic follow-up tied to something the skip-level actually said turns a single good conversation into the start of a relationship that compounds in value the next time an opportunity, a stretch project, or a promotion decision comes up.