Writing SMART goals: The complete guide with examples and templates

A SMART goal has to pass five tests: specific, measurable, achievable, relevant, and time-bound. Anyone who has sat through a planning offsite knows the acronym by heart.

A goal that reads well on a slide in the all-hands meeting is not the same goal that survives a sprint board. The slide version gets applause. The sprint-board version faces real tickets, real capacity, and a real date three weeks later, after the room that applauded it has moved to the next agenda item. This guide covers how to write SMART goals that hold up as a standing diagnostic you run against a goal all quarter, not a form you fill in once and file away.

This guide is written for team leads, PMO leaders, and project managers who need a SMART goal to survive past the kickoff meeting. It covers how to write, extend (with SMARTER and SMARTIE), and review them at the team and portfolio level. It doesn't cover OKR software selection or personal habit-tracking apps in depth – the comparison section below covers where SMART goals, OKRs, and KPIs each fit instead.

Why a 45-year-old checklist still beats "next-gen" goal frameworks

George T. Doran, a management consultant at Washington Water Power, published the SMART checklist in the November 1981 issue of Management Review, preserved on the Wayback Machine. Doran had watched Management by Objectives, the participatory goal-setting approach management theorist Peter Drucker popularized in the 1950s, produce objectives managers couldn't act on. "Improve morale" passed every meeting and failed every quarter, because no one could say what "improved" meant or by when. Doran built the five-letter test as a filter: Read the objective, run it against specific, measurable, achievable, relevant, and time-bound, and reject anything that fails.

Two decades later, organizational psychologists Edwin Locke and Gary Latham gave Doran's filter a research base it never had in 1981. Their 2002 synthesis in American Psychologist reviewed more than three decades of goal-setting studies and found that specific, difficult goals beat vague or easy ones in roughly 90 percent of them. That finding explains why the checklist has outlasted three decades of framework fashion. Every "next-gen" system built to replace it still borrows its core demand: Name the number, name the date, name the owner. Doran's checklist doesn't need to be new. It needs to force the three things most planning conversations skip on their own.

What does SMART stand for?

SMART stands for specific, measurable, achievable, relevant, and time-bound — the five SMART criteria a goal has to pass. Each letter catches a different way a goal quietly fails, and a goal only holds up when it passes all five, including the ones that are hard to write.

Specific: What outcome, exactly?

A specific goal names one outcome, not a direction. "Improve onboarding" fails the test. "Cut new-hire time-to-first-commit from 12 days to 5" passes it, because a stranger reading the sentence can tell you exactly what changes. A specific-sounding goal can still hide a missing owner. A goal without a named owner is a wish with better grammar.

Measurable: Whose number is it?

A measurable goal carries a number attached before anyone argues about it later, and that number needs a source the team already trusts, not one invented for the goal. OTP Bank Group built that kind of shared, trusted number set before it scaled its portfolio reporting across markets; read the case study on how it did it before you set your own metrics. Locke and Latham's research backs this up directly: Specific numeric targets outperformed "do your best" instructions consistently, because a vague target lets people lower the bar without anyone noticing. Tempo's 2026 State of SPM Report found the same pattern at the portfolio level: Teams that measure goals against a shared source of truth show roughly a 12-point ROI advantage over teams pulling whichever number is easiest to find that week.

Achievable: Given what capacity?

Achievable doesn't mean easy. It means a goal the team could plausibly hit given its actual headcount, budget, and calendar, not the headcount, budget, and calendar the plan pretends the team has. The pitfall cuts both ways: A goal padded so far below capacity that hitting it proves nothing, or a goal borrowed from a competitor's press release with no accounting for the team that has to deliver it.

Relevant: Whose priority does it serve?

A relevant goal connects to a portfolio priority someone above the team has signed off on, not one the team assumes matters. Strategic prioritization tools exist because "relevant" is the letter teams fake most often: A goal sounds strategic, but the leader who owns this quarter's priorities never approved it. More adjectives in the goal statement won't fix that. A named link from the goal to the priority it serves will.

Time-bound: By when, specifically?

A time-bound goal carries one fixed date. "By Q3" invites drift. "By September 30" doesn't. Milestone tracking keeps that date visible against the tickets feeding it, so the deadline doesn't live only on a slide.

A SMART goal is quarterly by habit, but it doesn't have to stay locked at that altitude. Break it into sprint goals, and let each sprint goal name its slice of the quarterly target instead of drifting into its own scope. A team running two-week sprints might set "raise checkout conversion by 4 points by September 30" as the SMART goal, then let sprint one cover the payment-page redesign and sprint two cover the cart-abandonment email, each tagged with how it rolls up to the September number. Agile planning and SMART goals aren't rival systems. The sprint sets the pace. The SMART goal names the destination.

What are SMARTER and SMARTIE, and when should you use them?

SMARTER and SMARTIE are the two SMART extensions worth adopting; both add a checkpoint the original framework never specified. SMART tells you how to write a goal, not what happens after you write it. SMARTER and SMARTIE add exactly that, which is why they've earned real adoption instead of fading into acronym fatigue like most attempts to extend it.

