Head of Product Accomplishments: 75+ Examples for Performance Reviews

Product leaders are accountable for outcomes they don't directly control. Your review should prove the decisions, frameworks, and leadership that made those outcomes possible.

The Unique Challenge of Writing Product Leader Accomplishments

Every feature you shipped involved ten engineers, three designers, and a PM. Every strategic win required executive buy-in you had to earn. Every customer insight came from research your team ran. So when review season arrives, it's tempting to write "we launched X" and call it done. That undersells you — and it won't get you promoted.

The hardest thing to articulate as a Head of Product, VP of Product, or Director of Product is the causal chain between your specific decisions and the outcomes the company cares about. The cross-functional team did the work. You shaped what work got done, how it was prioritized, and why the bets made sense. That's the story your review needs to tell.

Reviewers at the VP and C-suite level aren't evaluating features shipped. They're evaluating judgment — did you identify the right problems, build the right team, make the right tradeoffs, and communicate them well enough to keep 20 people aligned for 12 months? The examples in this post are designed to help you surface that judgment in concrete, credible terms.

Use these as starting points. Replace the bracketed metrics with your own. The structure — what you decided, how you decided it, what happened — is the part that matters most.

What gets you promoted are documented accomplishments with measurable impact.

Head of Product Accomplishment Categories

1. Product Strategy & Vision

Product Vision & Strategy

1. Inherited a product without a stated vision beyond "be the best in category." Ran a 6-week strategy process — customer interviews, competitive analysis, internal stakeholder sessions — and produced a 3-year product vision with 4 clear strategic bets. The vision passed the board review on first presentation and became the planning anchor for 3 subsequent quarters.
2. Our product was competing on features in a market where the category leader had a 5-year head start. I reframed our strategy around a specific underserved segment — mid-market operations teams — and repositioned the product accordingly. Within 2 quarters, win rate in that segment increased from 18% to 41%.
3. After an acquisition, our two product lines had conflicting positioning and overlapping functionality. I led a 4-month product consolidation strategy, conducted joint customer interviews across both user bases, and produced a unified roadmap. We sunset 3 redundant features and reduced the combined surface area by 30% while improving satisfaction scores by 14 points.
4. Our product strategy was being set reactively — one large customer would push a feature and we'd build it. I introduced a quarterly "strategic bets" framework: 3 strategic themes each quarter with defined success metrics and a clear process for evaluating requests against those themes. Unplanned work as a percentage of roadmap dropped from 44% to 17% in 6 months.
5. The company was entering a new vertical. I led the product strategy for the expansion: scoped the customer segments, ran discovery, built the go/no-go framework, and presented the recommendation to the CEO. The recommendation was to enter with a limited integration-first approach rather than a full build. We launched 4 months ahead of the originally proposed timeline at 40% of the estimated cost.
6. I identified a strategic gap: we had no clear narrative for why our product was better for enterprise buyers than our closest competitor. I partnered with Sales and Marketing to run a competitive teardown, synthesized the findings into a positioning brief, and translated it into 3 product differentiators we committed to building by year-end. Sales deal velocity for enterprise accounts improved by 22% in the following two quarters.
7. Our annual planning process was producing roadmaps that became obsolete by Q2. I redesigned planning around 6-week strategy cycles with explicit assumptions documented at the start of each cycle. When assumptions broke, we had a structured process for adjusting. Roadmap confidence (measured by features shipped vs. committed) improved from 52% to 79%.
8. Recognized that our North Star metric — monthly active users — was tracking engagement with low-value features rather than core product value. Ran an analysis with data science, identified the usage behaviors that predicted retention, and proposed a new North Star: weekly core actions per user. Reconfigured our roadmap around this metric. Retention at 90 days improved from 34% to 51% over the following year.

Market Positioning & GTM

