How to Run Your First 360 Review Cycle (Step by Step)

A 360 review cycle collects structured input about each team member from multiple perspectives — peers, direct reports, managers, and sometimes external collaborators. The “360” means feedback comes from all directions, not just top-down.

Most teams assume 360 feedback requires an HR department, expensive software, and months of planning. It doesn’t. A team of five can run a meaningful review cycle in a week.

Before You Start

Three decisions determine whether your first review cycle produces insight or noise:

Who gets reviewed? Start with everyone. When only selected people receive feedback, it signals that something is wrong with those individuals. Universal participation normalizes the process.

Who reviews whom? Every subject needs at least three reviewers for anonymity. In small teams, this often means everyone reviews everyone — which is fine for teams under ten. For larger teams, have each subject nominate 3-8 peers who know their work best.

What questions do you ask? Specific behavioral questions get useful answers. Generic questions (“Rate their teamwork from 1-5”) get generic answers. A strong default set combines ratings for measurable dimensions with open-ended questions that invite specific examples.

The Right Questions

Bad question: “How is their communication?”

Good question: “Describe a situation where this person’s communication positively impacted the team’s work.”

The difference is specificity. The first invites a number. The second invites a story. Stories contain the behavioral detail that makes feedback actionable.

A solid starting set for your first review cycle:

1. What does this person do particularly well? Give a specific example.
2. Describe a situation where this person positively impacted the team.
3. What could this person do differently to be more effective?
4. How would you rate their communication with the team? (1-5)
5. How would you describe their collaboration? (1-5)
6. Any other feedback you’d like to share?

Six questions take about five minutes to answer — short enough that reviewers complete them thoughtfully instead of rushing through twenty questions to get it over with.

Running the Review Cycle

Set a clear timeline. One week is enough for most teams. Shorter windows create urgency without dragging. Longer windows invite procrastination.

Send reminders. People forget. An automated reminder at the halfway point and 24 hours before the deadline keeps response rates high without manual nagging. Aim for above 90% — below that, you’re missing perspectives that matter.

Make it genuinely anonymous. This is the single most important factor in feedback quality. If reviewers suspect their responses can be identified, they’ll soften everything into useless platitudes. Individual responses should never be displayed — only AI-synthesized themes and insights, revealed after a minimum number of people have responded. That structural guarantee makes honesty safe.

Allow skip and decline. Some reviewers haven’t worked closely enough with a subject to provide useful input. “Haven’t worked closely” (skip) is better than fabricated feedback. “Conflict of interest” (decline) protects integrity. Neither counts toward the anonymity threshold.

After the Review Cycle Closes

Raw feedback is valuable but overwhelming. A review cycle with eight subjects and six questions each generates thousands of words. Three things make results useful:

Synthesis. Identify recurring themes across respondents. When four out of six people mention strong mentorship, that’s a pattern. When one person mentions debugging skills, that’s an observation. The distinction matters.

Self-review comparison. If subjects also reviewed themselves, compare self-ratings against peer ratings. Gaps between self-perception and team perception are the most powerful development signals — they reveal blind spots that no single piece of feedback can surface.

Action planning. Every growth area identified in synthesis should connect to a specific development goal. “Improve delegation” is a theme. “Hand off two tasks per sprint to junior developers” is a goal. Goals with deadlines and tracking mechanisms turn feedback into behavior change.

Common Mistakes in Your First Review Cycle

Starting with too many questions. Twelve questions per subject feels thorough. It feels exhausting to reviewers. Start with six. You can add complexity in future review cycles.

Reviewing only managers. This signals that feedback is for accountability, not development. Review everyone or review no one.

Skipping the action step. If feedback doesn’t lead to visible change, your team will treat the next review cycle as bureaucratic overhead. Show that synthesis leads to goals, goals lead to progress, and progress gets recognized.

Waiting too long to run the second review cycle. The value of 360 feedback compounds. One review cycle is a snapshot. Two reveal trajectory. Run your second review cycle within 90 days of the first.

The Minimum Viable Review Cycle

If everything above feels like too much for a first attempt, here’s the absolute minimum:

• 3+ people reviewing each subject
• 3 questions (strength, improvement area, collaboration rating)
• 5-day window
• Anonymous with threshold guarantee
• One development goal per person from results

That’s enough to demonstrate value. Expand from there.