Build an Honest Promotion Case That Maps Your Work to Next-Level Expectations

You get a promotion case with a short summary, an evidence table rating each next-level expectation, honest gaps with fixes, and likely manager questions.

Prompt

Prompt
You are a people manager who has sat on many promotion committees. Help me build a promotion case for my next performance review.

Right after this prompt I will paste two things: (1) the expectations for the level I am aiming for, in my company's words or my own, and (2) my work examples from this review period. If either is missing, or you cannot tell my current and target level, ask me up to 3 short numbered questions in one message and wait for my answers.

Rules:
1. Map every work example to a specific next-level expectation. One example can support at most two expectations.
2. Use only facts I gave you. Never add numbers, outcomes or praise I did not state. If impact is unmeasured, write "impact not quantified" and suggest how I could measure it.
3. Rate each expectation Strong, Partial or Gap, with one sentence explaining why.
4. Write each evidence bullet as: what I did, scope, result.
5. For every Gap, suggest one concrete action I can finish before the review.

Output format:
- Summary case (3-4 sentences, first person, no superlatives)
- Evidence map table: Expectation | My evidence | Rating | Why
- Gaps and actions (numbered list)
- Questions my manager will likely ask, with honest answers drawn from my material

End with one line naming the weakest part of the case and whether to raise it now or after closing the gap.

Example output

At a glancePromotion evidence by next-level expectationProduct Designer II aiming for Senior Designer, review in five weeks
Expectations rated Strong
3 of 5
Ownership, craft quality, independent research
Expectations rated Partial
1 of 5
Mentoring: real, but impact not quantified
Expectations rated Gap
1 of 5
Influence beyond own team
Invoice support tickets per month
140 to 60
After the billing redesign shipped

Example for: a Product Designer II at a mid-size SaaS company aiming for Senior Designer, review in five weeks.

Summary case

Over the past two quarters I led design for the billing redesign end to end and set up the team's shared component audit. I have started mentoring one junior designer and run research without needing review. I am still building the cross-team influence the Senior level expects, and I have a plan to show it before the review.

Evidence map

ExpectationMy evidenceRatingWhy
Owns ambiguous projects end to endLed billing redesign from discovery to launch; 3 squads; support tickets on invoices fell from about 140 to 60 per monthStrongClear ownership, scope and a measured result
Raises quality of the team's craftRan component audit; removed 22 duplicate components from the libraryStrongTeam-wide effect with a concrete count
Mentors other designersWeekly 1:1s with Priya Nair since March; reviewed her onboarding flowPartialMentoring is real, but impact not quantified
Influences beyond own teamPresented billing findings at one design reviewGapOne presentation does not show sustained influence
Plans research independentlyPlanned and ran 8 customer interviews for billingStrongDone without a lead's sign-off

Gaps and actions

  1. Influence beyond own team: Offer to run the onboarding pattern review with the Growth team before the review, and ask their PM for a short written note on the outcome.
  2. Mentoring impact: Ask Priya what changed in her work since March, and note one shipped screen she owned with less review.

Questions your manager will likely ask

  • "Who outside your squad would back this?" Today, mainly the billing PM. The Growth review is how I plan to add a second voice.
  • "Was the ticket drop caused by your design?" The drop started the week the redesign shipped; no other billing change went out that month.
  • "Are you ready to mentor more than one person?" I have mentored one so far and would like a second mentee next quarter.

Weakest point: cross-team influence. Close it with the Growth review first, then raise it in the review with that evidence.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Banning invented numbers and praise keeps the case credible when a manager or committee checks the facts.
  • The Strong/Partial/Gap rating forces an honest read instead of a padded list of wins.
  • Pairing every gap with an action you can finish before the review turns weak spots into a plan.

Use 3-6 weeks before your review so you have time to close gaps. Have your level guide (or your own notes on it) and a list of projects ready, then paste both into ChatGPT, Claude or Gemini.

Common edits

  • Ask for a one-page version to send your manager before the meeting.
  • Add a column linking each example to a doc, ticket or metric dashboard.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Career & Job Search