1. Our product was routinely losing late-stage deals to a competitor on the basis of one missing integration. I built the business case for building the integration — deal loss rate, ACV of lost deals, build cost — and got it funded. After launch, the integration was cited in 23 won deals in the following quarter, with an estimated ARR impact of $1.4M.
2. Worked with the CMO and VP Sales to redesign our product packaging. The existing 3-tier model was creating confusion at the bottom and leaving money on the table at the top. I led the pricing strategy workstream — customer interviews, willingness-to-pay analysis, competitive benchmarking. New packaging launched with a 12% improvement in average contract value and a 9-point improvement in demo-to-trial conversion.
3. Identified that our go-to-market motion was misaligned with how buyers actually discovered and evaluated our category. Conducted 40 buyer interviews, mapped the actual purchase journey, and briefed Sales and Marketing on the 3 most common decision triggers we weren't addressing. Two of the 3 triggers became content and product investments that improved marketing-sourced pipeline by 18% in the next half.
4. Led the product work for a new market entry into the European mid-market. Ran localization discovery, identified 4 compliance requirements absent from our roadmap, and coordinated with Legal and Engineering to scope the work. We launched 6 weeks late but at full compliance — avoiding a potential GDPR penalty that Legal estimated at €200K+.
5. Our self-serve onboarding had a 63% drop-off before users reached the core feature. I ran a 6-week discovery sprint — user recordings, exit surveys, prototype tests — and rebuilt the onboarding flow around the first meaningful moment of value. Drop-off decreased to 31%. Trial-to-paid conversion improved by 4.2 points.
6. Partnered with Sales leadership to introduce product-qualified lead (PQL) scoring. I defined the behavioral signals that correlated with conversion, worked with Engineering to surface them in Salesforce, and trained 14 AEs on the new qualification model. PQL-sourced revenue increased from 8% to 29% of new ARR within 3 quarters.
7. Identified a gap in our competitive positioning: we were consistently described as "hard to implement" in review sites, even though implementation time had improved significantly. Ran a messaging audit, found the problem originated in outdated case studies, and partnered with Marketing to refresh 6 flagship stories with updated implementation timelines and quotes. Review site sentiment on "ease of setup" improved from 3.8 to 4.4 within 2 quarters.

2. Roadmap & Prioritization

Prioritization Frameworks

1. My team of 5 PMs had no consistent framework for comparing roadmap items — every decision was a debate. I introduced a prioritization model: customer value score × strategic fit score × confidence level, divided by estimated effort. Not perfect, but it gave us a shared language. Cross-team disagreements that previously took 2+ meetings to resolve started resolving in one. PMs reported feeling 40% more confident in roadmap decisions in a team survey.
2. We were spending 35% of engineering capacity on feature requests from our 5 largest customers. I built a tiered customer input model: top customers got a formal quarterly business review with roadmap visibility; all others got a structured feedback form. I also introduced a "strategic fit" filter — if a request didn't map to a current strategic theme, it went on a parking lot with an explicit explanation. Custom work as a share of capacity dropped to 14%.
3. Ran a quarterly "kill list" exercise — the first time we'd ever formally decided what not to build. I scoped the process: every roadmap item older than 3 quarters with no active champion and no usage data got reviewed. We cut 11 planned features, freeing 8 weeks of engineering capacity that was redirected to our highest-priority strategic bet. That bet shipped 6 weeks ahead of schedule.
4. Product and Engineering were misaligned on estimates — we were consistently planning 60% more work than the team could ship. I introduced a formal capacity planning step at the start of each quarter: a realistic working-capacity number reviewed jointly with Engineering leadership before any roadmap commitments were made. Roadmap accuracy improved from 54% to 83% in 3 quarters.
5. Our roadmap was weighted toward retention features despite acquisition being the primary growth lever. I ran a portfolio analysis — mapped every roadmap item to a stage in the user lifecycle and compared the distribution to where growth gaps actually were. Reallocated 30% of capacity from mid-funnel retention to acquisition-adjacent features. Organic trial starts increased 27% in the following half.
6. Introduced opportunity scoring across all major roadmap investments: every item over 4 weeks of engineering effort required a 1-page opportunity brief with a stated hypothesis, success metric, and minimum viable test. This reduced the number of large bets from 12 to 7 per quarter — and the 7 we ran had a 71% success rate vs. the estimated 40% success rate on the prior unvetted list.

