SMART Goals: What They Are and How to Write Them

SMART is the five-letter test that tells you whether a goal is written well enough to be worth the work. Each letter adds one requirement. The goal has to be specific, measurable, achievable, relevant and locked to a time frame. The test does not choose the goal for you. It checks how you phrased it, so that months from now nobody wastes an hour arguing about whether you actually hit the mark. George T. Doran put the idea on paper in 1981 in Management Review, and it still works as the first filter to run.

Keep reading and you get the meaning of the five letters, a step-by-step method for turning a vague wish into a measurable target, good and bad examples side by side, the real difference between SMART and OKRs, the mistakes that sink most goals, and a template you can copy before you close this page.

What SMART stands for: the five criteria

Five criteria, nothing hidden. A goal that clears all five can be understood by anyone, tracked over time and judged without a meeting about feelings.

Letter	Criterion	The question it answers
S	Specific	What exactly do you want to achieve?
M	Measurable	Which figure will show that you reached it?
A	Achievable	Is it possible with the real resources and time?
R	Relevant	Why does it matter, and which strategy does it fit?
T	Time-bound	By when does it have to be done?

Where SMART comes from (and why the letters change)

The acronym comes from a paper by George T. Doran, published in November 1981 in Management Review: “There’s a S.M.A.R.T. way to write management’s goals and objectives”. His original letters were specific, measurable, assignable, realistic and time-related. The A meant assignable, tied to a named owner, and the R meant realistic. The version that spread later swapped the A for achievable and the R for relevant. Both are adaptations of the same framework, and knowing that saves you an argument when two teams use different letters for the same test.

The five criteria, one by one

Specific

Your goal has to say what you are after and what it applies to. “Improve the system” tells nobody anything. “Reduce the response time of the web server” tells everybody exactly what is on the table. The test is simple. Read your goal to two people. If both picture the same thing, it is specific. If they do not, keep narrowing. Ask what, about what, and to what end.

Measurable

Now attach a number. A percentage, a duration, a count of incidents. Without a figure you cannot tell if you are moving, and you cannot claim a win. This is where indicators and KPIs earn their place. Choose the metric as carefully as you choose the target, because measure the wrong thing and you will spend a quarter optimising something worthless. One question settles it. Which number moves when this works?

Achievable

An impossible goal demoralises a whole team and a trivial one motivates nobody. The useful zone sits in the middle, at a real stretch you can reach with the people and money you actually have. If the goal demands more than you own, split it into stages or set an intermediate target first. Ask two questions. Do we have the tools, the time and the people? What would have to change to make it feasible?

Relevant

It has to matter, and it has to line up with what the team is already fighting for. Hitting it should change something you can point at. Fewer incidents, more uptime and better-served customers. If reaching the goal changes nothing that matters, it does not deserve the hours. Ask who benefits.

Time-bound

A goal with no date cannot be judged, because “forever” fits anything. A deadline concentrates effort and lets you tell success from failure. On long projects you can break it into milestones. Ask by when, and ask what has to be ready at each stage.

How to write a measurable SMART goal, step by step

Here is the deal. Writing a goal is four decisions made in order, and the sentence comes out at the end.

1. Start from the outcome

Phrase your goal as a result. A to-do list is a different animal. “Install a monitoring tool” is an activity. “Cut the mean time to detect incidents” is an outcome, and the installation is only one way to get there. Keep the two apart and you stop confusing motion with progress.

2. Pick the indicator and its baseline

Before you fix the target, measure where you stand. If response time is 500 ms today, that number is your baseline. A good indicator is concrete, measures the same way every time, and depends on something you control. If your goal starts from a problem you do not understand, diagnose the cause first. Treating the symptom rarely helps, which is exactly what happens when a slow computer gets “fixed” by tinkering with a setting that was never the problem.

3. Set the threshold and the deadline

With the baseline clear, decide how far you want to go and by when. “Reduce from 500 ms to 200 ms in six months” is checkable. “Improve performance” is not. Make the threshold demanding but possible, and match the deadline to the size of the change.

4. Give it an owner

