360 Degree Feedback: Process, Sample Questions and Pitfalls

360 degree feedback collects input about an employee from the people around them: their manager, peers, direct reports, and sometimes internal or external customers, alongside their own self-assessment. The result is a rounded picture of how someone works, especially behaviours that a manager alone rarely sees, such as how a team lead treats their team when the boss is not in the room. Used well, 360 degree feedback is one of the most powerful development tools available to HR. Used badly, it becomes a popularity contest or a channel for anonymous grudges. This guide covers how to design and run a 360 process, how to choose raters, sample questions, report design and the pitfalls to avoid.

What 360 Degree Feedback Is For

The first decision is purpose. 360 feedback can be used for:

Development only: results go to the employee and, often, their manager or coach, to build a development plan. Not used for ratings or pay.
Input to appraisal: results inform the manager's rating, usually for competency or behaviour areas.

Most experienced HR practitioners recommend starting with development only. When raters know their input affects someone's increment, they soften, inflate or, in conflicted teams, weaponise their feedback. When it is purely developmental, feedback tends to be more honest.

Who Should Receive 360 Feedback

360 feedback works best for roles where behaviour toward others is central:

People managers at every level.
Senior individual contributors who influence across teams.
High-potential employees preparing for leadership.
Client-facing leads, where customer input adds value.

For frontline and junior roles, the effort usually outweighs the benefit; regular manager feedback and peer recognition may be enough.

Choosing Raters

Rater group	Typical number	What they see
Self	1	Intent and self-perception
Manager	1 (plus skip-level optional)	Results, alignment, judgement
Peers	3 to 5	Collaboration, reliability, influence
Direct reports	3 to 6 (all, if team is small)	Leadership, communication, fairness, support
Internal customers or stakeholders	2 to 3	Service, responsiveness, partnership

Good practice for selecting raters:

The employee proposes raters; the manager reviews and can add names to avoid a hand-picked group of friends.
Raters should have worked with the person for at least three to six months.
Limit how many 360s one person rates in a cycle, ideally no more than five or six, to avoid fatigue.
For anonymity, require a minimum number of responses in a group, commonly three, before showing that group's results separately. Otherwise merge them into a combined "others" group.

Designing the Questionnaire

Keep it short. Thirty to forty rating items plus three open questions takes most raters 15 to 20 minutes. Longer surveys get rushed.

Use a behavioural frequency scale rather than a quality scale. Asking "how often does this person do X" produces more reliable answers than "how good is this person at X".

Score	Label
1	Rarely
2	Sometimes
3	Often
4	Almost always
N/A	Not observed

Always include "not observed" so raters do not guess.

Sample 360 Feedback Questions by Competency

Communication

Explains priorities and decisions clearly.
Listens to others without interrupting.
Shares information that others need, on time.

Collaboration

Works constructively with other teams to solve shared problems.
Follows through on commitments made to colleagues.
Gives credit to others for their contributions.

People leadership (for managers)

Sets clear expectations for the team.
Gives regular, specific feedback.
Treats team members fairly and consistently.
Supports team members' development and career growth.
Is approachable when problems arise.

Execution

Plans work realistically and meets deadlines.
Makes decisions in a timely way, even with incomplete information.
Focuses the team on the most important priorities.

Integrity and values

Acts consistently with company values, even under pressure.
Admits mistakes and takes responsibility.

Open-ended questions

What should this person continue doing?
What should this person start doing to be more effective?
What should this person stop doing?

Tie items to your competency framework so 360 results connect with appraisal and development plans. For goal-related performance, see our guide to KRA and KPI examples.

Running the 360 Process Step by Step

Communicate purpose and confidentiality to participants and raters.
Nominate raters and get manager approval.
Launch the survey with a two week window and one or two reminders.
Check response thresholds before closing; extend for groups below the minimum.
Generate reports per participant.
Debrief each participant with a trained HR partner, coach or manager.
Create a development plan with two or three focus areas.
Follow up at three and six months; consider a repeat 360 after 12 to 18 months.

What a Good 360 Report Shows

Average scores by competency, by rater group, compared with self-rating.
Highest and lowest rated items.
Gaps between self and others, which often hold the most useful insight. A large gap where self-rating is much higher than others' is a "blind spot". A gap where others rate higher is a "hidden strength".
Verbatim comments, grouped and anonymised. Remove any comment that identifies the rater.

