TeamHive Logo

TeamHive

How Teams Improve: A team 360 puts the pattern in the spotlight, not the person

Kimberly Luffman

By Kimberly Luffman

•

November 10, 2026

•

4 min read

Kimberly Luffman

Kimberly Luffman

Nov 10, 2026•4 min read

How Teams Improve: A team 360 puts the pattern in the spotlight, not the person

How Teams Improve: A team 360 puts the pattern in the spotlight, not the person

Is team development safer than an individual 360?

I've sat beside a lot of leaders reading their individual 360 for the first time. Some of those conversations were the start of real change. Plenty were the start of a week spent trying to work out who wrote the comment on page six.

Individual 360s aren't bad tools. I've used them for years, particularly The Leadership Circle and LSI from Human Synergistics, and I still recommend and use these tools in my leadership work. But HR leaders ask me a version of the same question often enough that it's worth answering properly: is team development a safer place to start?

My answer is: in some important ways, yes. Not in every way.

What each tool puts in the spotlight

An individual 360 is about a person. Every score and every comment describes one human being, who then has to read it, usually alone, and decide what it says about them. However well it's debriefed, the feedback lands on one person.

A team 360 is about a pattern. The TeamHive 360 asks team members and stakeholders about how the team works: whether it's clear on its goals, whether people feel safe to speak up, whether leadership is shared, whether it learns from setbacks. Nobody is rated. The results describe what the team does together.

That changes the conversation more than you'd expect. 'You don't listen' and 'we don't always make sure every voice is heard' might describe the same behaviour. Only one of them makes someone defensive. When the subject is 'us', a team can look at a hard result together, rather than one person having to defend themselves.

Why that matters for safety

Amy Edmondson defines psychological safety as a belief held by the team as a whole, not by individuals: a shared belief that it's safe to take interpersonal risks. That's worth sitting with. If safety is a property of the team, the most direct way to build it is to work on the team. Sending every member off with a private report about themselves doesn't do that.

Her early hospital research has a lesson in it too. The teams that rated themselves better reported more errors, not fewer. They weren't making more mistakes. They were more willing to talk about them. A team that can discuss its own data honestly is already practising the thing that makes it safer.

Where team feedback still needs care

The main potential risks of a Team 360 include:

  • Rater anonymity. The fewer people in a team, the easier it is to guess who said what in the written feedback. That's why the TeamHive 360 uses AI text summaries rather than verbatim text. And why it won't give scores for single person rater categories. Coaches can pull out the anonymous verbatim text, if absolutely required.

  • The leader. A team result that says 'we don't share decisions' can still feel personal to the person who makes most of them. Brief the leader before the team sees the results, not at the same moment.

  • The person everyone is thinking about. Sometimes a team result points at a problem everyone privately attributes to one person. The data won't name them, and the facilitator shouldn't either. The conversation needs to stay on what the team can change, including how it holds each other to account.

  • No follow-through. Asking people what isn't working and then doing nothing does more damage than not asking. That's true of any feedback tool.

None of these is a reason not to start. They're reasons to start well.

Where an individual 360 still earns its place

If a specific leader needs to understand their own impact, an individual 360 is the right tool, and a team one won't replace it. They answer different questions. Our own validation work with the University of Newcastle found the PLUS dimensions captured something distinct from individual leadership measures. Different layer, different information.

What I'd suggest is the order. Start with the team. It's a lower-stakes way into feedback for everyone. It gives the team a shared language for how it works, and it often shows that what looked like one person's problem is really a team pattern. Then, if an individual 360 is still needed, the leader comes to it with context rather than in isolation.

How TeamHive is built for this

We designed the TeamHive 360 with these risks in mind. It measures team behaviours, not people. Written feedback is summarised and anonymised, and grouped by team members and stakeholders rather than attributed. When the HiveAI Coach works with a team's results, it never sees the organisation's or team's name. And the questions it generates are about what the team can do next, not who is to blame. If a team wants support working through its results, a coach can take it from there. We've also written about when a team needs a coach, and when it can do the work itself.

If you'd like a low-stakes first look, the Free Team Effectiveness Indicator is your own perspective only, and takes about ten minutes. The research behind PLUS is published if you'd like to see the evidence first.