SMART Goals: What They Are, How to Write Them, and 12 Examples (2026 Guide)

"Improve customer service." "Sell more." "Reduce errors." Almost every team has goals like these, and almost none of them can say in March whether they're on track, because no one ever defined what "on track" would look like. That is exactly the gap SMART goals close: a five-question filter that turns a vague intention into a commitment you can measure, assign, and review.

In this guide you'll see what SMART goals are and where the method comes from, what each of the five letters actually demands, how to write a goal step by step starting from a fuzzy idea, 12 real examples across functions (sales, marketing, product, HR, and personal development), a copy-ready template, how SMART differs from OKRs and KPIs, the mistakes that ruin the most goals, and the part most guides skip: how to make a goal survive the meeting where it was agreed.

⚠️ This article was independently compiled based on publicly available information and user feedback as of September 2026.

Table of Contents

1. What are SMART goals?
2. The 5 criteria, letter by letter
3. Why vague goals fail
4. How to write a SMART goal in 6 steps
5. 12 SMART goal examples by function
6. A copy-ready SMART goal template
7. SMART vs OKR vs KPI: which to use when
8. The 5 mistakes that ruin SMART goals
9. Tracking: where goals die or get done
10. How AI helps you set and track goals in meetings
11. Checklist: is your goal actually SMART?
12. FAQ
13. Conclusion

What are SMART goals?

SMART goals are goals written to meet five criteria: Specific, Measurable, Achievable, Relevant, and Time-bound. The acronym works as a checklist: if your goal can't answer all five questions, it isn't a goal yet. It's a wish.

The method has a documented origin. In 1981, consultant George T. Doran published "There's a S.M.A.R.T. way to write management's goals and objectives" in Management Review, proposing the original acronym (with Assignable and Realistic in the A and R positions). Over the years, the most widespread version replaced those two with Achievable and Relevant, which is what most teams use today and what this guide follows.

It's worth being clear about what SMART is not. It isn't a strategy methodology: it doesn't tell you which goal to pursue, only how to phrase it so it becomes verifiable. It isn't bureaucratic form-filling either: a goal can tick all five letters and still be useless if it measures the wrong thing. And it doesn't compete with frameworks like OKR. As we'll see, they combine rather well.

The 5 criteria, letter by letter

The value of SMART lives in the detail of each letter. This table summarizes the question each criterion asks and the failure it prevents.

• Specific. The quick test: if two people on the team read the goal and describe different outcomes, it isn't specific. "Improve the website" fails; "cut homepage load time to under 2 seconds" passes. Specificity includes ownership: a goal that belongs to everyone belongs to no one.
• Measurable. Not everything needs a revenue figure: percentages, frequencies, verifiable deliverables ("publish 8 customer case studies"), or thresholds ("average survey score of 4.5") all count. What matters is agreeing on the metric and its source before starting, not at the review meeting.
• Achievable. Ambition motivates; fantasy demoralizes. A good calibration: demanding enough to require changing how you work, but possible with existing resources or ones about to be approved. If the goal depends on budget nobody has confirmed, it isn't achievable yet.
• Relevant. Every goal should be able to complete the sentence "this contributes to X," where X is a recognizable company or quarterly priority. If the sentence won't come, the goal is competing against the ones that do matter for the same time and energy.
• Time-bound. A deadline turns intention into commitment and lets you catch slippage early. For goals longer than a month, add interim milestones: "first version by October 30, pilot with 5 customers by November 30" flags a delay far sooner than a single final date.

Why vague goals fail

Vague goals don't fail from lack of effort. They fail through three mechanisms that repeat in any team.

• Everyone executes a different interpretation. "Improve support quality" can mean answering faster, resolving on first contact, or sounding friendlier, depending on who you ask. Three people working on three interpretations produce activity, not progress, and the disagreement only surfaces months later, when it's expensive.
• There's no honest way to evaluate. Without an agreed metric, the end-of-quarter review becomes a rhetorical negotiation: whoever argues "I think we did improve" most convincingly wins. That erodes something more valuable than the goal itself: the belief that reviews mean anything.
• The urgent eats the important. A goal with no deadline and no milestones raises no alarm when it gets postponed. Every week it loses to the day's fires, and in December it sits untouched on January's slide.

There's a fourth mechanism that gets less airtime: the goal is agreed in a meeting and lost in that same meeting. It gets debated with energy, someone scribbles "raise retention" in a notebook, and weeks later nobody remembers whether the commitment was raising it to 85% or by 85%, or who ended up owning it. The problem wasn't the phrasing. It was the record. We'll come back to this, because the fix is cheap.

How to write a SMART goal in 6 steps

The most reliable way to write a SMART goal is to start from the vague intention and push it through the five questions, in order. Let's follow one real example end to end: a support team that wants to "improve customer service."

