A SMART goal is a goal written to be Specific, Measurable, Achievable, Relevant, and Time-bound. Instead of “improve sales performance,” a SMART goal reads: “Increase monthly recurring revenue by 15% by June 30 by closing 8 enterprise accounts per quarter.” The format forces clarity at the point of writing so teams know exactly what success looks like before the work begins.
In this guide
- What Is a SMART Goal? (And What the Acronym Actually Means)
- How Do You Write a SMART Goal? (Step-by-Step Format)
- What Are SMART Goal Examples by Role and Function?
- How Do SMART Goals Connect to OKRs?
- What Are the Most Common SMART Goal Mistakes?
- Frequently Asked Questions
Most goal-setting fails before the quarter even starts not because teams lack ambition, but because the goal itself is too vague to act on. SMART goals fix that at the source by building measurability directly into the format. Here is how to write them well, with 25+ examples across roles and functions.
What Is a SMART Goal? (And What the Acronym Actually Means)
SMART is a goal-writing framework, not a philosophy. Each letter represents a concrete constraint that makes a goal actionable. The OKR University covers every element in depth below is the practical definition you need before writing your first one.
S – Specific: The goal names one outcome, not a category. “Improve customer experience” is a category. “Reduce average support ticket resolution time from 48 hours to 24 hours” is specific.
M – Measurable: The goal includes a number. If you cannot measure it at the end of the period, it is not a goal it is a preference.
A – Achievable: The goal is stretchy but realistic. A 15% revenue increase in Q1 may be achievable; a 400% increase is fiction that damages trust in the goal-setting process.
R – Relevant: The goal connects to a business priority the team actually owns. Personal development goals that have no link to team outcomes are not SMART goals they are aspirations.
T – Time-bound: The goal names a deadline. “By the end of Q2” or “by March 31” – not “this year” or “soon.”
| Dimension | Weak Goal | SMART Goal |
|---|---|---|
| Specific | “Improve marketing performance” | “Increase qualified demo requests from organic search” |
| Measurable | “Get more leads” | “Generate 120 MQLs per month” |
| Achievable | “10x revenue in Q1” | “Grow MRR by 18% in Q1 by activating 5 enterprise accounts” |
| Relevant | “Learn Excel shortcuts” | “Build a pipeline dashboard that reduces weekly reporting time by 3 hours” |
| Time-bound | “Improve team communication” | “Launch a weekly async standup protocol by February 15” |
| Combined result | Unmeasurable, forgotten by week 3 | Trackable, owned, reviewable at quarter-end |
A goal that cannot be measured at the end of the quarter was never a goal. It was a wish with a deadline.
How Do You Write a SMART Goal? (Step-by-Step Format)
Writing a SMART goal takes five minutes when you follow the right order. The common mistake is starting with the action (“I want to improve X”) rather than the outcome (“I need X to reach Y by Z”). For a deeper walkthrough on turning SMART goals into tracked OKRs, the guide on how to write OKRs covers the full methodology.
Start with the outcome, not the activity
Define what a win looks like at the end of the period. “Increase net revenue retention from 88% to 93%” is an outcome. “Have more conversations with at-risk customers” is an activity. SMART goals track outcomes, not effort.
Attach a number to the outcome
Every SMART goal needs a baseline and a target. If you do not know the baseline, your first task is to find it. “Improve NPS from 32 to 45” requires knowing your current NPS. Measuring baseline is not prep work it is part of writing the goal.
Set the deadline first, then check achievability
Name the exact end date before you decide whether the target is realistic. A 20% increase in 90 days may be aggressive; the same increase in 180 days may be comfortable. Deadline shapes ambition.
Check that the goal connects upward
Every SMART goal at the individual or team level should map to a company-level priority. If you cannot draw that line, the goal may not be relevant and relevant goals are the ones people actually track.
Write it in one sentence
If your SMART goal takes three sentences to explain, it is two goals. Every SMART goal should fit in one sentence: [Outcome] [by how much] [by when] [by doing what].
SMART Goal Format Template
“[Verb] [metric] from [baseline] to [target] by [date] by [key action or approach].”
Example: “Increase customer retention rate from 82% to 88% by June 30 by implementing a structured onboarding programme for all new accounts.”
What Are SMART Goal Examples by Role and Function?
The best SMART goals are role-specific. Generic examples do not help managers and employees write goals that actually fit their work. Below are 25 examples across common functions see the full OKR examples by department library for cascaded versions of these at team and company level.
Sales
For sales-specific goal structures that connect to company revenue OKRs, the OKR examples for sales teams page covers 30+ additional examples.
- Increase monthly new ARR from $210,000 to $260,000 by Q2 by adding 3 outbound sequences targeting mid-market SaaS companies.
- Reduce average sales cycle length from 47 days to 35 days by Q3 by implementing a structured deal-review checkpoint at day 20.
- Achieve 90% of quota in every month of Q1 by holding 12 discovery calls per week, minimum.
Marketing
- Grow organic blog traffic from 18,000 to 28,000 sessions per month by June 30 by publishing 8 new SEO-targeted articles and improving 4 existing pages.
- Increase demo request conversion rate from landing pages from 2.1% to 3.5% by Q2 by running A/B tests on 3 headline and CTA variants.
- Generate 200 MQLs from LinkedIn by end of Q2 by running 3 sponsored content campaigns targeting VP HR and COO audiences.
Engineering
- Reduce production bug rate from 4.2 per sprint to under 2 by Q2 by introducing automated regression testing for all new feature releases.
- Increase deployment frequency from twice per week to daily by April 30 by completing the CI/CD pipeline migration by March 15.
- Cut average P1 incident resolution time from 6 hours to under 2 hours by Q3 by implementing an on-call rotation and a written runbook for the 10 most common failure modes.
HR / People Operations
- Reduce employee voluntary turnover from 18% to 13% by year-end by launching a structured 90-day onboarding programme and a quarterly manager effectiveness survey.
- Complete 100% of Q2 performance reviews on time by training all managers on the new review tool by May 1.
- Increase eNPS from 22 to 35 by December 31 by implementing bi-weekly pulse surveys and a manager action-required protocol for scores below 30.
Customer Success
- Increase net revenue retention from 104% to 112% by Q4 by launching a structured quarterly business review programme for all accounts above $20,000 ARR.
- Reduce time-to-first-value for new customers from 21 days to 10 days by Q2 by redesigning the onboarding checklist and adding two dedicated onboarding calls per new account.
- Achieve a CSAT score of 4.6 or above for all support interactions by Q3 by introducing a post-ticket survey and routing recurring issues to a dedicated resolution team.
Product
- Launch the mobile dashboard feature to 100% of paying customers by April 30, with a 4.2+ rating in the in-app feedback prompt.
- Reduce checkout abandonment rate from 34% to 22% by Q3 by shipping 2 UX improvements to the payment flow identified in the March usability study.
- Achieve 80% feature adoption for the new reporting module within 60 days of launch by creating 3 in-app onboarding tours and 2 walkthrough videos.
Operations
- Reduce invoice processing time from 5 days to 2 days by June 30 by automating the approval workflow and eliminating 3 manual handoff steps.
- Cut logistics cost per unit from $4.20 to $3.80 by Q3 by renegotiating the contract with the secondary carrier and consolidating 2 regional distribution routes.
- Achieve 98% on-time delivery across all product lines in Q2 by implementing a daily inventory variance check and a 48-hour pre-shipment alert protocol.
Finance
- Reduce monthly close time from 8 business days to 5 days by Q2 by automating 4 recurring reconciliation reports and standardising the accrual process across all entities.
- Increase gross margin from 61% to 66% by year-end by renegotiating vendor contracts above $50,000 and eliminating 2 underperforming SKUs from the product line.
Individual Contributor (Cross-functional)
- Complete an industry-recognised project management certification by March 31 by dedicating 3 hours per week to coursework.
- Reduce meeting time per week from 14 hours to 8 hours by Q2 by converting 3 recurring status meetings to async written updates in the team’s shared workspace.
- Present one cross-functional process improvement proposal to the leadership team by end of Q1, with at least one recommendation implemented by Q2.
SMART GOALS + OKR TRACKING
The difference between a SMART goal and a tracked OKR is one level of infrastructure
A SMART goal tells you what you are trying to achieve and when. An OKR connects that achievement to a company-level objective, assigns it a confidence level, and surfaces it in a weekly check-in that keeps the team accountable through the quarter — not just at the end.
Teams that write SMART goals but track them in spreadsheets spend the last two weeks of every quarter in catch-up mode. Teams that connect SMART goals to an OKR tracking system close that lag entirely, because progress is visible week over week, not quarter over quarter.
SMART Goals Meet Tracked OKRs
How Do SMART Goals Connect to OKRs?
SMART goals and OKRs are complementary, not competing. Understanding the relationship prevents teams from running two parallel systems that confuse rather than align. Profit.co’s performance management software connects both layers — individual SMART goals and company-level OKRs in the same platform view.
| Dimension | SMART Goals | OKRs (Objectives & Key Results) |
|---|---|---|
| Primary purpose | Define what an individual needs to achieve | Connect individual output to company strategy |
| Format | One sentence with 5 constraints | 1 objective + 2–5 measurable key results |
| Time horizon | Flexible — weekly to annual | Quarterly cadence is standard |
| Alignment | Set individually or by manager | Cascaded from company → team → individual |
| Progress tracking | Usually manual — spreadsheet or doc | Weekly check-ins, automated via integrations |
| Review process | End-of-period review | Mid-quarter check-in + end-of-quarter scoring (0–1.0) |
| AI support | None in standard practice | Profit.co’s 16 AI Agents write and track OKRs from strategy |
| Best used for | Individual task and project goals | Strategic execution across teams and functions |
OKRs use SMART criteria to write the key results the measurable milestones that define whether a team achieved the objective. The objective (“Build a world-class customer success function”) is qualitative and directional. The key results (“Achieve NPS of 50 by Q3,” “Reduce churn to under 5% by Q4”) are SMART.
Using Profit.co’s OKR management platform, teams can write key results using the SMART format, cascade them from company goals to individual goals, and track them automatically through 100+ integrations across CRM, project management, and marketing tools eliminating manual check-in work entirely. Profit.co’s AI Agents go a step further: the OKR Authoring Agent turns a strategy prompt into a full set of high-quality OKRs in under 30 seconds, so teams spend planning time on execution, not formatting.
What Are the Most Common SMART Goal Mistakes?
Doing it consistently across a team of 50 or 500 is where goal-setting breaks down. Most teams know what good goals look like — the failure is in execution. These are the five patterns that appear most frequently.
Confusing activity with outcome
“Conduct 20 customer interviews by March 31” is SMART in form but tracks an activity, not a result. The SMART version is: “Identify 5 product gaps from customer interviews and incorporate 2 into the Q2 roadmap by March 31.” Track what changes, not what you do.
Setting targets without a baseline
“Increase conversion rate to 5%” is not measurable if no one knows the current conversion rate. Every SMART goal requires a starting point. If you do not have data, the first sprint goal should be to establish the baseline.
Writing goals at the wrong level of specificity
“Improve the product” is too vague. “Increase the number of product features shipped from 2 to 4 per sprint by Q2” is specific. “Increase the number of product features shipped in the enterprise tier from 2 to 4 per sprint, measured by completed GitHub issues, by June 30” is the right level of specificity for an engineering team.
No owner, no accountability
A SMART goal needs exactly one owner not a team. “Sales and marketing will increase demo requests” is not a SMART goal. “The demand generation lead will increase demo requests from organic search by 40% by Q2” assigns ownership clearly.
Setting goals once and never revisiting them
Teams that write SMART goals in January and revisit them only in December are running an annual ritual, not a goal programme. High-performing teams review SMART goals monthly at minimum, flagging at-risk goals before the deadline, not after it. Profit.co’s OKR tracking software includes a Goals Progress Agent that surfaces at-risk goals in real time — so teams intervene before the deadline, not after it.
Start Writing Goals That Actually Get Hit
Frequently Asked Questions
A strong SMART goal at work looks like this: “Increase qualified demo requests from organic search from 80 to 140 per month by June 30 by publishing 6 new SEO-targeted blog posts and improving the top 3 landing pages.” It names one specific outcome, includes a measurable target, sets a deadline, and identifies the approach.
The SMART goal format is: [Verb] [metric] from [baseline] to [target] by [date] by [key action]. Each element maps to one of the five SMART criteria – Specific, Measurable, Achievable, Relevant, and Time-bound. The entire goal should fit in one sentence.
SMART goals define what an individual or team needs to achieve in a specific timeframe. OKRs connect that achievement to a company-level strategy, enforce a cascaded alignment structure, and run on a weekly check-in cadence. Teams typically write key results using SMART criteria. OKRs are the system; SMART goals are the format.
SHRM guidelines and the OKR methodology both recommend 3 to 5 SMART goals per quarter per employee — enough to challenge without diluting focus. Fewer than 3 may indicate a role is not being challenged; more than 5 tends to scatter attention and make meaningful tracking difficult. The goal count should reflect the scope of the role, not the number of tasks on a to-do list.
Yes. Team-level SMART goals follow the same format but name the team as the owner and typically roll up to a department-level objective. The key difference is accountability: team goals require one named lead to own the tracking and reporting, even when the work is shared across multiple contributors.
