For the past 12 months, I've been operating at Staff PM level: leading cross-team projects, delivering measurable business results, and leaving methodology behind for the team. This report proves it with 3 wins, 1 dataset, and 3 quotes from colleagues.
Every win is a complete STAR-R: Situation → Task → My actions → Numeric results → One reflection. Credit without numbers is an adjective — there are no adjectives here.
Panels don't read adjectives. Every curve is traceable: dashboard screenshots, A/B experiment reports, original quarterly survey data.
Panels trust colleagues more than self-praise. Every quote is attributed and tied to a specific project — empty "great person" fluff doesn't qualify here.
She turned chaotic requirements meetings into 30-minute decision sessions. During the big sale, she was up with us at 3 AM watching the dashboards — not "supervising," actually reading the curves.
She insisted on the A/B design for the recommendation revamp. Without a control group, we'd never dare claim that +38% — she cares about clean numbers more than we do.
I opposed her when she cut half the features. The data won me over: few people will let data kill their own v1, and even fewer will admit it in a meeting.
The growth section is this package's most credible page: honest about real weaknesses, which makes the wins believable. "Too much of a perfectionist" doesn't qualify here.
In H1 I twice accepted low-value work "to keep the peace," delaying the recommendation revamp by 2 weeks — the cost was real.
Since Q2 I've run a biweekly cross-team alignment with an open "business impact × cost" scoring sheet; Q3 had zero ad-hoc insertions and the revamp shipped on time. Still practicing, but the mechanism is running.
The revamp's v1 shipped 40+ features with flat results; v2 cut half of them and metrics rose +41%.
Lesson: let the simple version produce data first, then talk complexity. Now my first question in any design review is always "can we cut this version in half?"
Answering the question the panel won't ask out loud: if we promote her, what do we get next year? Every bet is tied to a team goal and one success metric.
Extend recommendation capability to push: personalized reach-outs by audience segment. Success bar: push CTR +25% (current baseline 3.2%).
Productize "The Recommendation Experiment Playbook" into a team experimentation platform so any PM can launch an experiment in 3 days. Success bar: experiment cycle from 2 weeks to 3 days.
Replicate this year's mentoring method: take one campus hire through a full project end to end. Success bar: shipping independently within 6 months, plus a v2 mentoring checklist.
This whole package argues one thing: I've already been working at the next level for 8 months.
For the past 8 months, everything I've done has been Staff PM work: leading the mega-sale pipeline rebuild across 3 teams, delivering DAU +38% business results, codifying methodology adopted by 2 teams. This promotion application isn't "I want to level up" — it's "my work is already at that level."
| Staff PM expectations | My evidence | Status |
|---|---|---|
| Lead cross-team projects | Mega-sale pipeline rebuild: aligned Algorithms / Engineering / Ops — 3 teams, delivered 2 weeks early, zero incidents | Met for 8 months |
| Measurable business impact | Recommendation DAU +38% (A/B control basis), checkout conversion +2.1pt, satisfaction 4.8 | Met |
| Develop others, codify methods | "The Recommendation Experiment Playbook" adopted by 2 teams; 2 new hires shipping independently in 3 months | Met |
| Cross-team priority negotiation | Was too soft, causing a 2-week slip → biweekly alignment mechanism in place, zero insertions in Q3 | Still improving |
This sample report was generated by Promotion Review Writer's 7-step process: evidence mining → STAR wins → next-level benchmarking → peer proof → honest growth → next-year bets → panel rehearsal. Your version will make an equally hard case — with your own wins, numbers, and colleagues' words.