Stakeholder & Executive Alignment

1. The executive team and the product team had fundamentally different views of the roadmap's strategic priorities. Rather than escalate, I designed a structured alignment session: I mapped every major roadmap item to a stated company OKR and asked each executive to score the OKRs by importance. The misalignment became visible in 30 minutes. We resolved 4 months of tension in one afternoon and produced a shared priority stack.
2. Sales was consistently over-promising roadmap commitments to prospects. I built a "committed vs. considering" framework: a shared view of the roadmap with clear language about confidence levels. Trained Sales leadership and AEs on how to use it in conversations. Deal-related roadmap escalations dropped from 3-4 per week to fewer than 1 per month.
3. I was spending 4 hours per week in reactive stakeholder update meetings. I replaced them with a written product update published every other Friday: 3 things shipped, 3 things in progress, top 3 decisions made and why. Async readership reached 85% of stakeholders within 6 weeks. I recovered 3+ hours per week while stakeholder satisfaction with roadmap visibility improved in our quarterly survey.
4. The board was receiving product updates that focused on features shipped rather than business outcomes. I redesigned our board product slides: one slide with the 3 core metrics and trend lines; one slide with the strategic bet, the hypothesis, and the current evidence. Feedback from the board chair was that it was "the clearest product narrative we've had."
5. A major enterprise customer was threatening to churn over a missing capability on our roadmap. Rather than accelerate the feature, I ran discovery to understand the underlying need. The actual problem was solvable with a configuration change that took 2 days of engineering time. Customer retained. We formalized the "what's the real problem" step into our customer escalation process.
6. Three business units were submitting roadmap requests independently with no coordination. I created a cross-functional product council — quarterly 90-minute session with one representative from each BU, Marketing, and Sales. Requests were batched, compared, and prioritized collectively. Duplicate or conflicting requests dropped by 60%. Time from request submission to roadmap decision dropped from 8 weeks to 3.
7. Engineering leadership was consistently surprised by complexity revelations late in delivery cycles. I introduced a "technical risk review" step at the start of every major initiative — a 45-minute session with the PM, lead engineer, and me. We caught 3 significant architectural issues before work started, saving an estimated 6 weeks of rework over the course of the year.

3. Execution & Delivery

Launch & Delivery

1. A flagship feature launch had slipped twice before I took over the workstream. I ran a launch readiness audit — identified 6 open items with no owner and 2 cross-team dependencies that hadn't been formalized. Assigned owners, established a weekly launch committee, and shipped 4 weeks later. Post-launch, I documented the readiness checklist as the standard process for all future major launches.
2. We were launching features without clear success definitions. I introduced a "launch brief" template: problem statement, target user segment, success metric at 30/60/90 days, and rollback criteria. Within 2 quarters, every PM was writing launch briefs without prompting. Feature evaluation quality improved — we were making go/no-go decisions on data rather than intuition for the first time.
3. Our mobile team and backend team were operating on independent release cycles, causing 3-4 weeks of coordination overhead per launch. I brokered a shared release calendar, documented API contract requirements, and established a weekly cross-team sync. Launch cycle time decreased from an average of 11 weeks to 7 weeks on coordinated features.
4. We had a major product launch tied to a customer event with 500 attendees. Three weeks out, a critical dependency from a third-party API failed certification. I assessed options, proposed a scoped down version that removed the dependent feature, communicated the change to the customer, and ensured the core launch still shipped on time. The customer launched successfully and renewed at expanded ARR 4 months later.
5. Our A/B testing practice was inconsistent — different PMs were running tests with different significance thresholds and different minimum sample sizes. I standardized the testing framework: a shared doc with minimum sample size calculator, significance threshold policy, and required analysis template. Test result reproducibility improved, and we stopped shipping features based on underpowered tests. 2 features that previously would have shipped were paused — both showed negative effects when run at proper power.
6. Post-launch retrospectives were rare and unstructured. I introduced a mandatory 2-week post-launch review for any feature that received more than 4 weeks of engineering investment. Format: metrics vs. hypothesis, what we learned, what we'd do differently. Made the outputs searchable in Notion. PMs started referencing prior retros before writing new specs — reducing repeated mistakes by an estimated 30%.

