Why Most Performance Goals Fail Before They Start

By Ty Sutherland

Most managers know they’re supposed to set performance goals. What they don’t always know is how to write goals that actually do something useful. The result is a lot of goals that sound reasonable on paper — “improve communication,” “be more proactive,” “take ownership of projects” — but give employees almost nothing to act on.

The problem isn’t effort. Most managers put real thought into their people’s development. The problem is specificity. A goal without enough detail to guide behavior isn’t really a goal. It’s a wish. And wishes don’t show up in performance reviews in any useful way.

This article walks you through how to write performance goals that are concrete enough to be useful — for your employees, for your reviews, and for your own credibility as a manager.

What “Specific” Actually Means in a Performance Goal

Specificity in a performance goal means three things: what the person will do, how you’ll know they did it, and by when. If your goal is missing any of those three, it’s not specific enough.

Here’s a common example of a vague goal:

• Vague: “Improve customer satisfaction.”

Now here’s the same goal made specific:

• Specific: “Increase our team’s average customer satisfaction score from 3.8 to 4.2 on post-call surveys by the end of Q3, by following up on unresolved tickets within 24 hours.”

The specific version tells the employee what the target is, how progress will be measured, when it needs to happen, and what behavior is expected to get there. That’s something they can actually work toward.

The Four Elements of a Useful Performance Goal

You don’t need a complicated framework to write a good goal. You need four elements. Build every goal around these and you’ll avoid most of the common problems.

1. A Clear Behavior or Outcome

Start with what the employee will actually do or produce. Use action verbs that describe observable behavior: complete, deliver, reduce, increase, present, respond, document, implement. Avoid verbs that describe internal states: understand, appreciate, demonstrate commitment, show initiative. Those are impossible to measure and open to interpretation.

If you can’t describe what success looks like in behavioral terms, go back and ask yourself: what would this person actually be doing differently if they were hitting this goal?

2. A Measurable Target

The target doesn’t always have to be a number, but it should be something you can verify. Numbers are cleanest — response time in hours, sales volume in dollars, error rate as a percentage. But qualitative targets can work too, as long as they’re tied to an observable output. “Submit a first draft of the onboarding guide by March 31” is measurable. “Work on the onboarding guide” is not.

When there’s no obvious metric, ask: what would I see or read or review that would tell me this goal was met? That answer is your measure.

3. A Timeframe

Every goal needs a deadline. Without one, there’s no urgency and no natural checkpoint for a conversation about progress. Deadlines also help you catch problems early — if someone is halfway through the quarter and nowhere near on track, you want to know that now, not at the end.

For annual goals, build in quarterly or monthly checkpoints. Don’t wait for the year-end review to find out a goal never got started.

4. A Connection to Context

The best goals explain why they matter. This doesn’t need to be a paragraph — one sentence is enough. “This supports our Q2 goal of reducing customer churn” or “This will free up three hours per week of the team’s time for higher-priority work.” Context helps employees prioritize and helps them stay motivated when the work gets hard.

It also helps you. When you can articulate why a goal matters, you’re more likely to have written a goal that actually reflects what you need from this person — rather than a goal that just fills a box on a form.

Common Mistakes Managers Make When Writing Goals

Even managers with good intentions tend to fall into the same traps. Here are the most common ones and how to avoid them.

Writing Goals That Are Too Broad

“Develop leadership skills” is a goal that could mean a hundred different things to a hundred different people. Break it down. What specific leadership skill? In what context? By what measure? A narrower goal — “Lead the weekly team meeting independently for the next eight weeks, gathering feedback from attendees after each session” — is harder to write but infinitely more useful.

Confusing Activity With Outcome

A goal that measures activity rather than outcome looks like this: “Attend three training sessions on project management.” That tells you what the employee did, not whether it made any difference. Better: “Apply the project scoping framework from the PM training to two upcoming projects by end of Q2, and present scope documents to stakeholders for sign-off.” Now you’re measuring whether the learning translated into something real.

Setting Goals Without Employee Input

