Performance review software for small companies: how to choose
Read more Tool Selection
To roll out 360 feedback for the first time, you decide what it’s for, have a leader go through it first, announce it in plain words, run one small round, and act on the results where people can see you doing it. That’s the whole sequence, and the order matters more than any single step.
Notice what’s not on that list: choosing software, building a competency model, or scheduling a training workshop. Most rollout advice is written for thousand-person organizations and starts with procurement. At 30 to 200 people, the rollout is a trust exercise, and trust doesn’t come from a vendor.
This post covers the introduction: how to bring 360 feedback into a company that has never done it, without half the team hearing “surveillance.” The mechanics of running the round itself, picking raters, writing questions, synthesizing responses, are a separate job, and I’ve covered them in how to run your first 360 review. Read this one first. A perfectly executed round can still fail if it was introduced badly.
Key takeaways
- A 360 rollout succeeds or fails on three visible moments: how it’s announced, who goes first, and what happens after the first results. Everything else is logistics.
- Decide the purpose before anyone hears about the initiative. A 360 tied to pay in round one produces polite fiction instead of feedback.
- The right pilot group is the founder or leadership team, not a junior team chosen as guinea pigs. People believe what they watch leaders do, not what leaders announce.
- Every employee silently asks three questions: who sees this, does it affect my pay, and why now. Answer all three in the kickoff message, unprompted.
- Expand from pilot to everyone only after one round has produced a visible change. Scaling a round nobody trusts multiplies the distrust, not the feedback.
The single biggest rollout failure happens before anything launches: the company starts collecting feedback without deciding what the feedback is for. Development and evaluation feel similar from the organizer’s chair, and they are opposites from the employee’s chair.
If the results feed into raises, promotions, or performance ratings, people will figure that out fast, sometimes before you do. From that moment, every response gets written for an audience of decision-makers rather than for a colleague’s growth, and you’ll collect a stack of polite, inflated, useless comments.
So make the decision explicit and write it down in one sentence before the rollout begins. Mine would be: “We’re doing this to help each person see what’s working and where to grow, and it is not connected to compensation or promotion decisions.” If you can’t say that sentence honestly, pause the rollout until you can, or rename the initiative, because what you’re rolling out is an evaluation program, and people deserve to know that.
Keep the first year developmental. There’s a longer argument about whether these two purposes can ever share a process, but for a first rollout the answer is settled: development only.
Here’s the part most rollout plans get backwards. The standard advice says to pilot with a small group, which is right, and then companies pick a junior team as the test subjects, which is wrong. Piloting on the least powerful people in the company teaches everyone that feedback is something done to you by the people above you.
Run the pilot on yourself. If you’re the founder, CEO, or Head of People driving this, the first 360 in company history should have your name on it. Then, and this is the step that does the real work, share something from your results. One theme, one thing you’re changing, said out loud in an all-hands or a written update.
Imagine a founder at a 45-person company who runs the first 360 on herself, hears from six raters that she interrupts in meetings and re-decides things that were already decided, and tells the company: “This came up in my 360, I’m working on it, and here’s what I’m asking you to call out when I slip.” The rollout is effectively complete at that moment. Every employee now knows the process is real, safe enough for the boss, and connected to visible change.
Now picture the opposite, a company where leadership announces 360 feedback, exempts itself, and pilots on the support team. The words say “development” while the structure says “monitoring,” and people believe structure over words every time.
When employees hear that 360 feedback is coming, three questions form immediately, and almost nobody asks them out loud: who sees what I write, does this affect my pay, and why is this happening now. An announcement that leaves any of the three unanswered gets filled in with the most cynical available guess.
So answer all three, unprompted, in plain language. Here’s a kickoff message you can adapt:
“We’re introducing 360 feedback, starting with a small pilot. What it is: a few short questions about what someone does well and where they could grow, answered by the people who work with them most. What it’s for: development only. It is not connected to salaries, promotions, or ratings, and it won’t be. Who sees what: peer responses are anonymous; each person gets a summary of themes, not a list of who said what. Why now: as we’ve grown, most of us get feedback from one person, our manager, and that’s too thin a picture. I’m going first, and I’ll share what I learn. Questions, concerns, or objections: bring them to me directly, I mean it.”
Two details in that message carry most of the weight. Naming the anonymity policy explicitly matters because vague promises of confidentiality read as no promise at all, and if you’re unsure what policy fits a small team, I’ve written about when anonymous feedback works at small companies. Inviting objections matters because the skeptics you hear from are recoverable, while the ones who stay silent quietly sandbag the response rate.
A first round should be almost anticlimactic: three to five people reviewed, four or five open questions, one week of collection, and a synthesized summary delivered in a real conversation. Resist every instinct to make it bigger. Twenty people reviewed in round one means twenty synthesis jobs and a hundred-plus requests landing on a team that hasn’t yet decided whether to trust this, and participation quality collapses exactly when you can least afford it.
Timing deserves one honest check before you commit. A rollout lands badly during crunch, immediately after layoffs, or in the middle of a quarter-close, and there are situations where the right call is to wait entirely; I’ve laid those out in when not to run a 360 review. Feedback asked for at the worst possible moment reads as tone-deaf, and the first impression is the one the whole program inherits.
For the round mechanics, rater selection, question wording, synthesis, and the delivery conversation, follow the step-by-step 360 process rather than improvising. The rollout post and the running post are deliberately separate skills: one builds the trust, the other spends it well.
And run the pilot with whatever tooling is closest to hand. A shared form is fine for round one. The trust problem is the hard problem, and no software solves it.
The rollout is judged not on the announcement or the collection week but on what visibly happens afterward, because everyone who wrote thoughtful feedback is now watching for evidence that writing it was worth ten minutes of their life.
Closing the loop takes two moves. Each person reviewed shares one theme from their results and one thing they’re doing about it, in whatever forum feels natural: a team meeting, a written update, a one-on-one. And the organizer reports on the process itself: what worked, what was awkward, and what will change in the next round. Both moves are small, and together they convert the pilot from an HR activity into evidence that feedback moves things.
Picture two companies three months after their pilots. In the first, results went out as PDFs, nothing was said again, and the second round’s completion rate drops by half because people concluded their effort evaporated into a folder. In the second, the two reviewed managers each named one change in front of their teams, the organizer shortened the questionnaire based on complaints, and the second round fills without a single chasing email. The difference between those companies isn’t the tool, the questions, or the anonymity policy. It’s the visible loop.
Go from pilot to company-wide when three things are true: the pilot round was completed without heavy chasing, at least one visible change came out of it, and, this is the tell I trust most, people outside the pilot start asking when it’s their turn. That pull is the signal that trust took. If you have to push the expansion, the pilot hasn’t finished its job yet.
When you do expand, set the rhythm conservatively: once or twice a year is plenty for a first-year program. The urge to make feedback constant is well-intentioned and usually premature, because each round costs attention, and a company that runs four mediocre rounds a year builds less trust than one that runs two careful ones.
If the pilot went badly, and sometimes it does, don’t scale it and hope. Diagnose which of the three visible moments failed: the purpose wasn’t believed, the leader didn’t go first convincingly, or the loop never closed. Fix that one thing and re-pilot with a different small group. A failed pilot is a cheap lesson, while a failed company-wide rollout poisons the idea for a year or more.
By the second or third round, the manual version starts to strain: chasing responses, collating answers, and writing summaries for a growing list of people becomes a real job. That’s the point where a focused tool earns its place, and you can start your first 360 in Lynxify.me without an annual contract or a credit card. But the tool inherits the trust you built in the rollout, and it cannot create what isn’t there. The order of operations, culture first and logistics second, is the whole reason building a feedback culture comes before buying anything.
Most companies treat the rollout as the boring administrative phase before the real program starts. I’d argue the reverse: the rollout is the most consequential feedback event your company will ever run, because it’s the round that sets everyone’s expectations for what this thing is. People decide whether 360 feedback at your company is safe, useful, and honest based on the first one they witness, and they rarely revise that verdict.
So spend your effort where the verdict is formed. Say what it’s for in one sentence you can defend. Go first, visibly. Answer the three silent questions before they’re asked. Keep round one small, and close the loop where everyone can watch it close. None of that requires budget, and all of it requires nerve. The companies that get 360 feedback right aren’t the ones with the best tools but the ones whose first round proved the words true.
How do you introduce 360 feedback without scaring people?
Answer the three questions people are silently asking: who sees the responses, whether it affects pay, and why it’s happening now. Put all three answers in the kickoff message before anyone asks, make the first round developmental only, and have a leader go through the process first and share a takeaway. Fear comes from ambiguity, and ambiguity is fixable with plain words and a visible example.
Should we pilot 360 feedback before rolling it out to everyone?
Yes, and the pilot group should be leadership, not a junior team. A pilot on the founder or the leadership team proves the process is safe and real, works out the kinks at small scale, and creates the demand that makes company-wide expansion feel like an invitation rather than a mandate. Expand once the pilot completed without chasing, produced a visible change, and people outside it are asking to join.
How long does it take to roll out 360 feedback at a small company?
Roughly six to ten weeks from decision to expanded rollout: a week to settle purpose and the anonymity policy, a two-to-three week pilot round including synthesis and delivery conversations, a few weeks of visible follow-through, then the first expanded round. The calendar time is mostly deliberate pacing rather than work; the actual setup for a small pilot takes an afternoon.
Do we need training before starting 360 feedback?
At a small company, a clear kickoff message and well-designed questions do the job that enterprise rollouts assign to training workshops. Open questions about observed behavior (“what should this person keep doing, what would make the biggest difference”) are hard to answer badly. Save the training budget, and spend the effort on synthesis and honest delivery conversations instead.
Dmytro Shtapauk
Practical tips and experience from top-notch experts