A goal with no owner goes nowhere. Doran’s original list carried this letter as the old A for assignable. Every goal needs a person or a role who answers for it and speaks up the moment it drifts.

With those four pieces in place, the sentence almost writes itself. The pattern: measurable verb + indicator + baseline → target + main means + deadline and owner.

Verbs that commit to nothing	Measurable equivalents
Improve, optimise, boost	Reduce or increase something by a specific amount
Modernise, update	Migrate X systems before a given date
Increase quality	Cut defects or incidents to N per period
Speed up, streamline	Shorten a process time from A to B
Strengthen security	Close N critical vulnerabilities before a given date

SMART goal examples: good and bad

The fastest way to learn this is to place a vague goal next to its corrected version, figure and deadline included.

Badly written goal	SMART goal
Improve service availability.	Raise the availability of critical services from 99.5% to 99.9% in 9 months, with redundancy on the key components.
Reduce support incidents.	Cut repeat incidents from 40 to 25 per month in one quarter, fixing the three most frequent causes.
Be more productive.	Reduce deployment preparation from 2 hours to 30 minutes before the end of the year, by automating manual steps.
Improve security.	Close critical vulnerabilities within 30 days and high ones within 90, with a monthly review.
Train the team.	Have 100% of the team complete incident-response training before 30 June, with one live drill per person.

A full example, letter by letter

Goal: reduce the response time of the web server.

S	M	A	R	T
Reduce the response time of the web servers.	Bring it down from 500 ms to 200 ms on average.	By optimising the server configuration and the content delivery network.	To improve the user experience and customer satisfaction.	Within six months.

In one sentence: “Reduce the response time of the web servers from 500 ms to 200 ms in six months by improving the server configuration and the content delivery network, in order to improve the experience of users and customers.”

SMART goals for IT and technical teams

Technical work is packed with goals that are easy to say and hard to prove, so the filter earns its keep there. A few phrasings survive it.

• Reliability: raise the availability of a critical service from 99.5% to 99.9% within two quarters, by removing single points of failure.
• Delivery: cut the median lead time for a change from ten days to three before the end of the quarter, by automating the build and test pipeline.
• Security: remediate all critical vulnerabilities within 15 days and all high-severity ones within 60, with a monthly exposure review.
• Cost: reduce cloud spend per active user by 20% over six months, without lowering the agreed service level.

Notice the shared shape. An indicator, a baseline, a target and a date. Only the metric changes from one case to the next. A goal such as “improve observability” fails all five letters at once, while “give every production service a dashboard and an alert threshold before the end of March” clears them without much effort.

SMART vs OKRs: differences and when to use each

OKRs (Objectives and Key Results) are another framework, popularised by Intel and adopted by plenty of technology companies. People often frame them as SMART’s rival, yet the two answer different questions. SMART is a writing test that says whether a goal is well put together. An OKR is a management structure that splits an ambitious objective into a handful of measurable results.

	SMART goals	OKRs
What it is	A filter for writing each goal well	A system of objective + key results
Scope	Any goal, individual or team-level	Team or organisation goals
Ambition	Realistic and achievable	Stretching, with room to fall short of 100%
Measurement	The goal carries its own figure and deadline	The key results carry the figures
Horizon	Whatever the goal requires	Usually quarterly
Relationship	Complementary	Can be written using the SMART filter

In practice you combine them. You set a quarterly OKR and run each key result through the SMART filter to confirm it is specific, measurable and dated. The real difference comes down to ambition. SMART assumes you should be able to deliver, while an OKR accepts that something may be left on the table. That balance between stretching and realistic targets is what Harvard Business Review examines. The tension has pushed some teams to question SMART in fast-moving environments, and the FAST framework by Donald and Charles Sull, published in MIT Sloan Management Review, proposes goals that are discussed often, ambitious, specific and transparent, because a target fixed once a year can go stale. SMART still holds up. Just do not turn it into a straitjacket.

What SMART is good for: benefits and limits

When goals clear the filter, several things show up at once. Clarity, because everyone understands what is being chased and how it is measured. Tracking against an objective yardstick instead of a hunch. Motivation from targets that are achievable and dated. And alignment with what actually matters. For a team, that alignment is the same reason working well as a team depends on shared, visible targets instead of private intentions.

