# Goals for a Performance Review: The Four Types and How to Set Them Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/goals-for-performance-review/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/goals-for-performance-review.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 Goals for a performance review come in four types. Learn what makes each one measurable, how many to carry, and how to agree them with your manager. ## Key facts - Title: Goals for a Performance Review: The Four Types and How to Set Them - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Setting Goals - Primary keyword: goals for performance review - Source page: https://headwayskills.com/knowledge/working-with-your-manager/goals-for-performance-review/ ## What this page covers - Goals for a performance review come in four types. Learn what makes each one measurable, how many to carry, and how to agree them with your manager. - Practical guidance for goals for performance review - How this topic connects to Working with Your Manager ## Detailed explanation Goals for a [performance review](/knowledge/working-with-your-manager/performance-reviews/) fall into four kinds: performance goals (a result you deliver), development goals (a skill you build), behavioral goals (how the work gets done), and alignment goals (work tied to a team or [company priority](/knowledge/influence/seeing-the-big-picture/)). A usable set covers more than one kind, and every goal on it names what will be done, how success is measured, and by when. Search this topic and you'll find lists of forty, fifty, sixty example goals ready to copy. Copying is tempting, especially the week the form is due. It also tends to produce a set your manager quietly rewrites — because an example lifted from a list isn't tied to your role, your team's priorities, or anything you can point to twelve months from now. The fix isn't a longer list. It's knowing which four things a goal set has to cover, and which test each goal has to pass. ## The four types of goals for a performance review Almost every example list mixes these four together without labeling them, which is how people end up carrying five output targets and nothing that develops them. Sorted, the categories are easy to tell apart, and the difference matters because each one is measured in a different way. ### Performance goals: the result you deliver These are targets tied to what your role is supposed to produce in the period — volume, quality, timeliness, or a specific deliverable. They're measured with numbers: project completion rate, error rate, revenue achieved, customer satisfaction score. The defining feature is that someone else can verify them without asking you how it went. This is the type the example lists handle best, and their wording is worth borrowing structurally even when the content doesn't transfer. Goals collected by TechTarget and ClearCompany read like commitments rather than intentions: reduce the average time spent on routine tasks by 15% within six months; resolve three critical issues by the end of the next review cycle. Each names a count, a change, or a deliverable, plus a horizon. If yours can be met without anything being different, it isn't finished yet. ### Development goals: the skill you build Development goals target something you can't do yet. HR comparisons from Primalogik, Factorial and Deel draw a clean line between the two: performance goals aim at an end result, development goals aim at the attainment of skills and knowledge. That difference changes how you measure them. Development goals are evidenced by activity — training hours completed, a certification obtained, mentorship sessions held — or by behavioral measures such as 360-degree feedback on a new way of working. This is the type most often missing from a copied set, and it's the one that compounds. A cycle spent hitting output targets leaves you where you started, only tireder. A cycle with one real development goal leaves you able to do something you couldn't do in January. ### Behavioral goals: how the work gets done These cover conduct rather than output: communication, collaboration, reliability, initiative. They recur in every example list — communication goals in particular are framed as improving both individual performance and team dynamics — and they're the ones most often written vaguely, because "improve my communication" has no visible finish line. The workaround is an observable proxy. Instead of naming the quality, name the instance that would prove it: a specific number of times you'll do the thing, in a specific setting, by a specific date. Deliver two presentations on new product updates to the team by the end of the quarter. Mentor two junior colleagues over six months. Neither sentence contains an adjective about your character, and both are checkable. ### Alignment goals: the line to a wider priority The fourth type isn't about ambition at all — it's about traceability. Culture Amp's guidance puts the bar higher than "make it relevant": the connection should be explicit enough that you can draw a line from your individual goal to a team objective, and from there to a company priority. That two-step line is the practical mechanism by which goals get approved, because your manager is the one who has to defend them upward. Institutional HR guidance points the same way from the other end. Pages like UIC Human Resources define performance goals as what an individual is expected to achieve in their role during a given period, tied to the job description and to identified development areas. Read together, the two ends give you a test: your goal should trace down to your actual job description and up to something the organization has already committed to. ## What makes a goal hold up SMART — specific, measurable, achievable, relevant, time-bound — is the near-universal framework here, cited across effectively every source that ranks for this topic. Its real value isn't as a template to fill in but as a test to run on a goal you've already drafted. Guidance from Indeed and Mitratech reduces it to three questions: what will be done, how success will be measured, and by when. Most weak review goals fail on the last two, which is exactly why they become impossible to defend when the cycle closes. The "achievable" criterion carries a protection that's easy to miss, and it matters most early in a career. The same guidance frames it around two constraints: goals shouldn't push into burnout, and they should focus on outcomes reasonably within your own control, with external factors excluded from whether the goal counts as met. If your goal depends on another team shipping, on a budget decision, or on how clients behave, you've accepted a target you can't guarantee. Rewrite it around your contribution to that outcome instead. How many should you carry? Sources genuinely disagree. PerformYard and Quantum Workplace recommend three to five per cycle for focus; a TechTarget feature argues six to ten with clear milestones gives the best balance of focus and ambition. Neither figure is tied to cited research — this space is prescriptive rather than evidential — so treat both as common practice rather than a finding. The direction of the advice is the usable part: a small set you can evidence beats a long list you can't. ## Getting your goals agreed, not assigned Here's what the example lists almost never cover, and it's the part that decides whether any of the above survives contact with your workplace: review goals are not written alone. TechTarget and Culture Amp both describe goal-setting as joint work — manager and employee setting SMART goals together — and note a second benefit that's easy to overlook. A documented, measurable target reduces the space for unconscious bias in the review, because it replaces impression-based judgment with something checkable. The goal you agree in advance is, in a real sense, the fairness mechanism of your own evaluation. That reframes the task. You're not filling in a form; you're proposing terms for how you'll be judged, in a conversation where you get a say. Draft your goals before the meeting so you arrive with something concrete to react to rather than [nodding along](/knowledge/working-with-your-manager/disagree-with-your-manager/) to whatever appears on screen. Bring the line from each goal to a team objective, because that's what makes it easy for your manager to say yes. And raise them in a [regular one-on-one](/knowledge/working-with-your-manager/one-on-one-meetings/) rather than treating the annual form as the only opening — priorities shift mid-cycle, and a goal nobody has revisited since January is a goal you'll be defending on stale terms. Choosing the development goal is usually the hardest part of that draft, because it asks a question the form doesn't help with: which gap is actually worth a whole cycle? Guessing wastes twelve months. If you're unsure, [checking which skills would move you most](https://assessment.headwayskills.com/) gives you an honest starting point rather than picking whatever sounds impressive. ## The skills behind a goal that gets agreed Read back over what separates a goal set that holds up from one that gets rewritten, and very little of it is about wording. It's about knowing what you're aiming at, being able to see your own work clearly, and being able to hold the conversation where the goals get set. **Working with Your Manager** is where most of this lives. Aligning expectations, agreeing goals that are challenging but achievable, settling how much decision-making authority you have, and making your results visible so a goal can actually be evidenced at review time — these are the mechanics of the relationship, not extras. The same skill covers the review itself: preparing properly, staying future-focused, and asking plainly for what you want. It treats the goal conversation as a partnership you can shape rather than terms handed down. **Building Self-Awareness** supplies the raw material. A goal is only as good as your read on where you actually stand, which means noticing what you're genuinely good at rather than merely competent at, and using feedback as input instead of just surviving it. Asking for specific, future-focused advice — what would make the biggest difference next quarter — turns a review from a verdict into the first draft of your next set of goals. **Setting Goals** is the one that decides whether the cycle is worth anything to you. It argues for shorter planning horizons of roughly six to eighteen months, which is almost exactly the length of a review cycle, and for weighting your effort toward your strengths rather than spending every cycle patching weaknesses. It also insists the direction comes from you — worth remembering when the easy move is to accept whatever your manager or a template proposes. The free Work Skills Test measures all twelve of the skills this framework covers, these three among them, and none of them is a fixed trait. If you already suspect one of the three is your strong suit, [seeing which ones you can lean on](https://assessment.headwayskills.com/) is a faster way to find out than waiting for the review to tell you. ## What this means for you Some of this may already describe how you work — the person who keeps a note of what actually shipped, who would rather ask what to improve than guess, tends to arrive at the goal conversation with something to say. None of it is fixed. These are behaviors you build at whatever pace the year allows, and you can build them without becoming a different person at work. They also tend to count for more as your responsibilities grow, since the goals get bigger and the room for a vague one gets smaller. The fact that you're reading about how goals work before the form is due already puts you ahead of most people, who open it the night before and start copying. The remaining step is small: find out which skills are worth aiming at. ## Find out which skills are worth aiming at The only thing left is to get an honest read on where you stand today. The Work Skills Test is a **free** self-assessment of the workplace skills this article has been circling — the same ones that decide whether your goals get agreed or rewritten. It shows you where you're strong across all twelve and which one or two would make the biggest difference right now, so the development goal you propose is aimed at something real. Do it before your next one-on-one and you'll walk in with a draft instead of a blank field. **[Get my skills profile](https://assessment.headwayskills.com/)** *Free, about 7 minutes, and nothing to prepare beforehand.* ## 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? Goals for a performance review come in four types. Learn what makes each one measurable, how many to carry, and how to agree them with your manager. ### 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/goals-for-performance-review/ Preferred summary: "Goals for a performance review come in four types. Learn what makes each one measurable, how many to carry, and how to agree them with your manager." ## Change log - 2026-07-07: Content collection version published.