Process & Velocity

1. Discovery and delivery were running in the same sprint, causing constant context-switching. I separated the teams into a discovery track and a delivery track, with discovery running 6 weeks ahead of delivery. Delivery predictability improved from 58% to 81% over two quarters as engineering teams stopped getting hit with scope changes mid-sprint.
2. Our spec process was producing documents that Engineering regularly described as "underspecified." I introduced a definition of done for specs: every spec required a user story, acceptance criteria, edge cases, and an engineering review sign-off before moving to the sprint. Time spent in engineering review before tickets were started dropped by 40%. Rework from spec ambiguity fell by half.
3. Identified that 22% of engineering capacity was going to bug fixes and support escalations from a single legacy feature. I built the business case for a rewrite, presented it to the CTO, and got 8 weeks of dedicated engineering time approved. Post-rewrite, support tickets for that feature dropped by 74%. Engineering capacity recaptured: approximately 12% per quarter ongoing.
4. My team was shipping features that customers weren't adopting. I introduced a feature adoption metric — percentage of target users completing the core action within 30 days — as a required KPI on every roadmap item. PMs started designing for adoption from the first draft of the spec, not as an afterthought. Feature adoption rates across the portfolio improved from an average of 31% to 47% over 3 quarters.
5. Sprint planning sessions were running 3+ hours due to unclear acceptance criteria and scope disagreements. I introduced a "three amigos" session for every story over 3 points — a 30-minute PM, Engineering, and QA review before sprint planning. Sprint planning dropped from 3 hours to 90 minutes on average. Stories that required mid-sprint clarification dropped by 55%.

4. Team Leadership & Org Building

Hiring & Team Building

1. Inherited a product team with a significant seniority gap — 6 of 8 PMs were mid-level with no senior ICs and no staff-level product leadership. I redesigned the leveling framework, identified 2 internal promotion candidates, and built a hiring plan for 2 senior PMs and 1 Group PM. Within 14 months, the team had a senior IC layer and reported higher confidence in technical and strategic decision-making.
2. Our PM interview process was inconsistent — different interviewers were evaluating different things and we had no structured feedback collection. I redesigned the process: a take-home case study, a structured 4-interview loop with defined rubrics per interviewer, and a calibration session before offers. Offer acceptance rate improved from 58% to 79%. First-year retention of new PMs improved from 67% to 88%.
3. Built the product function from 2 PMs to a team of 9 over 18 months, including a Group PM, 3 senior PMs, and 4 mid-level PMs. Designed the org structure by product area, defined the leveling criteria, and ran the full hiring pipeline. Maintained a 90-day ramp target — 8 of 9 new hires were producing independent roadmap decisions within 90 days.
4. Recognized that our PM team lacked technical depth — conversations with Engineering about feasibility and tradeoffs regularly stalled. I built a technical fluency curriculum: 6 monthly lunch-and-learns led by senior engineers, pairing PMs with an engineering partner for 1 sprint each quarter, and a recommended reading list on system design. PM confidence in technical conversations, measured in an anonymous survey, improved from 2.9 to 4.1 out of 5 over the year.
5. After a reorg, I inherited 2 PMs who had been managing their own roadmaps independently for 3 years with minimal oversight. I established 1:1 cadences, introduced shared OKRs, and ran joint roadmap reviews for the first time. Initial resistance settled within 6 weeks. Both PMs cited the collaboration as their top positive change in their annual review.
6. Identified a pattern: we were losing PM candidates to a competitor who offered more autonomy. I restructured our PM role scoping — gave each PM full ownership of a product area including the business metric, not just the feature backlog. 3 of the next 4 candidates we offered chose Prov over competing offers, citing ownership clarity as the deciding factor.
7. Our PM team had no career ladder. I wrote it from scratch: 5 levels from Associate PM to Director of Product, with clear criteria for each level across 5 dimensions. I calibrated every PM on the ladder before publishing. Within 2 quarters, 3 PMs had submitted promotion cases with clear evidence against the ladder criteria. All 3 were approved.

