Your Promotion Case Is Probably a List of Duties, Not Evidence

Most promotion cases read the same way. A list of projects. A list of responsibilities. A sentence that says "led the migration" or "managed the launch," as if the task itself was the achievement. The person deserves the promotion. The document just doesn't prove it.

Here's the problem. A list of duties tells a reviewer what you did. It doesn't tell them what changed because you did it. Those are different documents, and only one of them actually moves a promotion decision.

This week's prompt exists to fix exactly that gap. Write a compelling case for a promotion using your own real accomplishments takes your raw, unpolished list and turns it into something built around impact and scope, the two things promotion committees are actually trying to assess.

Why "led the migration" doesn't land

Say it out loud: "led the migration." Led how many people? Migrated from what, to what? What happened because it worked? None of that's in the sentence, so a reviewer fills in the blank with whatever level of effort they can imagine, which is usually smaller than what actually happened.

Now compare it to: "led a migration that cut deployment time from 45 minutes to 6, across 3 teams." Same accomplishment. Completely different weight. The task didn't get more impressive. The description just stopped hiding the impact behind vague language.

A quick example

Say your raw list includes "improved onboarding flow" and "mentored two junior team members," neither of which sounds like promotion evidence on its own. Fed into the prompt with real numbers attached, "improved onboarding flow" might become "redesigned onboarding, cutting time-to-first-value from 9 days to 3 and lifting 30-day retention by 12 points." And "mentored two junior team members" might surface as evidence of operating at the next level entirely, since mentoring at scale is often a criterion promotion committees look for explicitly, just never labeled that way in the original list.

The prompt also does something people rarely do for themselves: it flags which promotion criteria your current list doesn't clearly cover yet. That's uncomfortable to see, but it's far better to know before submitting than to find out from a rejection.

Where the real value is

The obvious win is a stronger document. The less obvious one is what happens to your own thinking in the process. Most people undersell their work not because they're being modest, but because they were too close to it to notice the actual size of the impact. Writing "led the migration" felt accurate in the moment. It just wasn't complete.

There's a filtering effect too. The prompt pushes you to cut anything that's really just "did my job well" rather than genuine evidence of the next level. That's not about padding a shorter list to look thinner. A case stuffed with routine work makes the strong parts look average by association. Three sharp, specific accomplishments beat nine vague ones every time.

How to use it

1. Pull up the prompt and paste your accomplishments exactly as rough as they currently are. Don't pre-edit them first, the raw version is what needs reworking.
2. Push for real numbers wherever you can find them, even rough ones. "Faster" and "better" don't survive scrutiny. Specific numbers do.
3. Take the flagged gap seriously. If a criterion for the next level isn't covered by anything on your list, that's worth addressing before you submit, not something to hope nobody notices.

Grab the promotion case prompt before your next review cycle, not the week it's due. A case built on real numbers takes longer to assemble than a list of duties, and it's the only version that actually changes the decision.