A 360-degree development review template collects structured feedback on an employee's competencies — leadership, communication, collaboration, results orientation and openness to learning — from their manager, peers, and direct reports, plus a self-assessment. Unlike a performance appraisal, the results go only to the recipient, never to HR or the supervisor, and never feed pay or promotion decisions. That separation is exactly what makes the feedback honest.

This article gives you a ready-to-use template with 12 proven example questions, a filter for good versus weak questions, a five-step process, and a concise note on GDPR and works council rules for DACH teams. The throughline most templates miss: how to use 360 feedback not just as a conversation starter, but as diagnostic input for individual skill profiles.

What makes a 360 development review different from a performance review?

A 360-degree review is multi-perspective feedback. Instead of a single rating from the manager, it pulls together several viewpoints: the manager, peers, direct reports, and where useful external partners or customers. A self-assessment completes the picture. The gap between how a person sees themselves and how others see them becomes the real engine of learning.

The feedback radius comes in graduated versions. Which one you choose depends on who can realistically and meaningfully assess the person.

The distinction that decides everything

This is the most common design error. Many teams set up a 360 but blend two goals that do not fit together structurally: development and evaluation. A development 360 differs fundamentally from a performance appraisal in several places — in the questions, in who receives the results, and in the legal obligations attached.

The separation is not a technicality. It is the precondition for honest answers. The moment raters suspect their feedback will influence the recipient's pay or promotion, they smooth out their ratings. A pure development 360 creates the psychological safety that honest input requires — which is why most organizations use it for that purpose alone. According to a review of current 360-feedback research, 95% of organizations use 360 feedback solely for individual development, not for compensation or promotion decisions.

The 360 development review template — competency areas and questions

The template below covers 8 competency areas. It combines closed scale questions with three open-ended development questions. For a clean cycle, around 20 to 30 items is enough — roughly 10 to 15 minutes of completion time, which keeps raters attentive (evasys HR guide).

Recommended rating scale: 1 to 5 (1 = strongly disagree, 5 = strongly agree) plus a "cannot assess" option. That last option matters: it stops raters from filling in fields they cannot actually observe — and producing distorted data in the process.

8 competency dimensions with example questions

Add three open-ended questions at the end of the form. They supply the qualitative context that numbers alone cannot:

For individual contributors without leadership responsibility, drop the "Leadership & direction" block and weight collaboration, communication and results orientation more heavily. A questionnaire that looks identical for every role produces useful data for no one.

What makes a development question work — and what doesn't

The quality of a 360 review is decided by its questions. Three criteria separate development-ready questions from useless ones.

Avoid questions like "Lives the company vision" or "Sees opportunity where others see problems." They sound like a mission statement but cannot be observed or developed — the answers reveal more about how much the rater likes the person than about their behavior. A good question describes a behavior so precisely that two different raters would interpret the same situation the same way.

That this difference is measurable is shown by research. A scientifically validated scale for "role-model behavior" reached a Cronbach's alpha of 0.96 and criterion validity of r = 0.93. Simple free templates almost never reach those levels — their questions often fail to reliably measure what they claim to. When the results feed personnel decisions or development budgets, question quality is worth a hard look.

How to run a 360 development review — 5 steps

Step 1 — Define the purpose and scope

Decide first: development or evaluation? This choice drives everything else — the questions, who receives the results, and any works council obligations. Define the target group (leaders, high-potentials, or all employees) and set the participation rules. For a development 360, voluntary participation is strongly recommended. In DACH, involve the works council early — see the section below.

Step 2 — Select raters

The recommendation is 8 to 15 raters per recipient (honestly.de); a minimum of 6 to 10 is workable (AIHR). A balanced mix for a leader is typically: 1 direct manager, 3 to 5 peers, 2 to 4 direct reports, and the self-assessment.

Mind the anonymity rule: at least 3 raters per group are needed before results can be reported anonymously. Below that threshold, individual answers become identifiable and the entire premise of honest feedback collapses.

Step 3 — Configure and communicate

Tailor the questionnaire to role and level. A leader needs different questions than a specialist without people responsibility. Brief everyone in advance and transparently: what the feedback is for, how anonymity is protected, who sees the results, and how they will be used. Plan 10 to 14 days for the survey window and 6 to 12 weeks for the full process.

Step 4 — Analyze results

Automated analysis through a feedback tool saves time, protects anonymity and avoids spreadsheet errors. What matters is not the average score but the self-versus-other gap: where does the person rate themselves clearly differently from those around them? Those are the blind spots — and the most valuable development areas. Organizations that use 360 feedback well see real returns; one analysis of SHRM data reports an average 14.9% performance improvement for employees receiving structured 360 feedback.

Step 5 — The development conversation and plan

Open the conversation with strengths before moving to development areas. Pick no more than 2 to 3 focus topics — usually the competencies with the largest self-versus-other gap. Each focus area becomes a concrete plan: one measurable behavioral change, a timeframe, a success indicator, and a follow-up check at around four months.

This is where a 360 stops being a one-off event and becomes a system. The competency gaps it surfaces feed directly into the person's individual skill profile, so development areas are not merely discussed but documented, tracked and made visible across cycles. Our ultimate guide to successful skill management shows how to run that systematically.

Common mistakes and how to avoid them

The most expensive mistake is running a 360 without support. A classic meta-analysis by Kluger and DeNisi (1996) found that around 38% of feedback interventions actually worsen performance when the process is poorly designed. Feedback is not a neutral act — handled badly, it demotivates instead of develops.

Linking 360 feedback to skill management

This is the lever most templates leave on the table. A 360 review is, at its core, a competency diagnosis. It reveals where a person stands today — and that data is the natural input for systematic skill management.

At the individual level, self-versus-other gaps become concrete entries in the skill profile: "needs development in X" turns into a documented goal you can track across cycles. At team and organizational level, aggregating multiple 360 cycles reveals systemic patterns — for example, when an entire department scores low on "developing others." That is no longer an individual problem but a structural skill gap you can address deliberately with training or mentoring.

Connecting feedback and skill profiles also keeps competency gaps from going undetected and talent from quietly walking out the door. Read more in our piece Skill Management: Stop the Hidden Employee Exodus. For an overview of suitable tools, see our Skills and Competency Management category.

DACH note — GDPR and works council requirements

In Germany, Austria and Switzerland, a 360 review is not only an HR method but also a data-protection and co-determination matter. Skipping this can get the entire process challenged.

FAQ — 360 development review template

How often should you run a 360 development review?

Annually is the standard for development 360s — sometimes paired with a lighter 180-degree check-in mid-year. More than twice a year tends to cause rater fatigue; too rarely makes it hard to measure progress.

How many raters does a 360 review need?

Between 8 and 15 total is ideal. The critical threshold is a minimum of 3 raters per group (peers, direct reports) — below that, anonymity cannot be reliably maintained.

Can 360 feedback results be used for performance ratings or compensation?

For a development 360: no. Mixing the two purposes destroys the psychological safety that makes honest feedback possible. State this explicitly before the process starts — the moment raters suspect a link to pay, they smooth out their ratings.

What is the difference between a 360 review and a 720 review?

A 360 includes internal stakeholders — manager, peers, direct reports, and self. A 720 review also incorporates external feedback from customers, partners, or suppliers. For most development contexts, a 360 is sufficient.

How do you turn 360 feedback into a development plan?

Identify the 2 to 3 competencies with the largest gap between the self-rating and others' ratings — these are the blind spots most worth addressing. Define one concrete behavioral change per focus area, assign a timeframe, and schedule a follow-up check at around four months.