Annual performance objectives: 30 SMART examples for employees and managers

"Improve communication."

"Be more proactive."

"Develop leadership skills."

"Work more efficiently."

These are familiar phrases in annual performance appraisals.

They're also examples of objectives that can be difficult to assess.

What does better communication actually look like?

How will someone demonstrate that they've become more proactive?

What evidence would show that their leadership skills have improved?

And how will either the employee or their manager know when the objective has been achieved?

Setting annual performance objectives should provide clarity, not create another administrative exercise.

A good objective gives employees a clear understanding of what they're working towards, why it matters and how progress will be assessed.

It should also be realistic enough to remain relevant when workloads, priorities and circumstances change.

The best performance objectives aren't necessarily the most ambitious. They're the ones that create clear expectations and support meaningful progress.

In this guide, we'll explain how to write effective annual objectives, explore 30 practical examples across different workplace roles and show how to connect performance expectations with professional development.

What are annual performance objectives?

Annual performance objectives are agreed goals that describe what an employee is expected to achieve during a defined review period.

They usually relate to an individual's responsibilities, team priorities or wider organisational objectives.

For example, an administrator might have an objective to improve the accuracy of monthly reporting.

A customer service employee might work towards reducing avoidable customer complaints.

A team leader might focus on improving the consistency of employee development conversations.

A practitioner might aim to strengthen a particular area of professional practice.

Effective objectives help answer three questions:

1. What needs to be achieved?
2. How will we know whether it has been achieved?
3. What support or resources are needed?

They should provide a shared understanding between the employee and their manager.

What makes a good performance objective?

One useful approach is the SMART framework.

SMART objectives are typically described as:

• Specific: Clearly describe the intended outcome.
• Measurable: Include a way to assess progress or completion.
• Achievable: Are realistic given the employee's responsibilities and circumstances.
• Relevant: Connect to meaningful workplace priorities.
• Time-bound: Include an appropriate deadline or review period.

Example: a vague objective

"Improve customer service."

This is difficult to assess.

It doesn't explain what needs to improve or how success will be recognised.

Example: a SMART objective

"Reduce average customer complaint resolution time from five working days to three working days by December, while maintaining agreed quality standards."

This provides a clearer expectation.

It identifies the outcome, baseline, target and timescale.

However, it should only be agreed after considering whether the employee can reasonably influence the result and whether the target is achievable.

The simplest test

Ask:

Could someone who wasn't involved in setting the objective reasonably assess whether it was achieved?

If the answer is no, the objective probably needs more detail.

Performance objectives versus development objectives

These terms are sometimes used interchangeably, but they serve different purposes.

Performance objectives

Performance objectives focus on what someone is expected to deliver or achieve.

For example:

"Complete the monthly reporting process within three working days of receiving the required data."

Development objectives

Development objectives focus on building knowledge, skills or capabilities.

For example:

"Develop intermediate Excel skills through relevant learning and apply them to improve monthly reporting."

Both can be important.

An employee may need to develop a skill before they can achieve a particular performance outcome.

That's where continuing professional development (CPD) becomes relevant.

Example: connecting performance and development

Performance objective: Improve the efficiency of monthly reporting.

Development objective: Develop confidence using Excel formulas and data analysis tools.

CPD activity: Complete relevant Excel learning and practise the techniques.

Application: Use the learning to simplify the existing reporting process.

Evidence: Updated reporting template, CPD reflection and relevant performance information.

This creates a clearer connection between learning and workplace outcomes.

30 annual performance objectives examples by role

The following examples are illustrative and should be adapted to individual responsibilities, organisational priorities, baseline performance and available resources.

Targets should be agreed rather than copied into appraisal forms without discussion.

Customer service and customer-facing roles

1. Improve complaint resolution times

"Reduce average customer complaint resolution time from five working days to three working days by the end of the review period, while maintaining agreed quality standards."

2. Improve customer satisfaction

"Achieve an average customer satisfaction score of at least 90% during the review period, using the organisation's agreed measurement approach."

