SMART goals are one of those frameworks that almost everyone knows and almost everyone misapplies. The idea is straightforward: make goals Specific, Measurable, Achievable, Relevant, and Time-bound. But in practice they often end up vague, set without real input from the person doing the work, and reviewed once a year if at all. The result is goals that sit in a document and do nothing. The problem is not the framework. It is how it gets used. Done properly, a SMART goal gives someone a clear target, a way to know when they have hit it, and a timeline to work towards. Done badly, it is just admin with a sense of structure.
A goal that is specific, measurable, and time-bound gives someone something to work towards. A vague goal just adds noise.
What SMART actually means
The acronym is widely known, but each letter deserves more than a one-word definition. Here is what each component actually requires in practice.
- SpecificThe goal names exactly what needs to happen, by whom, and in what context. "Improve communication skills" is not specific. "Lead the weekly team standup independently by the end of Q2" is.
- MeasurableThere is a concrete way to know whether the goal has been achieved. Numbers, deliverables, and observable outcomes all work. "Get better at code reviews" is not measurable. "Complete ten peer code reviews with written feedback by the end of the quarter" is.
- AchievableThe goal is a genuine stretch but not so far beyond current capability that it sets the person up to fail. It should challenge without demoralising.
- RelevantThe goal connects to the person's actual role, team priorities, or development direction. A goal that is technically well-formed but irrelevant to someone's work or growth is wasted effort.
- Time-boundThere is a clear deadline or timeframe. Without one, goals drift indefinitely. A date creates urgency and makes it possible to review progress.
Common SMART goal mistakes
Most goal-setting problems fall into a small number of patterns. Recognising them makes it easier to avoid them.
- Too vagueGoals like 'improve performance' or 'develop leadership skills' sound reasonable but give the person nothing concrete to aim at. If you cannot describe what success looks like, the goal is not ready yet.
- Set without inputA goal handed down without conversation is rarely owned. The person it belongs to should be involved in shaping it. They understand their work, their constraints, and what a genuine stretch looks like for them.
- Never reviewedA goal set in January and looked at again in December is not a goal. It is a formality. Regular check-ins, even brief ones, keep goals relevant and catch early signs that something needs adjusting. Review targets in your regular 1-1s so goals stay alive rather than gathering dust in a document.
- Not relevant to the roleA well-formed goal that has no bearing on someone's actual responsibilities or development direction feels like box-ticking. Goals should connect to what the person does and where they want to go.
SMART goal examples by scenario
These are real, usable examples, not template placeholders. Adapt the specifics to fit the person and context.
- Software engineerReduce average pull request review time on the core services team from three days to one day by implementing a team PR rotation, measured over the next eight weeks.
- Team leadRun a structured retrospective with the team at the end of each two-week sprint for the next three months, producing at least two tracked action items per session.
- Customer supportAchieve a customer satisfaction score of 4.5 or above (out of 5) on personally handled tickets for two consecutive months by the end of Q3, tracked via the team's existing CSAT tool.
- SalesBook 15 qualified discovery calls with net-new prospects in the mid-market segment by the end of this quarter, with each call logged in the CRM within 24 hours of completion.
- Product managerDefine and document a prioritisation framework for the roadmap backlog, shared with engineering and design leads, and used to make at least three documented prioritisation decisions before the end of the quarter.
- Junior employee growing skillsComplete two internal lunch-and-learn sessions on topics of the engineer's choice by the end of Q2, each with a written summary shared with the team in the #learning Slack channel.
Rewriting weak goals
Seeing the contrast between a weak goal and a well-formed one is often the fastest way to understand what is missing. Here are three examples.
Get better at presenting to stakeholders.
Deliver three project update presentations to the senior leadership group by the end of Q2, each with a written brief prepared in advance and reviewed with your manager beforehand.
Improve the onboarding process for new team members.
Produce an updated onboarding guide covering the first 30 days, reviewed with at least two current team members, and used with the next hire joining before the end of this quarter.
Be more proactive about my development.
Identify one skill gap in your current role, propose a specific learning plan to address it by the end of this month, and complete at least one concrete learning activity (such as a course, project, or mentoring session) within the following six weeks.
Track every goal in one place
Set targets per team member, connect them to catchups, and review progress over time.