Running Fair Reviews for a Remote or Hybrid Team

Proximity bias is one of the quieter ways a review cycle drifts unfair. The person who sits near you, who you happen to talk to most, ends up rated a little more generously than the person you barely see, and it rarely feels like bias from the inside. It just feels like knowing someone's work better.

The principles

These aren't steps to complete in order - they're the things worth checking yourself against, before and during the work. Read them once, then keep this page open while you go.

1. Check whether proximity is quietly deciding your ratings

   This bias is worth actively checking for, because it almost never announces itself.

   • Before finalizing ratings, check whether they correlate with how often you interact with each person, rather than with their actual output.
   • Ask yourself who you could list five concrete wins for without checking anything, and who you couldn't - that gap is often about your own visibility, not their performance.
   • Pay particular attention to anyone in a different timezone or office than you.

2. Build a record that doesn't depend on hallway visibility

   Remote work removes the accidental visibility an office provides. The record has to be built deliberately instead.

   • Keep written notes per direct report from 1:1s and project updates, not just general impressions.
   • Ask for written updates from remote reports at a similar or greater frequency than you'd get informally from someone in the office.
   • If a report keeps their own running log, use it directly rather than reconstructing your own version from memory.

3. Apply the same bar to a quiet Slack message as a loud meeting

   A confident contribution in a live meeting is not inherently more valuable than the same idea delivered quietly in writing. Don't let format determine how much credit something gets.

   • When assessing contribution, look at written channels with the same attention as meetings.
   • Don't let someone's comfort speaking up live become a proxy for the quality of their thinking.
   • Actively ask quieter or remote-first contributors what they'd want highlighted, since you may be missing it otherwise.

4. Watch for timezone doing someone's advocacy for them

   Someone in a very different timezone may simply not be in the room for the conversations where credit gets handed out informally.

   • Check whether key decisions or credit-giving moments happen at times a remote report can't attend.
   • Where possible, make sure async updates carry equal weight to live ones in how you form your own view.
   • Ask directly whether a remote report feels their work is visible to the wider team, not just to you.

5. Get a second opinion from someone who works with them directly

   Someone closer to the day-to-day work than you are can catch a gap in your own picture, especially for anyone you see less often.

   • Ask a peer or a close collaborator of the report for their honest read before finalizing a rating you're unsure about.
   • Specifically ask if anything about the rating surprises them, in either direction.
   • Treat a mismatch between your view and theirs as a signal to look closer, not to dismiss.

6. Make remote and in-office feedback equally specific

   It's easy to give an in-office report specific feedback because you've seen the work directly, and give a remote report something vaguer because you haven't. The fix is deliberate effort, not instinct.

   • Hold every piece of written feedback to the same standard for specificity, regardless of how well you know the person day to day.
   • If feedback for a remote report reads vaguer than feedback for someone in the office, that's worth going back and fixing before the review, not after.
   • Use the evidence you gathered in writing throughout the cycle to close this gap directly.

That's the whole playbook

None of this replaces judgement. It is the checklist for catching the moments where judgement quietly turns into habit, or into bias.