How to Set SMART Goals to Improve Performance Management

If you’ve sat in a performance review and heard “let’s set some SMART goals,” you’ve already met one of the most common tools in performance management. The idea is simple: turn a vague hope (“do better this year”) into a clear target that people can actually work toward.

In this article we’ll look at what SMART means, where it came from, how it connects to goal-setting theory, and where it falls short. We’ll also walk through one workplace example so you can see how the letters play out in practice.

Where Did SMART Goals Come From?

The SMART acronym is usually traced to a short 1981 article by George T. Doran in Management Review. Doran was writing for managers who had to write corporate and departmental objectives, and he offered SMART as a practical checklist.

His original letters were a bit different from the version most textbooks use today:

  • Specific: target a specific area for improvement.
  • Measurable: quantify progress, or at least suggest an indicator.
  • Assignable: specify who will do it.
  • Realistic: state what can realistically be achieved with the resources available.
  • Time-related: say when the result should be achieved.

Over time the letters shifted. The version you’re most likely to see in OB classes and HR handbooks is Specific, Measurable, Achievable (or Attainable), Relevant, and Time-bound. “Assignable” became “Achievable” once people started using SMART for personal goals as well as assigned ones. “Realistic” was often replaced by “Relevant,” so the checklist also asked whether the goal mattered to the job or the organization.

You’ll also see other variants (Ambition, Agreed, and so on). That’s fine for exam purposes as long as you know which version you’re using. The point of the mnemonic hasn’t really changed: write goals that are clear, checkable, and useful.

What Does Each Letter Mean?

Let’s take the common classroom version and unpack it.

Specific. The goal names a clear outcome, not a vague direction. “Improve customer service” is too broad. “Reduce average call handling time” is specific enough that everyone knows what we’re talking about.

Measurable. We need a way to tell whether progress is happening. That might be a number (calls per hour, error rate, sales), a milestone (proposal submitted), or a clear yes/no (certification completed). If we can’t tell whether we’ve got there, we can’t manage the goal.

Achievable / Attainable. The goal has to be within reach given the person’s skills, time and resources. Stretch goals can be useful, but a target that is obviously impossible just demotivates people. We’ll come back to this when we look at Locke and Latham, because “achievable” and “difficult” are not the same thing.

Relevant. The goal should matter to the role and to what the organization is trying to do. A neat, measurable target that doesn’t help the team or the business is just busywork.

Time-bound. There is a deadline or a review date. Without one, the goal drifts. “By the end of Q2” or “within 90 days” gives everyone a shared clock.

A Running Example: Priya and the Call Center Team

This is a hypothetical example.

Imagine Priya manages a customer support team of 12 in a mid-sized insurance firm. In last year’s appraisal her director said the team’s first-contact resolution rate was too low. Customers were calling back, and that was driving up cost and frustration.

A weak goal for Priya’s year would be: “Improve first-contact resolution.” It’s the right topic, but it’s not SMART. Nobody knows by how much, by when, or how they’ll measure it.

A SMART version might look like this:

“Raise the team’s first-contact resolution rate from 62% to 75% by 30 June, measured from the CRM weekly report, without increasing average handle time above 6 minutes.”

Let’s check the letters:

  • Specific: first-contact resolution, not “customer service” in general.
  • Measurable: 62% to 75%, tracked in the CRM.
  • Achievable: a 13-point lift is ambitious for six months, but Priya has coaching time and a new knowledge base, so it’s not fantasy.
  • Relevant: it cuts repeat calls, which is what the director cares about.
  • Time-bound: 30 June.

We’ll come back to Priya as we look at theory and at the limits of SMART.

How Does SMART Connect to Goal-Setting Theory?

SMART is a writing checklist. Goal-setting theory, developed by Edwin Locke and Gary Latham, is a research-backed theory of motivation. They are related, but they are not the same thing.

Across decades of studies, Locke and Latham found that specific, difficult goals usually produce higher performance than vague “do your best” instructions, as long as people are committed, get feedback, and have the ability to do the work. Goals work by directing attention, increasing effort and persistence, and pushing people to find better strategies.

So where does SMART fit?

The Specific and Measurable letters line up well with the theory. Vague goals don’t focus attention. Measurable goals make feedback possible, and feedback is one of the theory’s key moderators.

The Time-bound letter also helps, because a deadline creates a clear performance window.

The tension sits in Achievable. Goal-setting theory says difficult goals raise performance more than easy ones. SMART’s “achievable” is often read as “be realistic, don’t set the bar too high.” Those two ideas can pull in opposite directions. A goal can be achievable in the sense that it is possible with effort, and still be difficult. Priya’s 75% target is a good example: it’s hard, but not impossible.

