# Review Goals: What to Write and How to Agree on Them Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/review-goals/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/review-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 What review goals are, how specific they need to be, and how to agree on goals with your manager instead of accepting whatever lands in the form. ## Key facts - Title: Review Goals: What to Write and How to Agree on Them - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Setting Goals, Building Self-Awareness - Primary keyword: review goals - Source page: https://headwayskills.com/knowledge/working-with-your-manager/review-goals/ ## What this page covers - What review goals are, how specific they need to be, and how to agree on goals with your manager instead of accepting whatever lands in the form. - Practical guidance for review goals - How this topic connects to Working with Your Manager ## Detailed explanation The goals field on a review form is usually the last thing you fill in and the first thing your manager reads. Review goals are the objectives you and your manager agree on for the coming period — typically one or two performance goals tied to your current work, plus a development goal that builds a skill you'll need next. The good ones are specific enough to be judged without argument, and agreed together rather than handed down. That last part is where most of the advice quietly stops. ## What should I put as my review goals for the next period? Start with what the form is actually asking for. Published [self-appraisal templates](/knowledge/working-with-your-manager/self-appraisal/) from university HR departments — the University of Wisconsin–Madison's divisional HR guidance and Columbia Law School's employee self-assessment form among them — ask employees for the same short list: achievements from the past period, what is going well, the barriers you ran into, your areas of strength, skills you want to develop, and goals for the next period including career development goals. The goals field is not a standalone question. It is the last item in a sequence designed to make you review your own year first, so your goals come out of evidence rather than out of the air. Fill in the earlier fields honestly and the goals field gets much easier to answer. ## Who actually sets the goals — me or my manager? Officially, both of you. Nearly every guide on this topic describes goal-setting as collaborative and says employees should actively participate. Read those guides closely, though, and almost all of them are written to the manager, instructing them to facilitate your participation. Very few explain what participating looks like from your side: what to bring, what to propose, what to push back on. That gap matters, because a review goal you did not help write is one you will be measured against for a year. In practice the goals get set by whoever arrives at the meeting with something concrete. If you turn up with two or three drafted goals and your reasoning for each, that becomes the starting document. If you turn up empty-handed, your manager's version becomes the starting document by default. ## How specific does a review goal have to be? Specific enough that neither of you can reinterpret it at evaluation time. This is what the [SMART criteria](/knowledge/setting-goals/smart-criteria-for-goals/) — specific, measurable, achievable, relevant, time-bound — are actually protecting against, and the worked examples across this topic all follow one repair pattern: take a vague goal, then add a quantity and a deadline. The performance-management platform Trakstar illustrates it with a goal that starts as "update the report on emerging trends in e-commerce" and becomes "update the report on emerging trends in e-commerce with at least two new trends that aren't listed in the current report." The second version is not harder. It is just no longer arguable. Vague goals feel safer when you write them because they leave room, but that room cuts both ways — it is the same room your manager has to decide, twelve months later, that what you delivered was not quite what they meant. ## What is the difference between a performance goal and a development goal? Sources across this topic consistently split review goals into two kinds. Performance goals are tied to deliverables in your current role: output, quality, a project shipped by a date. Development goals build a competency you will need for future work — a skill, a qualification, an area of responsibility you have not held yet. The distinction is worth knowing because the two are judged differently. A missed deliverable usually reads as underperformance. A development goal you got two-thirds of the way through usually does not — progress is the point. Putting only performance goals in the form means every item on your list can be failed outright. ## How many review goals should I set? There is no standard number, and the guidance on this topic does not converge on one. The useful constraint is not the count but the follow-up: every goal you write is something you will have to evidence later, and something that should come up in your [one-on-ones](/knowledge/working-with-your-manager/one-on-one-discussion/) during the year rather than sitting untouched until the next review. A short list you can genuinely track beats a long list you will be scrambling to account for. If you cannot say how you would show progress on a goal in three months' time, it is probably one goal too many. ## How do I bring up the goals I actually want? Translate them into your organization's terms. Alignment with organizational objectives is presented across this topic as a scoring criterion, not a courtesy — the HR platform Peoplebox frames the process as analyzing your job responsibilities and the metrics attached to them so that personal goals connect to organizational ones. The practical consequence is blunt: a goal that is genuinely useful to you but invisible to the organization tends to score badly, while the same goal expressed in the organization's own language tends to get approved with very little argument. So do the translation yourself before the meeting. If you want to move toward client work, the goal is not "get more client exposure" — it is the specific piece of client-facing work you would take on and what it delivers for the team. Coming in with that framing already done is also easier when you have a clear sense of [your own strengths](/knowledge/self-awareness/how-to-identify-your-strengths/) to argue from; it is worth knowing [where your work skills stand](https://assessment.headwayskills.com/) before you sit down to negotiate, so your proposals come from evidence rather than from whatever you happen to feel shaky about that week. ## How do I write career development goals without sounding like I am leaving? You are being asked for them directly, so the fear is misplaced. The self-appraisal templates published by university HR departments explicitly request goals for the next period *including career development goals* — it is a named field, not something you are sneaking in. Keep the goal anchored to work you could plausibly do where you are, and the ambiguity disappears. "Take on a piece of budget responsibility this year" reads as commitment; "prepare for a management role" with no reference to your current team reads as an exit plan. Same ambition, different anchor. ## Can my review goals change during the year? Yes, and the sources are clear about it. People Managing People states that performance goals are not set in stone and should be adjusted when unforeseen challenges or opportunities arise, so they stay relevant. Goal-management systems assume the same thing structurally — Oracle's documentation for NetSuite describes managers monitoring progress toward goals throughout the evaluation period, not only at review time. That should take some pressure off the wording. You are not signing a contract you have to live with regardless of what happens to your team, your project, or your role. But it only works if someone raises the change, and the person with the most at stake in raising it is you. A goal that quietly became impossible in March and was never mentioned again still looks like a missed goal in November. ## What happens if I do not hit my goals? It depends which kind of goal it was and what happened in between. A performance goal missed with no explanation on record is the worst version. The same goal, discussed at a check-in when it started slipping and formally adjusted, is a different conversation entirely — the failure point that this topic keeps returning to is not missed targets but goals that are agreed at the review and then never revisited until the next one. Development goals are more forgiving still, because partial progress is legible progress. None of this means goals do not matter; it means the record you build between reviews matters as much as the goals themselves. ## The skills that make this conversation go better Notice what almost every answer above turned on. Not the phrasing in the box — the conversation around it, and how much you brought to it. The mechanics of a review goal take about ten minutes to learn. What makes the difference is a small set of things you either do or do not do in the months either side of the meeting. **Working with Your Manager** is the one this rests on most directly. Treating the relationship as a partnership rather than a chain of command changes what a review is: goals become something you negotiate, not something you receive. That means preparing properly for one-on-ones instead of showing up empty, keeping your results visible between reviews so the evidence is already there, agreeing what "challenging but achievable" actually means for a given goal, and asking straightforwardly for what you want rather than hoping it gets offered. **Setting Goals** supplies the filter that all those example lists cannot. Twenty ready-made goals do not tell you which one is right for you. A goal that came from outside you, or that exists mainly to patch a weakness, buys you a year of work you never wanted. It helps that this framework works in shorter horizons — six to eighteen months, which maps almost exactly onto a review cycle — and that it points you toward your strengths zone, which is usually what decides between two goals that both look reasonable on paper. **Building Self-Awareness** is what makes the self-assessment section survivable. Every guide tells you to start by assessing yourself; almost none of them tell you how. It comes down to two things: knowing what you are genuinely good at rather than merely competent at, and taking evaluative feedback without going defensive. Review season is also when a middling rating gets read as a verdict on your worth — noticing that reaction for what it is, rather than acting on it, is what lets you set next year's goals from evidence. None of these is something you either have or you do not. **The framework treats all twelve of the work skills it covers as buildable**, and a development goal needs one of them named specifically — so if you are unsure what to write in that field, the free Job Skills Test will show you [which skills to develop first](https://assessment.headwayskills.com/) instead of leaving you to guess. ## Where this leaves you If you have read this far before your review rather than the night before the deadline, you are already doing the part most people skip. Some of what is above may describe how you already operate — arriving prepared, tracking your own results, saying what you want out loud. Other parts may be exactly the thing you have been avoiding, and that is a gap rather than a limit; these are skills you build with practice, not traits you were issued at birth. They also compound. The goals conversation you have now is a small one, but the same skills run through every promotion discussion, every project you want to be on, and every manager you will work for after this one. Getting a clearer read on where you currently stand is a reasonable place to start. ## See where your skills stand before your next review The only thing left is to find out which of these are already working for you and which are not. The Job Skills Test is a **free** self-assessment of your work skills — it takes about 7 minutes, covers all twelve skills the framework is built around, and gives you back a picture of where you are strongest and which ones are worth putting a development goal against this cycle. **Get my skills profile** *Free, nothing to prepare, and you can do it before your review meeting.* ## 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? What review goals are, how specific they need to be, and how to agree on goals with your manager instead of accepting whatever lands in the form. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Setting Goals, Building Self-Awareness. ### 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/setting-goals.md - https://headwayskills.com/knowledge/self-awareness.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/review-goals/ Preferred summary: "What review goals are, how specific they need to be, and how to agree on goals with your manager instead of accepting whatever lands in the form." ## Change log - 2026-07-07: Content collection version published.