SMARTER adds Evaluate and Reassess: A built-in checkpoint that forces the team to look at the goal again before the quarter ends, not only at the end when it's too late to adjust. SMARTIE adds Inclusive and Equitable: A check on whether the goal's target population and its yardstick both account for people the original number quietly left out – a common blind spot in hiring goals, pay-equity goals, and customer-outcome goals measured only against the largest accounts.

The two extensions solve different problems, so pick based on which failure mode worries you more, or combine both instead of choosing. A goal can carry an Evaluate checkpoint and an Equitable lens at the same time. Neither framework rules out the other.

That flexibility extends past the office. Someone training for a marathon can run the same five tests against "finish in under four hours at the November race" the way a product team runs them against a roadmap item, and the checklist holds up outside work just as well as it does inside it. It strains on goals that resist a number by nature, like "be a more patient parent." Even there, the framework holds up. Find the observable behavior underneath the value – something like "read to my kids for 20 minutes, four nights a week" – and make that measurable instead.

SMART goals vs OKRs vs KPIs: What's the difference?

Why not replace the checklist with OKRs? That question surfaces in nearly every planning meeting, and it deserves a real answer, not a dismissal. OKRs earned that reputation honestly: Google and Intel built cultures around them, a history John Doerr's Measure What Matters documents in detail, and the framework is pitched, explicitly, as the way to align strategy across dozens of teams at once. No single SMART goal ever promised that. SMART goals, OKRs, and KPIs do different jobs at different time horizons. Teams that treat the three as rivals end up dropping a perfectly good one instead of using all three together.

A SMART goal is the unit. An OKR is often several SMART goals nested under one strategic objective. A team that drops SMART goals for OKRs alone keeps the alignment but loses the ownership: An objective can cascade through five teams with no one person accountable for a single number. A KPI keeps running after both close and tells you whether the system that produced them stayed healthy. Tempo's performance measurement and analytics tools track all three without forcing a team to pick one framework and abandon the others. Check the glossary before arguing over what "OKR" or "KPI" technically means, so the argument can move to which one to use.

What mistakes kill SMART goals?

In practice, five mistakes account for most of the SMART goals that fail.

• Teams measure activity instead of outcome. "Ship 12 features this quarter" passes the letter of "measurable" while missing its point. A shipped feature and a feature that matters are not the same thing.

• Teams set deadlines by the calendar instead of the dependency they're tracking. "By end of Q3" is easy to write because the quarter ends on a fixed date, not because September 30 is when the dependency clears.

• Teams leave a dependency unnamed. A goal depending on another team's roadmap, a vendor's release date, or a budget approval still produces a clean SMART sentence. The first missed handoff ends the goal, and no one marks it dead.

• One person owns a shared goal. Whoever presents the goal in the planning meeting becomes its owner by default, even when three other teams have to deliver pieces of it. That person ends up accountable for outcomes only part of it controls.

• No one reviews the goal on a set cadence. A goal without a standing review can drift for most of a quarter before anyone checks it against reality.

That fifth mistake lets the other four hide. Call it goal theater: An objective that passes every checklist test, gets its slide in the planning deck, and then dies quietly because no one built a mechanism to catch it drifting.

How do you track SMART goals after you set them?

A goal without a review cadence lets the other four mistakes hide unnoticed. A review cadence catches all five. A SMART goal needs a review interval matched to its length: Weekly for a goal running four weeks or less, biweekly for a quarter-length goal, monthly for anything spanning two quarters or more. A goal without that interval stops being a commitment. It ages quietly on a slide instead.

Gallup's 2024 workplace study found that US employee engagement hit an 11-year low, with declining role clarity among the clearest drivers. People disengage fastest when they can't tell whether what they're doing still matters to anyone above them. A goal that never gets a second look sends exactly that signal, whether or not the goal itself was written well.

The initiative tracker catches what review alone misses once a goal sits beside it. A SMART goal tracked beside the actual tickets feeding it exposes the mismatch between plan and delivery the moment it opens, not a quarter later. Add time tracking and you get something a status update never shows: Whether the hours logged against the goal match the hours the plan assumed – usually the exact point where an achievable goal turns unachievable.

Tempo's 2026 State of SPM Report found roughly a 12-point difference in ROI between organizations with integrated portfolio review processes and those without, alongside a failure rate near 30 percent for teams lacking one. A short post-mortem when a goal closes, whether it succeeded or not, turns that shortfall from a recurring surprise into a pattern the team can act on next quarter.

Seven SMART goal examples you can steal

Seven examples, across seven domains, follow the same shape: A verb, a number, a date, and a method for checking it. SMART goal template: [Verb] the metric from [baseline] to [target], by [date], measured against [source of truth]. Swap the specifics for your own team's reality and the structure should still hold.

Where does Tempo fit?

Every example above needs the same thing once someone writes it down: A system to track it after the kickoff meeting ends. Tempo's 2026 State of SPM Report put a number on what happens without one: Close to 30 percent of projects across the businesses it surveyed weren't delivering measurable value, and unreviewed goals kept surfacing as one of the reasons why.

Tempo Structure PPM gives a SMART goal a home beside the initiative it supports, so the goal, the tickets, and the date sit in one view instead of three. Tempo Capacity Planner checks the achievable letter against real numbers, showing whether a team has the hours a goal assumes before the quarter starts, not after it's already behind.

Doran's five letters don't need replacing. They need somewhere to live after the meeting ends – which is the part of the framework that was always missing.