# Employee Goals for Evaluation: How to Write Ones That Count Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/employee-goals-for-evaluation/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/employee-goals-for-evaluation.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 Most employee goals for evaluation get copied off a list. Here is how to write goals your manager agrees with, and that still count at review time. ## Key facts - Title: Employee Goals for Evaluation: How to Write Ones That Count - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Influence - Primary keyword: employee goals for evaluation - Source page: https://headwayskills.com/knowledge/working-with-your-manager/employee-goals-for-evaluation/ ## What this page covers - Most employee goals for evaluation get copied off a list. Here is how to write goals your manager agrees with, and that still count at review time. - Practical guidance for employee goals for evaluation - How this topic connects to Working with Your Manager ## Detailed explanation A form has landed in your inbox with a field marked Goals and a date beside it. Good employee goals for evaluation are the ones you agree with your manager before the cycle starts: two to four objectives, each tied to something your team already cares about, written clearly enough that the two of you would score them the same way at the end. That is the real test — not how well a goal is phrased, but whether anyone besides you has agreed it matters. Almost none of the advice you will find online covers the agreeing part. ## You write the goals, but someone else scores them This is what makes your side of the form different from your manager's. A manager who writes goals for a report is setting a standard they will apply themselves. You are writing a standard someone else will interpret, months from now, in a conversation you may not be in the room for. That asymmetry is why wording carries more weight here than it looks like it should. A goal that says you will "support the team on reporting" or "improve communication with stakeholders" leaves the whole judgment open. At review time somebody has to decide whether you did that, and you control neither who decides nor what they had in mind. This is where [the SMART framework](/knowledge/setting-goals/goal-setting-smart-goals/) earns its place. Specific, measurable, achievable, relevant, time-bound — Mitratech, Trakstar, Leapsome and ClearCompany all lead with it, and it is the near-universal framing across every guide on the subject. It is a useful check. But notice what it checks: SMART tests whether a goal is well-formed, not whether it is the right goal. A perfectly SMART objective aimed at something your manager does not care about is still a wasted year. Well-formed and worth doing are two separate questions, and only the first one has a framework. ## Most employee goals for evaluation assume a number you don't own Search for examples and you will find them in bulk. Indeed publishes 45 work evaluation goal examples, PerformYard 60, PeopleGoal more than 30, TechTarget nine. The format is popular because it converts a hard authoring problem into an easy browsing problem — you stop writing and start picking. Look at what the examples contain, though. Leapsome and ClearCompany both offer the canonical set: increase monthly sales by 15% within the next quarter, reduce customer support response time to 24 hours by the end of the year, save 10% on operating costs by the end of the next fiscal year, increase website traffic by 20% in six months. Every one assumes you control a number the business already tracks and already considers yours. In the first years of a career that is usually not the situation. Your work feeds someone else's number. You prepare the analysis that goes into the report that someone else presents; you handle the tickets that roll up into the response-time figure. Copy a goal built for the owner of a metric and you end up with an objective you cannot honestly claim in December, which is worse than a modest one you can. The way out is to measure the part that is genuinely yours: volume you handle without escalating, how long your piece of a process takes, how often something comes back to you for correction, how much of a task you can run start to finish without checking in. "Handle the monthly client reporting pack end to end by June, with no corrections needed from Sara" is a smaller claim than a 15% revenue lift, and it is one that will still be true at the end of the year. ## Nobody will start the goal conversation for you Across the sources that go beyond templates, one mistake comes up more than any other, and it is not a wording problem. Peoplebox and Lattice both name it directly: employees hesitate to take their draft goals to their supervisor, and so lose the input that would have shaped them. The form goes back filled in. The conversation never happens. What makes this worth changing is the other half of the picture. ClearCompany and Quantum Workplace, writing to managers rather than employees, describe goal-setting as something to hand to reports deliberately, because setting your own goals builds ownership of your own path. Read that from where you are sitting and it is useful intelligence: many managers are waiting for a proposal to come up, not preparing one to hand down. If you assume goals arrive from above, you are probably misreading the room. The mechanics are not complicated. Send a draft two or three days before your [next one-on-one](/knowledge/working-with-your-manager/effective-one-on-one-meetings/) so your manager has read it before you are both in the room. Then ask three things: is this the right thing to aim at this year, what would a clearly-exceeded version look like, and is there anything here you would drop. That last question is the one people skip, and it is the one that saves you from spending six months on the goal nobody needed. If it strikes you that this is less about writing and more about a conversation you have never been taught to run, that is the accurate read — and it is worth knowing [how your own habits rate](https://assessment.headwayskills.com/) before the next cycle opens rather than after it closes. ## Your manager sees a fraction of what you actually do Visibility runs one way here. Through the review, your manager gets a structured view of your output. You have no equivalent guarantee that your contribution is visible upward, and in a first job most of what you do sits inside a team's result where it is genuinely hard to see. That changes what the goals are for. They are not only targets; they are the record. What is written down at the start and referred back to during the year is what exists at review time. What was not written down tends to be remembered as the general work of the team. Two things follow. Keep a running note through the cycle — dates, what shipped, what you were asked for and what you delivered. Four or five lines a month is enough to reconstruct a year you would otherwise summarize from memory. And when you describe what you did, use the organization's terms rather than your own task list. Lattice and Culture Amp both make this point: connect the work to efficiency, revenue, customer satisfaction or team performance rather than listing what you were busy with. "Handled 300 tickets" is a task. "Cut the queue's average wait by taking the routine cases off the senior team" is the same work, stated in the terms the review is actually scored in. ## Growth counts as a goal early on Almost every source starts the process in the same place, and it is not the form. Indeed and ClearCompany both open with self-reflection: where you are, where you want to go, [your strengths and weaknesses](/knowledge/setting-goals/strengths-and-weaknesses/), and the feedback you have already been given. That last item is the most usable and the most ignored. The [developmental comment](/knowledge/self-awareness/how-to-take-criticism/) from your last review — the one you nodded at and moved past — is raw material. Turned into a specific objective it becomes this cycle's goal, and it shows that feedback lands with you, which managers score in its own right. The certification version of this is what shows up in the example lists: a PMP or PRINCE2 by a set date. Those are legitimate, but the everyday version often counts for more — running your own one-on-ones properly, taking a client thread end to end without handing it back, presenting a result without a rehearsal. There is a timing point worth knowing. Further up, capability is assumed and only outcomes get scored. Early on, becoming reliably good at something is part of what the organization is buying from you, which means a development goal sits legitimately alongside a delivery goal rather than as a soft addition to it. That window does not stay open indefinitely. ## The work will change before the review does This is the gap in nearly all of the published advice: it treats goal-setting as one event in January and the review as another in December, with nothing in between. In practice the middle is where goals fail. Priorities shift, a project gets shelved, your role quietly changes shape, and the objective you agreed in the spring describes a job you no longer have. You will notice this before your manager does. A manager can retire or reassign a goal whenever they like; you have to raise the mismatch and ask for it to be revised, in writing, at the time. Otherwise you get measured in December against work that left your plate in June, and "the priorities changed" is a far weaker argument after the fact than a revision agreed while it was happening. A short line in a one-on-one — this goal no longer matches what I am working on, can we replace it — costs nothing in the moment and protects the whole cycle. ## The skills behind a goal conversation that works Read back over what the practical advice actually asked of you: start a meeting, listen for what your manager values, look honestly at your own feedback, and make a case for what you want to be measured on. None of that is administrative, and none of it is really about goals. **Working with Your Manager** is doing most of the work here. The relationship runs on aligned expectations rather than good intentions: agreeing what results look like before the period starts, keeping your work visible while it happens, and treating the review as something you prepare for and shape rather than something that happens to you. Ask for what you want, and keep it future-focused. The goal form is simply where that partnership gets written down. **Building Self-Awareness** gives the goals their content. Knowing what you are genuinely good at, rather than merely competent at, is how you pick objectives worth pursuing. And using developmental feedback properly — understanding it first, reflecting before reacting — turns the last review into the raw material for the next one. Asking for specific, future-focused advice gets you input no template can supply. **Influence** decides whether the goal gets supported. Preparation is the core of it: understanding what matters to the other person and how the decision actually gets made, before you make your case. Then taking the initiative to propose rather than wait, and persisting — following up, seeing it through to a delivered result that speaks for itself. Influence here rests on what you deliver, not on how you present it. Those three sit inside a wider set of twelve work skills that keep resurfacing across a career, all of them learnable rather than fixed. The **free** Job Skills Test reads all twelve, which is useful here mainly because it tells you [which one is the bottleneck](https://assessment.headwayskills.com/) in your goal conversation rather than leaving you to guess. ## What this looks like for you Some of this may already describe how you work — the note you keep on what you delivered, the instinct to check before committing to something. Other parts may be the piece you were never shown, which is ordinary; almost nobody is taught how to negotiate the terms of their own evaluation, and it is a gap that closes with practice rather than personality. You can get better at this and still go about it in your own way. The stakes only rise from here. As responsibilities grow, more of what you are judged on gets settled in conversations like this one rather than in the work itself. Getting a handle on it now, while the goals are small and the consequences forgiving, is considerably easier than learning it later. You have already done the part most people skip, which is thinking about what makes a goal worth setting before filling in the box. What is left is knowing which skills you bring to that conversation. ## See where your work skills stand The only thing left is to find out where you are actually starting from. The Job Skills Test is a **free** self-assessment of your work skills: it takes you through all twelve, shows how you currently rate on each, and points to the ones that would make the biggest difference right now — including the ones behind aligning goals with a manager and making your results visible. **[Get my skills profile](https://assessment.headwayskills.com/)** *Free, takes 7 minutes, and your results appear the moment you finish.* ## 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? Most employee goals for evaluation get copied off a list. Here is how to write goals your manager agrees with, and that still count at review time. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Building Self-Awareness, Influence. ### 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/influence.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/employee-goals-for-evaluation/ Preferred summary: "Most employee goals for evaluation get copied off a list. Here is how to write goals your manager agrees with, and that still count at review time." ## Change log - 2026-07-07: Content collection version published.