SMART Goal Examples for Work

A SMART goal names one result, says how it will be measured, is within reach, matters to the team’s larger aim, and has a date. “Improve customer support” is not a SMART goal. “Cut the median first-response time on support tickets from 9 hours to 4 hours by December 31, 2026, by adding a second morning shift” is. Below are the criteria, where the acronym comes from, twelve work examples by role, a short comparison with OKRs, and how to break a goal into tasks.

The SMART criteria

• Specific: one result, stated plainly. Who is involved and what will be different when it is done.
• Measurable: a number, with its starting value. “From 9 hours to 4 hours” is measurable; “faster” is not.
• Achievable: stretching, but possible with the people and time you actually have. If it needs a hire you have not made, say so in the goal.
• Relevant: it serves a larger aim the team already agreed on. A goal that is measurable but unconnected is a distraction with a number attached.
• Time-bound: a date, not “this year” or “soon”. A date is what turns a goal into a plan.

Relevance is the letter people skip. The U.S. Office of Personnel Management’s guidance on planning in performance management↗ (opens in a new tab) describes planning as setting expectations and goals for groups and individuals “to channel their efforts toward achieving organizational objectives.” A good test: can you name the team goal this one supports? If not, it may not be worth the effort.

Where SMART comes from

The acronym is usually traced to George T. Doran’s 1981 article “There’s a S.M.A.R.T. way to write management’s goals and objectives.” The U.S. Department of Education’s SMART Objectives Toolkit↗ (opens in a new tab) cites it and notes that the letters originally stood for Specific, Measurable, Assignable, Realistic and Time-related, and that the acronym has since been adapted by many authors. The version most people use today, and the one above, reads Achievable and Relevant instead.

The original A is worth keeping in mind. Assignable meant naming who is responsible. Most goals that fail have a number and a date but no owner, so every example below says who does it.

SMART goal examples by role

The companies and numbers are invented, so each example can show every letter at work. Replace the figures with your own baseline; a goal copied without a real starting number is not measurable.

Engineering

1. The platform team will cut the median build time for the main app from 14 minutes to 7 minutes by November 30, 2026, by caching dependencies and splitting the test suite, measured on the build dashboard.
2. The backend team will reduce customer-reported bugs in the billing module from 12 a month to 4 a month by the end of Q1 2027, by adding tests for every bug fixed and reviewing the three most common failure types each month.

Customer support

1. The support team will cut median first-response time on email tickets from 9 hours to 4 hours by December 31, 2026, by adding a second morning shift and a set of reviewed reply templates.
2. Support lead Jordan will publish 20 help articles covering the 20 most common ticket topics by October 31, 2026, and measure the share of tickets on those topics in November against September.

Sales

1. Each account executive will book 12 qualified demos a month in Q4 2026, up from 8, by adding two outbound hours to every Tuesday and Thursday, tracked in the CRM.
2. The sales team will raise the trial-to-paid conversion rate from 14 percent to 18 percent by March 31, 2027, by calling every trial account on day three, measured on trials that start after October 1.

Marketing

1. The content lead will publish two in-depth guides a month from October through December 2026 and grow organic sign-ups from 150 to 250 a month by January 31, 2027.
2. The marketing team will grow the newsletter from 3,000 to 5,000 subscribers by June 30, 2027, through a sign-up box on every guide and one partner swap a month, with unsubscribes staying under 1 percent per send.

Operations

1. The operations manager will cut average invoice processing time from 6 business days to 2 by December 15, 2026, by moving approvals into one queue with a named approver for each budget.
2. The office manager will write and publish standard procedures for the five most common onboarding tasks by November 15, 2026, and have each one followed once by a new hire without help.

Solo founder

1. I will interview 15 current customers by October 31, 2026, record the top three problems they mention, and choose the next feature from that list by November 7.
2. I will ship a working first version of the export feature to five paying customers by December 1, 2026, spending no more than two mornings a week on it so support and sales still get covered.

Each example names an owner, a number with its starting point, the change that should cause the improvement, and a date. The “by doing X” part is not strictly required by SMART, but it is what makes a goal something a team can plan against rather than hope for.

A SMART goal template to copy

Goal: [Owner] will [change a measure] from [baseline] to [target]
      by [Month day, year], by [the main change you will make].

Specific:    what exactly will be different? [ ]
Measurable:  where is the number read, and what is it today? [ ]
Achievable:  who and how much time? Anything missing? [ ]
Relevant:    which team goal does this serve? [ ]
Time-bound:  final date [ ]  checkpoint dates [ ], [ ]

First three tasks:
1. [task that can start this week]
2. [task]
3. [task]

SMART goals vs OKRs

OKRs, objectives and key results, are a different shape. According to What Matters, John Doerr’s OKR site↗ (opens in a new tab), an objective is “what is to be achieved,” meant to be significant and ideally inspirational, while key results “benchmark and monitor how we get to the Objective” and should be specific and time-bound. The site credits Andy Grove at Intel with the method, and Doerr introduced it at Google in 1999.

• A SMART goal is one self-contained statement. An OKR is one qualitative objective with a few measured key results under it.
• SMART goals aim to be achievable. OKRs are meant to be challenging, and some are deliberately aspirational: stretch goals nobody has reached before.
• They combine well: each key result under an objective can be written as a SMART goal.

Turning a goal into tasks on a board

A goal is a destination; nobody can start work on “cut first-response time to 4 hours.” Someone can start on “draft ten reply templates for the most common ticket types.” Break each goal into tasks small enough that each one could be done in a day or two, and put them where the team already works.

On fenbs, a goal fits naturally as a project or a category on the board, with its tasks under it. Add many turns a pasted list into tasks in one step, so the “First three tasks” lines from the template, or a longer breakdown, go in together. Each task has a note for the problem, a plan for how it will be done, and an optional size from XS to XL; an XL means too big, split it. Give the tasks that move the goal soonest a higher priority, from 1 to 10 with 1 the most urgent, and pull them into Next Up.

Be clear about what fenbs does not do. It has no goal tracking, no due dates and no progress charts for a target number, so the goal statement, its measure and its dates live in your planning document, and the board holds the work. If the goal is a standing commitment, such as “first response within 4 hours”, record it on the Decisions and rules page as a rule: every connected AI assistant reads the rules first, so an assistant drafting support replies works to the same target the team set. The decider is always a person.