PM Development & Coaching

1. A senior PM was strong tactically but consistently struggled to articulate the strategic rationale for her roadmap decisions in executive reviews. I worked with her monthly on the "so what" layer — practicing the move from "we built X" to "we built X because we believed Y and we saw Z." Within 2 quarters, she was presenting independently to the CPO with no preparation coaching from me.
2. I had a PM who was technically excellent but avoided conflict with Engineering leads, resulting in scope creep and missed timelines. I coached him on structured disagreement — how to surface a tradeoff, name the cost, and propose a resolution without a confrontation. I role-played 3 scenarios with him. He navigated a major scope conflict independently 6 weeks later. Engineering lead cited the interaction positively in a cross-functional survey.
3. Established a PM peer review process: once per quarter, each PM presented their current roadmap and reasoning to the full team for 30 minutes of structured feedback. The first session was uncomfortable. By the third session, PMs were proactively incorporating feedback and the quality of strategy briefs improved noticeably — the CPO commented on the improvement in the next planning review.
4. Two mid-level PMs wanted to grow into senior roles but lacked exposure to cross-functional leadership. I created "sponsorship projects" — each PM led one cross-functional initiative with visibility at the VP level, with coaching from me. Both PMs were promoted within 14 months. One was promoted to Group PM 6 months after that.
5. I instituted a product review for every PM every 6 months — a structured 60-minute session reviewing outcomes, decisions made, and development areas. Not a performance review: a thinking partnership. PM satisfaction with management quality, measured in an annual survey, improved from 3.6 to 4.5 out of 5 in the year following the change.

5. Customer & Market Insight

Customer Research & Discovery

1. Our PMs were building features based on customer requests rather than customer problems. I introduced a mandatory discovery phase — 5 customer interviews minimum before any feature started spec. Initially met with resistance from PMs worried about timeline. Within 2 quarters, every PM was defending the time because 4 of the 7 features that went through discovery were materially changed before build started — avoiding 3 estimated dead-end features.
2. We had no systematic way to identify which customers were getting value and which were struggling silently. I built a health scoring model with Data and Customer Success — combining product usage signals, support ticket frequency, and NPS data into a single health score. Within 3 months of launch, CS was using health scores to prioritize outreach. Churn in the red-score segment decreased by 22% in the following two quarters.
3. Ran a 3-month jobs-to-be-done research program — 48 interviews across 6 customer segments. The output reshaped our understanding of why customers bought us and what success looked like to them. 3 roadmap items were deprioritized because they didn't map to any JTBD. The single most-cited JTBD became the anchor for our next major feature investment, which became the highest-adoption feature we'd shipped in 2 years.
4. Our team was relying on a customer advisory board that skewed heavily toward power users — the insights we were getting were optimizing for 10% of our user base. I restructured the CAB to include 5 seats for users in the lowest-usage quartile and introduced a separate quarterly session for new users. Discovery quality improved — we found 3 onboarding blockers that power users had long since forgotten.
5. Identified that our product was making assumptions about workflows that weren't true for most of our target segment. Ran a series of contextual inquiries — visiting 6 customers on-site and observing actual workflows. Found 2 critical workflow mismatches that no amount of remote research had surfaced. Both mismatches drove roadmap changes that improved activation by 19 points over the next two quarters.
6. We were making feature prioritization decisions without understanding the distribution of usage across our feature set. I partnered with Data to build a feature usage heatmap — percentage of active users who had used each feature, and frequency. We discovered 4 heavily-invested features with under 8% adoption. Two were redesigned; two were deprecated. Engineering capacity recovered: approximately 6 weeks over the year.