1. Write the intention exactly as you think it. Unpolished: "improve customer service." This honest draft is the raw material; skipping it and starting straight from the template tends to produce goals that sound good and commit to nothing.
2. Make it specific: what, who, where. Which part of customer service? Which channel? Who answers for it? Result: "reduce first-response time on the email channel, with Marta as owner."
3. Pick the metric and its source. Where will the number be read? What's the starting value? Without a baseline there is no provable progress. Result: "from the current 11 hours (helpdesk dashboard) to under 4 hours."
4. Check that it's achievable. What would have to change to get there, and is that change within reach? If it requires hiring three people nobody approved, adjust the target or get the approval before committing. Say reply templates and a reorganized shift make it viable.
5. Confirm relevance. Which priority does it serve? Here: the company is losing renewals to a feeling of neglect, and first-response speed is the factor churned customers cite most. The goal is now anchored to a real priority.
6. Set the date and milestones, then write it out in full. Final result: "Reduce first-response time on email from 11 hours to under 4 hours by December 31, 2026, reviewed monthly in the team meeting. Owner: Marta."

Compare the starting point with the result: the first version could neither be met nor missed; the last one can be planned, delegated, measured, and defended. That contrast is the entire value of the method.

12 SMART goal examples by function

The examples below show the before and after in the functions where goals are used most. The numbers are illustrative: what transfers is the structure, not the figure.

A copy-ready SMART goal template

This template condenses the five questions into a format that fits in any team document. Filling it in takes ten minutes; discussing it with the team takes one meeting.

