Promotions · Primly Community

how to write a promo packet when your manager gives you zero guidance

staff_steph · 5 replies

third time helping someone on my team write a promo packet and the pattern is always the same: manager says "you're ready, just put something together" and then disappears. no template. no examples. no calibration criteria. just vibes and a deadline.

so here's what I've figured out after watching four people get promoted and two get rejected at the same committee.

the frame that actually works:

your packet is a brief for people who have never worked with you and have 7 minutes to read it. write for that person, not for your manager who already believes in you. the committee is 5 directors who don't know your name.

what to put in it: one paragraph on scope. what you own, how big it is, what breaks if you stop showing up. not a list of tasks, a statement of ownership. 3-5 impact bullets. numbers where you have them. if you can't get exact numbers, relative numbers work ("reduced p95 latency by ~40%, verified in datadog"). fake precision is worse than honest ranges. cross-functional influence section. if you're going from senior to staff, this is the one that actually moves committees. internal consulting, unblocking other teams, forcing alignment on decisions nobody wanted to make. a "what changes at next level" paragraph. this one's painful to write but skipping it costs you. you're saying: here's the ceiling of my current level, here's the floor I'm operating at. don't be shy about it.

what to leave out:

length does not signal quality. I've seen 4-page packets get approved and 12-page packets get deferred. long packets usually mean the person couldn't figure out what mattered.

also, don't put in the work you did that didn't ship. I know that feels unfair. committees don't weight effort, they weight outcomes. put shipped stuff.

if you're at a company with a "bar raiser" or equivalent in committee, ask your manager if that role exists and what they look for. it's not a secret, it just takes asking.

the packet is 30% of it. your manager advocating in the room is the other 70%. make sure they know your packet before you submit it so they're not reading it the same day as everyone else.

5 replies

pm_priya

the "write for people who don't know you" framing is doing a lot of heavy lifting here and I wish someone had said it to me in those exact words when I was writing mine. I had my manager read it and she said "great" and then the committee deferred me because they had no context on why my project mattered. she already knew. they didn't.

staff_steph

exactly this. your manager is your biggest advocate but also your worst editor for this specific doc because they already have the context. ask someone two orgs over to read it cold and tell you what's unclear.

qa_quinn

the cross-functional influence thing is brutal for QA/SDET. "influenced" sounds fluffy when your actual job is blocking bad code from shipping. I reframed mine as "maintained quality bar across 4 teams releasing to shared prod" which apparently read better. still got deferred once before it landed.

frontend_fran

how far in advance should you actually start? I keep hearing "6 months" but my skip-level said "you should already be operating at the next level before you write the packet." those feel like different timelines.

staff_steph

your skip is right and the 6 months is roughly how long the evidence-gathering takes once you're operating there. you can't write the packet and then operate at the next level. it has to go in reverse.