360-Degree Feedback for Small Business: An Honest Guide
What 360-degree feedback is, when small businesses without HR should and should not use it, a 30-day plan, and alternatives that work better at 5-50 people.
360-Degree Feedback
An honest guide for small businesses without an HR department
The first time I tried to run 360-degree feedback at one of my early companies, I had 11 employees. I bought a survey tool, picked questions from a template, and launched the cycle in two weeks. Three weeks later, two people were not speaking to each other, one was actively job-hunting, and the recipient I had personally championed for the program told me he wished I had never started it. The data was honest. The team was not ready for honest data.
I tell this story because most articles on 360-degree feedback are written by HR consultants for HR-led organizations of 500+ people. They explain how 360 works in the environment it was designed for: dedicated facilitators, trained coaches, established performance management infrastructure. Reading them as a small business owner is misleading. The version of 360 that works at your scale is dramatically different from the version those guides describe, and for most companies under 15 employees, the honest answer is that 360 is the wrong tool entirely.
This guide covers what 360 actually is, the structural conditions under which it works at small scale, the conditions under which it backfires, alternatives that deliver most of the value with much less risk, and a practical 30-day plan if you decide your team is ready. I built FirstHR for owners and operators at exactly the 5-50 person stage this guide addresses, so the perspective here is shaped by what I have seen actually work versus what the consulting industry recommends.
What 360-Degree Feedback Actually Is
Three things 360 feedback is not, despite frequent confusion. First, it is not a performance review. Performance reviews evaluate; 360 develops. Mixing the two is the single most common implementation failure and tends to destroy the program within two cycles. Second, it is not a culture survey. Culture surveys ask questions about the organization; 360 asks questions about an individual. Third, it is not a conflict resolution tool. Using 360 to surface or address interpersonal conflict is a misuse that almost always makes the conflict worse rather than better.
The simplest working definition: 360 feedback is a structured way for one person to learn how they are perceived by the people around them, with enough rater diversity that the picture is more accurate than any single conversation could provide. The "360" refers to the circle of perspectives surrounding the individual; the recipient sits in the middle, with feedback flowing from above (manager), beside (peers), below (direct reports), and within (self).
Who Provides 360-Degree Feedback
The standard rater configuration distributes 8-13 raters across four or five categories. The exact mix depends on the recipient's role. An individual contributor might have 1 manager, 4 peers, and self-rating. A manager might have 1 manager, 3 peers, 5 direct reports, and self-rating. The rule of thumb is at least 3 raters in any category that is averaged separately, to preserve anonymity and reduce the influence of any single response.
Two rater categories deserve special attention. Direct reports are usually the most consequential category in any 360, because they observe behaviors that managers often miss: how the recipient handles disagreement, allocates credit, gives feedback under stress. Research from the Center for Creative Leadership consistently finds that direct-report ratings predict career derailment more reliably than other rater categories, which is why excluding them is one of the most common 360 errors at small companies that should know better.
Self-ratings are valuable not because they are accurate (they usually are not), but because the gap between self-rating and others' ratings produces the most actionable insight. A leader who rates themselves a 5 on "gives clear feedback" while their direct reports rate them a 2 has identified a blind spot worth investigating. A leader whose self and others' ratings closely match is signaling either high self-awareness or that the rater pool is afraid to be honest. Both are useful information.
360 Feedback vs Traditional Performance Review
Confusing these two is the most common 360 implementation failure I have seen. They are different tools with different purposes, and combining them either makes the performance review worse or makes the 360 worse, usually both.
| Dimension | Traditional Performance Review | 360-Degree Feedback |
|---|---|---|
| Primary purpose | Evaluate performance, inform compensation/promotion | Develop self-awareness, identify behavior changes |
| Rater count | 1 (manager) | 8-13 (manager + peers + reports + self) |
| Anonymity | Not anonymous; manager-employee conversation | Confidential and aggregated; individual raters not identified |
| Frequency | Annual or semi-annual | Annual or every 18-24 months |
| Output | Performance rating, goals for next period | Written report with self vs. others gap analysis |
| Tied to compensation | Yes, typically | No; separating from compensation is essential |
| Best for | Documenting outcomes, formal HR record | Behavior change, leadership development, blind-spot detection |
| What it answers | How is this person performing in their role? | How is this person perceived, and what should they work on? |
The most useful mental model: a performance review tells you whether someone is doing the job; a 360 tells them how to do it differently. They serve different decisions and should run on separate cycles. Mixing them creates two predictable failure modes. If 360 results affect compensation, raters adjust their answers strategically, and the data becomes politically calibrated rather than honest. If performance reviews include anonymous peer ratings, the manager loses the ability to have a direct conversation about the actual feedback because they cannot reveal who said what.
For the broader practice of running performance reviews at small business scale, the performance review guide covers the operational side. For the full performance management lifecycle, the performance management guide covers how 360 fits within the broader system.
Where 360 Feedback Came From
The origin of 360 feedback is older than most articles describe. The concept of multi-source rating was first systematically used by the U.S. Army during World War II to assess officer candidates. The early industrial application appeared at Esso (now ExxonMobil) in the 1950s, where researchers experimented with peer-rating systems for executive development. The format remained niche for decades, used primarily in military and academic settings.
The corporate adoption wave came in the 1990s, driven by two forces. First, the rise of leadership development as a distinct corporate function created demand for tools focused specifically on behavior change rather than performance evaluation. Second, the shift from hierarchical to flatter organizational structures meant that managers could no longer rely on a single boss to evaluate their effectiveness; their peers and direct reports were now equally important sources of insight. By 2000, 360 feedback was used in roughly 90% of Fortune 500 companies, often as a core part of leadership development programs.
The original Harvard Business Review article on the topic, published in 2001 by Cynthia McCauley and others, was titled "Getting 360-Degree Feedback Right" and remains one of the most cited references in the field. The follow-up 2019 piece on getting the most out of 360 reviews updated the practice for modern hybrid teams. Both articles reach the same conclusion that the original research established: 360 works when it is developmental, anonymous, and supported by coaching, and it backfires when any of those three conditions are missing.
The small business angle is largely absent from this history. Almost every published study and best-practice guide assumes the recipient works in an organization with 200+ employees, a dedicated HR function, and a leadership development budget. The application of 360 at 5-50 person companies is genuinely under-researched, and most of what has been written treats small business 360 as simply "the same thing, scaled down," which is the source of most failures at that scale.
Benefits of 360 Feedback (When It Works)
Done well, 360 produces value that is hard to generate any other way. The list below covers the genuine benefits I have observed when the conditions for success are met. The catch, addressed in the next section, is that most small businesses do not meet the conditions for success.
The strongest benefit is blind-spot detection. Almost every leader has at least one significant gap between how they perceive themselves and how their team perceives them. These gaps are extremely hard to surface through any normal management practice, because the people closest to you have political reasons not to tell you directly. Anonymous, aggregated feedback removes the political cost of honesty and surfaces patterns that would otherwise stay hidden for years. This is the single most defensible reason to run 360.
The second benefit is behavior change focus. Most performance feedback in small companies is either too general ("you are doing great") or too vague ("you should improve communication"). 360 forces specificity: the report shows that 5 of 7 raters mention you cut people off in meetings, or that your average rating on "delegates effectively" is 2.3 out of 5. These specific data points produce specific behavior changes in a way that general feedback does not.
The third benefit is leadership development at scale. For organizations growing into multiple management layers, 360 creates a consistent development experience across leaders, surfaces patterns that inform leadership programs, and produces a baseline against which progress can be measured year over year. The leadership development guide covers the broader context within which 360 fits.
The fourth benefit is cultural signaling. Running 360 well signals to the team that the company takes development seriously, that leaders are willing to receive feedback themselves, and that feedback flows in all directions, not just downward. This cultural signal is sometimes more valuable than any individual report.
Drawbacks and Risks (Especially at Small Scale)
The drawbacks of 360 feedback are not abstract. They are the specific failure modes I have watched destroy programs at multiple companies, including my own first attempt. Each of them is more pronounced at small business scale than the published literature acknowledges.
The first drawback is anonymity collapse. 360 requires anonymity to produce honest data, and anonymity requires statistical critical mass. With 3 peer raters, even aggregated comments often reveal who said what. With 2 peer raters, the recipient can almost always identify which one wrote which comment. At companies under 15 employees, structural anonymity is impossible to guarantee, and the moment one rater realizes their comment was identified, every future cycle is contaminated by that knowledge.
The second drawback is rater bias and unreliability. Raters bring all of their own biases into 360 ratings: recency effects (they remember last week, not last quarter), halo effects (one strong impression colors everything), reciprocity (rating you well because you rated them well last cycle), and political calculation (rating you based on what they want from you, not based on observed behavior). The aggregation across multiple raters partially controls for these biases, but only partially, and at small scale where rater pools are small, individual biases dominate.
The third drawback is cost without coaching. The single most expensive failure mode is delivering a 360 report to someone with no coaching support. The recipient reads it alone, focuses on the most negative comments, draws inaccurate conclusions about who wrote them, and either becomes defensive or loses motivation. Research from the Work Institute on retention consistently shows that mishandled feedback is one of the top drivers of voluntary turnover in the months following the conversation. A 360 program without coaching is statistically more likely to harm retention than improve it.
The fourth drawback is conflict amplification. 360 surfaces interpersonal tensions that were previously latent. In a healthy team with good coaching, surfacing the tension leads to constructive resolution. In an unhealthy team or a team without coaching support, surfacing the tension leads to escalation, faction formation, and sometimes departures. Small teams have less buffer to absorb this dynamic; one departure on a 12-person team is dramatically more disruptive than the same departure on a 1,200-person team.
The fifth drawback is survey fatigue and signal dilution. Each rater participates in multiple 360s per year if they sit on a team where 360 is run regularly. After the first or second cycle, response quality drops measurably. Comments become shorter, ratings cluster around 4 out of 5 to avoid difficult conversations, and the data quality degrades. Small companies running 360 too frequently see this signal dilution within 2-3 cycles.
Should Your 5-50 Person Business Run 360 Feedback?
The honest answer for most companies in this size range is "not yet" or "probably not." That answer surprises owners who have read enterprise content recommending 360 universally. The recommendation is not universal; it is contingent on a specific set of organizational conditions, most of which are not in place at small business scale.
Below is the readiness checklist I use when small business owners ask whether they should run 360. Read each item honestly. If you cannot answer "yes" to most of them, your team is not ready, and the appropriate next move is to build the missing items rather than launch 360 anyway.
Readiness Checklist
Most small business owners will fail this checklist on at least three items, most commonly: team size below 15, no working weekly 1-on-1 cadence, and no time budget for post-feedback coaching. These are not arbitrary criteria; they are the structural conditions under which 360 either creates value or actively destroys value. Running 360 without them is not a leaner version of the standard practice; it is a different and worse process that happens to share the same name.
Red Flags: When 360 Will Almost Certainly Backfire
Beyond the readiness checklist, there are specific situations where 360 is almost guaranteed to make things worse. These are the cases where I have watched the program create damage that took 6-12 months to repair. If any of the items below describe your team right now, postpone 360 until the underlying situation has changed.
The pattern across all seven red flags: 360 amplifies whatever is already true about your team. If trust is high, 360 amplifies trust. If trust is broken, 360 amplifies the brokenness. If management is strong, 360 reinforces good management practices. If management is weak, 360 exposes the weakness in a way that the team cannot un-see. Owners often hope 360 will fix the problems on the list. It will not. It will surface them faster and at higher volume.
Better Alternatives for Teams Under 15 People
If your team is too small for formal 360 but you still want the value 360 delivers (multi-source feedback, blind-spot detection, behavior change focus), the alternatives below cover most of the ground at a fraction of the risk and cost. None of them require software or HR infrastructure.
The most underrated of these is structured weekly 1-on-1s. Almost every value 360 delivers (clarity on perception, behavior-specific feedback, blind-spot detection) can be produced through a consistent weekly conversation in which the manager genuinely asks for feedback on themselves and acts on what they hear. The format is not glamorous and does not produce a printed report, but the cumulative effect over 12 months exceeds what most 360 cycles produce. Gallup's research on engagement drivers consistently finds the manager-employee relationship as the strongest single predictor, and that relationship is built in 1-on-1s, not in annual surveys.
The second most underrated is manager-led upward feedback. Once per quarter, you sit down with each direct report and ask one question: "What is one thing I could do differently as your manager that would make your work easier or more rewarding?" Then you listen, take notes, and act on what you hear within two weeks. This single practice captures most of the value of the direct-report category in 360 feedback, without the anonymity machinery that small teams cannot support. The conversation is harder than reading an anonymous report, but the data is better.
For the broader employee retention picture these alternatives support, the employee retention strategies guide covers the system. For the underlying management foundation, the people management guide covers what comes before any of this.
A 30-Day Plan to Run 360 Without an HR Department
If you have read the readiness checklist, considered the red flags, looked at the alternatives, and concluded your team is genuinely ready for formal 360, the 30-day plan below is the lightest defensible version of the practice. It assumes a team of at least 15 employees with established management practices and a willingness to invest 4-7 hours per recipient over the cycle.
Two notes on this plan that often get missed. First, the coaching conversation is the most important step, not the survey. If you cannot facilitate a coaching conversation for every recipient, do not run the cycle. Self-served reports without coaching produce more harm than benefit at a statistically meaningful rate. Second, the 90-day follow-up is what converts insight into behavior change. Without it, the cycle was just a survey, and the team will calibrate accordingly next time.
Sample 360 Feedback Questions
The questions below cover 8 common competency areas with 3-4 questions each, suitable as a starting template for small businesses. Adapt them to your specific roles and team context. Each question uses a 5-point scale (1 = strongly disagree, 5 = strongly agree, plus an "unable to assess" option). The 3 open-ended prompts at the end are where most of the actionable insight typically comes from.
| Competency | Sample questions |
|---|---|
| Communication | Communicates ideas clearly in writing and in meetings. Listens actively before responding. Adjusts communication style to the audience. |
| Collaboration | Shares information that helps others succeed. Resolves disagreements constructively. Treats colleagues with respect even under pressure. |
| Ownership | Takes responsibility for outcomes, not just inputs. Follows through on commitments. Raises problems early rather than hiding them. |
| Decision quality | Makes decisions with appropriate information rather than waiting for perfect data. Explains reasoning when others ask. Updates decisions when new information arrives. |
| Customer focus | Understands what customers actually need, not just what they ask for. Prioritizes customer outcomes over internal convenience. Advocates for customers in cross-functional discussions. |
| Feedback to others | Gives specific feedback in real time, not stored up for reviews. Recognizes good work publicly. Addresses problems privately and directly. |
| Self-awareness and growth | Acknowledges mistakes openly. Asks for feedback proactively. Demonstrates measurable growth on previously identified development areas. |
| Leadership (if applicable) | Develops the people who report to them. Makes the team better than they would be without them. Holds the team accountable to high standards without micromanaging. |
Open-Ended Prompts
The free-text prompts below typically produce more actionable insight than the rating questions. Place them at the end of the survey when raters are warmed up and thinking specifically about the recipient.
| Prompt | What it surfaces |
|---|---|
| Describe a specific situation where this person was at their best. What did they do that worked? | Concrete examples of strengths that the recipient can replicate |
| Describe a specific situation where this person could have handled things differently. What would have worked better? | Behavior-specific development areas with grounded context |
| What is one thing this person should start doing, stop doing, or continue doing in the next 90 days? | Forward-looking, action-oriented feedback that translates directly into a development plan |
One note on question design: avoid abstract personality traits ("is this person creative?") and focus on observable behaviors ("does this person bring novel approaches to problems?"). Trait questions invite stereotyping and produce data that is hard to act on. Behavior questions produce specific feedback that maps to specific changes.
How to Choose 360 Feedback Software
If you have decided to run 360, you will need software. Manual administration in spreadsheets is technically possible but almost always breaks anonymity through file metadata, email trails, or sloppy handling of individual responses. Dedicated software handles the mechanics that matter (anonymity, aggregation, report generation) and lets you focus on the parts that require judgment (coaching, action planning, follow-up).
The criteria below cover what matters when evaluating any 360 platform for a small business. The right tool varies by team size and budget; the criteria are stable.
| Criterion | What to look for | Red flag |
|---|---|---|
| Anonymity protection | Aggregates results when fewer than 3 raters in a category; never shows individual rater identity | Shows individual responses or allows the recipient to deduce who said what |
| Question library and customization | Validated competency library you can adapt, plus the ability to write custom questions in plain English | Either fully rigid or fully blank; no validated starting point |
| Rater nomination workflow | Recipient nominates raters with manager approval; clear minimum and maximum rater counts per category | Manager picks all raters with no input from recipient, or recipient picks raters with no oversight |
| Report quality | Clean visual report showing self vs. others gap, strengths, development areas, and verbatim comments grouped thematically | Raw data dumps, complex statistical outputs that require a consultant to interpret |
| Pricing structure | Per-recipient pricing with no minimum seat counts; transparent total cost including any required coaching add-ons | Annual contracts only, large minimums, hidden coaching fees, or per-employee pricing for the whole company |
| Coaching integration | Either built-in debrief workflow (templated coaching guide) or partner network of certified coaches | Software-only with no guidance on the post-feedback conversation, which is where most 360 implementations fail |
| Data ownership and export | Clear data export capability; clear retention policy; ability to delete recipient data on request | Locked-in data, no export, ambiguous retention terms |
| Implementation time | First cycle launchable within 2 weeks of purchase, with templates and example competencies provided | Multi-month rollout requiring dedicated project management and HR consulting hours |
Two practical notes on tool selection. First, prioritize anonymity protection above feature richness. A tool with fewer features but bulletproof anonymity will outperform a feature-rich tool that lets the recipient figure out who said what. Second, prioritize coaching support over reporting beauty. Pretty reports without coaching workflows are a luxury at small business scale; basic reports with templated coaching guides produce better outcomes.
The honest disclosure that this guide owes you: FirstHR does not include a 360 feedback module. The platform focuses on onboarding, employee profiles, training modules, document management, and the operational HR foundation that most small businesses without an HR department need first. If your team is genuinely ready for 360, you will need a dedicated tool from a vendor that specializes in performance feedback. What FirstHR does provide is the foundation that makes 360 useful when you eventually run it: documented role expectations, structured onboarding that establishes performance baselines, and training infrastructure to support the development plans that 360 surfaces.
What Comes Before 360
The most useful framing for owners considering 360 is: this is a tool for organizations that already have working management infrastructure, applied to teams where individual development is the binding constraint on performance. If your binding constraint is something else (unclear roles, weak onboarding, missing 1-on-1s, no documented expectations), 360 will not fix it; it will surface the underlying problem at higher volume.
The foundation that needs to be in place before 360 is worth running:
| Foundation element | Why it matters for 360 | How to build it |
|---|---|---|
| Documented roles and expectations | Without clear role definitions, raters use different mental models for the same job, and ratings become noise | Write a one-page role description for every position; review and update annually |
| Reliable weekly 1-on-1s | If you cannot run 1-on-1s, you cannot run the post-feedback coaching that makes 360 work | Establish 30-minute weekly meetings with every direct report; never cancel |
| Structured onboarding | Performance baselines are set in onboarding; without them, 360 has no anchor | Use a documented onboarding plan for every new hire; ensure first-90-day expectations are clear |
| Separation of development and evaluation | If your culture mixes the two, 360 will be read as evaluation regardless of stated purpose | Run performance reviews and developmental feedback on separate cycles, with separate documentation |
| Trust that anonymous feedback will not lead to retaliation | Without trust, anonymity is theoretical and ratings become politically calibrated | Demonstrate over multiple cycles of upward feedback that critical input does not lead to consequences |
| Time and budget for post-feedback coaching | Reports without coaching produce more harm than good | Block 90 minutes per recipient on the calendar before launching the cycle |
For most small businesses, the foundation work above takes 12-18 months to build properly. That timeline is not a flaw in the recommendation; it is what the underlying work actually requires. Owners who try to compress it usually run a 360 cycle on top of weak foundations, get poor results, and conclude that 360 does not work, when the actual issue is that they tried 360 too early.
For the operational foundation that supports all of this, the employee onboarding checklist covers the starting point, and the performance management guide covers how 360 fits within the larger system. Gallup data on the manager-employee relationship reinforces why the underlying management practices, not the survey instrument, drive engagement outcomes.
The Long-Term View on 360 Feedback
The most useful framing I can offer about 360 feedback at small business scale is this: it is a tool for a specific stage of organizational maturity, not a universal management practice. Companies that run it well have usually built up to it over years, with the underlying management infrastructure in place before the formal program launches. Companies that run it poorly almost always tried to install it before the foundation was ready.
For most owners reading this guide, the right path is not "should I run 360" but "what should I be doing in the 12-24 months before I am ready for 360." That work is unglamorous: weekly 1-on-1s, documented expectations, structured onboarding, separation of development from evaluation, and the slow cultural work of building the trust that makes anonymous feedback meaningful. None of it produces a printed report. All of it compounds.
When you eventually do run 360, the difference between a good cycle and a bad cycle will not be the software you chose or the questions you asked. It will be whether the foundation underneath was already strong enough to support the surfacing of honest feedback. Strong foundation, mediocre 360 implementation: the cycle creates value. Weak foundation, perfect 360 implementation: the cycle creates damage. The foundation matters more than the survey.
How FirstHR Fits
The honest disclosure repeated: FirstHR does not include a 360 feedback module. We made a deliberate choice not to build performance review or peer review functionality, because the small businesses we serve usually need to fix the foundation before they need the survey instrument. The platform focuses on the underlying work: structured onboarding, documented role expectations, employee profiles that capture what each person is working on, training modules to support development, and document management to keep the administrative work from consuming the time owners should be spending on people.
Pricing is flat: $98/month for up to 10 employees, $198/month for up to 50, regardless of features used. The flat structure exists because per-employee pricing penalizes growth, which is exactly the wrong incentive for a small business trying to build the foundation that supports later practices like 360. The small business HR guide covers the broader operational fit. The onboarding best practices guide covers the foundation under everything in this article. When your team is eventually ready for formal 360 feedback, you will need a dedicated specialist tool. Until then, the work is the foundation.
Frequently Asked Questions
What is 360-degree feedback?
360-degree feedback is a structured process where an employee receives confidential, anonymous feedback on their performance and behavior from multiple sources: their manager, peers, direct reports (if they manage people), and themselves. Some implementations also include external raters such as customers or partners. The result is a written report that compares how the person sees themselves with how others see them, focused on developmental insight rather than evaluation. The format originated in the US Army in the 1940s, was refined at companies like Esso in the 1950s, and became widespread in corporate use during the 1990s.
What is the difference between 360 feedback and a performance review?
A traditional performance review is a one-to-one evaluation conducted by the manager, typically tied to compensation, promotion, or formal performance ratings. 360-degree feedback is a multi-rater process focused on development, not evaluation, and intentionally separated from compensation decisions. Performance reviews answer 'how is this person doing in their role?' from the manager's perspective. 360 feedback answers 'what behaviors should this person work on?' from multiple perspectives. Most organizations that do both keep them in separate cycles to preserve the developmental focus of the 360.
How many people should give 360 feedback?
The standard configuration is 1 manager, 3-5 peers, 3-7 direct reports if applicable, plus self-rating, for a total of 8-13 raters per recipient. Below this range anonymity becomes hard to preserve at small companies. Above this range the volume of feedback becomes harder to act on. For small businesses with teams under 15 people, the math often does not work; you cannot get 3 anonymous peer raters when the recipient knows everyone they work with by name. This is one of the main reasons 360 feedback is structurally hard at small business scale.
Is 360 feedback anonymous?
Anonymity is the foundational requirement for 360 feedback to produce honest data, and it is also the requirement most often broken at small business scale. True anonymity requires at least 3 raters per category (peers, direct reports) so that no single response can be identified, results aggregated rather than shown individually, and a culture where people trust that anonymity will be preserved. At companies under 15 employees, structural anonymity is almost impossible: when the recipient knows there are only 3 people who could have given peer feedback, even aggregated comments often reveal who said what. This is the single biggest reason small businesses should think carefully before running 360.
Should 360 feedback affect compensation or promotions?
No. The single most consistent recommendation across decades of 360 feedback research is to separate developmental feedback from evaluation decisions. When 360 results are tied to pay, promotion, or termination, raters rationally adjust their feedback to either help or hurt the recipient based on their relationship, which destroys the data quality that makes 360 valuable in the first place. Compensation and promotion decisions should use traditional performance reviews, manager judgment, and documented outcomes. 360 feedback should be used only for self-awareness and behavior change. Organizations that violate this rule typically see the program lose value within 2-3 cycles.
How often should you run 360 feedback?
Annually is standard for organizations that have established the practice. Every 18-24 months is more appropriate at smaller companies where the change happens slower and the cost of running each cycle is proportionally higher. Running 360 quarterly or semi-annually is almost always too frequent: people cannot meaningfully change behavior in 90 days, and the survey fatigue dilutes the quality of responses. The right cadence is the longest interval at which people will still remember enough specific behavior to give grounded feedback, which for most teams is roughly once per year.
Does 360 feedback work for remote teams?
It can, with adjustments. The structural requirements are the same (anonymity, sufficient raters, developmental purpose, post-feedback coaching), but remote teams need to compensate for the lack of in-person observation. Practical adjustments: rely more heavily on raters who collaborate directly with the recipient on shared work, fewer raters from adjacent teams who only see them in meetings; use written examples in open-ended questions rather than general impressions; ensure the post-feedback coaching conversation is held over video, not text. Remote teams often produce more thoughtful 360 results than in-person teams because raters take longer to think through their answers, but the threshold of 'do we have enough close collaborators to rate this person' is easier to fail.
Can a small business run 360 feedback without HR?
Yes, but with significant trade-offs. The owner or operator running 360 themselves needs to take on roles that an HR department typically covers: rater selection, anonymity protection, results communication, and post-feedback coaching. The biggest risk is dual-role conflict: you cannot be both the person facilitating someone's 360 and the person making compensation decisions about them; the two roles contaminate each other. The honest answer for most small businesses under 15 people is that lighter-weight alternatives (structured 1-on-1s, manager-led upward feedback, peer recognition rituals) deliver most of the value of 360 with much less risk. Save 360 for when you have the team size, time, and trust to run it well.