Most SMART goals examples you will find are written for individuals: run a 5k, learn Spanish, read twelve books. Useful for a personal development plan, useless when you manage a team and your results depend on other people delivering.
A manager’s goals work differently. They are produced by other people, they compete with each other for the same finite hours, and they are only measurable if the reporting to measure them already exists. This guide covers SMART goals for managers specifically, with worked examples across delivery, capacity, performance, development, process and margin, plus a template you can copy.
What are SMART goals?
A SMART goal is an objective written to satisfy five criteria: Specific, Measurable, Achievable, Relevant and Time-bound. The framework exists to convert a vague intention into something you can tell whether you hit.
| Criterion | The question it answers | How it fails in practice |
|---|---|---|
| Specific | What exactly will change, and who does it? | “Improve team communication” |
| Measurable | What number tells you it happened? | No baseline recorded, so no way to show movement |
| Achievable | Can this be done with the people and budget you have? | Targets set by ambition rather than capacity |
| Relevant | Does it move something the business cares about? | A metric that improves while outcomes do not |
| Time-bound | By when, exactly? | “This year”, which everyone reads as December |
The framework itself is straightforward. Applying it to management objectives is harder, because the honest version of Achievable usually means confronting how much capacity your team actually has, and the honest version of Measurable means admitting which numbers you do not currently collect.
SMART goals examples for managers
Each of the SMART goal examples below shows the vague version first, then the rewrite, so you can see exactly what the criteria change, and what data each one turns out to need.
Project delivery
Vague: Deliver projects more reliably.
SMART: Increase the share of projects delivered within 10% of their original time estimate from 55% to 75% across the four projects closing in Q3, measured by the estimated versus actual hours report at each project close.
Note what the rewrite forces. You need a baseline, which means you need historical estimate data. A manager who cannot state the current figure cannot write this goal, and discovering that gap is itself worth the exercise.
Capacity and workload
Vague: Stop the team being overloaded.
SMART: Reduce the number of people logging more than 45 hours in a week from an average of 6 to fewer than 2 by the end of Q2, by reallocating the recurring support rota and declining two low margin engagements.
The Achievable test does real work here. If the workload is fixed and headcount is fixed, this goal is not achievable, and writing it down proves that to whoever set the expectation. Capacity goals are also the ones most often set without a number. That is usually why nothing changes.
Team performance
Vague: Improve team productivity.
SMART: Cut average time to first response on client tickets from 9 working hours to under 4 by 30 November, by introducing a morning triage rota and a documented escalation path.
Productivity is the most common vague goal and the least useful one, because it names no unit. Picking a single response, throughput or quality metric turns it into something a team can actually work on.
Quality and rework
Vague: Reduce mistakes.
SMART: Reduce hours logged to rework tasks from 11% of total project hours to under 6% by the end of Q4, by adding a peer review step before client delivery on all work over 8 hours.
Rework is one of the few quality measures that shows up directly in a timesheet. Defect counts and satisfaction scores need a separate system. This one you already have.
Development and retention
Vague: Develop the team’s skills.
SMART: Have three of the five mid level engineers independently leading client facing project calls by the end of the year, evidenced by each running at least four calls without a senior present.
Vague: Keep good people.
SMART: Reduce voluntary attrition on the team from 18% to under 10% over the next twelve months, reviewed quarterly against exit interview themes.
Development goals resist measurement, and so they slide year after year. Measure a demonstrated behaviour instead of a feeling of readiness.
Process improvement
Vague: Reduce admin overhead.
SMART: Reduce time spent compiling the monthly client report from 6 hours to under 90 minutes by the March reporting cycle, by moving from manual compilation to a saved report template.
Budget and profitability
Vague: Make projects more profitable.
SMART: Raise average gross margin across retained accounts from 32% to 38% by the end of the financial year, by reviewing cost of work against billing on every account monthly and renegotiating the two accounts that fall below 25%.
This is the one most managers cannot write, because it needs cost and billing data at project level. If you have hours but not what those hours cost, the goal is unmeasurable no matter how well it is phrased.
Now we can better predict future project requirements
Our company needed a simple way of tracking time used on multiple projects and actiTIME fit the need. Its interface is simple and easy to maintain. We use the application for time management, task estimation and also to communicate deadline information to our team members. Now having actiTIME we can better predict future project requirements!
Turning a team member’s goal into a SMART goal
Much of a manager’s goal setting happens in review conversations, where someone arrives with an intention rather than an objective. The gap between the two is usually a missing number and a missing date.
| What they say | The question to ask | What it becomes |
|---|---|---|
| “I want to get better at estimating.” | Better by how much, on which work? | Bring estimate variance on my own tasks from 40% to under 20% over the next two quarters. |
| “I want more responsibility.” | Responsibility for what, specifically? | Own delivery on two projects under 200 hours end to end by Q3, including client updates. |
| “I want to be less reactive.” | What would your week look like instead? | Keep unplanned work under 25% of logged hours by the end of Q2, reviewed monthly. |
The pattern is consistent: ask what number would move and by when, and the SMART version writes itself. What it does not do is guarantee the data exists, so check that before agreeing to the goal rather than at review time.
SMART goals template
Writing goals to this standard is faster with a structure that forces each criterion in turn. Our SMART goal setting worksheet is a Google Sheet with a column per criterion, a baseline field and a review date. Open it, make your own copy from the File menu, and fill it in.
The column that matters most is the baseline. A SMART goals template that captures only the target lets you write “reduce ticket response time to 4 hours” without ever recording that it currently sits at 9, and a goal with no starting point cannot be evaluated when the deadline arrives.
If you would rather manage goals in software than in a spreadsheet, we have compared the options in our roundup of SMART goal setting software.
How to write a SMART goal in five steps
-
Start from the outcome, not the activity.
“Run weekly one to ones” is an activity. “Reduce voluntary attrition from 18% to under 10%” is an outcome. Activities belong in the plan for reaching the goal, not in the goal itself, or you end up measuring effort while nothing changes.
-
Find the baseline before setting the target.
You cannot judge whether a target is achievable without knowing where you are starting from. If the number does not exist yet, establishing it becomes the first goal.
-
Pick a number you already collect, or commit to collecting it.
Goals measured by data nobody gathers go unmeasured by week three. Check the reporting exists before you commit to the metric, not after.
-
Test Achievable against capacity, not optimism.
For a manager this means checking the team has the hours. A goal that requires 20% more output from a team already at full utilisation is a plan for a missed target and a burned out team.
-
Set a review date, not just a deadline.
A deadline tells you when you will be judged. A mid point review tells you when to correct course while there is still time to do it.
Where SMART goals fall down
The framework has real limitations, and knowing them is what separates using it from performing it.
- It rewards what is easy to measure. Mentoring, morale and judgement resist quantification, so goal setting exercises drift toward the countable. The countable is not always the important.
- Achievable can suppress ambition. Anyone whose bonus depends on hitting the target has an incentive to set a soft one. Some goals should sit beyond what is comfortably achievable, and SMART is the wrong tool for those.
- Time-bound produces end loading. A December deadline generates a November scramble unless interim checkpoints exist.
- It assumes conditions hold. A goal set in January against a stable plan deserves revisiting when the plan changes in March. Rewriting a goal is not the same as failing it.
- Individual goals can compete. Two managers with perfectly well formed goals can pull in opposite directions if nobody checked the two were compatible.
Tracking progress once the goal is set
Most SMART goals fail somewhere between writing and review, not because the target was wrong but because nobody could see the number moving until it was too late to act on it.
Several of the manager examples above depend on data most teams already generate but cannot easily report on. Delivery reliability needs estimated versus actual hours per project. Capacity goals need weekly hours per person. Margin goals need cost of work and billing side by side. Rework goals need hours attributed to the right task.
actiTIME produces all of these from the same time entries. Set estimates on tasks and the Estimated vs Actual Time report shows variance as work progresses rather than at project close. Cost rates per person and billing rates per work type feed a Profit and Loss report by customer or project. Project budgets in hours, cost or billable amount show a progress bar that turns red once exceeded. That is a mid point review running itself.
Frequently asked questions
What are the 5 SMART goals?
SMART is not five goals but five criteria that a single goal must meet: Specific, Measurable, Achievable, Relevant and Time-bound. A goal qualifies as SMART when it names exactly what will change, attaches a number you can verify, sits within the capacity you actually have, connects to something the business cares about, and carries a firm date.
How do I write my SMART goals?
Start with the outcome you want, then find the current baseline for it. Pick a metric you already collect. Set a target your team’s capacity can support, and give it a deadline plus a mid point review date. Write it as one sentence containing the number, the change and the date. If you cannot state the baseline, establishing it is the real first goal.
How are SMART goals for managers different from personal ones?
A personal SMART goal depends mostly on your own effort. A manager’s goal is delivered by other people, and that changes two of the criteria. Achievable has to be tested against the team’s real capacity rather than your willingness to work harder. Measurable usually requires data the team generates, such as hours, delivery variance or margin, so the reporting has to exist before the goal is worth agreeing to.
How many SMART goals should a manager set?
Three to five per review period is the practical range. Beyond that, attention divides and progress on all of them slows. If a longer list feels necessary, most of it is usually activities rather than outcomes, and those belong in the plan beneath each goal instead of alongside them.
What should I do when a SMART goal is not met?
Separate the three reasons it can happen. The target was unachievable given capacity, in which case the goal setting was at fault. Conditions changed, in which case the goal should have been rewritten mid period. Or execution fell short, which is the only case that belongs in a performance conversation. Most missed goals are the first two, and treating them as the third is how goal setting loses credibility with a team.
Set the goal, then watch the number
The hard part of a SMART goal for a manager is rarely the wording. It is having the baseline to set it against and the reporting to watch it move before the deadline arrives.
actiTIME gives you estimate variance, capacity per person and project margin from the same time data, so goals about delivery, workload and profitability become measurable rather than aspirational. Start a free 30 day trial. No credit card required, and free onboarding is included if you would rather be walked through the setup.