Goals handed down from above without conversation tend to land poorly. Employees who had no say in their goals are less likely to own them. More practically, they may know things you don’t — about what’s actually achievable, what roadblocks exist, what resources they’d need. Build goals collaboratively where possible. You still own the final direction, but input makes the goal better and the employee more committed to it.

Writing Goals That Depend Entirely on Others

Be careful about goals that hinge on factors outside the employee’s control. “Close $500,000 in new business this quarter” sounds specific, but if your employee is in a support role that only assists sales, they can’t control whether deals close. Tie goals to actions and outputs within the person’s sphere of influence. If external factors matter, acknowledge them — and build in a discussion point for what to do if circumstances change.

Letting Goals Sit Untouched Until Review Time

Writing a good goal and then forgetting about it for six months defeats the purpose. Goals should come up in your regular one-on-ones. Not as an audit, but as a genuine check-in: how’s it going, what’s in the way, do we need to adjust anything? Goals that get revisited regularly actually get worked on. Goals that don’t get revisited become a source of anxiety at review time and not much else.

A Simple Formula to Get Started

If you’re staring at a blank screen trying to write a goal, use this fill-in-the-blank structure to get a draft down:

[Employee name] will [action verb + specific output] by [date], measured by [metric or observable evidence], in order to [connection to team or business priority].

For example: “Marcus will reduce average ticket response time from 18 hours to under 8 hours by June 30, measured by our helpdesk reporting dashboard, in order to improve customer satisfaction scores and reduce escalations to senior staff.”

It’s not the most elegant sentence, but it contains everything you need. You can refine the language later. The structure is what matters at this stage.

How Many Goals Is the Right Number?

Less than you think. Three to five goals per review period is the right range for most roles. More than that and priorities get diluted — everything matters equally, which means nothing gets treated as urgent.

If you’re feeling pressure to write eight or ten goals to cover every dimension of someone’s job, step back. Ask yourself: what are the two or three things that would genuinely move the needle for this person and for the team over the next six months? Start there. You can note other expectations as ongoing responsibilities without turning them into formal goals.

Quality beats quantity every time. A well-written goal with a clear target and a real conversation behind it is worth more than five vague goals that never get looked at again.

Adjusting Goals When Circumstances Change

Managers sometimes treat written goals as contracts that can’t be changed once set. That’s a mistake. If a priority shifts, a project gets cancelled, or an employee moves into a different role mid-year, the goal should be updated to reflect reality.

Sticking with an outdated goal because it was agreed to in January creates a situation where everyone is pretending to care about something that no longer matters. It also damages trust — employees notice when the work they’re being evaluated on has nothing to do with what they’ve actually spent the last six months doing.

Build in a formal mid-year check to review and adjust goals as needed. Make this a normal part of your process, not an exception. Goals are planning tools, not performance traps.

Using Goals to Support Development, Not Just Accountability

Performance goals serve two purposes, and both matter. The first is accountability — making clear what’s expected and giving you something concrete to evaluate. The second is development — helping the employee grow in ways that benefit them and the team.

The best goals do both at once. A goal that pushes someone slightly beyond their current comfort zone, with enough support to succeed, builds capability and demonstrates confidence. That’s motivating in a way that a pure accountability goal often isn’t.

When you’re writing goals, ask yourself: does this goal help this person get better at something? If all five goals are just “keep doing what you’re already doing, but measure it,” you’ve missed an opportunity. Look for at least one goal that involves the employee learning or applying something new.

The Bottom Line

Writing useful performance goals is a skill, and like most management skills, it gets better with practice. The foundation is specificity: a clear behavior or outcome, a measurable target, a timeframe, and a connection to what matters. Build your goals on those four elements and you’ll have something you can actually use — in check-ins, in coaching conversations, and at review time.

Vague goals don’t just fail to measure performance. They quietly communicate that you haven’t thought carefully about what you need from someone. Specific goals do the opposite. They tell your employees that you’ve invested real thought in their work and that you’re serious about helping them succeed.

That’s worth the extra twenty minutes it takes to write them well.