Book a Conversation

Rubric design

Four biases that shape promotion decisions

A rubric doesn't eliminate bias by existing. It reduces bias only if it's built to address specific, well-documented patterns. Here's what those patterns look like and how rubric design responds to each one.

Recency bias

A strong quarter right before a promotion cycle carries more weight than a full year of consistent work, simply because it's easier for a manager to remember.

Rubric response: Evidence logs collected quarterly instead of gathered from memory right before the review, so the full period is represented.

Similarity bias

Managers tend to rate employees who share their communication style, background, or working hours more favorably, often without noticing they're doing it.

Rubric response: Criteria tied to work output and decisions made, not to communication style or personal rapport with the manager.

Visibility bias

Employees who present in meetings, message frequently in shared channels, or work closely with leadership get noticed more than those doing equally significant work quietly.

Rubric response: A requirement that evidence come from multiple sources, including peers and cross-functional partners, not only the direct manager's impression.

Halo effect

Strong performance in one area, such as technical skill, gets generalized into an assumption of overall readiness, including in areas like leadership or judgment that weren't actually assessed.

Rubric response: Separate scoring categories that must each be evaluated individually, preventing one strength from covering for an untested gap.

Self-check

Questions worth asking before a promotion cycle

This is a starting checklist, not a complete audit. Click each item to see why it matters.

Can two different managers score the same employee and land within one point of each other?

If scores vary widely between reviewers, the criteria are probably too subjective or too loosely defined to apply consistently across teams.

Is evidence collected from more than one source per employee?

Relying only on a direct manager's impression recreates the visibility problem the rubric was meant to solve.

Does the rubric separate technical skill from leadership and judgment?

Combining categories makes it easy for strength in one area to mask a real gap in another.

Is there a documented reason on file for every promotion decision, including declines?

Without a written rationale, it's difficult to review decisions later or explain them if an employee asks why they weren't promoted.

Do managers calibrate scores together before decisions are finalized?

A short calibration meeting catches inconsistency between departments before it becomes an employee-facing problem.

Want a rubric reviewed against these patterns?

We can review an existing rubric or draft against these four bias categories as part of a scoped engagement.

Discuss Your Rubric