Feedback Systems

1. Our NPS process was producing a score with no actionable signal — we knew if customers were happy but not why. I rebuilt the NPS program: added an open response requirement, built a tagging taxonomy for the free text, and assigned a PM owner to each tag category. Within 2 quarters, NPS verbatims were driving roadmap prioritization conversations for the first time.
2. Customer support tickets were a goldmine of product insight that the product team was not systematically accessing. I built a bi-weekly ticket review ritual: a PM rotated into a 60-minute session with Customer Support to review the top 20 tickets by volume. Within 3 months, 4 product changes had originated directly from ticket review sessions, and support ticket volume for the affected features dropped by 37%.
3. We were running user research in isolation from Engineering — engineers never heard directly from customers. I introduced a "customer voice" slot in our monthly all-hands: a 15-minute session where a PM plays 3 customer call recordings with key moments annotated. Engineer-initiated feature suggestions increased measurably, and 2 of those suggestions became shipped features.
4. Our beta program was informal — we'd invite a handful of customers, get some Slack messages, and call it tested. I rebuilt it into a structured program: defined beta criteria, a screener process, structured feedback templates, and a debrief meeting before GA. The first feature run through the new program caught 3 critical UX issues that would have shipped to all users. Beta feedback quality in PM surveys improved from 2.8 to 4.3 out of 5.
5. Implemented a quarterly "win/loss analysis" process — debriefing every closed-won and closed-lost deal over $50K ARR with the AE and, where possible, the prospect. I ran the first 8 sessions myself to establish the process, then handed off to a PM. Within 6 months, we had identified 2 structural competitive disadvantages and 1 positioning problem that we'd previously attributed to pricing. Both drove roadmap and positioning changes.

6. Business Impact & Metrics

Revenue & Growth

1. Identified that our expansion revenue motion was almost entirely reactive — CS was waiting for customers to ask rather than identifying expansion opportunities proactively. I built a product-led expansion playbook with CS leadership: 4 usage-based signals that correlated with readiness to expand, and a sequence for each. In the quarter following rollout, expansion ARR increased by 31%.
2. Our freemium conversion rate had stagnated at 4.2% for 3 consecutive quarters. I ran a comprehensive conversion audit — cohort analysis, funnel mapping, user interviews. Identified that the paywall trigger was happening before users experienced the core value. Moved the gate to post-value-moment. Conversion rate improved to 7.1% within 2 quarters, representing approximately $800K in additional annualized ARR.
3. Proposed and led the launch of a new product tier targeting a previously unaddressed segment — solo practitioners who found our team plan too expensive. I scoped the MVP, ran the pricing research, and coordinated launch with Marketing. New tier reached $200K ARR in its first 6 months and opened a channel we'd never accessed.
4. Our annual contract renewal rate was declining — down 4 points year-over-year. I ran a churn diagnostic: exit interviews, product usage patterns of churned accounts, and a survey of at-risk accounts. Found that customers who hadn't activated a specific workflow feature within 60 days churned at 3× the baseline rate. Built an onboarding campaign targeting that activation milestone. Renewal rate recovered 3 points in the following year.
5. Led the product strategy for a partnerships program — building native integrations with 4 complementary tools used by 60%+ of our target customers. I scoped the integrations, prioritized by partner TAM and integration complexity, and owned the technical and commercial roadmap. Integrated customers showed 28% higher retention and 19% higher expansion ARR than non-integrated customers at 12 months.
6. Identified that our pricing structure was penalizing growth — customers who grew their user base were hitting a price step that created a churn trigger. I built the case for restructuring the pricing model, ran the willingness-to-pay research, and partnered with the CEO and Finance to model the revenue impact. Restructured pricing launched and reduced price-driven churn in the affected segment by 40% in the following year.
7. Drove a pricing experiment across 3 segments — tested raising the top-tier annual price by 18%. I designed the test, ran it for 90 days, analyzed the results. Conversion rate decreased by 2.1 points, but ACV increase more than offset the volume loss. Net revenue impact: positive $340K annualized. We maintained the new pricing.

