How to run a 360 evaluation in a mid-sized company
A 360-degree evaluation collects feedback about an employee from multiple directions: their direct manager, peers, direct reports, and self-assessment. Its purpose is professional development, not performance grading, and it works best for behavioral competencies — leadership, communication, cross-functional collaboration — while failing for technical knowledge or measurable individual performance.
When to use it and when not to
Before designing anything, it's essential to decide if a 360 is the right instrument, as it is frequently misused.
Evaluating how someone works with others: leadership, communication, conflict management, cross-departmental collaboration. Everything that is only perceived from the outside and that a manager cannot observe fully because no one behaves the same with their boss as with their peers.
Measuring technical knowledge, evaluating execution capability, or deciding promotions and bonuses. For technical skills, use practical exams. For compensation, a 360 degrades immediately: once people know their answers affect a teammate's bonus, honest feedback vanishes.
To understand how to evaluate real job capabilities beyond subjective perceptions, see our guide on how to assess employee skills.
Design: who evaluates whom
In a mid-sized company, the temptation is to evaluate everyone at once. Don't. Start with leadership positions — managers with teams — because that is where multi-directional feedback delivers insights unachievable through any other tool.
Recommended composition per evaluatee:
Designing the questions
The single biggest mistake is creating a 40-question survey on a 1-to-5 scale. No one fills it out thoughtfully past question 15, resulting in useless 3.8 averages across the board.
Examples of well-formulated behavioral questions:
- "Explains role expectations clearly so I can act without asking again."
- "When a mistake occurs, focuses on solving it before assigning blame."
- "Gives me feedback frequently enough to correct course on time."
- "Makes decisions within a timeframe that doesn't block my work."
- "During cross-department disagreements, seeks to understand the other side's perspective."
Notice these are written from the respondent's personal experience, not as abstract judgment. "Is a good leader" produces no actionable data; "explains expectations clearly so I can act" does. To structure job competencies logically, see what is a skills matrix and how to build one.
Actioning the results
This is where 360 evaluations succeed or fail. Most programs don't fail during collection, but in what happens afterward.
To verify if an employee is ready to work independently post-evaluation, read how to know if an employee is ready for their role.
Common pitfalls in mid-sized companies
Frequently Asked Questions
Can a 360 evaluation be done without specialized software?
Yes. An anonymous online form and a spreadsheet to aggregate scores are sufficient for under 50 evaluatees. Software saves time, not quality.
Must all responses be anonymous?
Peer and direct report feedback must be anonymous. Direct manager feedback is usually transparent, and doesn't need to be hidden.
What should you do if an employee receives very poor feedback?
Conduct the debriefing session with care, search for consistent patterns rather than isolated complaints, and separate coachable behaviors from fundamental role mismatches. Poor feedback isn't a termination decision — it's a starting point for development.
How long does implementation take?
4 to 6 weeks for an initial 10-leader cycle: 2 weeks for design and communication, 2 weeks for data collection, and 2 weeks for report processing and 1-on-1 debriefs.
Complement 360 perceptions with objective voice performance evidence
Hypsen complements 360 behavioral evaluations with empirical voice skills validation: while 360s measure how a person is perceived, Hypsen measures what they can actually execute in critical job tasks.