Coordinate project and line-manager input without conflicting ownership or duplicate review conversations. This practical guide to multi-manager performance management brings together a step-by-step approach, illustrative examples, a reusable worksheet and answers to common questions. Start with the section closest to your current challenge, then use the working session to turn the guidance into a clear next action.
Name one review coordinator
Multi-manager performance reviews bring together perspectives from people who see different parts of an employee’s work. They are useful in project, matrix and shared-service organisations, but they need clear ownership. Name the person responsible for coordinating evidence, discussing differences and completing the approved review process.
Distinguish contributing a perspective from making the final assessment. A project lead may understand delivery on one assignment while a line manager sees longer-term development. Neither view automatically represents the whole period. Explain the roles to the employee before collecting input.
Agree scope and questions
Ask each contributor about the work they actually observed and the period involved. Use consistent questions about expectations, actions, impact and relevant context. Include a way to say that a behaviour was not observed rather than forcing a rating.
Share enough role and goal context for the contributor to respond usefully. Do not distribute unrelated personal information or the full review history. Permissions should follow responsibility, and access should be reviewed when projects or reporting relationships change.
Preserve differences that need discussion
Conflicting observations may reflect different tasks, conditions or expectations. The coordinator should investigate the difference rather than automatically averaging scores. Ask what each contributor saw and whether priorities or dependencies changed.
Give the employee an opportunity to add context and correct facts. A review that collects several perspectives but never explains how they were interpreted can feel less transparent than a single-manager process. Record the reasoning behind the final conclusion in language the employee can understand.
Worked example: two project priorities
Illustrative scenario: one project lead praises rapid delivery while another criticises delayed support work. The coordinator finds that both assignments were treated as urgent and no owner resolved the conflict.
The review acknowledges the employee’s contributions and the organisational priority problem. The next plan names a person who can resolve competing requests and sets a shared view of capacity. The employee is not assessed as if both incompatible commitments could have been met independently.
Multi-manager review worksheet
- Coordinator: Who owns the complete process and final handoff?
- Contributors: Who observed relevant work, and during which period?
- Expectations: Which goals and responsibilities applied to each assignment?
- Evidence: What actions and effects can each contributor describe?
- Differences: Which accounts need clarification rather than aggregation?
- Employee context: What corrections or explanations must be considered?
- Next steps: Who owns development support and future priority decisions?
Use one coordinated request where possible. Several overlapping forms can create burden without adding a genuinely different perspective.
Improve the next cycle
Review whether important work was represented and whether contributors understood their responsibilities. Check the time spent reconciling evidence and remove duplicated questions. Explain access and retention so people know where their input will appear.
Connect the final actions to ordinary check-ins and project planning. If the same conflicts recur, change the ownership or workload process rather than asking the employee to manage competing leaders alone. Use the calibration guide for consistent interpretation and the performance review guide for the employee conversation.
Put the guide into practice
Set aside a working session with the people who own this process and one or two people who experience it. Use a fictional or appropriately authorised case, so the discussion can be specific without sharing unnecessary personal information. The purpose is to leave with a usable decision or document, not just agreement that the topic matters.
Prepare the case
Choose a fictional employee who reports to one line manager and delivers work for two project leads. List the outcomes each lead expected during the same period. Note where deadlines compete, where the employee had decision authority and where success depended on someone outside the team. Keep contribution evidence separate from each manager’s preference.
Write the starting assumptions down before discussing solutions. If the group disagrees on what happened, identify the information needed to resolve that difference rather than building a plan on an untested story.
Work through the decision
Allocate responsibility for one overall assessment to the line manager. Ask project leads to describe observable contributions using the same short questions. Have the group reconcile competing priorities before discussing an overall judgement. The employee should not be marked down for following a priority that the managers themselves agreed and then forgot to document.
Ask each participant to explain the proposed decision in their own words. Differences in interpretation often reveal an unclear criterion, a missing responsibility or an instruction that will be difficult to follow.
Test an exception
Introduce a project lead who submits negative feedback after the agreed deadline. Decide whether the information is relevant, specific and already discussed with the employee. If it could materially change the assessment, give the employee a fair opportunity to respond. Record the reason for reopening the discussion instead of quietly changing the final rating.
Record what changes in this situation and what remains the same. An exception should lead to a clear next step, with an owner, rather than an informal workaround that nobody can explain later.
Agree the handoff
Prepare a one-page summary that names the accountable manager, the contributors, the agreed priorities and the next review date. Show the employee how to raise conflicting instructions during the cycle. Ask a colleague unfamiliar with the project to read it and identify who makes a decision when two leads disagree.
Finish by confirming the owner, the next action and the date when the result will be reviewed. Give the person receiving the work enough context to continue without repeating the whole discussion.
Frequently asked questions
Who owns a review when someone has several managers?
Name one accountable manager who coordinates evidence, holds the main conversation and explains the final assessment. Other managers contribute observations about work they directly supervised. Accountability should not mean ignoring their input, but it should prevent the employee from receiving several incompatible final decisions. Explain the arrangement at the start of the cycle and revisit it when assignments change.
Should every manager have an equal vote?
A vote can hide differences in observation and responsibility. A project lead who worked closely with someone for six months may have more relevant evidence than a sponsor who attended one presentation. Discuss the quality and scope of each contribution rather than automatically averaging opinions. If a formal rating method is used, publish its rules and explain how conflicting evidence is resolved.
How can employees challenge conflicting feedback?
Give employees a named contact and a clear opportunity to add context before the review is finalised. Ask them to identify the work, the original instruction and the consequence of following it. The managers should resolve the conflict together rather than asking the employee to negotiate privately with each person. Record the clarified expectation for the next cycle and confirm who owns it.
Review the first cycle
Review whether the process reduced conflicting instructions and produced a clearer overall conversation. Ask employees which expectations were still ambiguous and ask managers how much time evidence collection required. Look for projects that repeatedly generate late feedback. Improve the contributor questions or timing before adding another layer of review meetings.
Keep a brief record of what was tried, what participants found useful and what needs to change. Compare the result with the original problem rather than judging success only by completion. If the process created extra work without improving clarity, quality or support, simplify it and test again. Share the agreed change with the people who will use it, and name the person responsible for keeping the guidance current.
About New Dynamics
New Dynamics connects goals, feedback, recognition and reviews around the way organisations work. This guide is published by the New Dynamics Editorial Team as part of our practical library for HR leaders, managers and People teams.
Use the examples and worksheets to structure your own discussions and adapt them to your organisation. Illustrative scenarios are not customer case studies. Policy and employment guidance needs appropriate local review before adoption.
For questions about this guide, corrections or a conversation about your performance management process, email contact@new-dynamics.com. Explore the complete guide library for related resources.
