Performance Review Tips for Project Managers

Project manager reviews have a hard job to do. They have to give the PM usable signal on craft, hold up at PMO calibration against PMs running different project shapes, satisfy executive sponsors who saw only the status-report layer, and avoid the generic-PM voice that strong practitioners recognise as filler.

Three sections: tactics for PMO directors, tactics for PMs writing self-evaluations, and the moves both sides should get right. For the underlying framework, see how to write a performance review for a project manager.

Tips for PMO directors and program leadership

1. Read the RAID log, not just the status report

Status reports are the polished surface. The RAID log is where you see whether the PM actually practiced risk discipline or just kept a tab open. Read the log for two of the year’s major projects: were risks raised in advance, were mitigations real, did the log reflect the actual risks of the project. RAID quality is the single best window into senior PM craft.

2. Talk to two sponsors and one team lead per project

Ten minutes each. You’re looking for the pattern beneath the polished steering-committee layer. Did the PM brief the sponsor cleanly on the hard moments, did they escalate at the right time, did the team-lead-level dynamics match the sponsor-level narrative. The gap between status- report claims and team experience is often the most informative thing in the review.

3. Read the variance against the right baseline

Schedule and budget variance against the original baseline can be misleading if the project was re-baselined cleanly mid-flight. Read both the original baseline and the most recent accepted baseline. A project re-baselined professionally in month 4 and then delivered against the revised plan is a different evidence base from a project that quietly drifted.

4. Don’t use methodology familiarity as craft proxy

PMP, PRINCE2, Agile, SAFe. Methodology familiarity is table-stakes. The differentiating question is whether the PM adapted methodology to the project context. A PM running rigid SAFe ceremonies on a small coordination program is showing weaker craft than a PM adapting the approach to the situation.

5. Weight the retrospective work

Retros that produced nothing are the floor of practice. Retros that produced template work, process changes, cross-project insights, or practice changes the PM has personally adopted are senior-level craft signal. The retro-to- change loop is often the highest-leverage thing the PM does in the year and reviewers tend to under-weight it.

6. Don’t deliver new feedback at review time

If the PM is hearing a piece of feedback for the first time in writing at the annual review, the steering-meeting and post-project conversation cadence has slipped. The review should formalise patterns you’ve been naming, not introduce them.

Tips for project managers writing self-evaluations

7. Build your evidence inventory in November

Self-evaluations written the night before they’re due lean on the project list. Sixty minutes pulling project variances with context, three risk moments, three stakeholder moments, and one project that didn’t go well, gives you the raw material. See the prep step in project manager self-evaluation examples.

8. Lead with the craft moment, not the project

“Delivered the platform migration” is a project. “Re-baselined the platform migration in month 4 by surfacing the engineering-capacity constraint six weeks ahead, framing three options to the steering committee, and landing an accepted revised plan” is a craft moment. The craft is what makes the work yours.

9. Name one specific risk moment

On the “biggest impact” prompt, pick one specific risk-management moment and tell the story. The risk that didn’t materialise because of your mitigation. The escalation that landed at the right time. The change request you ran through change-control rather than absorbing silently. These moments are senior PM craft and they’re invisible in the Gantt.

10. Surface the work beyond your projects

The PMO template you contributed. The cross- project lesson you documented. The earlier-career PM you mentored. The cadence improvement you suggested that got adopted. Process-and- improvement work is where senior PM contribution lives.

11. Name one project moment that didn’t land

Pick a real situation. The schedule slip you should have flagged earlier. The change request you absorbed silently. The stakeholder relationship that strained. Specific honesty builds credibility; generic “could improve communication” evidences nothing.

12. Frame goals as practice changes

“Run better retros” is a non-goal. “Build a quarterly cross-PM retrospective into the PMO cadence with structured pattern- finding, with target adoption by the full PMO by mid-year” is a goal.

Tips for both sides

13. Have a pre-review conversation

Two weeks before the review meeting, schedule 30 minutes to compare notes. The point is to surface disconnects on the headline narrative, not to align documents.

14. Acknowledge project context openly

Both sides should name the project context: the vendor changes, the sponsor turnover, the engineering capacity context, the scope-change pressure. Leaving these implicit is one of the most common ways calibration outcomes go sideways twelve months later.

15. Treat the review as the start of the next year

Agree on two or three specific things to do differently next year. Write them down. Return to them in February. A review that doesn’t change practice is paperwork; the follow-up cadence is where the actual development happens.

The shape of a PM review that ages well

Twelve months from now, read the review and ask whether you could picture the year of project work it described. The strong reviews pass. They have specific projects named, specific variance context, specific risk and stakeholder moments, specific retro-to-practice loops. The weak reviews could be about any PM at any company on any project.

The rest of the cluster:

• How to write a performance review for a project manager for the four-pillar framework.
• Performance review examples for project managers for five worked examples.
• Project manager self-evaluation examples for the PM-side counterpart.