Product managers have a strange problem at review time. You were involved in almost everything, but you built almost nothing yourself. Engineers shipped the code, designers made the screens, sales closed the deals. So what goes in your self-evaluation?
The answer is your part: the problem you found, the call you made, the people you aligned, the risk you caught early. The examples below show how to write that down for five areas most PM review forms cover.
All examples are illustrative. Replace the details with your own work and only keep a number if you can point to where it came from.
The formula: decision, action, result
A strong PM self-evaluation line answers three questions:
- What decision or problem was yours?
- What did you do about it?
- What changed because of it?
For example: "Noticed most trial users never finished setup (problem), ran five user calls and cut the setup flow from four screens to two with design (action), and setup completion went up the following month (result)."
If you have the actual figure for "went up", add it. If you don't, the sentence still works.
Product outcomes and strategy
- "Owned the reporting roadmap for the year. Chose to rebuild exports before adding new charts because support tickets showed exports were the top complaint; export-related tickets dropped after the release."
- "Wrote the case for retiring the legacy plan, aligned sales and finance on the migration, and moved existing customers over without a pricing escalation reaching leadership."
- "Defined the success metric for the onboarding project before kickoff, which let the team stop work on two ideas that didn't move it."
Execution and delivery
- "Shipped the pricing page relaunch on the planned date after legal requested late copy changes, by re-sequencing design work and running a daily 15-minute check-in for the final two weeks."
- "Cut the scope of the mobile release to the three features customers asked for most so it could ship before the holiday freeze."
- "Set up a weekly written status update for the project, so stakeholders stopped asking for separate briefings."
Discovery and customer insight
- "Ran [number] customer interviews on the reporting workflow and turned them into three themes that shaped the next quarter's roadmap."
- "Spotted in support data that churned accounts rarely used the integration, and brought that to the team as the first problem to investigate."
- "Tested two versions of the upgrade prompt with design before engineering started, which avoided building the version users found confusing."
Collaboration and influence
- "Built a shared launch checklist with marketing, support and sales so every release now has docs, a help article and a sales note on day one."
- "Mediated the disagreement between design and engineering on the editor rewrite by writing up both options with costs; the team agreed on a phased approach in one meeting."
- "Onboarded two new engineers to the product area with a written context doc that the team still uses."
Growth and leadership
- "Took over the analytics backlog when the data PM left, learned the event schema and kept the dashboards accurate through the transition."
- "Started running quarterly roadmap reviews with customer-facing teams, which gave sales an earlier view of what was coming."
- "Asked for feedback on my written specs and changed the format to start with the problem and the success metric."
Areas for improvement (honest examples)
Most forms ask what you'd do differently. Pick something real and show what you're doing about it.
- "I said yes to too many small requests in the first half, which delayed the reporting rebuild. I now batch small asks into a monthly review with my manager."
- "My early specs were long and skipped the 'why'. I've moved to a one-page format and ask an engineer to review it before kickoff."
Fill-in template
Role: Product Manager
Review period: [start] to [end]
Top outcomes
1. [Decision/problem that was mine] -> [what I did] -> [what changed]
2. ...
3. ...
Execution
- [Release or project] shipped [on time / with scope change] because I [action].
Discovery
- [Research or data I gathered] led to [decision].
Collaboration
- [Team or person] + [what we did together] -> [result].
Growth
- [Skill or habit I improved] and how I know.
Next period
- [1-3 goals tied to the team's priorities]
Mistakes that weaken a PM self-evaluation
| Mistake | Better |
|---|---|
| "We launched X" with no sign of your role | "I scoped X down to three features so we could launch before the freeze" |
| Listing every meeting and doc | Three to five outcomes tied to team goals |
| Vague impact like "greatly improved retention" | The real figure, or a plain description of what changed |
| Only wins | One honest miss and what you changed |
| Writing it the night before | Weekly notes you can pull from |
Start collecting examples now
The examples above are easy to write when the details are fresh and almost impossible to reconstruct in November. A two-line note each Friday ("what did I decide, what changed") is enough. If you already send a weekly status update, you have most of it.
Looking for a different role? See project manager self-evaluation examples for delivery-focused roles, or the full list on the resources page.
To turn a single note into a structured story right now, try the free STAR method generator. To keep notes every week and get a brag sheet at review time, start free on WinStash.