3. Improve response consistency

"Respond to at least 95% of assigned customer enquiries within the agreed service standard each month."

4. Reduce recurring customer issues

"Identify the three most common causes of repeat customer enquiries by the end of quarter one and work with relevant colleagues to implement improvements by quarter three."

5. Develop product or service knowledge

"Complete the agreed product knowledge programme by June and demonstrate the ability to answer common customer enquiries accurately through an appropriate workplace assessment."

Team leaders and managers

6. Improve one-to-one consistency

"Hold a meaningful one-to-one meeting with each direct report at least once a month, recording agreed actions and following them up at subsequent meetings."

7. Strengthen employee development planning

"Agree an individual development priority with each team member by the end of quarter one and review progress at least quarterly."

8. Improve delegation

"Introduce clearer task ownership and follow-up arrangements for team projects by the end of quarter two, reviewing their effectiveness through team feedback."

9. Support new starters

"Ensure every new team member receives the agreed induction activities, regular check-ins and appropriate support during their initial employment period."

10. Improve team communication

"Introduce a weekly team briefing with a written summary of key decisions and actions distributed within one working day."

Administration and coordination roles

11. Improve reporting efficiency

"Redesign the monthly reporting process so the standard report can be produced within one hour of receiving complete and accurate source information by September."

12. Improve record accuracy

"Reduce identified errors in the monthly records sample by 25% against the agreed baseline by the end of the review period."

13. Improve document organisation

"Review the department's document management structure by June and implement an agreed filing approach that improves retrieval and version control."

14. Improve meeting administration

"Distribute agreed meeting minutes and action summaries within two working days of each scheduled departmental meeting."

15. Improve process documentation

"Create or update five priority administrative procedure guides by the end of quarter three, following appropriate review and approval."

Sales and business development roles

16. Improve sales pipeline management

"Update assigned opportunities in the CRM system within two working days of significant customer interactions throughout the review period."

17. Improve proposal turnaround

"Reduce average proposal preparation time from seven working days to five by quarter four, without reducing agreed quality standards."

18. Develop customer relationships

"Complete structured account reviews with each assigned priority customer at least twice during the review period."

19. Improve lead qualification

"Introduce the agreed lead qualification framework by the end of quarter two and apply it consistently to new opportunities."

20. Strengthen product knowledge

"Complete relevant product and service training by June and demonstrate the ability to explain the main customer benefits through an appropriate assessment or observed presentation."

Education, health, care and professional practice

21. Maintain relevant professional development

"Complete the CPD activities required by the applicable professional framework during the reporting period, maintaining accurate records and supporting evidence."

22. Apply evidence-informed practice

"Identify and trial one relevant evidence-informed approach during each term, evaluating its application and discussing the findings during supervision."

23. Improve professional documentation

"Complete required professional records within the organisation's agreed timescales, subject to appropriate workload and operational arrangements."

24. Strengthen professional knowledge

"Review relevant updates to professional guidance at least quarterly and identify any changes that need to be reflected in day-to-day practice."

25. Improve reflective practice

"Complete a structured reflection following each agreed professional development activity and review key learning themes during quarterly supervision."

Project, technical and operational roles

26. Improve project delivery

"Deliver the agreed system migration by the approved project deadline, with any significant risks, dependencies or proposed changes escalated through the agreed governance process."

27. Improve quality assurance

"Introduce a documented quality-checking process for the team's priority outputs by the end of quarter two and review its effectiveness quarterly."

28. Develop technical capability

"Complete agreed training in the new system by July and demonstrate the ability to complete the identified core tasks independently."

29. Reduce avoidable rework

"Identify the main causes of rework within the assigned process by quarter one and implement agreed improvements aimed at reducing rework by 20% by year-end."

30. Improve project communication

"Provide a fortnightly progress update for assigned projects, including milestones, risks, decisions required and agreed next steps."

How to write your own annual performance objectives

You don't need to start with a complicated template.

A useful objective can often be created in four steps.

Step 1: start with the outcome

