Features
SMART Validation
The criteria everyone knows. Almost nobody completes.
SMART has been taught in every leadership programme, productivity course, and management training for decades. Yet goals set without fully satisfying its criteria fail at a predictable and disproportionate rate. Each dimension left unchecked is not a minor omission — it is a compounding risk that makes failure far more likely before you have even started.
Scientific foundation
50 years of research.
Not a management trend.
SMART traces back to Goal-Setting Theory, developed by Edwin Locke and Gary Latham across hundreds of studies spanning industries, cultures, and task types. SMART operationalises what that science consistently found actually works.
Specific goals outperform vague ones
A goal without specificity leaves room for interpretation. Different interpretations produce different actions — and different outcomes. This finding has replicated across fifty years of field and lab studies.
Difficult but attainable goals outperform easy ones
The sweet spot is meaningful challenge within reach. Goals set too low produce low effort; goals set beyond reach produce disengagement. Achievable stretch is not a compromise — it is the optimal condition.
Feedback is necessary for goals to work
A goal without feedback does not improve performance. People need to know whether they are on track. This is not optional infrastructure — it is a structural requirement for the goal to function.
Commitment moderates goal effectiveness
A goal the person does not genuinely own will not drive the same behaviour as one they are committed to. Assignment and commitment are not the same thing. How a goal is set matters as much as what it says.
These effects are robust across lab, field, individual, team, and organisational contexts, with meta-analytic support showing consistent and meaningful performance gains.
The real problem
Knowing the acronym is not the same
as applying it
SMART is widely recognised, yet it is consistently misapplied — especially in group settings, performance reviews, and cross-functional goal-setting sessions. The reasons are predictable.
Social friction
Challenging a colleague's goal — in front of a manager, or in a team workshop — feels confrontational. So weak criteria pass unchallenged to avoid awkwardness. The cost arrives months later.
The illusion of good enough
Goals that sound purposeful feel finished. "Increase team engagement" is directionally correct. That feels sufficient. The missing criteria are invisible — until execution reveals them.
Criteria treated as optional
People pick the dimensions that feel easy and quietly skip the ones that require real thought — usually measurability and time constraints. The result is a goal that is half-formed but looks complete.
Each skipped criterion is not a cosmetic issue. It is a structural failure in the goal itself — a gap that will produce confusion, misaligned effort, or outright abandonment when you reach it during execution. The compounding effect matters: skip two criteria and the probability of meaningful progress drops dramatically. Skip three, and the goal is essentially unworkable.
Specific
Narrow enough to act on without interpretation.
Why skipping it is costly
A vague goal guarantees that every person working toward it has a slightly different mental model of what it means. This produces invisible misalignment — everyone is "working on it" and nobody is working on the same thing. Effort gets distributed across interpretations rather than concentrated on the actual outcome. Months later, the goal hasn't moved, and nobody can agree on why.
How to make it specific
Ask: What exactly changes? For whom? In what context? A specific goal names the subject, the action, and the domain. It should be narrow enough that someone unfamiliar with the goal could take a meaningful first action without asking a clarifying question.
Improve the onboarding experience
Reduce the time new customers take to complete their first successful export from 14 days to under 5 days.
Under uncertainty: If you genuinely don't yet know the exact target, make the goal of this cycle specific to the discovery process itself. "Identify the three highest-friction points in the onboarding flow and document them with supporting evidence" is specific — even though it doesn't contain a final number.
Measurable
Progress is trackable. Completion is undeniable.
Why skipping it is costly
Without a measurable definition, completion becomes subjective. People claim the goal as done when they feel it's done — not when the outcome is confirmed. This leads to premature closure, where effort stops before the real result has been achieved, and optimistic self-reporting that makes it nearly impossible to learn from the cycle. Worse: teams can spend months on a goal and never agree on whether they succeeded.
How to make it measurable
Ask: What would a stranger need to see to confirm this is done? The answer must be observable — a number, a state change, a documented artefact, a confirmed behaviour. If the answer requires interpretation or relies on the person's own judgement, it is not yet measurable.
Be more consistent with stakeholder updates
4 written update summaries sent and acknowledged by the relevant stakeholders within the next 4 weeks — one per week.
Under uncertainty: A baseline often needs to be established before a target can be set. That's fine — make the measurement of the current state the measurable outcome of this cycle. "Establish a baseline NPS score across three customer segments, documented and shared" is fully measurable, even if the improvement target comes in the next cycle.
Achievable
Realistic given your time, capacity, and constraints.
Why skipping it is costly
An unachievable goal doesn't just fail — it damages the capacity to pursue the next one. People who set goals they cannot reach learn, gradually, that setting goals is a performative exercise rather than a real commitment. Motivation collapses not at the moment of failure, but well before — once the gap between effort and progress becomes apparent. The goal that seemed ambitious on paper becomes a source of anxiety rather than direction. And the more frequently this happens, the harder recovery becomes.
How to make it achievable
Ask: Given what I actually have available — time, access, energy, skills — can I genuinely reach this? This is not an invitation to set comfortable goals. Stretch is valuable. But stretch must be grounded: what needs to be true for this to be possible, and are those things actually true?
How many hours per week can realistically go to this?
What skills or access does this require — and do I have them?
What else is competing for this capacity during the same period?
Has anyone done something similar in a comparable timeframe?
Under uncertainty: If you're unsure whether something is achievable, make the achievability assessment explicit — with a clear decision point built in. "Run a two-week pilot and assess whether the full goal is within reach, documenting the evidence" turns uncertainty into a structured milestone rather than an unexamined assumption.
Relevant
Tied to something that genuinely matters right now.
Why skipping it is costly
A goal that is specific, measurable, achievable, and time-bound — but not relevant — is still the wrong goal. Relevance is what connects the goal to the person pursuing it: to their priorities, their context, and the moment they are in. Without it, goals get deprioritised the instant something more pressing appears. They survive in planning documents and disappear in practice. Irrelevant goals are completed by nobody, because at some level, everyone knows they don't matter enough.
How to make it relevant
Ask: Why does this matter right now, specifically — and to whom? The answer should connect the goal to a current priority: a broader objective, a performance need, a problem that is genuinely pressing. If the honest answer is "it seemed like a good idea at the time", the goal probably needs to be either reframed or replaced.
When goals are set for others — in performance reviews, team planning, or delegation — this dimension is the most commonly ignored. A goal assigned to someone who doesn't see its relevance will be deprioritised quietly, without announcement. Relevance must be understood by the person doing the work, not just the person setting the goal.
Under uncertainty: If the relevance is unclear, surface it as a dependency. "This goal assumes that improving X is the highest-leverage use of this capacity right now. Validate this assumption with [person/data] before committing fully." Naming an unverified assumption is better than pretending the relevance is settled.
Time-bound
A real deadline, not "soon" or "ongoing".
Why skipping it is costly
Without a deadline, goals expand to fill available time — or simply drift indefinitely. The absence of a time constraint removes urgency and makes it structurally impossible to assess whether progress is on track. Parkinson's law is not a metaphor: work genuinely does expand to fill the time allocated. "Ongoing" goals produce ongoing effort with no clear moment of accountability. They survive every review cycle because they can never technically be failed.
How to make it time-bound
Ask: By what specific date will this be done — and what has to be true by then? A time-bound goal has a named date, not a duration. "In the next quarter" is a duration. "By 30 April" is a deadline. The difference matters: a duration shifts forward as time passes; a date does not.
Rebuild the internal documentation over the coming months
All 12 core process documents reviewed, updated, and republished to the shared wiki by 15 May.
Under uncertainty: If the final deadline is genuinely unclear, set an explicit review date — a point at which you will assess progress and either confirm or revise the deadline. That date is still time-bound. "First milestone completed and deadline confirmed or revised by [date]" is a legitimate structure that creates accountability without pretending to certainty you don't yet have.
"A goal with three unchecked dimensions is not a goal — it is a wish with extra steps."
Other frameworks
SMART is not the only lens. Other frameworks get to the same place differently.
Several other frameworks approach goal quality from different angles. Each has genuine merit. None of them contradict SMART — they extend or reframe it for particular contexts.
Organisational alignment
MBO — Management by Objectives
Goals are set collaboratively between managers and their direct reports, then cascaded through the organisation. The emphasis is on shared ownership and alignment between individual goals and company direction — not just the structure of the goal itself.
Ambitious direction + verifiable evidence
OKRs — Objectives & Key Results
Separates the qualitative direction (where you're going) from the quantitative evidence (what you need to observe to know you've arrived). Key Results function similarly to SMART's measurability and time-bound criteria — but the framework adds an explicit emphasis on ambition and organisational transparency.
Purposeful · Actionable · Continuous · Trackable
PACT Goals
Shifts focus from outcome to process — particularly useful for goals where the result depends heavily on consistent behaviour over time. Emphasises the habit layer that SMART doesn't explicitly address.
Frequently discussed · Ambitious · Specific · Transparent
FAST Goals
Prioritises organisational visibility and review cadence. The premise is that goals decay without regular discussion — transparency and frequency of check-in matter as much as the goal's initial structure.
Motivation + mental contrasting
WOOP — Wish, Outcome, Obstacle, Plan
A branded form of Mental Contrasting + Implementation Intentions (MCII). Adds a psychological layer that SMART omits: what stands in the way? By pre-mapping obstacles and building if-then responses in advance, WOOP directly targets the gap between having a well-formed goal and actually following through.
The real point
The framework matters less than what it produces. Any well-formed goal — regardless of which framework it was built with — should satisfy one test: when the person doing the work reads the goal six weeks from now, with no memory of the conversation that produced it, can they continue executing without needing to reinterpret it?
If the answer is yes, the goal is well-formed. If not — if it would require someone to ask "but what did we actually mean by that?" — then regardless of how good it sounded at the time, it is structurally incomplete. The framework is a checklist. The output is a goal that stands on its own.
Apply for access
Goals that pass every check — before you start
Outcome Otter validates every dimension of your goal through coaching — not a form you fill out. Each criterion is tested in conversation, so nothing gets quietly skipped.