The 7 most common 360 assessment mistakes and how to avoid them

In more than two decades of working with 360 assessments across the Americas, I have seen processes that open up valuable conversations and others that end with the delivery of a report. The difference often lies in how the assessment is prepared, communicated and supported. A well-designed questionnaire needs a process that helps people understand the results and turn them into development actions. Here are seven mistakes I recommend checking for before starting a 360 assessment project.

1. Starting without visible leadership commitment. When senior leaders do not understand the purpose of the process or present it as an HR formality, involving participants becomes harder. How to avoid it: agree at the outset on what you want to develop, why it matters and what support people will receive after the assessment. Ask leaders to explain its importance, respect the process guidelines and participate where appropriate.

   Commitment also means making time for feedback and follow-up, as well as completing the questionnaire.

2. Failing to explain the purpose and participation guidelines Sending an invitation with a deadline is not enough. Raters need to know which behaviors to consider, while feedback recipients need to understand how the results will be used. How to avoid it: provide a brief explanation of the objective, roles, schedule, response scale, report access and where to ask questions. A video or virtual meeting can reinforce the message.

   If a process is presented as developmental, its results should not later be used for other decisions without having communicated that use in advance. Clarity about how information will be used is part of the agreement with participants.

3. Promising confidentiality without defining how it will be protected Trust requires clear rules. Confidentiality means controlling access to and use of information; anonymity means that a response cannot be attributed to an individual. They are not interchangeable. How to avoid it: explain who will see the results, how responses are grouped and which categories may be identifiable, such as the direct manager. Define a minimum number of responses per group and what happens if that threshold is not met. Do not promise protection the design cannot provide. Open-ended comments can also reveal identities through their content. Give guidance on writing them and establish consistent handling practices. An external consultant can facilitate the process, but their involvement alone does not guarantee anonymity.

4. Making assessments too long or overloading raters. The workload depends on both questionnaire length and the number of people each rater must assess. Ten assessments taking 30 minutes each amount to five hours of work. How to avoid it: focus on priority competencies and pilot the questionnaire to estimate completion time. In my practice, I have used questionnaires of up to 40 items as a reference point and aimed to limit assignments to five assessments per person. These are practical guidelines to adapt to each project, not universal rules. Choose raters who know the person’s work, without reducing their number so far that you lose relevant perspectives or compromise response protection. Where appropriate, allow raters to indicate that they have not observed a behavior.

5. Delivering the report without a feedback conversation. A report may reveal differences between self-perception and others’ perceptions, but those differences need context. Sending the file without support can leave questions unanswered. How to avoid it: schedule a conversation with a professional who is prepared to interpret the instrument. Review strengths, patterns and opportunities without turning an isolated score into a label about the person. Provide results promptly and agree on one or two development priorities. The conversation should help identify which behavior to practice and what support is needed..

6. Using ambiguous questions or combining several behaviors in one item. An unclear item makes it difficult to know what is being assessed. For example, “communicates well, motivates others and resolves conflict” combines three different behaviors in a single response. How to avoid it: build each item around an observable behavior that is relevant to the role and expressed in plain language. Instead of “is a good leader,” a more specific statement would be: “Clarifies team priorities when work requirements change.” Review the response scale, reference period and participants’ understanding of the items before launch. Clear wording improves interpretation, although it does not, on its own, establish an instrument’s validity.

7. Ending the process when results are delivered. A 360 assessment can offer valuable perspectives when there is clarity, trust and support. My recommendation is to plan from the outset what will happen before, during and after the assessment. At OD Evolution, we combine the 360 Evolution platform with training to support organizations and consultants in their assessment and development processes.