Skip to content
Convergo360

360 feedback in South Africa, a complete guide

A 360 gathers ratings on a leader from their manager, peers, direct reports and other staff for development. How it works in South Africa, step by step.

· 12 min read · Convergo360 team

A 360 feedback review asks the people who work around a leader to rate how often that leader shows specific behaviours, and compares their view with the leader's own self-rating. In South Africa it is used mainly for leadership development, a full cycle runs over six to eight weeks, and the ratings and comments count as personal information under POPIA. This guide covers who rates, how a cycle runs, how anonymity works, what the report shows and how to choose a provider.

What is 360 feedback?

A 360 (also called multi-rater feedback or a 360 degree assessment) gathers structured ratings and written comments about one person from several directions at once. The person being rated, usually called the ratee, answers the same statements about themselves. The report then shows where the leader's view of themselves lines up with what colleagues see and where the two differ.

Most leadership 360s use behavioural statements instead of personality labels. A direct report can observe whether their manager "explains the reasons behind decisions", while a statement such as "is a strategic thinker" forces raters to guess. Each statement should describe one behaviour, and raters score how often they see it. A common scale runs from 1 (Rarely) to 5 (Almost always), with a "Not observed" option for raters who haven't had the chance to see that behaviour.

A typical leadership questionnaire has 20 to 30 statements grouped into competencies such as communication, developing people and decision making, plus two open questions for written comments. Our guide to leadership 360 questions has examples and tips on wording.

Who gives feedback in a 360?

Five rater groups are standard. Each one sees a different side of the leader, which is why the report keeps them apart.

Rater group Who they are Typical number Anonymous in the report?
Self The leader being rated 1 Shown on its own, never mixed into other averages
Manager The person the leader reports to 1 No, a single rater is always identifiable
Peers Colleagues at a similar level who work with the leader 3 to 5 Yes, when 3 or more respond
Direct Reports People who report to the leader All of them, ideally Yes, when 3 or more respond
Other Staff People in other teams who deal with the leader regularly 3 or more Yes, when 3 or more respond

The Other Staff group is useful in South African workplaces where a manager's decisions affect shift workers, administrators or support teams who sit outside their reporting line. These raters often answer a shorter survey focused on respect, fairness, responsiveness and follow-through, because they see less of the leader's day-to-day work.

Who chooses the raters shapes how much people trust the result. If the leader picks every name, colleagues assume the list favours friends. A better approach starts from reporting lines, adds peers who work with the leader often, and has someone independent approve the final list. See how to choose 360 raters for a full method.

What is 360 feedback used for?

Use a 360 for development. It shows a leader how their behaviour lands with the people around them, so they can decide what to change and get support to do it.

Keep it apart from pay, bonuses, promotion and discipline. Raters soften their scores when they know the result affects a colleague's income, and leaders who see money at stake spend the debrief defending themselves instead of listening. A meta-analysis of 22 studies by Jawahar and Williams (1997) found that ratings collected for administrative decisions came out about a third of a standard deviation higher than ratings collected for development or research. See 360 feedback vs performance reviews for a full comparison.

Common reasons to run a 360 include:

  • A manager in their first year of leading a team
  • A baseline at the start of a leadership programme, repeated 12 to 18 months later
  • The starting point for a coaching engagement
  • Development of people on a succession list

How does a 360 cycle run, step by step?

A well-run cycle follows the same order every time.

  1. Agree the purpose and tell people. Before any invitation goes out, brief leaders and raters on what the 360 is for, who will see each report, and how anonymity works. State in writing that results won't be used for pay or performance ratings.
  2. Confirm the questions. Choose a question set that matches the behaviours your organisation expects from leaders. Use the same set for everyone in the cycle so results can be compared later.
  3. Appoint an administrator. One person runs the cycle, approves rater lists, reviews comments and releases reports. An external or independent administrator gives raters more confidence than a line manager or someone in the leader's own team.
  4. Build and approve rater lists. Pull Self, Manager and Direct Reports from reporting lines, then add peers and other staff. Check that each anonymous group will reach at least 3 responses and that nobody has more than 5 surveys to complete.
  5. Send invitations. Each rater gets a private link. Tell them how long the survey takes and when it closes.
  6. Keep the survey open for two to three weeks. Send reminders only to people who haven't finished, typically around day 7 and day 14.
  7. Close and review comments. When the survey closes, the administrator reads every written comment and removes details that would identify the writer.
  8. Generate and release reports. Check a sample of reports for errors, then release each one to the leader and to their coach or debrief partner.
  9. Hold the debrief. A trained coach or the leader's manager walks through the report with the leader within one to two weeks of release.
  10. Agree a development plan. The leader writes a short plan within 30 days of the debrief and reviews progress with their manager or coach.

