Performance systems are usually redesigned in response to a complaint: ratings are inconsistent, appraisals are late, or high performers are leaving. The redesign then adds forms, competencies and calibration steps. Completion rates fall further, and the system is blamed again.
The binding constraint is almost always manager time and manager confidence. A performance system should be designed against that constraint first.
Start from the conversation, not the form
The output of a performance system is a manager and an employee agreeing what good work looks like, how it is going and what happens next. Every form should be judged only by whether it makes that conversation easier and more honest.
Design rules that hold up in practice
- No more than five to seven objectives per person, written so success is observable.
- Objectives set once, reviewed quarterly in a short structured check-in.
- One rating scale used across the organization, with written definitions and examples.
- Separate the development conversation from the reward conversation.
- A documented route for disagreement that does not require going through HR first.
- Manager guidance that fits on two pages, including sample wording.
If a manager cannot complete the cycle honestly in the time available, they will complete it dishonestly.
Handle the hard cases explicitly
Most performance systems fail at the edges: the employee whose objectives changed mid-year, the strong performer in a failing team, the person who meets targets but damages colleagues, and the underperformer whose manager has never documented anything. Each of these needs a stated position before the cycle opens, otherwise managers avoid the case entirely.
Measure the system, not just the people
- 01Completion on time, by department, visible to the leadership team.
- 02Distribution of ratings compared with business results.
- 03Proportion of employees who can state their objectives without checking.
- 04Number of documented underperformance cases that were addressed rather than carried.
- 05Manager confidence, sampled directly rather than inferred.
A performance system earns its place when managers use it to make decisions they were previously avoiding. That is the test, not the elegance of the framework.
Key takeaways
- Design against manager time and confidence, not around an ideal process.
- Five to seven observable objectives, reviewed quarterly, beats an annual essay.
- Separate development from reward conversations.
- State a position on the hard cases before the cycle opens.