Ask what the employee or team needs to achieve.

For example:

"Improve the monthly reporting process."

This identifies the direction but isn't yet specific enough.

Step 2: describe the observable result

What would successful improvement look like?

For example:

"Reduce the time required to produce the monthly report."

Now the objective has a clearer focus.

Step 3: add an appropriate measure and deadline

For example:

"Reduce monthly report preparation time from three hours to one hour by September."

This makes progress easier to assess.

Step 4: agree the support and conditions

Consider:

• Does the employee have the necessary skills?
• Are the relevant systems available?
• Does the objective depend on other teams?
• Is the workload realistic?
• What training or support is needed?
• What happens if priorities change?

The final objective might be:

"By September, redesign the monthly reporting process to reduce preparation time from three hours to one hour, following completion of the agreed Excel training and subject to access to the necessary source data."

This is more realistic than setting a target without considering how it will be achieved.

Why measurable doesn't always mean fair

This is one of the most important considerations when setting performance objectives.

An objective can be measurable and still be inappropriate.

For example:

"Achieve a 95% customer satisfaction score."

This is measurable.

But what if the employee has little control over staffing levels, product availability or service delays?

Or consider:

"Deliver every project on time."

What happens when project timelines depend on suppliers, approvals or decisions outside the employee's control?

Good objectives should consider influence

Employees should understand which parts of an outcome they can reasonably influence.

Where outcomes depend on external factors, objectives may need to focus partly on the employee's actions and responsibilities.

Example: project delivery

Potentially unfair objective:

"Complete every assigned project by the original deadline."

More balanced objective:

"Maintain accurate project plans, review milestones fortnightly, communicate emerging risks promptly and deliver agreed activities within approved timescales, subject to documented changes and dependencies."

This doesn't remove accountability.

It makes expectations more realistic and evidence-based.

How many annual objectives should an employee have?

There is no universal number suitable for every role.

However, too many objectives can make performance management difficult.

Imagine an employee with fifteen separate annual objectives.

Some may overlap.

Others may compete for time.

The employee may struggle to identify which are most important.

For many roles, a smaller number of meaningful objectives can provide greater clarity.

For example:

• Two or three core performance priorities.
• One quality or improvement objective.
• One or two professional development priorities.

This is a suggested approach, not a mandatory framework.

The appropriate number depends on the role and organisational requirements.

The aim is to prioritise objectives that genuinely matter.

Common mistakes when setting annual objectives

Mistake 1: using vague language

"Be more proactive."

This doesn't explain the expected behaviour.

Better: "Identify and propose at least one practical improvement to the team's existing workflow during the review period."

Mistake 2: setting objectives without employee input

Objectives are more likely to be understood when employees have an opportunity to discuss expectations, resources and feasibility.

Mistake 3: measuring activity rather than outcomes

"Attend three training courses."

This measures attendance.

It doesn't necessarily demonstrate improved knowledge or application.

Better: "Develop the agreed technical capability through relevant learning and demonstrate its application in an appropriate workplace task."

Mistake 4: setting unrealistic targets

Objectives should be challenging where appropriate, but achievable within the employee's responsibilities and circumstances.

Mistake 5: ignoring dependencies

If an employee needs support from another department, that dependency should be recognised.

Mistake 6: setting objectives once and never reviewing them

Business priorities change.

Projects are delayed.

Responsibilities evolve.

Objectives should be revisited when circumstances change.

Mistake 7: using objectives as a substitute for feedback

An employee shouldn't discover at their annual appraisal that they have been missing an objective for months.

Progress should be discussed throughout the year.

Why annual objectives need regular check-ins

A performance objective agreed in January can become irrelevant by July.

Perhaps a project has been cancelled.

A new system has been introduced.

The employee has changed roles.

Or the organisation's priorities have shifted.

If objectives are never revisited, the annual appraisal may assess employees against expectations that no longer reflect their work.

A practical quarterly review