Our how it works page shows how each of these steps runs in Convergo360.

How long does a 360 take?

Phase Typical time
Planning and briefing 1 to 2 weeks
Building and approving rater lists About 1 week
Survey open 2 to 3 weeks
Comment review and report checks About 1 week
Debriefs 1 to 2 weeks after release
Development plan Within 30 days of the debrief

From first briefing to signed development plans, most cycles take six to eight weeks. For a rater, a survey of 21 statements and two open questions takes about 10 to 15 minutes. Someone rating five colleagues therefore gives over an hour of their time, which is why capping each rater at 5 surveys helps completion rates.

How does anonymity work in a 360?

Raters write candidly only when they trust that their answers can't be traced back to them. Anonymity in a 360 rests on a few rules that should be fixed in advance and enforced the same way in every report.

  • A minimum group size. An anonymous group needs at least 3 responses before its results appear on their own. If only two direct reports respond, their scores and comments are merged into a combined "Others" group so neither can be singled out.
  • Manager feedback is labelled. The manager group has one rater, so the report shows it separately and marks it as not anonymous.
  • Comments in a neutral order. Showing comments alphabetically within each group, never in the order they were submitted, stops anyone matching a comment to the time a person finished.
  • Comment review. The administrator removes names, dates or details that point to one person before the report is released.
  • Separation of identity and answers. The system should record that a person completed a survey without storing which answers were theirs.

In Convergo360, an independent administrator runs each cycle and holds the only key to the answers, using a passkey on their own device. Our servers never see an individual's answers in readable form, and the answers are shuffled when the cycle closes so nobody can match a person to their responses. The anonymity page explains how this works, and our article on 360 feedback anonymity covers the rules in more depth.

What is in a 360 report?

A good report moves from the overall picture to the detail. A typical leadership 360 report includes:

  • A response summary showing how many people in each group replied
  • A competency summary with averages for each rater group
  • A comparison of the leader's self-rating with the combined view of others
  • Blind spots and hidden strengths
  • The top 5 and bottom 5 behaviours as rated by others
  • Detailed results for every statement, by rater group
  • A separate section for Other Staff
  • Written comments, grouped by rater group
  • A development plan page

Blind spots and hidden strengths come from the gap between self and others. Where the gap is 0.5 or more on the five-point scale, the statement is flagged. If a leader rates themselves 4.5 on "listens actively before responding" and others average 3.8, the 0.7 gap shows the leader is rated lower by others than by themselves on that behaviour. If the leader gives themselves 3.2 on "recognises good work promptly" and others give 4.0, that is a hidden strength, a behaviour others value more than the leader does.

You can see a full example in our sample report.

How should a 360 debrief work?

The debrief is where a report turns into a change in behaviour. Plan 60 to 90 minutes with a trained coach or the leader's manager, in private, with the report in front of both people.

Look at the gaps between self and others, and the behaviours rated lowest. Focus on two or three themes that show up across rater groups and in the comments, instead of working through every number. Steer the leader away from guessing who wrote which comment, because it shifts attention from the message to the messenger and it erodes the trust that makes the next cycle work.

Our 360 feedback debrief guide has a session outline and questions to ask.

What goes into a 360 development plan?

Keep the plan short enough to act on. Most leaders work best with one to three behaviours to develop over the next six to twelve months. For each one, the plan should record:

Field Example
Behaviour to develop Keeps people informed of changes and progress
Why it matters Direct reports rated this lower than other communication items, and comments mention late news about shift changes
Specific actions Weekly 15 minute team update every Monday, written summary after each management meeting
Support needed Monthly check-in with coach for three months
How progress will show Fewer questions from the team about changes, raised in the next pulse check
Review date 90 days after the debrief

Repeat the 360 after 12 to 18 months with the same questions so the leader can see whether others notice the change.

What does POPIA mean for 360 feedback?

