What 360 feedback software should do: read the comments into themed development areas by rater group, not average ratings into a spider chart.
360 feedback software gathers ratings and comments about a person from their manager, peers, and direct reports to give a rounded view of how they work. Good 360 software does the hard part: it reads the open-ended comments, where the developmental substance lives, into themes the person can act on — rather than averaging competency ratings into a spider chart that says a leader is a 3.4 on communication and nothing about what to do differently. The ratings are the frame; the comments are the coaching.
The complaint about 360s is almost always about the report: “I got a radar chart and a wall of anonymous comments, and I have no idea what actually to change.” Software that averages the numbers and dumps the comments produces a document that is simultaneously precise and useless, because the average hides the pattern and the raw comments overwhelm it.
Key takeaways
The signature output of most 360 software — a radar chart of averaged competency scores — is the least useful part of the exercise. Averaging a person’s ratings across raters flattens the exact thing a 360 exists to reveal: that peers see them one way and reports another, or that their strength in one situation is a weakness in another. A 3.4 on communication is a number with no direction, and the wall of raw anonymous comments beneath it is direction with no structure. Between the over-averaged number and the unread comments, the actionable finding disappears.
The value is in reading the comments into themes, by rater group, while protecting anonymity. Sopact calls the record it reads the Verbatim Thread: every 360 comment themed against a development framework on arrival, cited, and grouped by rater perspective without exposing individual raters. The output becomes a small number of themed development areas rather than a chart and a comment dump, the read the broader feedback tools apply to a developmental context.
360 feedback software moved through three eras. First, paper forms collated by an HR administrator. Then the online 360 platform, which automated distribution and produced the radar chart and a raw comment list, structured but shallow. The current era reads the comments into themes by rater group on arrival, so the person gets a focused development picture instead of a chart to interpret alone.
The one test that separates the eras: does the 360 output name two or three specific things to work on, themed from the comments and shown by rater perspective — or a spider chart and a page of anonymous quotes? A platform can average the ratings; it cannot theme the comments. If the report is a chart plus raw comments, the software collated the 360 rather than making sense of it.
The most valuable signal in a 360 is not the average but the divergence: where a manager and a peer see the same person completely differently, or where direct reports raise something no one above them mentioned. That divergence is exactly what averaging destroys, folding a sharp disagreement into a bland mid-range score. Reading the comments by rater group preserves the divergence and makes it the finding, because a gap between how a leader is seen by those above and below them is usually the most developmental thing the 360 can surface.
Preserving that requires reading the perspectives separately while still protecting the anonymity that makes raters honest — theming at the group level, not attributing to individuals. Doing both is what turns a 360 from a scored formality into genuine development input, and it is the same protected-group read the 360 feedback report is built on.
Require that it reads the open-ended comments into a small number of themed development areas by rater group, cited, while protecting rater anonymity — not just an averaged competency chart and a raw comment list. A tool that produces a spider chart and a comment dump leaves the recipient to do the analysis alone. Evaluate on whether the output names what to work on, not what the scores are.
The output that matters is developmental: two or three themed focus areas, the divergence between rater perspectives surfaced, quoted at the group level, and anonymity intact. Because Sopact reads on arrival on the Verbatim Thread, that is what the software produces, so a 360 becomes coaching a person can act on rather than a chart they have to decode, as the 360 feedback practice intends.
A radar chart averages away the pattern; a themed read surfaces the development areas and the rater divergence. The difference is whether the comments are read by rater group.
| Requirement | Radar chart + dump | Themed read (Verbatim Thread) |
|---|---|---|
| Main output | Averaged competency scores | Two or three themed development areas |
| Reads the comments? | No: a raw list | Themed by rater group, cited |
| Shows rater divergence? | No: averaged away | Yes: the most useful finding |
| Protects anonymity? | Yes, but unread | Yes, and read at the group level |
The practice and the report are 360 feedback; the read across all comments is feedback tools.
A feedback score is a lagging summary; the reason behind it is in the comment, and only if someone reads the comment while it still matters. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, analyze the moment a response arrives, improve while there is still time to act. A detractor’s reason is themed the day it lands and routed to someone who can respond, not filed for a quarterly readout.
The Loop is also what makes a feedback finding defensible: every driver and theme traces to the exact response it came from, the standard detailed in Loop traceability, so a reported reason is backed by the words, not a hunch.
One method, three moves that never stop
Then the cycle runs again, a little sharper each time. Read the method: the Loop methodology →
The fastest way to test 360 software is to make it theme the comments. Export a set of 360 comments by rater group, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Analyze open-ended responses
Here is a batch of feedback with each respondent's score and segment: [ATTACH]. Theme every comment against our codebook, cite the sentence behind each theme, and show the top drivers by segment so I can see who is raising what.
Academy walkthrough → Analyze sentiment and its drivers
For these open-ended responses: [ATTACH], score sentiment per comment, then show the specific drivers behind the negative sentiment — the recurring reasons, each with a quoted example — so I know what to fix, not just the mood.
Academy walkthrough → Connect quant and qual data
Here are our scores and open-ended comments on the same respondent IDs: [ATTACH]. Show which themes explain the lowest scores, quote a comment for each, and list the specific respondents worth a personal follow-up.
Academy walkthrough → The Loop: continuous, not point-in-time
We collect feedback [CURRENT CADENCE]. Using this data: [ATTACH], show what a continuous read would catch earlier — the segments whose sentiment is slipping between waves and the comments explaining why — so we can act before the next report.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: reading feedback on arrival and keeping every response on one record.
Gather ratings and comments about a person from manager, peers, and reports, and read the open-ended comments into themes the person can act on, by rater group, while protecting anonymity. Most tools average the ratings into a chart. Sopact reads the comments on the Verbatim Thread into themed development areas.
Because averaging competency ratings across raters flattens the pattern a 360 exists to reveal — that peers and reports see the person differently — and a 3.4 says nothing to act on. Sopact reads the comments into themes by rater group, so the developmental substance surfaces instead of being averaged away.
The divergence between rater perspectives — where a manager and a peer see the person differently, or reports raise something no one above did. Averaging destroys it. Sopact reads the comments by rater group, so the divergence becomes the finding, which is usually the most developmental one.
Require that it reads the comments into a small number of themed development areas by rater group, cited, while protecting anonymity, rather than a chart and a comment dump. A tool that leaves you to analyze raw comments is a collator. Sopact themes the comments on the Verbatim Thread.
Yes — by theming at the group level rather than attributing to individual raters. That preserves the honesty anonymity protects while still reading the substance. Sopact reads by rater group without exposing individuals, so the report is both candid and usable.
Two or three specific things to work on, themed from the comments and shown by rater perspective, not a spider chart and a page of quotes. Sopact produces that focused development picture, so a 360 becomes coaching rather than a document to decode.
It reads every 360 comment against a development framework on arrival, themes it by rater group with the source cited, surfaces the divergence between perspectives, and protects rater anonymity — all on the Verbatim Thread. So the output is a small set of actionable development areas, not an averaged chart.
Next: the practice and the report on 360 feedback, or the read across all comments on feedback tools.
