Most projects start with an intention: "improve the customer experience", "digitalise the ordering process", "become more efficient". These give a direction. None of them says what has to exist at the end, which means everyone carries their own version of success until the day it matters.
What a SMART objective is
A SMART objective states the result the project has to produce, in terms precise enough that two people reading it describe the same ending.
The acronym names five criteria: Specific, Measurable, Ambitious and action-oriented, Realistic, Time-bound. They are not an administrative checklist. They force one question: when will we be able to say this project is finished?
If that question has no clear answer, what you are holding is not yet an objective. It is still an intention.
The five letters, and what each one rules out
Each criterion exists to remove one kind of objective that does not hold up. Taken one at a time, each has a question that settles it.
- Specific: it names a result, not a territory. "Improve customer satisfaction" is a territory; "bring first response time under 4 hours" is a result. The question: would two readers describe the same ending?
- Measurable: the outcome can be observed without arbitration. It does not have to be a number: "the module is in production and used by all three branches" is observable too. The question: who checks, and against what evidence?
- Ambitious and action-oriented: it commits you to doing something, and to more than the status quo. An objective you would reach by changing nothing is not a project objective. The question: what do we do differently because of it?
- Realistic: it accounts for the means you actually have, not the ones you hope for. This is the criterion you cannot judge alone; it is settled with the people who will do the work. The question: with today's team and budget, does it hold?
- Time-bound: a date, not a season. "End of Q1" leaves three months of interpretation. The question: on what date will we know it is won or missed?
Miss one criterion and the objective becomes negotiable again, which defeats the point. A result that is renegotiated at every meeting is no longer a reference.
Where SMART comes from, and why the A keeps changing
The acronym has not always had the letters we use. It comes from George T. Doran, who published it in November 1981 in Management Review, under the title "There's a S.M.A.R.T. way to write management's goals and objectives". His five criteria were Specific, Measurable, Assignable, Realistic, Time-related.
The third one is worth a pause. Assignable meant: you know who the objective is given to. Not achievable, not ambitious: assignable. Doran held that an objective with no named owner was not an objective at all.
That A has drifted, and it is still drifting. Depending on the source you will read Achievable, Attainable, Ambitious or Action-oriented. The R went the same way: Realistic in Doran's text, now often Relevant. This is not a translation error, it is usage moving, but it explains why two teams that both say they "do SMART" are not checking the same thing.
Doran also set a limit that usage has forgotten: not every objective has to be quantified at every level of management, and forcing a number sometimes produces a measure nobody looks at.
Source: George T. Doran, "There's a S.M.A.R.T. way to write management's goals and objectives", Management Review, vol. 70, no. 11, November 1981.
What a SMART objective is not
Three other objects on a project get confused with it. None of them plays the same role.
| What it is | How many per project | |
|---|---|---|
| The objective | The result expected, and the condition for calling the project finished | One, sometimes two |
| A deliverable | A concrete thing to produce in order to get there | As many as the breakdown holds |
| An indicator | A measure watched during the project, saying where you stand | A handful |
| A milestone | A date marking a passage, producing nothing itself | A handful |
The costly confusion is the first one. "Deliver the new portal" is a deliverable: you will know it was delivered, not that it was any use. The objective is what the portal has to produce once it exists. An objective is then broken down into deliverables, which is the job of a work breakdown structure, never the other way round.
Confusing the objective with an indicator costs less but misleads as much. An indicator is watched continuously and serves to steer. The objective is checked once, at the end.
Three intentions, three objectives
The difference shows better on examples than on a definition. On the left, what a project usually starts with. On the right, what holds up in front of a steering committee.
| The starting intention | The objective |
|---|---|
| Improve customer satisfaction | Bring first response time under 4 working hours for 90% of support requests, by 30 June |
| Digitalise the ordering process | Let all 40 sales reps enter an order from mobile, with no re-keying into the ERP, before the September return |
| Become more efficient on payroll | Cut the monthly payroll close from 5 days to 2, at constant headcount, from the March close onwards |
Notice what the three right-hand cells share: each one says how you will see that it is done. And none of them says how to go about it: that is the work of scoping, which comes next.
What it changes
A SMART objective clarifies the expected result, so the discussion stops being about the intention and becomes about something observable. It makes success checkable: reached, partly reached, or missed.
It also helps you decide. A request that does not contribute to the objective is easier to challenge, and the conversation moves from taste to contribution. That is the same test a prioritisation matrix applies later, line by line.
What it does not replace
A SMART objective is not a plan, and it is not a scope. It says what has to be true at the end, not what has to be produced or in what order. The constraints it has to live within (the date, the budget, the content) are the three sides of the iron triangle, and a realistic objective is one that respects them.
It is also not written alone. The Realistic criterion cannot be judged from a desk, and Doran's Assignable is a reminder that an objective nobody owns stays a sentence.
In short
A SMART objective is specific, measurable, ambitious and action-oriented, realistic and time-bound. It turns an intention into a result that can be checked, shared and defended.
Everything else on the project (deliverables, indicators, milestones) hangs off it, and none of them replaces it. The test fits in one question: on what date, and on what evidence, will we say this is done?
