
Quick answer: performance appraisal methods are structured ways to evaluate how well employees do their jobs. The main ones are rating scales, management by objectives (MBO), OKRs, 360-degree feedback, BARS, checklists, critical incidents, ranking, forced distribution and self-assessment. Most companies combine a goal-based method for results with a behaviour-based method for how the work was done.
Below, each method is explained with an example, its strengths and weaknesses, and when it suits a team.
Traditional and modern methods
Traditional methods (ranking, rating scales, checklists) focus on past performance and are quick to run. Modern methods (MBO, OKRs, 360-degree feedback, BARS) focus on goals, behaviours and development. Neither group is wrong; the point is to pick methods that match what you need to decide: pay, promotion, development or all three.
HR, GPS attendance, shifts, leave, payroll, tax declarations, onboarding, engagement, projects and timesheets — one employee record behind all of it.
Start free See the demo1. Graphic rating scale
Managers rate employees on traits or competencies such as quality of work, communication and teamwork, usually from 1 to 5.
Example: "Customer focus: 4 – consistently resolves issues on the first call."
- Pros: simple, fast, easy to compare
- Cons: subjective; ratings drift upwards without clear definitions
- Best for: large teams needing a consistent baseline
2. Management by objectives (MBO)
Manager and employee agree measurable objectives at the start of the period and review achievement at the end.
Example: "Reduce average invoice collection time from 45 to 30 days by March."
- Pros: clear, results-focused, motivating when goals are fair
- Cons: can ignore how results were achieved; goals may be set too low
- Best for: sales, operations and roles with measurable output
3. OKRs (objectives and key results)
A qualitative objective with three to five measurable key results, reviewed quarterly. OKRs are often deliberately ambitious, and 70% achievement can be a good outcome.
Example: Objective "Make onboarding delightful"; key results "90% of new hires complete setup on day one", "new-hire survey score above 8".
- Pros: aligns teams to company priorities, encourages ambition
- Cons: tying OKRs directly to pay can make people set safe targets
- Best for: fast-growing teams; best combined with a separate review for pay
4. 360-degree feedback
Feedback is gathered from the manager, peers, direct reports and sometimes customers, plus a self-assessment.
Example questions: "How well does this person share information with the team?" "What should they start, stop and continue doing?"
- Pros: rounded view, highlights leadership and collaboration issues a manager may not see
- Cons: time-consuming; feedback can be political without anonymity and training
- Best for: managers, leaders and customer-facing roles; development more than pay
5. Behaviourally anchored rating scale (BARS)
Each rating level is defined by specific behaviour examples, which makes ratings more objective.
| Rating | Behaviour for "handles customer complaints" |
|---|---|
| 5 | Resolves complex complaints, follows up and prevents repeats |
| 3 | Resolves routine complaints politely within the target time |
| 1 | Escalates simple complaints or leaves them unresolved |
- Pros: consistent, legally defensible, clear expectations
- Cons: takes effort to design for each role
- Best for: customer support, sales, frontline and technical roles
6. Checklist method
Managers tick yes or no against statements such as "meets deadlines" or "follows safety procedures". Weighted checklists give some statements more importance.
- Pros: very quick, easy for new managers
- Cons: little nuance or development feedback
- Best for: compliance-heavy or standardised roles
7. Critical incident method
Managers record specific examples of very good or poor performance during the year.
Example: "Handled the server outage on 12 August, informed clients within 15 minutes and restored service in two hours."
- Pros: evidence-based, reduces recency bias
- Cons: requires managers to keep notes consistently
- Best for: supporting any other method with real examples
8. Ranking method
Employees are ranked from best to worst, or compared in pairs.
- Pros: simple for small teams
- Cons: says nothing about how far apart people are; demotivating for those at the bottom
- Best for: rarely recommended except for small, similar roles
9. Forced distribution
A fixed share of employees must fall into each band, for example 10% top, 70% middle, 20% bottom.
- Pros: prevents everyone being rated "excellent"
- Cons: harms collaboration and can push out solid performers in strong teams
- Best for: very large organisations, with caution
10. Self-assessment
Employees evaluate their own performance before the manager review.
- Pros: encourages reflection, surfaces achievements managers missed
- Cons: some over-rate, others under-rate themselves
- Best for: every team, as an input to the manager's review
Comparison at a glance
| Method | Focus | Effort | Objectivity | Good for pay decisions |
|---|---|---|---|---|
| Rating scale | Traits | Low | Low–medium | With clear definitions |
| MBO | Results | Medium | High | Yes |
| OKRs | Goals | Medium | Medium | Better kept separate |
| 360-degree | Behaviours | High | Medium | Development mainly |
| BARS | Behaviours | High (setup) | High | Yes |
| Checklist | Standards | Low | Medium | Limited |
| Critical incident | Evidence | Medium | High | As support |
| Ranking | Relative | Low | Low | Not recommended |
| Forced distribution | Relative | Low | Low | Use with caution |
| Self-assessment | Reflection | Low | Low | As input |
How to choose a method
- Decide the purpose. Pay and promotion need defensible, results-based methods. Development needs rich feedback.
- Match the role. Sales suits MBO; customer service suits BARS; leaders benefit from 360-degree feedback.
- Keep it light enough to finish. A simple process done well beats a complex one abandoned halfway.
- Train managers on giving specific, fair feedback and avoiding bias.
- Review regularly. Quarterly check-ins make the annual review a summary, not a surprise.
Avoiding common biases
- Recency bias: judging on the last month, not the year. Use critical incident notes and quarterly check-ins.
- Halo effect: one strength colours every rating. Rate competencies separately.
- Central tendency: rating everyone average. Use behaviour anchors.
- Similarity bias: favouring people like the reviewer. Calibrate ratings across managers.
A simple process for a growing company
- Set three to five goals per person at the start of the year
- Hold short quarterly check-ins
- Collect a self-assessment and manager review at year-end, with peer feedback for managers
- Calibrate ratings across teams
- Link final ratings to increments using a published matrix
- Share outcomes in a one-to-one conversation with next year's goals
MizUp BMS supports goals, review cycles and appraisals alongside recognition and HR records, so reviews draw on the whole year's context. Pair performance reviews with a good employee recognition program, and read about HRM functions and roles to see where performance management fits.
Frequently asked questions
What are the most common performance appraisal methods?
Graphic rating scales, management by objectives (MBO), OKRs, 360-degree feedback, behaviourally anchored rating scales (BARS), checklists, critical incidents, ranking and forced distribution, and self-assessment.
What is 360-degree feedback?
A review that collects feedback from a person's manager, peers, direct reports and sometimes customers, alongside a self-assessment, to give a rounded view of behaviour and impact.
Which appraisal method is best?
There is no single best method. Many companies combine goal-based reviews (MBO or OKRs) for results with rating scales or 360-degree feedback for behaviours.
How often should appraisals happen?
An annual review for pay decisions, supported by quarterly or monthly check-ins, works well for most teams.
What is forced distribution?
A method where a fixed percentage of employees must fall into each rating band. It prevents rating inflation but can damage collaboration, so many companies have moved away from it.
