top of page

Rating People You Only See Through the Project Plan

2 days ago
4 min read
Rating People You Only See Through the Project Plan
Project Planning Meeting

Project managers spend their days measuring work. Milestones, burn-down charts, earned value, risk logs. Then review season arrives and someone asks a different question: how did each person on the team actually perform?

That question is harder than it looks. Most project managers have no line authority over the people on their projects, yet their view of those people often carries more weight than the line manager’s. The line manager sees an employee once a week in a one-to-one. The project manager watched them deliver, or fail to deliver, for six months.

So the project manager’s input matters. The trouble is that very few have been taught how to give it well.

The plan is not the person

A project plan records whether tasks finished on time. It says very little about why. A developer whose tickets slipped for three sprints may have been carrying the hardest integration on the project. A business analyst who hit every deadline may have done it by quietly pushing problems downstream to testing.

When a project manager is asked for feedback, the temptation is to read the plan back as a verdict. Late equals weak and on time equals strong. It is fast and it feels objective, because the numbers came from a tool. It is also how good people get marked down for taking on the work nobody else wanted.

A fairer approach starts by separating two things the plan blends together: what the person was asked to deliver, and what got in their way. The first is a performance question. The second is usually a planning question, and the project manager may own part of the answer.

Write objectives you could actually assess

Most project roles come with objectives written months earlier by someone who had never seen the project. “Contribute to successful delivery of Phase 2” tells a reviewer nothing. By the end of the year nobody can say whether it was met.

Project managers can fix this at kickoff. For each core team member, agree two or three outcomes that are specific to their part of the work and can be checked without argument. For a test lead, that might be the share of critical defects caught before user acceptance testing. For a data engineer, it might be the migration finishing with reconciliation signed off by finance. These sit comfortably alongside the project plan, but they describe the person’s contribution rather than the schedule.

It takes perhaps an hour per person. It saves far more than that when review time comes, because the conversation is about evidence instead of impressions.

Keep a light record as you go

Memory is a poor witness. By December, a project manager remembers the crisis in October and very little of the steady work in March. Recency shapes the rating more than anyone admits.

The simplest defense is a running note: a few lines per person each month, written while the facts are fresh. What they delivered, and where they struggled and why. Most project tools already have somewhere to put this. The habit matters more than the format.

Those notes earn their keep in two places. They make the end-of-year feedback specific, which employees value far more than general praise. And they protect the project manager when a line manager or calibration panel pushes back, because there is a dated record behind every judgment.

Watch who you can’t see

Distributed teams add another distortion. People in the same office as the project manager get noticed. Their late nights and corridor conversations all register. Remote colleagues are judged on what shows up in the ticketing system and the status report.

Researchers call this proximity bias, and it keeps turning up in studies of promotion decisions. The practical answer for a project manager is to apply the same evidence test to everyone: what did this person deliver against what they were asked to deliver, regardless of whether you saw it happen. If the honest answer for a remote team member is “I’m not sure,” that is a signal to ask their peers before writing anything down.

Nobody teaches this part

None of this comes naturally. Project managers are trained to manage scope and schedule, risk and stakeholders. Very few certifications in the field spend any time on assessing people fairly, even though it is one of the things project managers are most often asked to do.

Bodies such as the Institute for Performance Management teach the people side as a discipline in its own right: setting objectives that survive contact with real work, and running a review conversation that holds up to scrutiny because the evidence was gathered all year. Whether a project manager takes formal training or builds the habits alone, the principle is the same. The rating should rest on what the person did, recorded close to when they did it.

A better question for review season

When the line manager next asks for input, try answering a different question from the one you were asked. Instead of “how good is she?”, answer “what did she deliver, and what made it harder?”

That answer is fairer to the employee and far easier to defend. It also turns the project plan back into what it should be: one source of evidence among several, rather than the verdict itself.


Thanks for signing up

© 2026 Project Manager Templates

Contact us on contact@projectmanagertemplate.com

Our network provides end-to-end support for project leaders, from downloadable industry-standard templates to in-depth technical guides and the latest PM software insights. Explore our specialized hubs to scale your PMO and drive strategic value in 2026

bottom of page