Review point	Questions to ask
Quarter 1	Are the objectives clear, realistic and appropriately supported?
Quarter 2	What progress has been made? Are there barriers or development needs?
Quarter 3	Have priorities changed? Do objectives need adjustment?
Quarter 4	What evidence demonstrates progress, achievement or remaining gaps?

Quarterly reviews can complement regular one-to-one meetings.

Significant concerns or changes should still be discussed when they arise rather than waiting for the next scheduled review.

Connecting annual objectives with CPD

Performance objectives and professional development should work together.

If an employee needs a new skill to achieve an objective, that development requirement should be recognised.

Example: developing leadership capability

Performance objective: Coordinate a small improvement project by the end of quarter three.

Development need: Build confidence in project planning and delegation.

CPD activities: Complete introductory project management learning and shadow an experienced colleague.

Application: Use the learning to plan, coordinate and review the project.

Evidence: CPD reflections, project documentation and appropriate feedback.

Example: improving digital skills

Performance objective: Improve the efficiency of monthly reporting.

Development need: Develop confidence with data analysis tools.

CPD activities: Complete relevant Excel learning and undertake guided practice.

Application: Introduce improved formulas or reporting methods.

Evidence: Learning records, updated reporting outputs and a review of the changes.

Example: improving communication

Performance objective: Deliver clearer weekly team briefings.

Development need: Strengthen presentation and communication skills.

CPD activities: Relevant professional reading, mentoring and practice.

Application: Introduce structured briefings and request feedback.

Evidence: CPD reflections, meeting summaries and relevant feedback.

This approach helps employees understand why their development activities matter.

It also gives managers a clearer basis for supporting learning.

How to measure progress without creating unnecessary administration

Tracking objectives shouldn't require employees to complete endless forms.

For each objective, consider recording:

The objective: What needs to be achieved?

The measure: How will progress be assessed?

The deadline: When should it be achieved?

The owner: Who is responsible?

The support: What resources or learning are needed?

Progress: What has happened so far?

Evidence: What information supports the assessment?

Next action: What needs to happen next?

Example

Objective: Improve the monthly reporting process.

Measure: Reduce preparation time from three hours to one hour.

Deadline: September.

Progress: New template developed and tested.

CPD: Completed relevant Excel training.

Evidence: Updated template and time comparison.

Next action: Review the revised process with colleagues before implementation.

This provides a useful progress record without requiring a lengthy narrative every month.

What happens when an employee doesn't achieve an objective?

Not every objective will be achieved.

That doesn't automatically mean the employee has performed poorly.

The reasons matter.

For example:

• The target may have been unrealistic.
• Priorities may have changed.
• Resources may have been unavailable.
• External dependencies may have caused delays.
• The employee may have needed additional support.
• Performance may genuinely have fallen below the expected standard.

A fair review should consider the evidence and context.

Useful questions for managers

Was the objective clear?

Was it achievable?

Did the employee understand the expected standard?

Were barriers discussed?

Was appropriate support available?

Were changes to the objective documented?

Did the employee take reasonable action?

The answers can help distinguish between individual performance issues and wider organisational problems.

Annual objectives and the no-surprises appraisal

One of the most important principles of effective performance management is that significant concerns shouldn't appear for the first time during the annual appraisal.

Imagine an employee has an objective to improve report accuracy.

By April, the manager has noticed that errors remain frequent.

If the manager waits until December to discuss this, the employee loses valuable time to respond.

A better approach is to discuss the concern promptly.

Example

January: Objective agreed.

April: Progress reviewed and an accuracy concern identified.

April one-to-one: Manager and employee discuss the issue and identify possible causes.

May: Additional support and checking arrangements introduced.

July: Progress reviewed.

December: Appraisal considers the full development journey.

The annual appraisal then becomes a summary of conversations that have already happened.

Objectives should guide performance throughout the year, not become evidence against an employee at the end of it.

What employees should ask before agreeing objectives

Employees should have an opportunity to clarify expectations.

Useful questions include:

