# Examples of Work Goals for Annual Review: The Seven Steps That Produce Them Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/examples-of-work-goals-for-annual-review/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/examples-of-work-goals-for-annual-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 Examples of work goals for annual review, plus a seven-step process for choosing, wording, and agreeing goals your manager will actually sign off on. ## Key facts - Title: Examples of Work Goals for Annual Review: The Seven Steps That Produce Them - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Setting Goals, Building Self-Awareness - Primary keyword: examples of work goals for annual review - Source page: https://headwayskills.com/knowledge/working-with-your-manager/examples-of-work-goals-for-annual-review/ ## What this page covers - Examples of work goals for annual review, plus a seven-step process for choosing, wording, and agreeing goals your manager will actually sign off on. - Practical guidance for examples of work goals for annual review - How this topic connects to Working with Your Manager ## Detailed explanation The goals section of an annual review form is usually the last box people fill in, and the hardest. Work goals for an annual review are specific, measurable commitments for the year ahead — a delivery target, a quality improvement, a named capability you'll build — each worded so that you and your manager can both tell, twelve months later, whether you reached it. A strong set usually mixes two or three performance goals with one or two development goals. Most examples of work goals for annual review are handed over as lines to copy. They work better as the last step of a short process, because the wording is rarely the thing that makes a goal hold up. ## How to write work goals for an annual review, step by step The steps below run in order, and the order does the work: each one narrows what the next has to decide. Almost all of it happens before you write a single goal, which is why goals drafted the night before the meeting come out generic so reliably. ### 1. Reread last year's goals, your job description, and the feedback you already have Start with what already exists. UC Davis's HR guidance for employees writing a self-evaluation puts this first: review your job description, the performance goals set for the year, and any [feedback you received](/knowledge/working-with-your-manager/appraisal-feedback/) along the way, then reflect on what you delivered and where you struggled. It reads like housekeeping, but it does two useful things. It reminds you what you were formally measured on — which is rarely identical to what actually filled your days — and it surfaces the feedback themes you have already been given, which are the safest source of a development goal, because your manager has effectively pre-approved them. Do this a week or two ahead, not the night before. You need time for a second thought. ### 2. Gather the evidence of what you actually delivered Next year's goals are only credible if this year's [results are visible](/knowledge/working-with-your-manager/one-on-one-with-manager/). Guidance from USC and Stanford on writing your own review converges on the same instruction: identify your key achievements with specific examples and data, and quantify the impact wherever you can — a percentage, a count, a before-and-after. Collect that evidence now, while you are looking backward anyway. It does double duty: it carries the [self-assessment](/knowledge/working-with-your-manager/year-end-self-assessment/) half of the review, and it tells you which kinds of results you can realistically commit to repeating. A goal you have already hit a smaller version of is a goal you can defend. ### 3. Decide how many goals, and what mix Before wording anything, settle the shape of the set. Three to five goals is the range most review processes work with — enough to cover a year, few enough to still remember in March. Then split them by type. Indeed's roundup of work evaluation goals sorts them into areas such as productivity, communication, leadership, compliance, innovation, and customer service; the practical version of that split is simpler. Nearly every goal is either a performance goal (a result the business wants this year) or a development goal (a capability you will have that you don't have now). A set that is all performance leaves you no room to grow. A set that is all development reads as though the work itself isn't your focus. The development slot is usually the one people leave blank longest, because naming a gap in writing feels risky. It is less risky than it looks — a specific, named development goal reads as self-awareness rather than weakness. If you are unsure which one to name, a read on [your current skill levels](https://assessment.headwayskills.com/) narrows the field quickly, and whatever it surfaces is something you can build rather than something fixed about you. ### 4. Write each goal so the review can score it Now the wording. Every mainstream performance-management guide anchors this to the same five-part test — [SMART](/knowledge/setting-goals/smart-principles-examples/): specific, measurable, achievable, relevant, and time-bound. Trakstar's guidance for review goals states the standard plainly: a goal is written well enough when you could explain to a colleague exactly what you are working toward, how you will know it is achieved, and by when. "Improve my communication" fails all three. "Cut our average support response time to 24 hours by the end of the year" passes all three. Examples that recur across published goal libraries from TechTarget, Indeed, and PerformYard, grouped by what they measure: **Output and delivery** - Complete assigned work on time or ahead of schedule across the next three review cycles. - Reduce the average time spent on a defined routine task by 15% within six months. - Cut customer support response time to 24 hours by the end of the year. **Communication and collaboration** - Increase positive colleague feedback on communication by 15% by the end of the next review cycle. - Improve peer feedback scores by 10% by year-end by giving teammates more frequent and more specific feedback. - Contribute to at least one cross-functional initiative per quarter, taking on a defined deliverable with a named owner and a deadline. **Customer and stakeholder results** - Maintain customer satisfaction ratings of at least 85% through the final quarter of the year. - Plan and run four customer education sessions by a fixed date, each with a target attendance and a satisfaction threshold. **Development and capability** - Complete one named course or certification before year-end and apply it to a specific piece of work. - Complete a leadership development program and mentor two junior colleagues by mid-year. Read these as patterns rather than scripts. Each one names the thing, attaches a number, and fixes a date — that is the whole mechanism. Swap in your own numbers and your own deadlines and the pattern still holds. ### 5. Check each goal against what your manager and the department are measured on A goal can be perfectly measurable and still be the wrong goal. Case Western Reserve University's HR toolkit puts the rule directly: performance objectives should be linked to key departmental goals and to the employee's job description. So take each draft and name the larger priority it feeds. If you cannot name one, the goal is probably serving your convenience rather than the organization's, and it will quietly lose its place the first time the year gets busy. This is also the step where you catch goals that depend on other people, on budget you don't control, or on a decision that hasn't been made — those need a conversation before they become commitments. ### 6. Bring them to the meeting as proposals, not decisions Case Western's guidance also frames the employee's role clearly: develop and suggest your objectives for discussion with your evaluator. Hold on to that word — suggest. Arriving with drafts hands you the initiative, because the conversation starts from your framing instead of your manager's. Arriving with a finished list you defend line by line achieves the opposite. Annual review meetings typically run 45 to 90 minutes and goal-setting is only one part of that, so send your drafts ahead when you can; a manager reading them cold will default to editing rather than engaging. Expect two of them to change in the room. That is the process working, not a rejection. ### 7. Agree how the goals will stay visible until the next review The most common failure is not a badly written goal. It is a well-written goal nobody looks at again until the following review. Before the meeting ends, agree two things: when you will check progress — most organizations revisit at mid-year, and the more deliberate ones check quarterly — and what evidence will count as progress. Then put the checkpoint in your own calendar rather than waiting to be asked. A goal you have reported on twice during the year is a goal your manager already knows you hit, which turns next year's review into a summary rather than a surprise. ## The skills behind a set of goals that lands Read back over those seven steps and notice how few of them are actually about wording. Most are about reading your manager accurately, choosing a direction that fits you, and seeing yourself clearly enough to name a gap out loud. Those are behaviors, and behaviors can be practiced. **Working with Your Manager** carries most of the weight here. The review is where you and your manager align expectations — agreeing targets that are challenging but achievable, agreeing which decisions are yours to make, and making sure your results are visible long before anyone evaluates them. Treating that as a partnership you help shape, rather than a verdict you receive, is what turns the annual review into something you take part in. **Setting Goals** decides whether the year's targets are yours or somebody else's. The goals that survive twelve months tend to point at work you genuinely want to get better at and at your existing strengths rather than your weakest areas — a shorter horizon, honestly chosen, beats an ambitious one lifted from a template. A goal set mainly to please someone will be quietly renegotiated by spring. **Building Self-Awareness** is what makes the development goal honest. Knowing what you are genuinely good at, and treating feedback as information instead of a threat, is the difference between naming a real gap and naming a safe one. It also makes the self-assessment easier to write: specific about strengths, specific about what comes next. How those three are currently working for you is worth knowing before the meeting rather than after it, because the conversation runs on them whatever your form says. The free Job Skills Test scores you across the twelve work skills these three belong to, so you can walk in [knowing your actual starting point](https://assessment.headwayskills.com/) on each one — and wherever the score is low, that is a gap you can close, not a fixed limit. ## Where this leaves you Some of this may already match how you approach a review — thinking ahead about what your manager needs, or being wary of goals that sound impressive but cannot be scored. Those instincts are worth trusting, and the rest is learnable without becoming a different kind of employee. The weight of it also grows: as the work gets bigger, the goals you set start to shape which projects come your way, not just how a form gets filled in. You are drafting these before the meeting instead of improvising them inside it, which is the part most people skip and the part that decides how the conversation goes. What's left is choosing which skills to build the coming year around. ## Start the year from a clear picture The only thing left is to find out where you are starting from. The **free** Job Skills Test is a short self-assessment of your work skills: in about seven minutes it shows where you stand across all twelve and which of them would make the biggest difference to the goals you are about to agree — so the development goal on your form comes from evidence about you, rather than from whichever example on a list sounded best. ## 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? Examples of work goals for annual review, plus a seven-step process for choosing, wording, and agreeing goals your manager will actually sign off on. ### 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/examples-of-work-goals-for-annual-review/ Preferred summary: "Examples of work goals for annual review, plus a seven-step process for choosing, wording, and agreeing goals your manager will actually sign off on." ## Change log - 2026-07-07: Content collection version published.