The Protection of Personal Information Act (POPIA) applies to 360 feedback, and organisations have had to comply with it since 1 July 2021. POPIA's definition of personal information includes the views or opinions of another person about an individual, so ratings and comments about a named leader are covered. Information about raters, such as their names, email addresses and whether they completed a survey, is covered too.

The main points for a 360 are:

  • Purpose. State that the 360 is for leadership development and say who will see the reports.
  • Minimality. Collect only what the 360 needs. Leave out demographic questions that aren't required.
  • Operators. Any provider that processes the data on your behalf is an operator, and section 21 requires a written contract covering security measures.
  • Cross-border transfers. If data is stored or processed outside South Africa, section 72 sets conditions that must be met.
  • Retention. Decide how long raw answers and reports are kept, and delete them on schedule.
  • Security. Protect the data against loss and unauthorised access, and have a process for reporting a breach to the Information Regulator.

Convergo360 is hosted in South Africa, and raters answer through single-use links without creating an account. Our article on 360 feedback and POPIA goes through each requirement in more detail. It is a practical guide and not legal advice, so check your approach with your Information Officer.

What are the most common 360 feedback mistakes?

  • Linking results to pay or ratings. Raters inflate scores and leaders become defensive, which defeats the purpose.
  • Letting the leader pick every rater. The list leans towards supporters and other colleagues stop trusting the result.
  • Running with groups that are too small. Two peer responses can be traced back to individuals. Plan for at least 3 responses per anonymous group, and invite a few more to allow for people who don't finish.
  • Overloading raters. A rater with eight surveys starts rushing by the fourth. Cap the load at 5.
  • Using a long questionnaire. Raters with several surveys to complete tire quickly. Keep the leadership survey to about 20 to 30 statements.
  • Releasing reports without a debrief. A leader reading low scores alone, late at night, is more likely to fixate on one comment than to plan a change.
  • Skipping the follow-up. Without a development plan and a repeat cycle, raters see no change and put less effort into the next survey.

How do you choose a 360 tool or provider in South Africa?

Ask each provider the same questions and compare the answers side by side.

Question to ask Why it matters
Who can read an individual rater's answers? The fewer people with access, the more candid raters will be. Ask whether the provider's own staff can see answers.
Where is the data hosted? Hosting outside South Africa brings POPIA's cross-border rules into play.
What is the minimum group size, and what happens below it? A minimum of 3, with smaller groups merged, is the usual standard.
How are comments ordered and reviewed? Alphabetical order and administrator review protect writers from being identified.
Do raters need an account? Single-use links mean raters don't have to register or remember a password, which helps completion.
Can you see the full question set and a sample report first? You should know exactly what raters will answer and what leaders will receive.
Who runs the cycle? An independent administrator separates the people running the process from the people being rated.
What does debrief support look like? A report without a debrief seldom leads to change.
How is pricing structured? Ask whether you pay per leader, per rater or per cycle, and whether setup and debriefs are included.

For typical price ranges and what drives them, read our guide to 360 feedback costs in South Africa.

Next step

Write down the purpose of your 360 and who will see each report, then list the leaders and likely raters to check that every anonymous group can reach 3 responses. When you have that list, compare it against the sample report to see what each leader would receive.

Sources

Common questions

What is 360 feedback?

A 360 collects ratings and comments about one leader from the people around them, usually their manager, peers, direct reports and other staff. The leader rates themselves on the same statements so the report can show where their view matches what others see.

How many raters does a 360 need?

Each anonymous group needs at least 3 responses so nobody can be singled out. Most leaders end up with 8 to 15 raters across all groups.

Should 360 feedback be linked to pay?

Keep 360 feedback for development only. When raters know scores affect a colleague's bonus or promotion, they tend to rate more generously and write less candid comments.

How long does a 360 feedback cycle take?

Plan for six to eight weeks from briefing to development plan. The survey itself is usually open for two to three weeks, and each survey takes a rater about 10 to 15 minutes.

Is 360 feedback subject to POPIA?

Yes. Ratings and comments about a named leader are personal information under POPIA, so the organisation needs a stated purpose, a written contract with any provider that processes the data, sensible retention periods and proper security.

See a sample report and how a cycle runs

A 30-minute walkthrough with someone who has run 360s before.

Book a demo