1. What does successful achievement look like?
2. How will progress be measured?
3. Is the target realistic given my responsibilities?
4. What factors are outside my control?
5. What resources or support will be available?
6. Will I need additional training?
7. How often will we review progress?
8. What happens if priorities change?
9. What evidence should I maintain?
10. How will the objective contribute to my wider development?

These questions help create a shared understanding from the beginning.

How WorkplaceHero supports objectives and professional development

WorkplaceHero's approach connects individual professional development with ongoing workplace performance conversations.

For individuals, the free CPD log provides a structured way to record learning and reflect on progress.

For organisations, Passport for Teams is designed to support more connected performance management.

Ongoing objectives

Performance priorities can be reviewed throughout the year rather than forgotten between appraisals.

Regular one-to-one conversations

Managers and employees can discuss progress, challenges, development and agreed actions.

Connected professional development

Relevant CPD activities can support development conversations and provide context for progress towards objectives.

Continuous feedback

Achievements and concerns can be discussed when they arise.

More meaningful appraisals

The annual review can draw on the employee's development and performance journey instead of relying entirely on memory.

Technology doesn't replace effective management.

But it can help organisations maintain continuity between objectives, feedback, learning and appraisals.

The goal isn't to set more objectives. It's to make the important ones clearer and easier to manage.

Explore WorkplaceHero for Teams

Annual performance objectives checklist

Before agreeing an objective, check:

• The intended outcome is clear.
• The objective is relevant to the employee's role.
• Success can be assessed using appropriate evidence.
• The target is realistic.
• The employee can reasonably influence the result.
• Dependencies and resources have been considered.
• The deadline is appropriate.
• Any necessary development or CPD has been identified.
• The employee has had an opportunity to discuss the objective.
• Progress review arrangements are agreed.
• Changes can be made when circumstances require them.

If several of these are missing, the objective may need further discussion.

Frequently asked questions

What are annual performance objectives?

Annual performance objectives are agreed goals describing what an employee is expected to achieve during a defined review period.

What is a SMART objective?

A SMART objective is specific, measurable, achievable, relevant and time-bound.

What are examples of good employee objectives?

Examples include improving reporting accuracy, reducing customer response times, delivering an agreed project, strengthening communication or developing relevant technical skills.

How many objectives should an employee have?

There is no universal number. A smaller set of meaningful objectives is often easier to prioritise and review than a long list of competing targets.

What is the difference between a performance objective and a development objective?

Performance objectives focus on outcomes or responsibilities. Development objectives focus on building knowledge, skills or capabilities.

Should all objectives include numbers?

No. Some outcomes are better assessed through observable changes, appropriate qualitative evidence or completion of clearly defined work.

How often should performance objectives be reviewed?

Regular one-to-ones and periodic formal check-ins can help maintain progress. Objectives should also be reviewed when significant circumstances change.

What happens if an employee doesn't meet an objective?

The reasons should be considered fairly, including expectations, support, resources, external factors and individual performance.

Can CPD help employees achieve performance objectives?

Yes. Relevant learning and development can help employees build the knowledge and skills needed to achieve agreed objectives.

Can performance management software help track objectives?

Yes. Suitable systems can help maintain records of objectives, progress, feedback and development, although effective management remains essential.

Final thoughts: good objectives create clarity, not pressure

Annual performance objectives should help employees understand what matters.

They should explain what success looks like.

Provide a basis for meaningful feedback.

Identify where development is needed.

And help managers and employees recognise progress throughout the year.

But objectives shouldn't become a collection of ambitious statements that are forgotten until the next appraisal.

They need to be realistic.

Relevant.

Measurable where appropriate.

And reviewed when circumstances change.

Most importantly, employees should understand how they're progressing long before the annual review arrives.

A good objective isn't just something you can measure in December. It's something you can meaningfully work towards all year.

Build a more connected approach to objectives and development with WorkplaceHero

Related reading

• Your year-end review starts in January
• Skills gap analysis: find the gap between you and your next role
• Boosting career growth: The power of a personal development plan
• How to build a promotion case that gets a yes
• Nothing in an appraisal should be a surprise