Promotion Peer Review Generator

A peer review written to support someone's promotion case has to be specific about impact, not just complimentary. This is a full one, rated an 8.

Liam's Promotion Review - Peer Assessment

What this was generated from

Review Type: Peer Assessment
Assessment Period: Promotion Review
Job Title: Product Manager
Project or Team: Onboarding redesign
Industry: Software & Technology
Company Type: Startup
Tone: Encouraging
Rating: 8 out of 10

Key Tasks & Responsibilities

Own the roadmap and prioritisation for the onboarding product area
Run discovery with customers and translate findings into specs
Work with engineering and design leads to ship features
Present roadmap and results to leadership each quarter

Key Accomplishments & Contributions

Rebuilt the onboarding roadmap around what discovery actually showed
Shipped the self-serve onboarding flow that measurably cut support tickets
Other PMs now ask him to review their specs before they go to engineering
Presents to leadership with more clarity and confidence than a year ago

The review

Working alongside Liam on the onboarding redesign has given me a pretty good window into how he operates as a PM, since our teams sync weekly and our roadmaps constantly intersect. What's stood out most this year is how he rebuilt the onboarding roadmap around what discovery actually showed rather than what everyone assumed going in. That's a harder call than it sounds. It means telling stakeholders that some pet feature isn't actually the priority, and Liam did that without making it feel like a fight. He ran the customer interviews himself, pulled out the real friction points, and turned that into specs that engineering could actually build against instead of vague direction that gets reinterpreted three times before it ships.

The self-serve onboarding flow is the clearest example of that work paying off. It shipped, and support tickets related to onboarding dropped in a way that was noticeable to teams outside product, which says a lot given how many groups touch that funnel. I remember hearing about it secondhand from someone on support before Liam even brought it up, which tells you the impact was real and not just something written up in a launch doc. That's the kind of outcome that's hard to argue with when you're building a case for what a PM has actually delivered.

What I've appreciated from a cross-functional standpoint is how he handles the handoff between discovery and execution. A lot of PMs are strong in one direction or the other, either great at talking to customers or great at working the engineering side, but Liam's specs are clean enough that other PMs, myself included, now ask him to review theirs before they go to engineering. That's not a small thing at a startup where everyone's stretched thin. It means his judgment is trusted beyond his own product area, which is honestly one of the better signals of readiness for more scope. I've sent him a spec or two myself just to get a second pair of eyes, and his feedback is usually the kind that saves a sprint's worth of back-and-forth later.

On the leadership side, I've sat in on a couple of his quarterly roadmap presentations, and the difference between where he was a year ago and now is obvious. He presents with more clarity and confidence, less hedging, more direct ownership of the numbers and the tradeoffs behind them. Where he used to lean on the deck to carry the narrative, now he's the one steering the room, fielding pushback on prioritization calls without getting rattled. That matters a lot in a startup environment where leadership is making fast calls on where to invest, and a PM who can clearly connect roadmap decisions to customer evidence and business outcomes makes those calls a lot easier.

If I had to point to a growth area, it'd be that Liam's strength in discovery and spec-writing sometimes means he's pulled into helping other teams (myself included) more than his own bandwidth probably allows. I think there's a version of this where he's a bit more protective of his own roadmap time, or at least more explicit about the tradeoff when he says yes to reviewing someone else's spec. It's a good problem to have, honestly, since it's a direct result of people trusting his judgment, but it's worth watching so it doesn't quietly turn into scope creep without the title to match.

Taken together, this has been a year where Liam moved from "executes well on a defined product area" to something closer to a cross-team resource whose judgment other PMs actively seek out. The onboarding roadmap rebuild, the self-serve flow shipping with a measurable drop in support load, and the shift in how he shows up in front of leadership all point the same direction. I'd be glad to have him weigh in on my own team's specs going forward, and I think that's exactly the kind of informal signal that should carry weight in a promotion conversation. He's earned the case being made for him.

That one is Liam's. Yours would be built from your work.

Every specific in the review above comes from the handful of inputs listed with it. Swap those for your own tasks and achievements and our generator writes the same quality of draft about your year instead of Liam's.

Generate your own review free - Start with Free Credits. No credit card required.