Retention & Engagement Metrics

1. Day-30 retention had been flat at 41% for 6 months. I ran a segmented analysis — found that retention varied from 18% to 67% depending on the activation path. Built a hypothesis that the low-retention paths were failing to deliver the core value moment. Redesigned 3 onboarding paths to route to the value moment earlier. Day-30 retention improved from 41% to 54% over the following quarter.
2. Our engagement metrics were tracking feature breadth — the number of features a user had tried. I argued that breadth wasn't predictive of retention. Partnered with Data to identify the usage patterns that actually predicted 12-month retention. Found that depth in 1-2 core workflows was far more predictive than breadth. Reconfigured our engagement model around depth signals. Retention prediction accuracy improved from 61% to 78%.
3. Identified a silent churn pattern: customers were staying subscribed but ceasing active use 60 days before cancellation. By the time CS noticed, it was too late. I built an early warning system with Engineering: a 30-day usage decline alert routed to CS. CS ran a save program against the alerts. Save rate for the alerted cohort was 34% vs. 11% for the unalerted control group.
4. Our power users were getting no dedicated product investment despite representing 40% of referral-driven pipeline. I proposed and delivered a "power user program" — 3 features exclusively for the top usage decile, built in collaboration with 12 volunteer power users. NPS among the power user segment increased from 48 to 71. Referral-attributed pipeline from the segment increased by 22% in the following two quarters.
5. Feature engagement was consistently higher at launch than 90 days post-launch — features were sticky for early adopters but lost momentum. I ran a feature lifecycle analysis and found that most features had no ongoing engagement loop. Introduced a habit-loop review step in the spec process. The next 4 features designed with the habit-loop review showed 90-day engagement rates 31% higher than the preceding cohort of features.

How to Adapt These Examples

Plug In Your Numbers

Every example above follows: [Action] + [Specific work] + [Measurable result]. Replace the numbers with yours. If you don't have exact metrics, use ranges ("improved by roughly 20-30%"), directional language ("measurably improved"), or leading indicators ("reduced the primary driver of churn in that segment").

Don't Have Numbers?

Product leaders often struggle with metrics because the causal chain from your decision to a business outcome is long. Start closer to your decision: How many customer interviews did you run? How many stakeholders did you align? How many roadmap items did you kill, and what capacity did that free? How many PMs did you hire or promote? These are real measurements even when revenue attribution is hard. Also: dig back through your launch briefs, OKR documents, and quarterly reviews. The numbers are usually there — you just haven't collected them into a single document before.

Match the Level

At the Head of Product and VP of Product level, reviewers expect organizational scope. "I wrote a spec" is IC work. "I established the spec process that improved delivery quality across 8 PMs and 3 engineering teams" is leader work. Shift your language from the feature to the system: the framework you built, the team you developed, the alignment you created, the org change you drove. The higher the level, the more your accomplishments should describe changes to how the organization works — not just what it shipped.

Start Capturing Wins Before Next Review

The hardest part of performance reviews is remembering what you did 11 months ago. Prov captures your wins in 30 seconds — voice or text — then transforms them into polished statements like the ones above. Download Prov free on iOS.