Relevant is useful for managers, but it isn’t a core variable in the classic theory. Commitment, self-efficacy, task complexity and feedback matter more in the research.

In short: SMART is a handy mnemonic for writing clearer objectives. Locke and Latham give us the deeper account of why clear, challenging goals change performance. If you’re studying OB, treat SMART as a practical tool that borrows from goal-setting research, not as a substitute for the theory.

Why Do Managers Use SMART Goals in Performance Management?

Managers reach for SMART for a few practical reasons.

First, it reduces ambiguity. When Priya and her director write the 75% target down, both of them know what “good” looks like at the mid-year review. That makes approaching an appraisal less of a guessing game.

Second, it supports fairer conversations. A measurable goal is easier to discuss than a gut feel. In the appraisal interview, Priya can bring the CRM chart rather than argue about whether the team “tried hard.”

Third, it links individual work to team and organization priorities. If the firm needs fewer repeat calls, SMART goals are one way to cascade that priority into day-to-day targets.

And fourth, it helps with planning. Once the goal is clear, Priya can ask what coaching, scripts or knowledge-base updates the team needs. The goal becomes a plan, not just a hope.

What Are the Limits of SMART Goals?

SMART is popular, and that popularity can hide its gaps.

It is a mnemonic, not a theory. Doran’s article was a short practical note. It does not explain the psychological mechanisms the way Locke and Latham do. Students sometimes treat SMART as if it were the whole of goal-setting research. It isn’t.

It is vague on difficulty and commitment. “Achievable” doesn’t tell a manager how hard the goal should be, or how to build commitment when the target is set from above. Theory says commitment and difficulty both matter. SMART barely mentions them.

It underplays feedback. A measurable goal without regular feedback is still a weak system. Priya needs weekly CRM numbers, not a surprise chart in June.

It can push people toward easy metrics. What gets measured gets managed. If Priya’s only target is first-contact resolution, agents might close calls quickly and miss complex cases, or discourage customers from asking follow-up questions. Good SMART goals often need guardrails (like her handle-time limit) so one metric doesn’t wreck another.

Not every worthwhile goal fits neatly. Some development goals are hard to quantify early on (“become a stronger coach for new starters”). Forcing a fake number onto a learning goal can create busywork. In those cases a clear learning goal with milestones may be better than a pseudo-SMART target.

So we should use SMART where it helps, and not pretend it covers everything that matters in motivation and performance.

Practical Tips for Using SMART in Performance Management

A few habits make SMART more useful and less ritual.

Write the goal as an outcome, then check the letters. Start with what needs to change, then test it against SMART. Don’t start with the acronym and invent a goal to fill the boxes.

Keep difficulty in view. Ask: is this a stretch that people can reach with effort and support, or an easy target that won’t change much? Easy SMART goals feel comforting and achieve little.

Agree how progress will be reviewed. Monthly check-ins beat a once-a-year surprise. Feedback is part of the system, not an optional extra.

Watch for gaming. If a metric can be hit in a way that harms customers or colleagues, add a quality constraint or a second measure.

Link individual goals to team goals. Priya’s 75% target should sit under a team or department objective, so agents can see why it matters.

Leave room for learning goals. When the task is new or complex, a learning goal (“identify the three main causes of repeat calls and test two fixes by March”) can work better than a pure performance target at the start.

Back to Priya. By March her CRM shows 68%. That’s short of 75%, but the trend is up. In the check-in she and the director look at which call types still bounce back, adjust coaching, and keep the June deadline. The SMART goal didn’t magically fix performance. It gave them a shared target and a reason to review progress while there was still time to act.

Key Points to Take Away

  • SMART is a practical checklist for writing clearer goals, usually Specific, Measurable, Achievable, Relevant and Time-bound.
  • George T. Doran’s 1981 version used Specific, Measurable, Assignable, Realistic and Time-related. Letter meanings have shifted over time.
  • SMART helps performance management by reducing ambiguity and supporting fairer appraisal conversations.
  • Locke and Latham’s goal-setting theory is broader: specific, difficult goals raise performance when people have commitment, feedback and ability.
  • SMART is weak on difficulty, commitment and feedback, and it can encourage metric gaming if used carelessly.
  • Use SMART as a writing tool, not as a full theory of motivation, and pair it with regular review.
Sources
  • Doran, G. T. (1981). There’s a S.M.A.R.T. way to write management’s goals and objectives. Management Review, 70(11), 35–36. PDF copy
  • Locke, E. A., & Latham, G. P. (2002). Building a practically useful theory of goal setting and task motivation: A 35-year odyssey. American Psychologist, 57(9), 705–717. PDF
  • Farrington, J. (2014). Objectify this: A brief history of SMART criteria. jfarrington.com
Scroll to Top