Most review conversations are lost before they start — not because you didn't do the work, but because you walk in with a feeling instead of a case. This turns your scattered wins into an evidence-backed narrative, then has Claude role-play your manager so the objections land in private first. Thirty minutes of prep buys you a calmer, sharper twenty in the room.
Who this is for
Run this before a performance review, a promotion case, or a comp conversation — any time you need to argue your own value and you'd rather not wing it. It works whether you're asking for a rating, a title, or a raise.
What you'll need
- A Claude account.
- Ten minutes of raw material: your goals from the period, anything you shipped, and any praise or feedback you've gotten (Slack, email, 1:1 notes).
Dump the evidence · 10 min
Open a doc and brain-dump everything from the review period — projects, metrics, fires you put out, people you unblocked, praise you received. Don't organize it. Quantity first; the next step finds the signal.
Paste it all into Claude with this:
Below is a raw, unsorted list of what I did this review period. Help me turn it into a tight performance case. 1. Group everything into 3–4 themes that map to what my company actually rewards (impact, scope, leadership, judgment). 2. For each theme, pull the 2–3 strongest, most concrete proof points — prefer numbers and named outcomes over adjectives. 3. Flag anything vague or unsupported so I can go find evidence or cut it. 4. Draft a two-sentence "headline" for the whole period that I could open the conversation with. My role and level: [paste] What my org says it rewards at the next level: [paste rubric if you have one] Here's my raw material: [paste your dump]
Name what you actually want · 5 min
A review without an ask is just a status update. Decide the one concrete outcome — a rating, a promotion, a specific number — and a fallback you'd accept. Tell Claude both and ask it to phrase the ask in one clean sentence, plus a version for if the answer is "not yet."
Run the objections in private · 10 min
The whole game is hearing the pushback before the room does. Have Claude play a skeptical-but-fair version of your manager.
You're my manager in a performance review. You're fair but budget-constrained and slightly skeptical. I'll make my case; you push back the way a real manager would — "that was a team effort," "the bar at the next level is higher," "the timing's tough this cycle." After each of my answers, rate how convincing it was (1–5) and tell me the strongest counter I left on the table. Don't go easy on me. Here's my case and my ask: [paste from Steps 1–2]
Go a few rounds. When a "5" answer comes out of you naturally, write it down — that's your talking point.
Cut it to a one-pager · 5 min
Ask Claude to compress everything into a one-page brief: headline, three themes with proof, the ask, and your three best objection responses. Read it out loud once. You're not memorizing a script — you're making sure the case lives in your own head.
Leading with effort, not outcomes. "I worked really hard on X" invites a shrug. "X cut churn 8%" doesn't. If a proof point has no result attached, it's a task, not an accomplishment.
Walking in without an ask. If you don't name the outcome you want, your manager will fill the vacuum with theirs. Decide it before the meeting, not during.
Over-scripting. Memorized lines sound memorized. Internalize the three themes and let the words be yours in the moment.
Do this next
- Send a short pre-read a day before if your manager is open to it — the case lands better when they've already seen the numbers.
- Save the one-pager. It's the seed of next cycle's case; keep adding to it as wins happen instead of scrambling at review time.
- Log what objection actually came up. If Claude missed it, add it to the role-play prompt for next time.