Key things to know before setting performance objectives
- Good objectives focus on outcomes, not just activity or effort.
- In UK performance management, objectives should be fair, realistic, and aligned with the employee’s normal workload.
- Simple work usually suits SMART targets, while complex work often needs learning, behaviour, or quality-based objectives.
- Each objective should have a baseline, a target, and a clear deadline.
- Progress works best when it is reviewed regularly, not left until the annual appraisal.
- One strong objective is better than three vague ones that nobody can track properly.
What makes a performance objective worth using
When I review objectives, I look for one simple test: could a manager and employee both tell, without guesswork, whether it has been achieved? If the answer is no, the objective is still too vague. A useful objective describes the outcome, the measure, and the time frame, instead of hiding behind words like “improve” or “work harder”.
In practice, that usually means four ingredients. The objective should be specific, so the employee knows what success looks like. It should be measurable, so progress can be checked. It should be achievable, so it stretches people without turning into theatre. And it should be relevant to the role, because a good objective has to sit inside the employee’s actual job, not outside it. Acas recommends that objectives are fair and workload-aware, while CIPD notes that complex roles often work better with learning outcomes or behaviour-based goals rather than rigid targets.
That distinction matters more than many managers realise. A call centre adviser can often be measured by response time, resolution rate, or customer satisfaction. A project lead, analyst, or people manager may need a different kind of target, because the real value lies in judgement, influence, or decision quality. Once you see that difference, the examples become much easier to write, which is where I’d take the conversation next.
Performance objectives that work in real roles
The examples below are not meant to be copied word for word. They are models that show how a strong objective combines outcome, measure, and deadline. I would treat the baseline as the starting point and adjust the target to fit the team’s actual numbers.
| Role or situation | Example objective | Why it works |
|---|---|---|
| Customer service | Reduce average first response time from 24 hours to under 8 hours for 90% of tickets by the end of Q3, while keeping customer satisfaction at 4.5/5 or above. | It balances speed and quality, so the employee is not rewarded for rushing replies. |
| Sales | Build a qualified pipeline worth £150,000 by the end of the quarter by completing 20 discovery calls per week and reviewing stalled leads every Friday. | It is outcome-led, but it still shows the actions that support the target. |
| Operations | Cut invoice processing errors to below 1% and complete 95% of invoices within two working days by month-end. | It measures both accuracy and speed, which is usually what operations teams need. |
| People manager | Hold monthly one-to-ones with every direct report, document agreed actions within 48 hours, and review each person’s development plan once a quarter. | It turns management into a visible habit instead of an informal intention. |
| Project delivery | Launch the new onboarding process by 30 September, complete user testing with at least 10 employees, and keep high-priority defects below five during rollout. | It focuses on delivery quality, not just the date on the calendar. |
| Development objective | Complete two shadowing sessions per month and handle standard customer queries independently by the end of 12 weeks. | It is useful for newer employees or people moving into a broader role. |
| Team objective | Achieve 100% on-time submission of the monthly report for the next six months and reduce rework by 20%. | It works when results depend on shared effort rather than one person alone. |
Two things stand out in the stronger versions. First, they avoid vague language. Second, they make trade-offs visible. A target for speed that ignores quality is usually a bad objective, and the same is true of a target for output that says nothing about accuracy, customer impact, or collaboration. If a manager can only describe success in general terms, the objective is not ready yet.
How to write them so they are measurable, fair, and achievable
I usually recommend a simple writing pattern: start with the outcome, then add the measure, then finish with the deadline and the support that will make it realistic. That structure keeps the objective grounded in performance management rather than drifting into wishful thinking.
- Start with the business result. Ask what the role is meant to change, improve, or protect.
- Choose one primary measure. If there are three metrics competing for attention, the objective is probably too crowded.
- Set a baseline and a target. “Improve response times” is weaker than “reduce average response time from 24 hours to 8 hours”.
- Add a deadline that fits the work. A good target is firm enough to drive action, but not so short that it becomes unrealistic.
- Agree the support needed. Training, templates, coaching, or better tools can be part of the objective if they are necessary to make it fair.
A practical template I use is this: By [date], improve [metric] from [baseline] to [target] by [action or behaviour]. It is simple, but it forces clarity. It also stops managers from writing objectives that sound impressive yet collapse the moment someone asks how progress will be checked.
If the work is complex, I would shift the wording slightly. Instead of forcing a hard number onto every role, I would use a learning or behaviour outcome, such as making better decisions, improving stakeholder communication, or handling escalations more consistently. That is not a softer option; in many jobs, it is the more accurate one.
Where objectives usually go wrong
Most weak objectives fail for predictable reasons, and the patterns are easy to spot once you know what to look for. The problem is usually not that the employee lacks ability. It is that the objective was written badly in the first place.
- They measure activity instead of outcome. “Make more calls” is weaker than “book 12 qualified meetings per month”.
- They are too many. Five half-finished objectives create noise. Three well-chosen ones create focus.
- They are too vague. Words like “improve”, “support”, and “be proactive” need a measurable finish line.
- They ignore workload. A fair objective reflects what the employee can realistically do alongside their existing responsibilities.
- They do not allow for quality. Faster is not better if errors rise or customer trust falls.
- They are written without follow-up. If there are no check-ins, the objective becomes a paperwork exercise rather than a management tool.
There is another mistake I see often in performance reviews: managers use the same style of objective for every job. That rarely works. A finance analyst, a warehouse supervisor, a designer, and a line manager do not need the same kind of target. The wording should fit the work, not the other way around. That is where UK performance management practice becomes especially useful, because it asks for fairness as well as clarity.
How this fits UK performance management in practice
In the UK, performance objectives are not just a planning tool. They also shape how feedback, appraisals, and improvement conversations are handled. A good objective gives people a clear standard, but it should also be fair enough to stand up in a real workplace conversation.
That is why written records matter. I would always document the objective, the baseline, the support offered, and the review date. If the objective is part of a performance improvement plan, it needs an even clearer timeline and a more explicit description of what happens next. Acas is quite direct on this point: objective-setting should be fair, and if performance is slipping, employers should try to help the employee improve before escalating matters. If an employee needs reasonable adjustments, those should be considered as part of the plan, not treated as an afterthought.
For team-based work, I would also be careful not to overuse individual targets. When results are shared, a team objective is often cleaner and more honest. In my view, that is one of the simplest ways to avoid resentment, because it recognises how work actually gets done. The strongest performance systems do not try to force every outcome into a personal KPI; they choose the right level, individual or team, for the task at hand.
A simple starter set for the next review
If I had to build a practical objective set from scratch, I would start with three types. One objective should focus on output, one on quality, and one on development or behaviour. That combination covers most roles without overcomplicating the review.
- Output objective: Deliver the agreed monthly report by the fifth working day each month for the next six months.
- Quality objective: Keep rework on submitted reports below 3% during the next quarter.
- Development objective: Lead one stakeholder update meeting per month and gather feedback after each session to improve clarity and confidence.
That is usually enough to make a review feel concrete, useful, and fair. If you keep the objective tied to the role, the measure tied to the outcome, and the deadline tied to reality, the rest of the performance conversation becomes much easier to manage.
