Skip to main content
All articlesLeadership & HR

360 degree performance review for managers in Iran

By HR Bamboos Editorial Team

360 degree performance review for managers in Iran

A 360 degree performance review is useful when it is treated as a development process: choose raters who have observed the manager, explain confidentiality, ask about specific behaviour, and turn the report into a safe feedback conversation and an action plan. Collecting forms alone will not improve leadership. A 2005 meta-analysis by Smither and colleagues found that performance improvements after multisource feedback tend to be modest and depend on how the process is used. Design quality and follow-through matter more than the volume of ratings. Source: Personnel Psychology, 2005

What should a 360 degree performance review achieve?

A line manager sees targets and reporting. Peers see cross-functional cooperation. Direct reports experience delegation, clarity, conflict management, and the everyday consequences of leadership style. Combining these perspectives can reveal patterns that one observer would miss. It should complement business results and role objectives, not replace them.

Write the purpose before drafting the questionnaire. A development process requires psychological safety, room to test a new behaviour, and clear limits on access to raw comments. If the same data will directly affect promotion or pay, raters may become cautious or strategic. Mixing developmental and administrative purposes without warning damages trust. CIPD's 2025 performance appraisal guidance also places feedback within an ongoing process of clear objectives and employee development. Source: CIPD, 2025

Define competencies from the actual role. A sales manager, plant manager, and HR manager all lead people, but their critical situations differ. Use the article on successful manager qualities as a starting point, then convert each broad competency into observable behaviour. 'Explains changed priorities to the team' is easier to rate than 'thinks strategically.'

Design rule: clarify the purpose, evidence, and intended use before inviting raters.
PurposeUseful evidenceDecision
Leadership developmentObserved behaviour and examplesChoose a habit to practise
Succession planningPatterns across rater groupsSet development needs before a larger role
Better collaborationImpact on other functionsAgree a change in working practice

How should organisations select and prepare raters?

Select people who have had enough recent interaction to observe the behaviour in question. A manager's supervisor, peers, and direct reports usually provide complementary views. An internal customer or project partner can help when the working relationship is regular. Someone who only knows the manager by reputation cannot provide dependable behavioural evidence.

Let the manager suggest an initial list, but have HR or the process owner review it. This reduces the risk of selecting only friendly voices without excluding legitimate critics. The test is opportunity to observe and absence of an obvious conflict of interest. Where a rater group is so small that a comment would reveal its author, aggregate the data or do not show that group separately.

The invitation should explain purpose, confidentiality, reporting, data access, and expected effort. Train raters to describe a situation, the manager's action, and its effect. Labels such as 'poor' or 'excellent' offer little development value without an example. A 'not observed' option is essential because an honest gap is more useful than a guess.

In Iranian workplaces, hierarchy and concern about identification can make direct reports cautious. A written assurance may not be enough. The process owner should answer questions, explain how group reporting works, and name who can see raw responses. Trust comes from specific access rules that are consistently followed.

How should the questionnaire and report be designed?

Keep the questionnaire focused on the role. Common themes include setting direction, decision-making, delegation, developing people, handling conflict, and cross-functional cooperation. Use a small set of distinct behaviours for each theme. Repetitive items create fatigue without adding useful management insight.

Give rating options behavioural definitions and include 'not observed.' Read averages alongside response distribution and written examples. The same average can hide broad agreement or two groups with sharply different experiences. Scores help locate a pattern, but context explains what the pattern means.

Place the manager's self-assessment beside the views of others. A gap is a subject for inquiry, not a verdict about self-awareness. The manager may perform an action whose effect is unclear to the team, or the team may experience constraints the manager does not see. Atwater and Brett's 2005 research links the way feedback is presented and received with managers' development intentions. Source: Journal of Occupational and Organizational Psychology, 2005

A useful report moves from overview to detail. Show shared patterns first, differences between rater groups next, and anonymised comments last. Avoid ranking managers by a single composite score: role context, team conditions, and observation opportunities differ. A structured candidate evaluation form can be adapted to record behavioural evidence and agreed follow-up actions.

How should the feedback meeting lead to action?

Do not send the report without a supported conversation. Multisource feedback can trigger surprise, shame, or a sense of unfairness. A facilitator should give the manager space to react, then separate data, interpretation, and action. The aim is to find patterns worth testing, not to prove that every comment is correct.

  1. Restate the purpose and confidentiality rules, then allow uninterrupted reading time.
  2. Ask the manager to separate expected messages, surprises, and questions before explaining the results.
  3. Look for repeated patterns across groups. Treat one comment as a signal rather than a final conclusion.
  4. Choose one or two behaviours with meaningful work impact that the manager can control.
  5. Agree when progress will be reviewed and what observable evidence will count.

An action should be visible. 'Communicate better' is vague; 'close each meeting by confirming the decision, owner, and due date' can be observed and discussed. The manager's supervisor must also provide practice opportunities and timely feedback. The U.S. Office of Personnel Management's 2024 guidance emphasises specific, timely feedback focused on behaviour that a person can act on. Source: U.S. Office of Personnel Management, 2024

How can bias and common implementation errors be controlled?

A recent event can colour the whole judgement. Personal liking, similarity, different rating standards, and fear of consequences can also distort responses. Brief rater training, behavioural definitions, and requests for examples reduce these effects but cannot remove them. Treat multisource data as a collection of work-related perceptions, not as objective truth.

  • Allow 'not observed' when a rater has insufficient contact; do not force a score.
  • When groups disagree, examine their work situations because managers may behave differently with senior leaders and direct reports.
  • Remove identifying details from comments before reporting them while preserving the feedback's meaning.
  • If the review informs an administrative decision, disclose that use and the other decision criteria before collecting responses.

FAQ

Should 360 feedback determine a manager's bonus?

Development is the safer primary purpose for a new programme. Directly connecting confidential feedback to pay can reduce candour. If the organisation will use the data administratively, it should disclose the use, weighting, and access rules in advance. Source: CIPD, 2025

Should managers choose their own raters?

Managers can propose an initial list because they know their working network. HR or the process owner should review it for observation opportunity, relationship diversity, and obvious conflicts so that only supportive voices are not selected.

How should one very negative comment be handled?

Check whether it includes an observable example and context, then compare it with other patterns. Do not automatically discard an isolated comment, but do not treat it as a final conclusion without supporting evidence.

How often should the review be repeated?

The interval should give the manager time to practise and receive feedback in real work. Repeating too soon may reproduce the same perceptions; waiting too long weakens accountability. Base the timing on the work cycle, development goal, and opportunity to observe change.

What if the manager rejects the results?

Do not demand agreement with every comment. Explore recurring patterns, differences between groups, and the situations in which perceptions formed. A low-risk behavioural experiment is often more constructive than arguing about whether each perception is right.

A 360 degree performance review works when role-specific design, credible confidentiality, and management follow-through support one another. If purpose and access rules remain unclear, fix the process before sending a questionnaire. The HR consulting page outlines support for performance system design and manager development in Iran.

Prefer to talk directly?

Our consultant answers — call us, or request a consultation and we reply within one business day.