But SMART has limits. It can run rigid when the world changes under a perfectly written goal. It can drift into an over-focus on the result that ignores what the journey teaches. And there is one classic trap. Once a metric becomes the goal, people optimise the metric and stop caring about the outcome, like chasing “close tickets” by shortening the logging time instead of solving the real problem. Frameworks organise effort and leave the choosing to you. A time-blocking technique gives structure to the day without deciding what you work on, and SMART organises your goals without setting your priorities.

Common mistakes when setting SMART goals

• Confusing the task with the outcome. “Roll out a system” is a means. The goal is what it should achieve.
• Measuring what is easy rather than what matters. A convenient indicator can miss the actual problem.
• Figures with no baseline. “Improve by 20%” means nothing when you do not know where you started.
• Impossible or trivial goals. Unreachable targets demoralise, and ones already met teach nothing. Aim for the middle.
• No deadline and no owner. A goal for “some day” with nobody responsible is a wish.
• Too many at once. Make everything a priority and nothing is. A small, well-chosen handful wins.
• Setting them and forgetting them. A goal nobody reviews goes out of date.
• Treating SMART as paperwork. Filling five boxes out of obligation satisfies the form and misses the point.

SMARTER and other variants of the acronym

Over time, variations have appeared. The best known is SMARTER, which adds Evaluation and Review. Under that version you assess progress as you go and revisit the goal to check whether it still matters. Others add Ethical to stress honest measurement. The underlying idea stays the same. A goal is a working document you keep returning to.

A template for writing SMART goals

This template gathers everything above. Fill in the blanks and check that none is left empty.

Goal:
  [Measurable verb] [indicator] from [baseline] to [target]
  by [deadline], through [main means or action].

Check:
  S - Specific    -> What, about what, and to what end?
  M - Measurable  -> Which figure proves it?
  A - Achievable  -> With which resources and in what time?
  R - Relevant    -> Who benefits, and which priority does it fit?
  T - Time-bound  -> What is the deadline and what are the milestones?
  +   Owner       -> Who is accountable for making it happen?

Worked example:
  Reduce the response time of the web servers from 500 ms
  to 200 ms in 6 months by optimising the configuration and
  the content delivery network. Owner: systems team.

A simple routine: write the sentence without thinking about the letters, then walk it question by question. If any of the six, the five in SMART plus the owner, has no clear answer, that is the part to fix.

Conclusion

SMART goals are how you make sure that what you set out to do can be understood, tracked and checked. The acronym dates back to 1981 and George T. Doran, and it still holds up because it solves a problem every team meets: goals so vague that nobody ever knows whether they were met. It is not the only tool. OKRs bring ambition and rhythm, and frameworks such as FAST remind you that context changes. As a quality check before you commit, though, it is hard to beat. For goals you carry alone the same discipline pays off, and treating your own targets with the rigour you apply at work sits at the heart of a proactive attitude. So take one goal you are carrying right now, write the sentence with a figure and a date, and name the owner before the day ends.

Frequently asked questions

What is the difference between a goal and an objective?

They are used as synonyms in practice, but it helps to separate them. The goal is the general destination, such as more reliable services, and the objective is the concrete, measurable result that moves you towards it. SMART applies to the objective. The underlying aspiration can stay broad.

Do SMART goals work for personal goals or only for companies?

They work for anything you want to be able to verify. Learning a language or preparing for an exam benefits from the same filter of pinning down what, how much and by when. The only difference is the owner, who in personal goals is you.

What if my goal cannot be measured with a number?

It can almost always be turned into something observable. If the result is qualitative, look for an indirect indicator: a scaled survey, a completion percentage, a number of cases resolved. If you genuinely cannot find any measurable signal, the goal may need rewording so that it produces a checkable effect.

Can you use SMART and OKRs at the same time?

Yes, and it is common. The OKR sets the ambitious objective and its key results. SMART is applied to those results to make sure they are well written, with a figure and a deadline. They work together: one sets the direction and the other sharpens the wording.