# Performance Evaluation Goals: How to Choose the Right Few

Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/performance-evaluation-goals/
Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/performance-evaluation-goals.md
Entity type: Article
Last updated: 2026-07-07
Language: en
Primary audience: professionals improving working with your manager at work
Owner: Headway Skills
Contact: https://headwayskills.com/contact/

## Short answer

Performance evaluation goals come in four kinds. Here is how to choose the two to four that fit your role - and how to get your manager to agree to them.

## Key facts

- Title: Performance Evaluation Goals: How to Choose the Right Few
- Category: Working with Your Manager
- Primary skill: Working with Your Manager
- Related skills: Building Self-Awareness, Setting Goals
- Primary keyword: performance evaluation goals
- Source page: https://headwayskills.com/knowledge/working-with-your-manager/performance-evaluation-goals/

## What this page covers

- Performance evaluation goals come in four kinds. Here is how to choose the two to four that fit your role - and how to get your manager to agree to them.
- Practical guidance for performance evaluation goals
- How this topic connects to Working with Your Manager

## Detailed explanation

Performance evaluation goals are the small set of commitments — usually two to four — that you and your manager agree to measure your work against over a review period. They come in distinct kinds: what you will deliver, what skill you will build, how you will work, and what standard you will hold.

If you are looking at an empty goals box with a deadline attached, the search results are not much help. They hand you forty-five examples when your actual problem is choosing three. The examples are the easy part. Deciding which goals are worth a year of your working life, and getting your manager to agree they are the right ones, is the half almost nobody writes down.

## The four kinds of performance evaluation goals

A goals section is not one list written four different ways. Across HR platforms like Deel, Factorial and ClearCompany, the same four categories keep surfacing, and each does a different job. That matters, because the example inventories dominating search results front-load productivity entries — so a reader picking from a flat list of forty-five usually ends up with a set that is all one type. Four output targets can be completely hit by someone who learned nothing all year and is hard to work with. Four development goals produce nothing visible to be evaluated on.

One filter runs across all four. MAP Consulting and ClearCompany both put alignment with team and organizational objectives at the center of what an evaluation system is for. The practical consequence is legibility: a goal not visibly attached to something your team is measured on can be fully achieved and still not read as valuable to the person writing your evaluation.

### Performance goals: what you will deliver

These are the short-term, measurable targets tied to your job responsibilities inside the review period — output, quality, throughput, deadlines met. What separates them is that they are judged on the result, not on effort or growth, and they have a finish line inside the cycle. A project shipped by a date. A number moved by an amount.

This is the category people find easiest to start and hardest to finish. "Improve reporting quality" cannot be scored: if you cannot say what number or artifact would exist at the end of the period, you have written a topic, not a goal.

### Development goals: what skill you will build

Here the deliverable is capability rather than output: a competency gap you intend to close, or a skill you will need for wider responsibility. Deel, Factorial and others all define them the same way — addressing gaps, preparing for a future role — and then assume you already know what your gap is. Nobody explains how you would find out.

