A 360 review template for startups (copy and customise)
Read more Questions & Templates
A 360 feedback round and a performance review are different instruments built for different jobs. A performance review evaluates outcomes for pay and promotion decisions. A 360 develops behaviour through multi-source perspective. Most teams should run both, separately, with the 360 never tied to a compensation outcome. That’s the whole answer, and almost nobody ships it cleanly.
I sell software in this category, so discount my view accordingly. But the part nobody outside of vendorland talks about is what happens when teams mash the two together: the 360 stops surfacing anything honest, the performance review gets worse not better, and a year later you’ve burned both. This article is for the People Ops lead or founder who already runs one of these (or is about to) and is asking the practical question: do I need the other, when do I run it, and how do I keep them from corrupting each other?
Most 360 feedback vs performance review writeups stop at definitions. The structure here goes further: a side-by-side that gives you the answer in fifteen seconds, then the decision rule, then the cadence that lets both instruments do their job, then what happens when you have to pick one.
Key Takeaways
- A performance review evaluates outcomes for compensation and promotion decisions. A 360 develops behaviour through multi-source perspective. They are not substitutes; they are tools for different jobs.
- The single axis that matters most in any 360 feedback vs performance review comparison is whether the instrument is tied to compensation. Once a 360 is tied to comp, honesty in it collapses by round two.
- The decision rule is “run both, separately, with the 360 decoupled from any pay decision.” If you can’t decouple them, run only the performance review and keep the 360 for next year.
- Small teams under about 25 people often can’t sustain both. Pick the one that matches the missing piece: 360 for development culture, performance review for compensation defensibility.
- The fastest way to ruin both is to run a 360 two weeks before a performance review and use its themes as input. By round two, raters notice, and the 360 dies.
Most articles on this give you a list of six differences and let you decide which matter. They all matter; they don’t all matter the same.
| Axis | Performance review | 360 feedback |
|---|---|---|
| Purpose | Evaluate outcomes against expectations | Develop behaviour through reflection |
| Inputs | Manager only | Manager, peers, direct reports, self |
| What’s measured | Goals, projects, results, KPIs | Communication, collaboration, growth |
| Frequency | Annual or biannual | Quarterly to twice a year |
| Anonymity | Attributed to the manager | Anonymous to the recipient |
| Tied to compensation | Usually yes, by design | Should never be, by design |
| Best for | Pay decisions, promotion, defensibility | Blind spots, leadership growth, repair |
Read the rows in order and the bottom one looks like one of seven. It isn’t. The compensation tie is the master axis: every other row cascades from it.
If an instrument is tied to compensation, it has to be attributed, manager-led, defensible, and specific enough to justify a pay decision. That’s the entire performance review.
If an instrument isn’t tied to compensation, you can ask peers, you can promise anonymity, you can ask about behaviour rather than KPIs, and you can run it often enough to be useful. That’s the entire 360. The rest is design detail.
Performance reviews exist because companies have to make pay decisions, and pay decisions have to be defensible. Someone has to commit a judgment to paper that says “this person earned a raise, this person didn’t.” A manager is the person with both the context and the authority to make that call, and the document has to survive a comparison conversation, a promotion-committee debate, or in the worst case, a legal challenge. The annual cadence, the manager-only input, the outcome focus: all of that follows from the job the instrument has.
360 feedback exists because the people closest to someone’s work see things their manager can’t. A peer knows how someone shows up in a working session. A direct report knows whether the manager actually changes a decision after hearing concerns. A senior leader knows whether someone’s strategic instincts hold up under ambiguity. None of that is visible to a single observer. So the format collects from multiple raters, promises anonymity to make the responses honest, focuses on behaviour because that’s what raters can see, and runs more often because behaviour is what changes between rounds. That’s the case why 360 feedback matters goes deeper on if you want the longer argument.
The two instruments break in opposite ways. A performance review without manager authority becomes vague: nobody owns the call, the rating is consensus mush, the pay decision it informs is no better than a coin flip. A 360 with compensation attached becomes dishonest: raters hedge, responses get safer, and the signal disappears. Each is well-designed for its own job and badly-designed for the other one’s.
The rule, written out so you can disagree with it cleanly: run both, run them separately, and never tie the 360 to a compensation decision. That’s it. The rest of this article is mechanics.
Three diagnostic questions for the version of “which do I need next” most People Ops leads actually face:
Do you currently have a credible way to decide raises and promotions? If you don’t, build that first. A 360 won’t help; it will make the comp question harder by introducing input that everyone will assume informs pay. Build the performance review process (or a defensible substitute, even an honest manager-driven 1:1 trail) before you layer in a 360.
Does anyone on your team have a development blind spot their manager can’t see? If yes, you have a 360 problem, not a performance review problem. The manager’s perspective is already in the review and isn’t going to surface what the manager can’t see. Run a 360 to widen the input.
Are your existing performance reviews delivering useful behaviour change, or just a score? If the answer is “just a score,” you’re getting the evaluative job done and missing the developmental one. Add a 360 to the rhythm, decoupled from the next review.
If you’re running neither and you’re a small team, the practical version of “where do I start” sits in the 360 advantage small companies already have, which is more useful at small scale than redoing the annual-review playbook a smaller way.
Want to see what a structured 360 actually looks like without the platform overhead? How to run your first 360 review covers the full mechanics: picking raters, writing the questions, handling anonymity, delivering results.
Most teams that say they “do both” do them poorly: the 360 lands a week before the performance review, the manager reads the themes on the way to the comp conversation, and somewhere in there the 360 becomes a stealth performance score. Raters figure this out faster than you’d think. Four rules keep both instruments doing their actual jobs.
Rule 1: separate calendars. If the performance review lands in Q4, the 360 should land in Q1 or Q3, ideally both. The calendar gap signals to the team that the 360 isn’t comp prep. Raters answer differently when they know the comp conversation is six months away.
Rule 2: separate conversations. The development conversation is the 360 conversation: an hour, anonymous themes, no compensation talk in the room. The compensation conversation is the review conversation: an hour, manager judgment, comp on the table. Same person, two meetings, a month apart minimum. Blend them and both get worse.
Rule 3: themes feed in, never quotes. A 360 surfaces patterns that a manager would be foolish to ignore when she’s preparing a review. It’s fine for those patterns to inform her thinking. It’s not fine for 360 responses to be quoted in the review document, attributed even by implication to specific raters, or used as “evidence” in a comp decision. One quote that traces back to a comp outcome, and the 360 dies for that team.
Rule 4: tell the team what’s decoupled from what. Say it in the kickoff email and say it again in the debrief: this 360 is not tied to compensation, the manager will see themes not quotes, and the pay conversation will happen separately. People will still suspect what they suspect. The disclosure isn’t there to convince the cynics. It’s there so the people who would have been honest aren’t second-guessing themselves.
Picture a 60-person company that runs a 360 in Q1, themes go to managers (no quotes attached), managers use them to calibrate their own view going into the Q4 performance review. The Q4 review is a separate document, manager-attributed, with comp tied to it. No rater can trace a sentence in the comp conversation back to their input. Two years in, completion rates on the 360 sit around 90%, the responses carry specific behavioural detail instead of generic praise, and the Q4 review lands with fewer surprises because the calibration work happened earlier. That’s what “both, done well” looks like.
Most companies under about 25 people can’t sustain both well at the same time. Three or four people doing both properly is two people’s full attention for a month, and at that scale the work has nowhere to go. The 360 feedback vs performance review question, at this size, often becomes “which one do I start with.”
If you have to pick one, pick the one that matches the job in front of you.
If feedback culture is the missing piece, pick the 360. A small team usually has informal alignment on pay: the founder picks numbers, everyone knows roughly where they sit. What it doesn’t have is a structured signal on how people are actually showing up. The 360 fills that gap. Use a 1:1 document and a simple growth conversation to cover the development job; use the founder’s judgment for the comp job until the team grows past the size where that’s possible. The case against annual performance reviews covers why running the lighter, multi-source version is often the better starting point at this scale.
If pay decisions are the missing piece, pick the performance review. A small team that’s growing fast often hits a point where the founder’s intuition isn’t a defensible system anymore: three people in similar roles get different raises, nobody can explain why, and the trust cost is real. Build the review process first. Add the 360 the following year, on a separate calendar, once the comp question is settled.
For the harder version of this question, when running a 360 right now would actively damage the team, when not to run a 360 review covers the five situations where the right call is to skip it and what to do instead in each one.
The most common version of “doing both” that fails: a team runs a 360, gets useful results, and then runs a performance review two or three weeks later that draws heavily on the 360 themes. The manager isn’t malicious. She’s pattern-matching, using the freshest input available, doing the job she was given.
By round two, raters notice. They notice that someone who got bad 360 feedback also got a tough review. They notice that someone whose 360 was glowing got the raise. They don’t have proof. They don’t need proof; correlation is enough to change behaviour. Round three comes back faster and emptier than round one. Completion rate stays the same. The signal collapses.
Now you’ve spent two years building a 360 program and you have less honest input than you would have had if you’d never started. The performance review didn’t get better either: it picked up some peer-perspective texture and lost an entire feedback channel.
This is the failure mode no vendor flags because it’s the failure mode the customer creates after the sale closes. It’s also the most common reason “we tried 360s and they didn’t work” gets said in rooms I sit in. The 360 was fine. The bundling killed it.
Ready to try a structured 360 without the bundling risk? Start your first 360 in Lynxify, no annual contract, no credit card required. Or paste questions into a Google Form and run it manually: the design discipline matters more than the tool.
These are not competing instruments. They’re different tools for different jobs that happen to share the word “review.” A performance review answers “what did this person produce, and what does that mean for their pay?” A 360 answers “how is this person showing up, and what can they work on?” Both questions matter at almost every stage of a growing team’s life.
The teams that get the most out of both treat them as additive, separated by calendar and by purpose, and decoupled from each other in the way that lets each instrument do the job it was designed for. If you run only one today, the question isn’t “should I switch to the other one.” It’s “is there a job in front of me that the instrument I’m running isn’t designed for?” Usually the answer is yes. Add the other one, run it well, keep it separate, and resist the urge to mash them together at the end of the year.
When you’re ready to run a 360 alongside your existing review process, start your first 360 in Lynxify, no annual contract, no credit card required. Or run it with a shared document and prove you don’t need a tool yet. Either way, run them separately. That’s the whole game.
What is the difference between 360 feedback and a performance review?
A performance review evaluates outcomes against expectations and informs pay or promotion decisions. It’s usually annual, manager-led, attributed, and tied directly to compensation. A 360 collects feedback from multiple people who work with someone (manager, peers, direct reports, sometimes the person themselves), runs more often, is anonymous to the recipient, and is designed for development rather than evaluation. The biggest practical difference is the compensation tie: a performance review exists because of it; a 360 only works without it.
Can a 360 review replace a performance review?
No. A 360 isn’t designed to make compensation decisions. The input is anonymous, the focus is behaviour rather than outcomes, and there’s no single owner of the judgment. The format that makes a 360 honest is the format that makes it a bad fit for a pay decision. Use the two for different jobs. The strongest version of “doing both” runs the 360 for development a quarter or two away from the performance review, with explicit decoupling.
Should 360 feedback be tied to compensation?
No. This is the single design choice that determines whether a 360 stays honest. The moment raters figure out that their input shapes someone’s raise (and they will figure it out by round two), the responses get safer, vaguer, and politer. You get a 360 in name and a stealth performance score in fact. Keep them on separate calendars, with separate conversations, and tell the team explicitly that the 360 doesn’t inform comp.
How often should you run 360 feedback vs performance reviews?
Performance reviews work well at annual or biannual cadence: the rhythm matches comp planning, gives runway for behaviour change between reviews, and keeps documentation tractable. 360s work best at quarterly to twice-yearly cadence: more often than the annual review, because development is the goal and faster feedback is more useful, but not so often that the round itself becomes the burden. A common combination is one 360 in Q1 and one in Q3, with the performance review landing in Q4.
Do small companies need both 360 feedback and performance reviews?
Eventually, yes, but most teams under about 25 people can’t sustain both well at the same time. If you can only run one, pick the one that matches the job in front of you: 360 if feedback culture is the missing piece, performance review if comp decisions are getting harder to justify. Add the second one the following year, on a separate calendar. For more on what a structured review process looks like at small scale, performance reviews for small companies covers the practical version.
Dmytro Shtapauk
Practical tips and experience from top-notch experts
