A 360-degree review collects the views of the manager, peers and direct reports, plus the employee's own view of themselves, so you get a wider picture than one manager's opinion. In a 30-employee company you can finish it in a single cycle if you decide in advance who rates whom, keep the form to five to eight questions, and keep reading the results separate from pay decisions.
When does 360 feedback suit a small company?
It suits you when you want to know how a person works with others, not only how much they delivered: a new team lead, an employee who hits targets while colleagues complain, or a team whose managers want to understand their impact. It should not be the company's first review experience. A regular review cycle should come before it. Preparing a performance review cycle covers how to lay that groundwork.
Who rates whom in a 30-employee company?
Assume a structure of 30 people: a general manager, four team leads and 25 team members. The rules are:
| Person rated | Rated by | Forms about them |
|---|---|---|
| Team member (25) | themselves, their lead, three peers | 5 |
| Team lead (4) | themselves, the general manager, two peer leads, three of their team | 7 |
| General manager (1) | themselves, the four team leads | 5 |
The math:
- Team members: 25 × 5 = 125 forms.
- Team leads: 4 × 7 = 28 forms.
- General manager: 1 × 5 = 5 forms.
- Total: 125 + 28 + 5 = 158 forms in the cycle.
Each team member fills about 4 to 5 forms: their own, three about peers, and possibly one about their lead. A lead fills about 10 to 11. That is a reasonable load for a small team to complete in a week, and each extra rater per person adds to the load by the same amount.
Steps in the cycle
1. Set the purpose
Write one sentence on why you are running the cycle, for example developing leads. State that it will not be tied to pay in this cycle, because an employee who knows a colleague influences their salary will not write candidly.
2. Choose the criteria
Five to eight criteria that management agrees on, such as collaboration, communication, meeting deadlines, taking responsibility and initiative. Each criterion gets one scale for all raters, such as 1 to 5, with a free-text comment field at the end of the form.
3. Assign the raters
Use the who-rates-whom table above. Pick peers from outside a person's closest friendships, in consultation with the lead, so that nobody writes only about friends. Keep the number fixed for each member so one employee does not get five raters and another two.
4. Brief the team before launch
Explain the purpose, the timeline, how results will be used and who sees them. Answer "will my colleague know what I wrote about them?" before anyone asks, and decide on one way of presenting feedback for everyone.
5. Launch with a fixed window
One week to fill the forms is enough at this size, with a reminder midweek. Track the completion rate daily and chase anyone who has not finished.
6. Read results as patterns
Do not stop at a single average. Compare the person's own view with how others see them, look at gaps between the lead's view and the peers' view, and at criteria where more than one rater left similar comments. A comment that appears in three forms matters more than one numeric score.
7. Turn results into a conversation and a plan
Hold a short session with each employee and agree two or three development goals with a date and a follow-up. For anyone whose result needs closer follow-up, link them to a performance improvement plan with specific tasks.
A sample three-week timeline
| Week | Work |
|---|---|
| Before launch | Set the purpose and criteria, build the who-rates-whom table, brief the team |
| One | Fill the forms, with a midweek reminder |
| Two | Review results and read the patterns with the general manager |
| Three | One-to-one sessions and development goals |
Mistakes that keep repeating
- A long form: it tires the rater, who then answers without thinking.
- Tying the result to pay from the first cycle: it changes what people write.
- Not sharing the result with the lead: the cycle ends with no effect.
- Showing named comments without prior agreement: the team loses trust in the cycle.
Sample questions for the form
Use behavioral questions a rater can back with an example:
- Explains what they expect from colleagues in a way everyone understands.
- Delivers what they committed to on time.
- Listens to a differing view without getting defensive.
- Admits a mistake and corrects it.
- Helps others when they ask.
- Takes the initiative to solve a problem before being asked.
Each is answered on a 1 to 5 scale, with two free-text fields at the end: "What do they do well?" and "What would help them if they changed it?"
How do you present results to the team?
Do not post individual results or send each employee's report to everyone. Present a company-level summary of the main strengths and the criteria that need development, then give each employee their own report in their one-to-one session. Tell the team in the group session what will change after the cycle: training, goals, or a change in how work is done. A cycle followed by no change makes the next cycle less honest.
360 feedback in TAC HR
The performance appraisal system in TAC HR offers review cycles with calibration, 360 feedback, goals and follow-ups, self-assessment, and improvement plans linked to tasks in the task management service. What concerns the employee appears in their file. To try it on your own team, request a demo.
FAQ
Does 360 feedback work for a ten-person company?
It can, but with few peers it is hard to hide who wrote what. Agree in advance how feedback will be presented.
How many criteria should the form have?
Five to eight is enough. More than that lengthens the form without adding value.
Should I tie 360 feedback to bonuses?
Better not in the first cycle. Use it for development first. The decision is yours.
How long does it take?
In a 30-employee company, a week to fill forms, a week to read results and a week for the sessions, as in the timeline above.
What is the difference between 360 and an annual review?
An annual review is the manager's view of performance. 360 is several views of behavior and how someone works. They complement each other.
