HR & performance glossary
What are SMART goals?
SMART goals: Goals written to meet five criteria — specific, measurable, achievable, relevant and time-bound — so everyone can tell what will change, how it will be measured and by when.
Definition
SMART goals are goals written to meet five criteria: specific, measurable, achievable, relevant and time-bound. The acronym is a test for the wording of a goal rather than a method for choosing it. A goal that passes all five says exactly what will change, how anyone will know, why it is realistic, why it matters to the team and when it will be done.
The letters have picked up variants over the years — attainable for achievable, realistic for relevant, timely for time-bound — but the intent is the same. SMART is most useful for individual and team goals, where the gap between a vague intention such as ‘improve customer service’ and a usable goal such as ‘resolve 75% of tickets on first contact by the end of June’ is the difference between a clear review conversation and an argument about what was meant.
SMART goals are not a rival to OKRs or KPIs. SMART describes how a single goal is written, not how a set of goals is organised. A key result can, and usually should, meet the SMART criteria; a KPI target becomes a SMART goal once someone owns it and a date is attached.
How it works in practice
Most organisations use SMART goals at two points in the performance cycle. At the start of a period, an employee and their manager agree a small number of goals, each tested against the five criteria and linked to a team or organisation objective, so its relevance is visible rather than asserted. At the end of the period, the same wording is what the goal is assessed against, which is why precision at the start saves disagreement later.
In practice the criteria are easiest to apply in order. Start with the outcome and make it specific; choose the measure and record today’s baseline; check the target against the time and resources available; confirm the objective it serves; then set the deadline and one or two checkpoints. Development plans benefit from the same discipline: ‘improve presentation skills’ becomes useful only when it names a presentation, a date and the feedback that will show progress, which is why individual development plans are best written as SMART actions with an owner and a due date.
Goals are then revisited at regular check-ins. If priorities change mid-period, the goal is rewritten openly and agreed again, rather than left in place and quietly ignored.
A worked example
An illustrative example: the team described is hypothetical, not a customer.
Consider a hypothetical accounts payable team whose manager asks an analyst to ‘speed up supplier payments’. As written, nobody could say at the end of the quarter whether that had happened.
Rewritten as a SMART goal, it becomes: ‘Reduce the average time from invoice receipt to approved payment from 12 working days to 7 by 30 September, by routing invoices under €1,000 to a single approver.’ It is specific (invoice-to-payment time, and the change that will move it), measurable (the average from the finance system, against a recorded baseline), achievable (the routing change is within the analyst’s remit and has the finance manager’s support), relevant (it serves the department’s objective of paying suppliers on agreed terms) and time-bound (30 September, with a check at the end of July).
At the July check-in the average is nine days and falling, so the goal stays as written. Had a system migration intervened, the manager and analyst would have agreed a revised date and recorded why.
Common mistakes
Measuring the wrong thing. ‘Send 200 outreach emails a month’ is easy to count, but it measures activity. The result the team wants is meetings booked or opportunities opened, and the goal should say so.
Setting a target with no baseline. ‘Raise satisfaction to 90%’ means very little until you know whether the starting point is 60% or 89%.
Treating achievable as safe. A goal that could be met without any change passes the test on paper and improves nothing. Achievable means realistic with effort and the resources available, not certain.
Writing too many. A handful of SMART goals can be tracked properly; a dozen become a checklist that is looked at once, at year end.
Skipping the relevant test. A precisely specified goal that serves no team or organisation objective is well-written busywork.
How CLEAR Talent supports it
In CLEAR Talent’s OKR and goal-setting software, SMART goals sit alongside OKRs and weighted KPIs on one platform, and every individual goal must link to a parent objective, which makes the relevant test structural rather than a matter of opinion. Ava can suggest SMART goals for a role as a starting point for the employee and manager to edit, goals an employee drafts go to their manager for approval, and goal scores roll into the performance review with the weighting you configure.