Performance Management Best Practices

Most people do not dislike performance management. They dislike performance management done badly: goals set in April and forgotten by June, a rushed review in March that surprises everyone, and a rating that seems to depend more on the manager's mood than on the work.

Done well, performance management is simply the habit of agreeing what good work looks like, talking about progress regularly, and making fair decisions on pay and growth. This guide lays out a practical system you can run in a startup of 20 people or a business of 2,000.

What performance management should achieve

Before choosing forms and rating scales, agree on the purpose. A good system does four things:

• Sets direction: every employee knows what they are expected to deliver and how it connects to company goals.
• Improves performance: regular feedback helps people correct course early instead of learning about problems at year end.
• Supports fair decisions: increments, promotions, and role changes are based on evidence, not memory.
• Develops people: employees leave each cycle with a clearer sense of their strengths and what to work on next.

If a step in your process does not serve one of these, it is probably paperwork.

Step 1: Set clear goals

Everything else depends on goals. Vague goals produce vague reviews.

Cascade, but not too rigidly

Start with three to five company priorities for the year. Each team translates those into team goals, and each person sets three to five individual goals that support their team. Leave room for goals that come from the role itself, such as keeping customer response time low or closing the books on time.

Make goals specific and measurable

Agree on weightage

Not every goal matters equally. Assign a weight to each so the total is 100%. This makes the review conversation clearer and prevents a small win from masking a big miss.

Separate the "what" from the "how"

Goals cover what someone delivers. Competencies or values cover how they deliver it: collaboration, ownership, communication, quality. Most organisations review both, often weighting goals at 60–70% and competencies at 30–40%. Pick a split and apply it consistently.

Step 2: Hold regular check-ins

An annual review cannot carry the weight of a whole year of feedback. Short, regular conversations do most of the work.

• Frequency: a 30-minute one-on-one every two to four weeks works for most teams.
• Agenda: progress on goals, blockers, feedback both ways, and one development topic.
• Notes: record two or three lines after each check-in. These notes become the evidence base for the formal review and remove recency bias.
• Goal updates: if priorities change mid-year, update the goals formally. Reviewing someone against goals that no longer matter is unfair.

Step 3: Give useful feedback

Feedback is the part most managers find hardest. A few habits make it easier:

• Be specific: describe the situation, the behaviour, and the impact. "In Tuesday's client call, you answered the pricing question before checking with finance, and we had to correct the quote later" is useful. "You need to be more careful" is not.
• Be timely: give feedback within days, not months.
• Balance it: recognise good work as specifically as you point out problems. People repeat what gets noticed.
• Make it two-way: ask employees for feedback on how you manage them, and act on it.
• Focus on behaviour, not personality: "the report missed two data sources" rather than "you are careless".

Step 4: Run a fair formal review

Choose a cycle

Annual reviews tied to the April–March financial year are common in India, often with a mid-year review in October. Fast-moving teams may prefer half-yearly or quarterly cycles. Choose what you can actually sustain; a well-run annual cycle with monthly check-ins beats a poorly run quarterly one.

Use a simple rating scale

A five-point scale is common and easy to understand. Define each point in plain words so managers interpret it the same way:

"Meets expectations" should be a respectable rating for solid work, not a disappointment. If most people end up at 4 or 5, your goals were probably too easy or your definitions too loose.

Collect input from more than one person

• Self-review: the employee reflects on achievements, challenges, and goals for the next cycle.
• Manager review: the manager rates against goals and competencies, using check-in notes as evidence.
• Peer input (optional): two or three colleagues who worked closely with the employee answer a few focused questions.

Calibrate before you share

Calibration is a meeting where managers in a department review proposed ratings together. It catches managers who rate everyone high, or everyone low, and makes ratings comparable across teams. Keep it evidence-based: every rating should be backed by examples.

Hold the review conversation

1. Share the written review a day in advance so the employee can read it calmly.
2. Start by asking for their view of the year.
3. Walk through goals and competencies with specific examples.
4. Explain the rating and how it was reached.
5. Spend at least a third of the meeting on the next cycle: goals, development, support needed.
6. Record the employee's comments, including disagreements.

Nothing in the formal review should be a surprise. If it is, the check-ins were not doing their job.

Step 5: Link performance to pay and growth carefully

Employees will connect ratings to increments whether you do or not, so be transparent about how the link works. A simple approach is an increment matrix agreed with finance:

The ranges above are placeholders; set your own based on budget and market data. Some organisations hold the pay conversation a few weeks after the review conversation, so that the review stays focused on development rather than numbers.

Step 6: Handle underperformance properly

When someone is consistently not meeting expectations, act early and follow a clear process:

1. Diagnose: is it skill, clarity, motivation, or something outside work? The fix differs for each.
2. Set a performance improvement plan (PIP): two or three specific, measurable targets, the support you will provide, and a review period, often 30 to 90 days.
3. Check in weekly: record progress and feedback in writing.
4. Close the plan: confirm success, extend once with reasons, or move to the next step under your policy.

A PIP should be a genuine attempt to help someone succeed, not a formality before exit. Document every step, and follow the due process set out in your HR policies and standing orders.

Step 7: Make development part of the cycle

Every review should end with a short development plan: one or two skills to build, how they will be built (a project, a course, mentoring), and when you will check progress. High performers need this as much as anyone; they are often the first to leave when growth stalls.

Reducing bias in reviews

• Recency bias: use check-in notes from the whole cycle, not just the last month.
• Halo or horn effect: rate each goal and competency separately before arriving at an overall rating.
• Similarity bias: ask "what evidence supports this?" for every rating, especially in calibration.
• Visibility bias: remote and hybrid employees can be overlooked; judge outcomes, not time seen in the office.
• Leniency or strictness: calibration across managers is the main fix.

Using a system to run the process

Spreadsheets work for a small team, but they break down as you grow: versions multiply, deadlines slip, and nobody can see who has finished their reviews. A performance tool keeps goals, check-in notes, self-reviews, manager reviews, and ratings in one place, sends reminders, and gives HR a live view of progress. Qrew HR's Performance Management supports goal setting, review cycles, and feedback, and connects to employee records so review history stays with the employee.

Whatever tool you use, the habits matter more than the software. Clear goals, regular conversations, and evidence-based reviews will improve performance even on paper.

Performance management checklist

• Company priorities shared before goal setting starts
• Three to five weighted, measurable goals per employee
• Competencies or values defined with examples
• Check-ins scheduled every two to four weeks, with brief notes
• Rating scale defined in plain words
• Self-review and manager review templates ready
• Calibration meeting planned for each department
• Increment matrix agreed with finance
• PIP process documented
• Development plan included in every review