Avoid ranking participants against each other in the report. The point is individual development.

The Debrief Conversation

Never email a 360 report without a conversation. Reading critical anonymous comments alone is hard, and people tend to fixate on one negative remark. A good debrief:

Starts with strengths.
Looks for patterns, not individual comments.
Explores blind spots with curiosity: "What might people be seeing that leads to this?"
Discourages guessing who said what.
Ends with two or three concrete development actions.

Making 360 Feedback Work in Indian Workplaces

Some features of Indian workplace culture affect how 360 feedback lands, and designing for them improves the quality of responses.

Hierarchy and deference. Direct reports are often reluctant to rate a manager critically, even anonymously. Stress anonymity repeatedly, use frequency scales rather than "good or bad" judgements, and show that leaders acted on earlier feedback.
Politeness in written comments. Open comments tend to be mild. Prompts such as "one thing this person could do differently that would help you most" draw out more useful answers than "any areas of improvement".
Language. For teams where English is not everyone's first language, offer the questionnaire in a second language or keep items very short and concrete.
Small offices. In a branch of 12 people, anonymity is fragile. Merge rater groups and rely more on facilitated conversations.
Fear of consequences. If 360 results were ever used to punish someone in the past, rebuild trust with a development-only cycle and clear communication before expecting candour.

Watch response patterns in the first cycle. If almost every score is 4 out of 4, people are not yet comfortable being honest, and the process needs more trust-building before it can be useful.

A Sample Development Plan After a 360

The report is only useful if it turns into action. Here is an illustrative development plan for a hypothetical first-time manager whose 360 showed strong execution scores but a blind spot on delegation and feedback.

Focus area	What the 360 showed	Actions	How progress will be seen
Delegation	Self-rating high, direct reports rated "sometimes"; comments mention last-minute takeovers of work	Agree ownership of two recurring tasks with team members; weekly check-in instead of taking over	Team members report clearer ownership in next pulse check
Regular feedback	Direct reports rated "rarely" for specific feedback	Fortnightly one-to-ones with a simple agenda; one piece of specific feedback per meeting	One-to-ones held as planned; manager's manager reviews notes monthly
Cross-team communication	Peers rated "often", a strength	Share approach with other new managers in a short session	Session delivered

Two or three focus areas are enough. A development plan with ten items is a list nobody completes. Link actions to available support, such as a manager development course, a mentor or a coach, and review progress with the manager at three and six months.

Rolling Out 360 Feedback for the First Time

Start with the leadership team. When senior leaders go first and share what they learned, others see it is safe.
Run a pilot with one group of managers before extending it.
Train debrief facilitators so every participant gets a skilled conversation.
Ask pilot participants and raters for feedback on the questionnaire and process, and adjust.
Extend to all people managers in the next cycle.

Common 360 Pitfalls

Using it for pay too early. Undermines honesty.
Breaking anonymity. Small rater groups or identifiable comments destroy trust permanently.
Too many questions. Rater fatigue leads to straight-line answers.
No follow-up. If nothing happens after the report, people stop taking part seriously.
Everyone at once. Running 360s for the whole company in one month overwhelms raters.
Retaliation. Any attempt to identify or punish raters must be treated as misconduct.

Frequently Asked Questions

Is 360 degree feedback anonymous?

Peer and direct report feedback should be anonymous, with a minimum number of responses before group results are shown. Manager feedback is usually identifiable.

Should 360 feedback be linked to appraisal ratings?

Many companies keep it development-only, at least initially. If you link it, use it as one input for competency ratings, not as a formula.

How many raters are needed?

Typically 8 to 12 in total across groups, with at least three in any group whose results are shown separately.

How often should 360 feedback be done?

Once every 12 to 18 months per person is common, with development follow-up in between.

Can 360 feedback work in small companies?

Yes, but anonymity is harder. Combine rater groups and focus on open questions and facilitated conversations.

Run 360 Feedback in Fininvo HRMS

Fininvo HRMS includes 360-degree feedback, competency frameworks, review templates and continuous feedback within its performance module. See performance management, learning and development for follow-up plans, and pricing.