Why do employee goals slip?

Usually because they were set once and never revisited, or because they were written at a level of abstraction that never connected to the actual work. A goal nobody looks at between the setting and the review is a document, not a goal.

Are SMART goals enough?

They help, and they have a real limit. SMART pushes goals toward things that are easy to measure, which quietly biases them toward the countable over the important. Use the structure, but check that what you ended up measuring is what you actually wanted.

How do I tie goals to real work?

Write them against what the person is genuinely going to spend their time on. A goal that sits outside the actual work becomes a second job nobody has time for, and it is the first thing dropped when the real work gets busy.

How often should goals be reviewed?

Often enough that they can change. Goals set annually and inspected annually cannot respond to a year that turned out differently, and by the time anyone looks, it is too late for the check-in to affect the outcome.

Guide

How to set employee goals

Most goals are set with good intentions in January and forgotten by March. Here is how to set employee goals that survive contact with a real week — plus seven examples you can adapt today.

Why goals slip

Goals rarely fail because the employee stopped caring. They fail for ordinary, fixable reasons. The goal was written once and never revisited. It lived in a document nobody opened. It was vague enough that "progress" was impossible to see. Or it had nothing to do with the work that actually filled the person's day, so it always lost to the urgent thing in front of them.

The fix is not more ambition. It is making goals small enough to track, close enough to real work that pursuing them is the same as doing the job, and visible enough that they come up in conversation. A goal you check on every two weeks is worth ten goals you set and forget.

SMART goals, and where they fall short

The SMART framework is a useful checklist. A goal should be:

Specific — names the thing, not a theme. "Reduce ticket backlog," not "improve support."
Measurable — you can tell whether it happened. A number, a shipped thing, or a clear yes/no.
Achievable — a stretch, not a fantasy. If the person privately thinks it's impossible, it's already dead.
Relevant — it matters to the team's actual priorities, not just easy to measure.
Time-bound — it has a date. "By end of Q3," not "soon."

Where SMART falls short: it nudges people toward whatever is easiest to count. That is how you get a support rep who closes tickets fast and leaves customers angry, or a goal of "send 50 emails" that has nothing to do with whether anyone replied. SMART also assumes the world holds still. Priorities shift, and a goal that made sense in January can be irrelevant by April. Treat SMART as a way to sharpen a goal you've already chosen for good reasons — not as the reason to choose it.

Tie goals to real work

The best goals are barely distinguishable from the job done well. Before you finalize one, ask: if this person did their normal work thoughtfully for a quarter, would they move this goal? If the answer is no, you've created homework, and homework loses to the inbox every time.

A good test is to trace the goal back to something concrete the person already touches — a project, a customer, a recurring problem. If you can't connect it to real work in one sentence, it's probably a goal about looking busy rather than getting better.

Cadence and check-ins

Setting the goal is maybe ten percent of the work. The other ninety is the check-in. Pick a rhythm and hold it:

Quarterly goals are big enough to matter and short enough to stay real.
Every 1:1 (weekly or biweekly), spend two minutes on the goal: what moved, what's stuck, what you can clear.
Mid-quarter, ask honestly whether the goal still makes sense. Killing or rewriting a goal that the world made irrelevant is a sign of good judgment, not failure.

A goal you revisit every two weeks will outperform a more ambitious goal you set once and never mention again. Frequency beats grandeur.

Seven example employee goals

These are written to be specific and measurable while staying tied to real work. Adapt the numbers to your context.

Support rep: Cut median first-response time from 6 hours to under 2 hours by end of Q3, without letting customer-satisfaction scores drop below 90%.
Salesperson: Move 8 stalled deals (open 60+ days) to a clear yes or no by the end of the quarter, so the pipeline reflects reality.
Software engineer: Reduce the team's flaky-test count from 14 to under 5 by end of Q2, and document the two worst offenders so others can maintain them.
Designer: Ship a reusable component library covering the five most-used UI patterns by July, cutting new-screen design time noticeably.
Marketer: Publish six customer case studies this quarter and get at least three cited by sales in live deals.
Operations / admin: Document the three processes only you currently know, so any teammate can run them, by end of next month.
New manager: Hold a consistent biweekly 1:1 with every direct report for a full quarter, and end each one with a written, agreed next step.
Individual development: Lead one cross-team project end to end this half, presenting the outcome to the wider team — building the visibility needed for the next role.

Notice what these share: a number or a clear deliverable, a date, and an obvious link to work the person already does. That combination is what makes a goal stick.

The fast way: let it capture itself

Goals slip when they live in a document nobody opens. Performle keeps each report's goals next to your 1:1 notes, so progress comes up naturally every time you talk — no separate tracker to maintain. Stuck on what to set next? Its goal coach suggests a few tailored goals for a person — each with the why and how to measure it — that you can add with a click or ignore.

Start a 14-day free trial →