The Annual Review Problem
Every year, the same ritual plays out in companies across India. In March, HR sends a reminder: "Annual appraisal forms are due by the 31st." Managers scramble to fill out forms for 8–15 direct reports, trying to recall what each person did over the past 12 months. Employees fill out self-assessments that are either overly modest or wildly optimistic. The forms are submitted, reviewed by HR, and filed away.
Two weeks later, employees receive their ratings and increment letters. Half of them are disappointed. A few are angry. Some start updating their LinkedIn profiles.
The annual review has failed at its core purpose: improving performance. Research consistently shows that annual reviews have minimal impact on employee behaviour, create significant anxiety, and often damage the manager-employee relationship. Yet most Indian companies continue to run them because "that's how it's done."
The problem isn't the review itself - it's the system design. Annual reviews fail because they violate basic principles of effective feedback: feedback must be timely, specific, and actionable. A review of work done 8 months ago is none of these things.
The Engineering Principles of Effective Performance Management
Before designing a new system, it helps to understand what the research says about what actually changes performance:
Principle 1: Feedback must be proximate to the behaviour
Feedback given within 24–48 hours of a behaviour is 3–5x more effective than feedback given weeks or months later. The brain's ability to connect feedback to specific actions degrades rapidly with time.
Principle 2: Goals must be visible and current
Employees perform better when they can see their goals, track their progress, and understand how their work connects to team and company objectives. Goals set in April and reviewed in March are not visible or current.
Principle 3: Calibration prevents bias
Without calibration, different managers apply different standards. One manager's "meets expectations" is another's "exceeds expectations." This creates pay inequity and erodes trust in the system.
Principle 4: Separation of development and compensation conversations
When performance reviews are directly tied to compensation decisions, employees become defensive rather than open to feedback. The conversation shifts from "how can I improve" to "how can I justify a higher rating."
Designing the New System: Four Components
Component 1: Continuous Goal Management (OKRs)
Replace annual goal-setting with quarterly OKRs (Objectives and Key Results). OKRs have three properties that make them effective:
Objectives are qualitative and inspiring: "Build a customer support function that makes customers feel genuinely helped" rather than "Achieve 85% CSAT score."
Key Results are quantitative and measurable: "Reduce average response time to under 2 hours," "Achieve CSAT score of 85%+," "Resolve 90% of tickets without escalation."
OKRs are public: Every employee can see every other employee's OKRs. This creates alignment (everyone can see how their work connects to company objectives) and accountability (it's harder to miss a goal that everyone can see).
The quarterly cadence: OKRs are set at the beginning of each quarter and reviewed at the end. This means goals are never more than 3 months old. When priorities change (and they always do), OKRs can be updated at the next quarter boundary.
Implementation in a software system:
- •OKR hierarchy: Company OKRs → Department OKRs → Team OKRs → Individual OKRs
- •Each OKR has an owner, a due date, and a current progress score (0–1.0)
- •Progress is updated weekly by the owner (takes 5 minutes)
- •The system automatically calculates alignment - what percentage of individual OKRs roll up to team OKRs, which roll up to company OKRs
- •Dashboard shows company-wide OKR health at a glance
Component 2: Continuous Feedback (Check-ins and Kudos)
Replace the annual review with two types of continuous feedback:
Weekly check-ins: A structured 15-minute conversation between manager and direct report, every week. The agenda is always the same:
- 1What did you accomplish this week? (5 minutes)
- 2What are you working on next week? (5 minutes)
- 3What blockers do you have? (5 minutes)
The check-in is documented in the system. Over time, this creates a rich record of each employee's work, challenges, and growth - the raw material for meaningful performance conversations.
Peer recognition (Kudos): A lightweight mechanism for employees to recognise each other's contributions. "Kudos to Priya for staying late to help the customer support team during the system outage." Kudos are public, visible to the whole team, and create a culture of recognition.
360-degree feedback (quarterly): Once per quarter, each employee receives structured feedback from 3–5 peers and their manager. The feedback is structured around specific competencies (communication, problem-solving, collaboration, etc.) and uses a simple scale (needs development, meets expectations, exceeds expectations) with mandatory written comments.
The system design for continuous feedback:
- •Check-in notes are stored against the employee record and visible to the manager and employee
- •Kudos are displayed in a company-wide feed
- •360 feedback requests are sent automatically at the start of each quarter
- •Feedback is anonymous (except manager feedback) to encourage honesty
- •Feedback is aggregated and presented as trends over time, not just point-in-time snapshots
Component 3: Calibration Sessions
Calibration is the process by which managers align their ratings before communicating them to employees. Without calibration, the same performance level gets different ratings from different managers.
The calibration process:
- 1Pre-calibration: Each manager rates their direct reports on a 5-point scale (1=significantly below expectations, 2=below expectations, 3=meets expectations, 4=exceeds expectations, 5=significantly exceeds expectations). Ratings are submitted to HR before the calibration session.
- 1Calibration session: All managers in a department meet (typically 2 hours). HR facilitates. Each manager presents their ratings and the evidence supporting them. Other managers can challenge ratings. The goal is to ensure that a "4" from Manager A means the same thing as a "4" from Manager B.
- 1Distribution check: The calibration session also checks the rating distribution. If one manager has rated 80% of their team as "4" or "5," that's a signal of grade inflation. The expected distribution (for a healthy team) is roughly: 5% at 5, 20% at 4, 60% at 3, 15% at 2, 5% at 1.
- 1Post-calibration: Final ratings are locked after calibration. Managers communicate ratings to employees.
The system design for calibration:
- •Pre-calibration ratings are submitted in the system and visible only to HR until the calibration session
- •The system shows the rating distribution for each manager and department
- •Calibration session notes are recorded in the system
- •Final ratings are locked by HR after calibration is complete
Component 4: Separating Development from Compensation
The most important structural change is separating the development conversation from the compensation conversation.
Development conversation (quarterly): Focused entirely on growth. What are the employee's career goals? What skills do they need to develop? What projects would stretch them? What support do they need from their manager? This conversation is not about ratings or money - it's about the employee's future.
Compensation conversation (annual): Based on the calibrated annual rating, market data, and budget. The manager communicates the increment and explains the rationale. This conversation is brief and factual - the rating has already been communicated, so there are no surprises.
When these conversations are separated, the development conversation becomes genuinely developmental. Employees are more open to honest feedback when they know it won't directly affect their paycheck.
The Data Model for Performance Management
A performance management system needs to store:
Goals/OKRs: Objective text, key results with targets and current values, owner, quarter, parent OKR (for alignment), status.
Check-in records: Date, employee, manager, accomplishments, next week plans, blockers, any action items.
Feedback records: Giver, receiver, type (peer/manager/self), competency, rating, written comment, quarter, visibility (public/private).
Performance ratings: Employee, rating period, pre-calibration rating, post-calibration rating, manager, calibration notes.
Development plans: Employee, goal, actions, timeline, status, manager notes.
Measuring Whether the System Is Working
Track these metrics quarterly:
- •OKR completion rate: What percentage of OKRs are completed at the target score? Target: 60–70% (OKRs should be ambitious enough that 100% completion indicates they were too easy).
- •Check-in completion rate: What percentage of scheduled check-ins actually happen? Target: 85%+.
- •Feedback participation rate: What percentage of employees give and receive 360 feedback? Target: 90%+.
- •Rating distribution: Is the distribution healthy, or is there grade inflation/deflation?
- •Attrition by rating: Are high performers (4s and 5s) staying? If high performers are leaving at higher rates than average performers, the system isn't retaining the right people.
- •Employee satisfaction with performance process: Annual survey question. Target: 70%+ satisfied.
The Change Management Challenge
The biggest obstacle to implementing a new performance management system is not technology - it's behaviour change. Managers who have been doing annual reviews for 10 years need to learn a new way of working. Employees who are used to once-a-year feedback need to adapt to continuous feedback.
Manager training: Invest in training managers on how to give effective feedback, how to run check-ins, and how to have development conversations. This is the highest-leverage investment in the system.
Pilot before rollout: Pilot the new system with one department for one quarter before rolling out company-wide. Use the pilot to identify problems and refine the process.
Communicate the why: Employees and managers need to understand why the system is changing. "We're moving to continuous feedback because annual reviews don't actually help people grow" is a compelling reason. "HR decided to change the system" is not.