Goal: [verb + concrete outcome + target figure]
Owner: [one person, not a department]
Metric and source: [what is measured and where the number is read]
Baseline: [today's starting value]
Deadline: [a concrete date, not "next quarter"]
Milestones: [2-3 interim points with dates]
Relevance: [which company priority this serves]
Review: [in which meeting, at what cadence]

Two usage notes. First, the "Review" field is not decorative: a goal with no assigned meeting to be reviewed in is a goal without an immune system, and the tracking section explains why. Second, resist the urge to fill the template in alone and present it finished: the disagreement that doesn't surface when the goal is set surfaces, multiplied, when it's evaluated.

SMART vs OKR vs KPI: which to use when

SMART coexists with two other terms it gets confused with constantly. The distinction is simpler than it looks: they are tools for different questions.

The practical relationship between the three:

• SMART and OKR combine; they don't compete. The key results of a well-written OKR meet nearly every SMART criterion: they're specific, measurable, and scoped to the quarter. The philosophical difference sits in the A: OKRs are deliberately set beyond the comfortable (hitting 70% counts as a good outcome), while a classic SMART goal commits to full delivery. If your company runs OKRs, apply the SMART filter to each key result and make explicit which kind of ambition you're agreeing to.
• KPIs watch; goals change things. A KPI is a standing thermometer (churn rate, margin, response time). When a KPI drifts from where it should be, you write a SMART goal to correct it. "First-response time" is the KPI; "cut it from 11 to 4 hours by December" is the goal.
• For a small team with no framework, SMART is enough. OKR earns its overhead when several teams need aligning; if you're eight people, three well-tracked SMART goals beat a half-adopted OKR rollout.

The 5 mistakes that ruin SMART goals

The format doesn't protect against misuse. These five mistakes show up again and again in teams that "already use SMART."

1. Measuring what's easy instead of what matters. "Publish 20 articles" is measurable and comfortable; "grow organic visits 40%" is measurable and uncomfortable, because it can fail. If all your goals measure activity (doing things) and none measure outcomes (something happening), the SMART filter is approving goals that risk nothing.
2. Setting too many goals. Eight simultaneous SMART goals amount to none: attention divides until it disappears. One to three per team per quarter is the range where focus survives daily reality.
3. Turning them into an immediate evaluation weapon. If every missed goal dents someone's pay, the team learns to negotiate soft targets, and the whole system degrades into theater. Goals and compensation can connect, but the link needs shock absorbers: context, external factors, and the agreed level of ambition all count.
4. Writing them in January and rereading them in December. The annual goal with no interim review fails silently for ten months and causes a scandal in the eleventh. Review cadence matters more than elegant phrasing.
5. Not recording where the number came from. Six months later, nobody remembers why the target was 30% and not 20%, whether it was ambitious or conservative, or which assumptions held it up. Without that context, the review teaches nothing. A goal needs a birth certificate: what was discussed, which alternatives were discarded, and why that number was agreed.

Tracking: where goals die or get done

The difference between teams that meet their goals and teams that archive them is almost never in the phrasing. It's in the tracking cadence, which plays out across three specific meetings.

• The meeting where the goal is born. Quarterly planning, a kickoff, a leadership meeting: this is where the figure, deadline, and owner get agreed. It's also where the most gets lost: the reasoning behind the number, the objections someone raised, and the assumptions everyone accepted rarely make it into the final document. All of that will be needed at review time.
• The periodic review (weekly or biweekly). Five minutes per goal is enough if the question is right: not "what did you do?" but "is the indicator on track for the target, and if not, what do we change?". The goal enters the agenda as a fixed item; what isn't on the agenda doesn't exist.
• The 1:1 and the performance review. Individual goals live or die in one-on-ones. If someone's development goal has gone three 1:1s without a mention, it's no longer a goal for that person. It's a decoration on the annual form.

Across all three meetings the weak point is the same: the conversation is rich and the record is poor. Figures get qualified, dates get moved, conditions get added, and none of it is written down in the moment because everyone is busy debating. Each attendee's memory fills the gaps, each in its own way, and by Monday there are three versions of the same commitment.

How AI helps you set and track goals in meetings

AI is not going to decide your goals, and you should be suspicious of anyone promising otherwise. Where it does change the rules is the weak link we just named: recording faithfully what was agreed, and being able to consult it later without archaeology.

SuperIntern is a botless desktop app for Mac and Windows: it captures audio directly from the device, so no bot joins the call and it works the same in Zoom, Google Meet, Microsoft Teams, Webex, and in-person meetings. For the life cycle of a goal, it contributes three pieces.

• A live note structured around your goals. The AI Canvas builds the note in real time as the meeting unfolds, and you define its structure in plain language: "capture each goal with its metric, baseline, owner, deadline, and the reasoning discussed." The template in this guide stops being an after-meeting chore and starts filling itself in while the team deliberates.
• Speaker-attributed transcription to recover context. When someone asks at the quarterly review "why did we agree on 30% and not 20%?", the transcript with speaker identification takes you back to the original discussion, with the objections and assumptions as they were actually said, instead of reconstructing them from memory.
• Chat across all your meetings afterwards. Questions like "which goals did we commit to in the October planning meeting, and who owns each one?" are answered from the real content of your meetings. Your history of notes becomes the institutional memory of your goals, searchable in seconds.

For international teams there's one more piece: real-time subtitles and translation in over 50 languages, so agreeing on a goal doesn't depend on each participant's English level. A commitment half the team only half understood is half a commitment. There's a free plan, so you can try it in your next planning meeting at no cost.

Checklist: is your goal actually SMART?

Before signing off on a goal, run it against these ten points. At eight or more, it's ready; below that, go back to the step that fails.

• Would two people on the team read it and describe the same outcome?
• Does it have a single named owner?
• Is the metric agreed, with a concrete source where it's read?
• Is today's baseline written down?
• Is it demanding but possible with real or already-approved resources?
• Can you complete "this contributes to X" with a recognizable priority?
• Does it have a concrete deadline, plus interim milestones if it runs over a month?
• Does it measure an outcome, not just activity?
• Is it assigned to a recurring meeting where it will be reviewed?
• Are the reasons and assumptions behind the number on record?

If several fail, start with the owner and the review meeting: those two pull most of the others along.

FAQ

What does the SMART acronym stand for?

Specific, Measurable, Achievable, Relevant, and Time-bound. A SMART goal answers all five questions: what exactly, how it will be measured, whether it's possible, why it matters, and by when.

Who created SMART goals?

Consultant George T. Doran proposed the acronym in 1981, in an article in Management Review. His original version used Assignable and Realistic for the A and the R; over time the variant with Achievable and Relevant became the most widely used.

How do you write a SMART goal?

Start from the vague intention and push it through the five questions in order: pin down what and who, choose the metric and baseline, check it's possible with real resources, anchor it to a company priority, and give it a deadline with interim milestones. The result should fit in one or two sentences that anyone on the team interprets the same way.

Can you give a quick SMART goal example?

Vague: "improve customer service." SMART: "Reduce first-response time on email from 11 hours to under 4 hours by December 31, 2026, reviewed monthly in the team meeting. Owner: Marta." The difference is that the second version can be planned, measured, and evaluated without interpretive debates.

What's the difference between SMART goals and OKRs?

SMART is a quality filter for phrasing any goal; OKR is a quarterly alignment framework combining one qualitative objective with 2-4 measurable key results. They complement each other: good key results meet the SMART criteria. The main difference is the agreed ambition: OKRs are deliberately set beyond the comfortable, with 70% counting as success, while a classic SMART goal commits to full delivery.

How many SMART goals should you have at once?

One to three per team per quarter. Beyond that, attention fragments and tracking turns superficial: eight goals reviewed shallowly deliver less than two reviewed seriously every week.

How often should goals be reviewed?

Team goals weekly or biweekly, with the question "is the indicator on track for the target?". Individual goals in every 1:1. An annual goal with no interim reviews fails silently: by the time the gap is discovered in December, there's no room left to correct course.

Conclusion

SMART goals aren't a template to fill in. They're five questions that make you uncomfortable in the right way: what exactly, how will we know, is it possible, does it truly matter, and by when. Pushing a vague intention through that filter takes half an hour, and it's the highest-return half hour of the quarter, because everything else (planning, delegating, evaluating) rests on it.

From this guide, keep two habits above the rest: no goal without a named owner and an assigned review meeting, and no goal without a record of the reasoning behind its number. For the second one you no longer need a note-taker: let AI keep the minutes while the team debates, and spend the meeting agreeing on targets worth chasing.

Try SuperIntern Free : Live, botless meeting notes that capture every goal, metric, and owner while your team deliberates.