Part 1 · Article 2 of 14
Who should own 360 feedback?
In short
- In an Org360 360, the person receiving the feedback owns it and decides who else sees the report.
- Engagement surveys describe the organization, so the leader or HR runs them.
- When HR, the department and a manager can all read a 360, it becomes semi-public, and people soften what they say.
- HR's role shifts to encouraging 360s and sending reminders, without reading the reports.
Org360 defines feedback ownership as the principle that whoever launches a 360 controls its report, and nobody else sees it unless that person chooses to share it.
Which surveys belong to the organization, and which belong to the person?
- Organizational surveys cover employee engagement, satisfaction, exit and client feedback. They describe the organization, so someone at the center runs them: the CEO, the leadership team or the HR lead.
- Personal surveys cover 360 feedback and personal performance. They describe one person, which makes them individual and sensitive.
Org360 supports an HR team running a 360 on someone's behalf, and a coach running one for a client. Org360's preference is that each person launches their own 360 and keeps the results private until they decide otherwise.
Why do people hold back in a 360?
The most common reason is kindness. If your feedback on a friend or peer will land on their supervisor's desk or in an HR file, you'll soften it. Why risk hurting a colleague's career?
So people split their feedback into 2 channels. They give the honest version over coffee, in private. Then the form arrives and they fill it in with the politically correct one. That split is the distortion.
The second reason is fear. A 360 that goes to management can become a way for someone with a grudge to settle a score. People know unfair feedback can slip in and follow them, so they come to dread the process.
Org360 saw both effects while preparing the platform. Even well-meaning people wouldn't give frank feedback once they knew the report would travel up the line.
What is semi-public feedback?
Org360 uses the term semi-public feedback for a 360 report that several people can read: HR, the department, the person's leader. Every extra reader changes what respondents write. In a semi-public space, people watch what they say.
That's the contradiction in most feedback processes. They ask for frank feedback, then deliver it to an audience that makes frankness risky. Org360 resolves it by keeping the space between the person giving feedback and the person receiving it protected.
What changes when the person owns their feedback?
- They asked for the feedback, so they actually want to hear it.
- Respondents know only that person reads the report, so nobody's career is at risk and there's no route for retaliation.
- The report opens a frank conversation on the person's own terms.
- If they share it with their manager or HR, they do it by choice, and they arrive owning the story.
Across a whole organization, this creates a different psychological space. Employees drive the feedback process themselves, because they want to become better teammates and better leaders, and their colleagues answer honestly because it's safe to.
What's left for HR to do?
HR keeps the habit alive: encouraging people to run 360s, keeping an eye on how often they happen, and sending reminders. None of that requires reading anyone's report.
Some people won't ask for feedback at all, and that has to be accepted. A 360 someone was pushed into brings back every distortion above.
How does Org360 protect the report?
- The launcher controls the report. Whoever starts a survey decides who else, if anyone, sees it.
- Standard confidentiality. The report opens after 3 replies, and open-text answers appear without names.
- Highest confidentiality. The report opens after 5 replies, reminders go to the whole group, and an AI summary replaces raw open-text answers.
Article 3 covers these modes in detail.
What the research says
- Feedback can backfire. Kluger and DeNisi's (1996) meta-analysis of 607 effect sizes found that feedback improved performance on average, but that "over 1/3 of the FIs decreased performance" (FIs are feedback interventions). Feedback worked worse the more it turned attention toward the self and away from the task.
- Purpose changes the quality of ratings. Greguras, Robie, Schleicher and Goff (2003) found that direct reports' ratings were of significantly better quality when made for development than when made for administrative decisions. Peer ratings showed no difference, so the evidence supports development-only use most clearly for upward feedback.
- Safety comes first. Kahn (1990) identified psychological safety, feeling able to be yourself at work without fear for your image, status or career, as one of 3 conditions for people to engage fully.
Key readings: Kluger and DeNisi (1996); Greguras and colleagues (2003); Kahn (1990). Full references are in the research reading list.
Org360's view
Org360 thinks most 360 tools are compromised by who sees the data. Many sit inside HR suites, next to goals, OKRs and performance ratings, where a 360 report becomes part of someone's record by default. Respondents sense that and adjust their answers. Org360 is built as a place where it's safe to give honest feedback, because the feedback goes to the one person who asked for it.
Frequently asked questions
Who sees a 360 report in Org360?
Only the person who launched the survey, unless they choose to share it.
Can HR run a 360 on someone's behalf?
Yes. Org360 supports it, and a coach can also run a 360 for a client. Org360's preference is that people launch their own.
Who should run an employee engagement survey?
The CEO, the leadership team or the HR lead, because an engagement survey describes the organization.
What if someone doesn't want a 360?
Accept it. A 360 imposed on someone produces distorted feedback.