360 Feedback Examples: From Insight to Action

How to read a 360 feedback pattern

Start with the purpose and limits of the exercise. A development review gathers perspectives from people who have seen your work. It is not an objective ranking of your worth or a substitute for your employer's performance process. Different working relationships create different opportunities to observe you.

Look for strengths, development areas and differences between your view and the pooled view. Check whether a pattern matches your recent work evidence. A discrepancy could reflect how your behaviour lands, but also context, expectations or limited exposure. Do not assume that a small numerical difference is meaningful without understanding the assessment's guidance.

CCL's guidance on interpreting 360 results recommends looking for themes and patterns rather than fixating on one data point. Its best-practice guidance also stresses purpose, preparation, action planning and follow-up. Receiving a report is not the same as making progress. Choose a small number of useful hypotheses, then connect one to behaviour you can practise in your actual work.

Example: you see more clarity than others do

Illustrative pattern: you see explaining clearly as a strength, while the pooled feedback is less positive. You often know the project history, but colleagues may only see the latest update. That difference is a possible explanation to explore, not an established diagnosis.

Review a recent update and ask whether it named the decision, the reason and the next action. You might ask someone who used it: ‘What did you need to act, and what was missing?’ This asks about observable work rather than whether they supplied a particular rating.

Practice: for the next few project updates, lead with the recommendation or request, then give only the background needed to evaluate it. Check understanding before moving on. Observe whether colleagues can identify the next step without another explanation. Do not claim that the practice worked simply because you wrote shorter updates.

Example: others see a strength you overlook

Illustrative pattern: pooled feedback is more positive about following through than your self-assessment. You may see careful handovers and early risk updates as routine rather than valuable. Alternatively, you and your colleagues may be using different standards. Both possibilities are worth considering.

Look for work examples that could explain the pattern. Did you make commitments clear, flag uncertainty early or help another team plan? Ask a development question such as ‘Which parts of our coordination are useful to keep?’ rather than fishing for praise or asking a person to disclose their answer.

Practice: preserve that reliability when workload rises by making commitments explicit and communicating trade-offs. A hidden strength is not a reason to take on every request. Protect the behaviour by setting realistic expectations, not by promising more than you can deliver.

Example: both views point to a growth area

Illustrative pattern: your self-assessment and the pooled feedback both suggest that speaking up could be more consistent. Agreement can help you choose a focus, but it still does not tell you why the behaviour is difficult. The issue may involve preparation, timing, role expectations or whether the setting welcomes concerns.

Choose a work opportunity with a clear purpose. Before the next planning meeting, write one question about a risk or dependency. Raise it while the options are still open, and explain what decision it affects. You do not need to speak more in every meeting to contribute more usefully.

Check whether the concern was understood and considered. If the environment discourages questions or a concern involves safety, address the process or use the appropriate reporting channel. A personal practice cannot repair every organisational problem.

Example: the overall picture feels inconsistent

Illustrative pattern: you receive a broadly positive view of collaboration but a less positive view of adapting to change. That is not necessarily a contradiction. You may coordinate well when responsibilities are stable and struggle to reset expectations when priorities shift.

Use your own work records to investigate that possibility. Compare a routine handover with a project that changed scope. Did you clarify what should stop, who owned the revised tasks and which deadlines were no longer realistic? Avoid inventing subgroup explanations such as ‘the client must have rated me lower’. Pooled results do not reveal individual raters.

Practice: after the next significant change, confirm priorities and trade-offs with the relevant people before accepting new commitments. Ask whether they had enough information to adjust their work. That check helps you understand the effect of the change, not merely whether you completed the practice.

Turn one insight into a growth plan

Write a short plan with four parts: the behaviour, the situation in which you will practise it, the feedback you need and the point when you will reflect. For example: ‘After the next planning discussion, I will summarise the decision and owner. I will ask whether the summary made the next action clear, then review what I learned after several opportunities.’

Keep the plan within your influence. You can change how you explain a recommendation; you cannot guarantee that everyone will support it. Seek support from a manager or trusted colleague where needed, and share only what you choose to share. You do not have to distribute a private report to ask for help with a behaviour.

Do not treat every new observation as evidence of improvement or failure. Look across comparable situations and allow time to practise. A later feedback round can offer another perspective, but changing raters, responsibilities or work conditions limits a direct comparison.

How this relates to EraSkills

EraSkills compares self-assessment with pooled feedback on Communication, Collaboration, Influence, Leadership and Adaptability. Results require at least three completed raters and update at completion milestones of 3, 5, 8, 12, 16 and 20—not after each extra response. These safeguards matter when reflecting on a pattern without isolating a person's contribution.

Raw rater comments are never shown to the user. Only AI-written themes drawn from at least two raters are shared, and nobody but the user sees their composite ERA Score. The illustrative patterns in this guide do not imply that you can inspect individual answers or identify which relationship produced a score. Start with the free self-assessment to put your own view on record before exploring other perspectives.