That diagnosis is the real work. The raw material is not a category from a list; it is the feedback already on record — the things a manager or a colleague has actually said to you — plus an honest read of what you are genuinely good at rather than merely competent at. If you cannot name the gap yet, it is worth [pinpointing your real skill gaps](https://assessment.headwayskills.com/) before you commit one to paper, because a development goal aimed at the wrong thing still costs you a full cycle. Then add the part most people forget: say in advance what demonstrating the skill would look like, or nobody can score it in ten months.

### Behavioral goals: how you will work

These cover conduct rather than output — collaboration, reliability, how you communicate, how you show up in work other people depend on. They differ from the first two in one important way: they are usually ongoing rather than time-bound, evidenced by a pattern observed across the period rather than by a completed deliverable.

People skip this category because writing it down feels like admitting a problem. It is also the one that quietly shapes a lot of evaluations: how you work with others is observed all year whether or not it appears on the form.

### Operational goals: the standard you will hold

The fourth kind covers the core functions of your role held at a defined standard of quality and efficiency. It is the only category where no change is a successful outcome, which is precisely why early-career people leave it out — a goal ought to be an improvement, surely.

It earns its place by making the baseline explicit: if a large part of your job is keeping something running well and nothing in your goals says so, that work is invisible at review time.

## How many performance evaluation goals to set

Two to four per cycle is the recurring practitioner recommendation, though it circulates as advice rather than research, so treat it as a sensible default rather than a rule. The contrast with the search results is stark: the same ecosystem that recommends restraint publishes inventories of forty-five and sixty examples.

Ambition says list eight. Eight reads as unfocused at evaluation time and guarantees several will be unfinished — a worse outcome than three that were all delivered. Spread the small number across categories instead of stacking them: at least one thing you will deliver, at least one capability you will build, and — where it matters for your role — one about how you work or the standard you maintain.

## Why SMART is not the hard part

Almost every top result frames goals through SMART: specific, measurable, achievable, relevant, time-bound. It is genuinely useful, because it forces "get better at communication" into something that can be checked at the end of the period.

But it is a formatting convention. It tells you how to phrase a goal once you have chosen it, and nothing about which goal to choose. The selection problem sits upstream of the formatting problem, and selection is what you are actually stuck on. Two questions do most of that work: does this connect visibly to something my team is measured on, and would achieving it change something real about my output or my capability? A goal that fails both is decoration, however neatly it is worded.

## The half of goal-setting the example lists leave out

Sources state the principle and move straight past it: the manager and the employee work together to set the goals and confirm what success looks like. None explain how. The gap between how the process is described and how you experience it is the whole problem — you are treating it as a form to submit alone, while the process assumes a two-party agreement.

Closing that gap costs one conversation, and it works better if you bring drafts rather than blanks. Ask what "done well" would look like for each goal and get the answer in words you would both still recognize in ten months. Confirm how much decision-making room you have, since a goal you cannot influence is not really yours. Then write down what you agreed, so neither of you is reconstructing it from memory later.

The other half is keeping them alive. Review cadence is shifting toward quarterly rather than annual, and both AllVoices and Workleap describe an evaluation as an ongoing conversation rather than a one-time verdict, with feedback built into the cycle so goals can be adjusted or dropped as circumstances change — AllVoices lays out a four-stage cycle in which shortcutting any stage weakens the whole. In practice that means one habit: when a priority shifts, say so and agree the change, rather than quietly abandoning a goal and hoping nobody looks.

## The skills that make this easier to get right

Read back over the last few sections and notice how little of the work is about wording. Choosing goals is mostly reading what your team is trying to do, judging your own capability honestly, and having one clear conversation with the person who will eventually score you.

**Working with Your Manager** is where the goals are actually decided. The framework treats this as a partnership built around shared work: you align expectations, agree goals that are challenging without being unachievable, settle how much decision-making authority you have, and make your results visible so there is something concrete to assess. Preparing properly for the review, staying future-focused in it, and asking for what you want all belong to the same skill. That is why the goals conversation is ordinary preparation rather than a campaign — you are both trying to describe the same year in advance.

**Building Self-Awareness** supplies the raw material for the half of the set you cannot copy from anywhere. A development goal needs an honest read of what you are genuinely good at rather than merely competent at, and it needs the specific feedback already on record about where you fall short. The framework points to performance reviews and one-on-ones as exactly where this skill gets used: you take feedback in, add your own view of it, and ask for the future-focused advice that tells you what to aim at next.

**Setting Goals** decides which goals are worth having at all. The framework's position is that they work best when they emerge from what the work has actually taught you rather than being fitted to a plan written in advance, when they lean into your strengths instead of spreading effort thinly across your weaknesses, and when the horizon stays short — six to eighteen months, roughly one review cycle. A goal adopted because it looked impressive on someone else's list is precisely the kind this skill warns against.

None of the three is a personality trait; each is a habit that can be practiced. They are also the habits your evaluation is assessing whether or not the form names them, which is why it is worth [knowing which ones are solid](https://assessment.headwayskills.com/) before you commit to a year of goals — the free assessment covers **all twelve of the work skills the framework treats as learnable**, so what your review is quietly measuring stops being guesswork.

## What this means for the goals you write

Some of this may already match how you operate — you might already check what your team is being measured on before deciding what to push, or already have a rough sense of the feedback that keeps coming back. None of it asks you to become a different kind of employee. The habits behind a good goal set are things people build, and the version of you who walks into next year's review with three goals that turned out to be the right ones is a version you assemble deliberately. This gets more useful rather than less: the further a career goes, the more of the work is judged against goals you helped set rather than tasks you were handed — which is why it pays to find out now which of these habits you can already lean on. You came looking for examples and read past them to the part that decides the outcome, which is already the harder half.

## Know what your review is measuring before you write your goals

You have the four categories and you know what the conversation needs to cover; the only thing left is an honest read of the skills underneath them. The **free** Job Skills Test is a short self-assessment of your work skills — it takes about seven minutes and shows where you stand across all twelve, including the manager, self-awareness, and goal-setting habits this article has been circling. You come away with one concrete thing: a profile telling you which skill would repay attention first, which is exactly the input a development goal needs. Do it before your next one-on-one and you walk into the goals conversation with something to point at instead of a blank form.

**[Get my skills profile](https://assessment.headwayskills.com/)**

*Free, seven minutes, and your results appear immediately.*

## Who this is for

- Professionals building practical workplace skills
- Readers looking for specific, usable work advice
- Managers, educators, and coaches supporting career readiness

## Common questions

### What is this guide about?

Performance evaluation goals come in four kinds. Here is how to choose the two to four that fit your role - and how to get your manager to agree to them.

### Which Headway skill does this connect to?

This guide connects primarily to Working with Your Manager. It also relates to Building Self-Awareness, Setting Goals.

### What is the recommended next step?

Use the free Work Skills Test to reflect on which work skill to improve next.

## Related pages

- https://headwayskills.com/knowledge.md
- https://headwayskills.com/knowledge/working-with-your-manager.md
- https://headwayskills.com/knowledge/self-awareness.md
- https://headwayskills.com/knowledge/setting-goals.md
- https://headwayskills.com/work-skills-test.md

## Citation guidance

Use the canonical page when citing this content:
https://headwayskills.com/knowledge/working-with-your-manager/performance-evaluation-goals/

Preferred summary:
"Performance evaluation goals come in four kinds. Here is how to choose the two to four that fit your role - and how to get your manager to agree to them."

## Change log

- 2026-07-07: Content collection version published.
