360 degree feedback for managers: what it really reveals, and where businesses get the response wrong
The Friday afternoon he sat down with the report, the managing director had a fair idea of what he was about to read. He ran a manufacturing business of around 60 people, with three operations managers between him and the floor. Two of them he trusted completely. The third, he had been quietly losing faith in for about six months, and the 360 he had commissioned was supposed to settle it.
He expected the data to confirm what he already thought. It didn't.
The manager he had been losing faith in came out roughly mid-pack. Capable and well-regarded by his team. The two he trusted came out very differently from each other. One was strong in every direction except with his peers, where he came across as territorial and difficult to work with on shared projects. The other was loved by his team and respected by his boss, but the data suggested he wasn't actually driving anything. He was popular and well-regarded, and his department's output had been quietly plateauing for two years.
The MD now had a problem that the 360 had created rather than solved. The original question had been about one manager. The report had given him three different questions, none of which had a clean answer.
The data you commissioned versus the data you got
An MD commissioning a 360 usually goes in with an assumption that doesn't survive the results. The expectation is that the data will validate something already felt. A weak manager will be exposed, or a strong one confirmed. The unspoken purpose of the exercise is often confirmation rather than discovery.
That assumption rarely survives contact with the results. A properly designed 360 doesn't tell you what you already know. It surfaces the patterns you weren't looking at. Occasionally, it surfaces something more uncomfortable: your own leadership behaviours that have been quietly shaping the rest. For an MD expecting a clear answer to a single question, the experience can be unsettling. The report tends to hand back a new set of decisions rather than resolve the one it was commissioned to answer.
The research bears this out. The most-cited meta-analysis on 360-degree feedback, by Smither, London, and Reilly in Personnel Psychology in 2005, examined whether multisource feedback actually improves performance over time. The answer was yes, but with significant caveats. The improvements were modest rather than dramatic. And they only appeared in organisations that did several things in combination: defined the framework properly, debriefed the results skilfully, gave the manager structured support afterwards, and revisited the development plan in a sustained way. Where any of those conditions were missing, the 360 generally produced no measurable change at all.
That finding is worth holding on to, because it sets a realistic expectation about what a 360 can and can't do. The value of the assessment is in surfacing what's actually present in the leadership team. Whether anything changes depends entirely on what happens afterwards.
What 360-degree feedback typically surfaces in an SME context
In an SME context, the patterns that emerge from a 360 tend to fall into a small number of categories. None of them are surprising in the abstract. All of them tend to surprise the MD reading the report.
The first pattern is the manager whose results are good but whose 'how' is quietly corroding the team. The numbers look fine, and delivery is steady. But somewhere in the team feedback, a picture emerges of someone who is short with people under pressure, slow to recognise effort, or visibly stressed in a way the team has started to absorb. The data points to something that hasn't shown up in performance yet but will, given enough time. The team is absorbing pressure that the manager isn't seeing.
Then there's the well-liked manager who isn't actually driving anything. Feedback from the team and boss is consistently positive. The department they run hasn't materially moved in two years. The 360 makes them look pleasant in a way that has come to substitute for leadership, which is a different kind of problem, one of a failure of drive rather than capability and harder for the MD to act on.
A third common finding is the manager whose perception across team, peers and boss is fragmented to the point where the three sources read almost like different people. What the team experiences and what the boss sees often look like reports on two different people. The peer view adds a third angle that frequently doesn't match either. This usually points to inconsistency under pressure. The person is one thing when the day is going well and another when it isn't. It's a behavioural pattern that's hard for the individual to recognise in themselves, because each audience only experiences their own slice.
And then there's the pattern MDs least expect to find. When the data is read carefully, the MD's own leadership behaviours often show up indirectly through the inconsistency they produce below them. If the managers being assessed are reacting to unclear direction or shifting priorities from above, that comes through in their results. A 360 isn't designed to assess the MD. But the MD often shows up in it anyway, and the honest reading of the data accepts that.
Where most businesses get the response wrong
The harder problem with 360-degree feedback in SMEs is what happens between the report landing and a year later. The assessment itself is usually the easier part. Three failure patterns account for most of the gap between what the data could have produced and what actually changed.
The first is straightforward. The report is read, possibly discussed once, and then quietly absorbed back into business as usual within a fortnight. The development conversations that should have followed don't happen because the day-to-day pulls everyone back to the operational pressure that prompted the 360 in the first place. Research on multisource feedback consistently suggests that meaningful action planning afterwards is the exception rather than the norm. What's usually missing is structure and follow-through, not intent.
The second is harder. The report is acted on, but the debrief is delivered poorly. The manager receives the document and a short meeting, often led by whoever commissioned the assessment. The conversation reads as performance feedback rather than development feedback. Defensiveness sets in. The honest insights in the data, particularly the perception gaps, get rationalised away rather than absorbed. Smither, London, and Reilly's research is explicit about this: the quality of the debrief is one of the strongest determinants of whether the 360 produces any behavioural change. A skilled debrief makes the data actionable, while a weak one inoculates the manager against ever taking 360-degree feedback seriously again.
The third is the most operationally damaging. The MD acts on the report quickly and in a structured manner. A manager gets moved sideways, or a team is restructured, before the picture is fully understood. Sometimes a difficult conversation happens without proper preparation. All of this is based on a partial reading of the data, often coloured by what the MD wanted to find in it. The 360 was supposed to inform a development decision and ends up triggering a personnel decision the business may struggle to recover from. Acting on the data disproportionately, before the picture is fully understood, tends to do more damage than the underlying issues the assessment was meant to surface.
What a practical response looks like
A practical response treats the 360 as the start of a development cycle rather than the end of an assessment. That distinction matters because almost everything that determines whether the assessment produces change happens after the report has been written.
The starting point is the competency framework itself. A generic management questionnaire pulled from an off-the-shelf platform will produce generic results. A framework designed around the specific responsibilities of the role being assessed produces data that the manager and their MD can actually use. For a head of operations in a manufacturing business, that means competencies that reflect what operations leadership actually demands in that environment. The closer the framework is to the real job, the more useful the data becomes. For the mechanics of how a structured 360 leadership assessment is built and delivered, the methodology is covered in detail in a companion article.
The debrief comes next, and how it's delivered determines almost everything that follows. Done well, it's an hour of one-to-one conversation with someone experienced enough to read the data with the manager rather than at them. The facilitator helps the manager work out what the patterns mean in the context of their actual role, distinguishes between findings that need urgent attention and those that don't, and ends the conversation with a small number of clear priorities rather than a list of twenty things to fix.
This is where the third element comes in, and where most SME approaches stop short. The development plan that emerges from the debrief should focus on the top three priorities for that individual manager. Three is enough to be specific and few enough to be remembered. The plan only works if it's tied to actual leadership situations the manager faces in the role, not to abstract competency improvement.
The final element is the part that turns the assessment into measurable change. A 360 in isolation, even with a good debrief, rarely produces sustained behavioural change. Ongoing coaching over six to twelve months is what actually shifts how a manager leads, because behaviour change requires repeated practice and someone capable of helping the manager work through real situations as they arise. This is the rationale behind ProgressA's structured leadership development for SMEs, which combines the 360 assessment with sustained coaching designed around the manager's specific role and the priorities the assessment surfaces.
Run together, these elements turn a 360 into something with measurable commercial value. Run separately or in part, the value drops sharply.
The debrief conversation most managers never get
Of all the elements above, the debrief is the one that does the most disproportionate work. It's also the one most likely to be cut short or skipped entirely in a smaller business.
Done properly, it's modest in scope. An hour of focused conversation, one-to-one, with no slide deck and no agenda beyond the data and what it might mean. Someone experienced in leadership development, who has read the report carefully before the meeting and can hold space for the manager to react honestly without becoming defensive. The conversation moves at the pace of the manager's recognition rather than the facilitator's agenda. By the end of the hour, the manager leaves with three honest priorities they understand and have chosen, not twenty they've been handed.
Almost none of this is technically difficult. It just requires someone capable of doing it, and the time and structural commitment to make it happen. In most SMEs, neither is reliably available. The MD doesn't usually have the training to deliver a debrief of that quality, and there's rarely an internal head of people development to take it on. External support, if engaged at all, often delivers the assessment but stops short of the sustained involvement needed to make the debrief land properly.
What's lost when the debrief doesn't happen properly is hard to see in the short term. The report goes in a drawer. The manager carries on doing what they were doing. Sometimes the data influences a small adjustment here or there, but the larger development that the assessment was capable of producing quietly evaporates. The business doesn't notice, because the absence of change feels indistinguishable from the previous state. The opportunity cost stays invisible until someone runs the assessment again two years later, and roughly the same patterns appear in roughly the same places.
For an MD weighing whether to commission a 360 in the first place, the harder question to ask is whether the business is ready to do the work that turns the data into change. The assessment is almost always worth doing. Whether the value actually lands depends entirely on what happens in the year that follows. If the debrief and the coaching aren't part of the plan from the start, the assessment will surface real findings, and the business will struggle to act on them in any sustained way. That's the conversation most managers never get to have. And it's why most 360 processes deliver less than the people who commissioned them hoped for.
