Guide · Self-reviews

Self-review examples for product managers.

A PM's output is mostly documents and decisions, so a PM self-review can turn into a list of meetings. Reviewers want to know what changed for users and for the business, which bets you made, which you stopped, and how well the team understood why.

What reviewers look for in a product manager

Outcomes over features. Adoption, retention or task success that moved, against what you expected.
Decisions. What you chose not to build, and the evidence behind it.
Discovery. How you found out what to build before the team spent a quarter on it.
Clarity. Whether engineers and designers knew the why without asking you.
Delivery. Launches on the date you set, or a clear reason the date moved.

Example: impact

The projects, people and numbers in these examples are made up. Keep the shape and use your own facts.

Impact • Launched Recipe App 2.0 with offline sync. Weekly active recipe editors grew about 18% in the eight weeks after launch, compared with the eight weeks before. • Stopped the social feed after a two-week discovery spike: 5 of 12 people we interviewed liked the idea, and none said they'd use it weekly. That returned roughly a quarter of the team's time to sync quality. • Wrote the Sync SDK adoption plan. Three internal apps moved to the SDK this half, which let us retire two old sync services.

A stopped project is impact. Write it with the evidence and the time it gave back, the same way you'd write a launch.

Example: collaboration

Collaboration • Ran a weekly 20-minute decision review with Ravi (engineering) and Neha (design). Every decision went into one log with its reason: 31 this half. • Rewrote the 2.0 spec as a one-page brief plus open questions. Engineering estimates came back in days instead of weeks. • Shared launch numbers with the whole team every Friday for the first month, including the ones that were flat.

Example: growth

Growth • Learned enough SQL to answer my own adoption questions instead of queueing them for the data team. • Got better at saying no in writing. Three requests this half got a short "not now, because" note instead of a vague maybe. • Next half: run discovery for meal plans with a stop rule agreed before we start.

Phrases that land

"we decided not to build X because Y": judgement, which is most of a PM's output.
"up about 18% against the eight weeks before": a comparison with a baseline.
"returned a quarter of the team's time": the cost of a decision, made visible.
"including the ones that were flat": trust, shown rather than claimed.

Phrases that don't

"Drove alignment." Say who disagreed, and what they agreed to.
"Owned the roadmap." Say what changed on it and why.
"Worked cross-functionally." Every PM does. Name the trade-off you brokered.
"Shipped 14 features." Output. Which ones mattered, and how do you know?

Gather your evidence

PM evidence lives in documents. Gather it into one place before review week:

Specs and briefs. The first version and the final one. The difference shows your thinking.
Launches. Announcements, release notes, and a metrics snapshot from launch day and a month later. Dashboards change; screenshots don't.
Decisions. Your decision log, or the threads where a direction changed.
Discovery. Interview notes and the summary: how many people, and what you concluded.
Calendar. Count the customer calls and research sessions. It's a quick measure of time spent with users.

Let Sill keep the record

Sill is built for developers, but a PM's year has the same shape: tasks finished, releases shipped, and a lot of waiting on other people. Sill records your tasks and follow-ups on iPhone, iPad and Mac, with receipts on every dependency, like day 6, asked 3×. Commits only appear if you work in a git repo on a Mac.

At review time, Sill Pro's Review generator turns months of that into a draft per project. Where Apple Intelligence is available it writes a first-person draft on the device, and nothing leaves it. The last 7 days are free; longer periods need Sill Pro, an optional paid upgrade.

Get Sill on the App Store — for Mac, iPhone, iPad and Apple Watch. The daily standup and its set-time reminder are free.

More self-review examples: backend engineers · frontend engineers · iOS engineers · Android engineers · QA engineers · SRE and DevOps engineers · data engineers · engineering managers · product designers. Or start with how to write a self-review.