Build fluency in the vocabulary of structured, multi-source performance review processes.
0 / 5 completed
1 / 5
At standup, a dev mentions a structured cycle where each employee's manager, peers, and the employee themself all submit written feedback before a formal review conversation. What is this process called?
A 360-degree performance review cycle gathers structured written feedback from multiple perspectives, like a manager, peers, and the employee's own self-assessment, before a formal review conversation happens, giving a more rounded picture than relying on a single manager's viewpoint alone. This multi-source approach helps surface both blind spots and consistent strengths that one person's perspective might miss or overstate. It's a common structured alternative to a purely top-down, manager-only review process.
2 / 5
During a design review, the team wants each employee's individual goals to be visibly linked to the broader company or team objectives they support. Which concept supports this?
Goal alignment, often implemented through a framework like cascading OKRs, explicitly connects an individual's specific goals to the broader team or company objectives they contribute to, making that connection visible rather than leaving individual goals feeling disconnected from larger strategy. This visibility helps an employee understand how their specific work contributes to something bigger. It's a structural feature many performance and goal-tracking platforms are built around supporting.
3 / 5
In a code review, a dev notices the platform tracks a running log of specific praise and feedback moments throughout the quarter, not just feedback collected right before the formal review. What does this represent?
Continuous, ongoing feedback tracking captures specific moments of praise or constructive feedback as they happen throughout a review period, rather than expecting a manager to accurately recall an entire quarter's worth of performance from memory right before the formal review. This ongoing record produces a more accurate and complete picture at review time. It addresses a well-known weakness of relying purely on end-of-period recall, which tends to overweight recent events.
4 / 5
An incident report shows a manager's end-of-cycle review scored an employee's performance almost entirely based on the last few weeks, ignoring strong work earlier in the period. What practice would address this?
Relying on continuous feedback logs collected throughout the review period, rather than a manager's unaided memory at the end of the cycle, directly counters the well-documented tendency for recent events to disproportionately dominate a review, known as recency bias. Assuming this bias doesn't meaningfully affect outcomes ignores a known and well-studied weakness in purely memory-based evaluation. Building ongoing feedback capture into the process is a structural fix rather than relying on a manager's individual discipline to avoid the bias unaided.
5 / 5
During a PR review, a teammate asks why the team uses a structured 360-degree review process instead of relying solely on each employee's direct manager for performance evaluation. What is the reasoning?
Relying solely on a single manager's viewpoint means the evaluation reflects only one person's visibility into the employee's work, which may miss contributions or patterns that peers or the employee's own perspective would surface. A 360-degree process combines multiple viewpoints into a more balanced, complete picture. The tradeoff is the added time and coordination effort of collecting and synthesizing feedback from several different sources instead of just one.