The opener that sets the meeting
Never open with "how are things going with you?" That gives control of the meeting away in the first fifteen seconds. Open with a one-line read on your team, delivered as judgment, not status.
"Team's on plan for Q3. The risk I'm watching is the migration timeline slipping into the AI launch - I'm working with [peer] on a sequenced rollout so we don't force a bad trade-off. Happy to go deeper if that's useful."
Three signals in one sentence: you know the plan, you can name a real risk, you are already working across teams. That is what a skip is scanning for. Not the risk itself - the fact that you named it before they had to ask.
How to talk about your scope upward
The single most common failure I see in staff-plus and director promo packets is language that describes what the team did. Skip-levels do not promote teams. They promote the person who owns the call.
Weak (reads as "still senior"):
"We shipped the new pricing engine last quarter."
Stronger (reads as "already staff-plus"):
"I called the architecture on the pricing engine after we hit the third rewrite. Team shipped in six weeks after that. It's now handling 3x the load without incident."
Notice what changed. You named the call, the moment, and the outcome. You did not take credit for the team's work - the team shipped it. You took credit for the judgment that made shipping possible. That is what a promo committee reads as staff-plus signal.
Handling loaded questions
"How is [peer / manager / another team] doing?"
The trap is the invitation to comment. Do not take it. The answer:
"Better read from them than me. What I can tell you is where the interface between our teams is working and where it's not - [one sentence]."
You just refused to be a source of gossip and simultaneously demonstrated cross-team read. That is the answer they were actually testing for.
"What would you change about how the org is running?"
Never lead with a critique. Lead with the frame:
"The thing I'd change is one level down from strategy - it's the loop between design review and delivery. I've been talking to [peer director] about a proposal. Want me to send you the draft?"
You just moved from complaining to proposing, and you handed them a follow-up they will remember you by.
"Are you happy here?"
The dangerous question. "Yes" reads as no leverage. "No" reads as flight risk. The answer:
"I'm invested. What I care about is whether the trajectory of the seat matches where I'm pushing. That's the conversation I'd rather be in."
You did not answer the question. You reframed it into the conversation you actually want.
The sentences to stop using
- "I think maybe we should..." - Hedging. Skips are calibrating conviction.
- "To be honest..." - Implies everything else was not.
- "I just wanted to..." - The word "just" makes you smaller. Cut it every time.
- "Does that make sense?" - Puts them in the judge seat. Use "let me know if that's useful."
- "Sorry, quick question, ", Never apologize for taking the meeting they scheduled.
The close
The last thing you say is what they remember. Not "thanks for your time." Not "let's do this again." Something specific:
"One takeaway I'm leaving with: [name the specific thing]. I'll come back in six weeks with the result."
You just committed to a follow-up. You just gave them a specific memory. And you just earned the next skip on your terms, not theirs.
Why the words are the work
Every senior leader I have worked with who was "stuck at Senior" or "stuck at Director" was saying the right things about the wrong subject - describing team output when they should have been describing judgment, hedging when they should have been calling, apologizing when they should have been proposing. The Recode is six months of rewiring exactly that, in your actual meetings, until the sentences that used to feel arrogant feel accurate - because they are.