What makes a goal review-ready?
SMART goals examples for performance reviews is a key topic in modern project management and teamwork. SMART goals are specific, measurable, achievable, relevant, and time-bound. For a performance review, add two more tests: attributable and evidenced. If the result would have happened without the person, or if the proof lives only in someone’s recollection, the goal cannot carry a rating.
The SMART formulation dates to George T. Doran’s 1981 article in Management Review. Goal-setting research by Edwin Locke and Gary Latham found that specific, difficult goals outperform vague “do your best” targets when people receive feedback and have the ability to act. A performance review is the formal feedback loop in that model. If the loop contains no data, the goal loses most of its effect.
| Test | Question | Fails when |
|---|---|---|
| Specific | What exactly changes, for whom? | The goal uses a verb like “support” or “improve” with no object |
| Measurable | Which number, from which system? | The metric is a survey sentiment with no baseline |
| Achievable | Could a competent person hit this with normal resources? | The target depends on another team’s roadmap |
| Relevant | Does it connect to a team or company priority? | The goal is a personal hobby dressed as strategy |
| Time-bound | When are the checkpoints and the final measurement? | The deadline is “end of year” with no interim review |
| Attributable | What did this person specifically do? | The result is a team outcome with no role clarity |
| Evidenced | Where will the proof live in December? | The evidence is a memory or a Slack thread |
The last two tests are what separate a development plan from a review document. Write them into the goal at kickoff, not at review time.
How do you write a goal so it survives the review?
Three habits do most of the work.
Name the artifact. Every goal should point to something that will exist: a dashboard, a signed contract, a runbook, a hiring plan, a customer letter. “Reduce churn” is a wish. “Reduce logo churn from 14% to 9%, tracked in the monthly retention dashboard, with two documented save plays” is a goal with a paper trail.
Set the baseline in the first two weeks. A baseline measured in November is a negotiation. A baseline measured in January is a fact. If the metric has no history, run a two-week sample and label it as an estimate.
Agree the weighting early. A goal that carries 40% of the rating deserves more scrutiny than one that carries 10%. Write the weights into the plan document and have the employee confirm them. Reviews get contentious when weights appear for the first time in the calibration room.
There is also a language habit worth adopting: write each goal in the past tense as a completed sentence. “Reduced onboarding time from 34 to 21 days for engineering hires, measured across 12 hires in H2.” If the past-tense sentence sounds implausible when you write it, the goal needs work.
Join Doitify Today
Move projects forward without the chaos: all your tasks, progress, and team reports in one unified workspace. Built for companies, startups, and remote teams — with a quick setup and a free trial.
What are 14 SMART goal examples for performance reviews?
The examples below are organized by role family. Each includes the goal, baseline, target, evidence source, and the line you would use in the review conversation.
Individual contributors
1. Improve delivery predictability. Ship 85% of committed sprint scope, measured as completed story points against committed points. Baseline: 68% average over the previous two quarters. Evidence: sprint reports exported quarterly. Review line: “You closed the commitment gap from 32 points to 12, and the trend held for six sprints.”
2. Cut code review turnaround. Reduce median first-review time from 19 hours to 6 hours without increasing review comments per pull request. Evidence: repository analytics, monthly median. Review line: “Median review time fell to 5.4 hours while review depth held steady at 3.1 comments per pull request.”
3. Close incident follow-through. Complete 100% of post-incident action items within 30 days, with an owner and a verification step for each. Baseline: 54% completed on time across the prior 13 incidents. Evidence: incident tracker. Review line: “Eleven of eleven action items closed within 30 days, and repeat incidents in the same service fell from four to one.”
4. Raise documentation adoption. Move runbook usage from 38% to 70% of on-call resolutions, measured by links opened during incidents. Evidence: documentation analytics plus a five-question on-call survey. Review line: “Runbook usage reached 74%, and median time-to-resolution dropped by 11 minutes.”
5. Build a promotion case with evidence. Deliver three scoped projects at senior scope, each with a written impact statement covering problem, action, result, and peers affected. Baseline: one project at that scope in the prior year. Evidence: project archive and two peer confirmations. Review line: “All three impact statements were reviewed by your skip-level, and two peers cited your work in their own reviews.”
Customer-facing roles
6. Improve retention in a named account book. Reduce logo churn from 14% to 9% across a 60-account book. Evidence: CRM retention report, reviewed monthly. Review line: “Churn landed at 9.8%, with two of the three saved accounts documenting a named save play.”
7. Shorten time to first value. Reduce median onboarding time from 34 to 21 days for new accounts. Evidence: onboarding tracker with dated milestones. Review line: “Median onboarding fell to 23 days across 28 accounts, and 30-day activation rose from 61% to 79%.”
8. Improve escalation quality. Cut escalations caused by missing context from 7 per quarter to 2, with a handoff template used on every enterprise ticket. Evidence: escalation log with root-cause tags. Review line: “Two context-related escalations this year, down from seven, and the template is now standard for the team.”
Managers
9. Reduce time-to-productivity for new hires. Cut ramp time from 12 to 8 weeks for engineering hires, measured by first independent shipped change. Baseline: 12.4 weeks across the last six hires. Evidence: onboarding records and manager check-ins at 30, 60, and 90 days. Review line: “Five hires ramped in an average of 8.6 weeks, and two of them shipped independently in week seven.”
10. Act on engagement data. Raise the team’s “I receive useful feedback” score from 3.1 to 4.0 on a five-point scale, with two documented process changes. Evidence: twice-yearly pulse survey and a change log. Review line: “The score reached 3.9, and the monthly feedback ritual you introduced is now used by two other teams.”
11. Improve hiring throughput without lowering the bar. Reduce median time-to-offer from 41 to 28 days while maintaining a 90% offer-acceptance rate. Evidence: applicant tracking system plus offer log. Review line: “Time-to-offer fell to 27 days, acceptance held at 92%, and no hire was downgraded at the debrief stage.”
12. Build a bench of internal successors. Identify and develop two ready-now successors for critical roles, each with a documented development plan and at least one stretch assignment. Evidence: talent review notes and assignment records. Review line: “Both successors were rated ready-now in calibration, and one has already backfilled a leave.”
Operations, project, and specialist roles
13. Reduce process cycle time. Cut invoice processing from 6.2 to 3.5 days median, with an error rate below 1.5%. Evidence: finance system report, monthly. Review line: “Median cycle time reached 3.4 days and the error rate finished at 1.1%, so the automation paid for itself in the first quarter.”
14. Deliver a cross-functional dependency on time. Land the data migration by the agreed date with zero unplanned downtime and a documented rollback test. Baseline: the previous migration slipped 19 days. Evidence: change record, rollback test log, and stakeholder sign-off. Review line: “The migration landed on the committed date, the rollback test passed, and the finance close ran without a manual workaround.”
Development and improvement plans
15. Turn around a performance gap in 90 days. Raise on-time delivery from 61% to 90% and reduce rework from 18% to 8% within one quarter, with weekly check-ins and a written recovery plan. Evidence: weekly dashboard snapshots and check-in notes. Review line: “Delivery reached 91% and rework 7% in week eleven, and the weekly cadence is now part of the team’s operating rhythm.”
How do you turn a result into review language?
The difference between a weak and a strong review sentence is usually structure, not adjectives. Use problem, action, result, and evidence in that order, and keep it under 40 words.
| Weak phrasing | Review-ready phrasing |
|---|---|
| “Did a great job on onboarding.” | “Cut engineering ramp time from 12.4 to 8.6 weeks across five hires by rebuilding the first-two-weeks checklist.” |
| “Improved customer satisfaction.” | “Raised CSAT from 4.1 to 4.6 on 212 surveys by adding a 48-hour follow-up on low scores.” |
| “Helped with the migration.” | “Owned the rollback plan for the migration, which passed testing and cut the cutover window from 9 to 4 hours.” |
| “Missed the target but worked hard.” | “Delivered 86% against a 90% target, closing 78% of the gap from the 72% baseline.” |
That last example is the most useful pattern in a review. Expressing results as gap closure is fairer than a raw percentage and more informative than a pass/fail. The math is simple: actual minus baseline, divided by target minus baseline. At 86% actual, 72% baseline, and 90% target, the result is (86 − 72) ÷ (90 − 72) = 14 ÷ 18 = 77.8%.
The same approach works for a partial miss on a bigger goal. A churn target of 9% from a 14% baseline, with an actual of 9.8%, closes 84% of the gap: (14 − 9.8) ÷ (14 − 9) = 4.2 ÷ 5 = 84%. That reads very differently from “missed the target by 0.8 points,” and both statements are true.
How do you use SMART goals in calibration?
Calibration is where goal quality gets tested by people who did not write the goals. A simple weighted score keeps the conversation anchored.
| Goal | Weight | Attainment | Weighted points |
|---|---|---|---|
| Retention | 40% | 120% | 48.0 |
| Onboarding time | 25% | 90% | 22.5 |
| Escalation quality | 20% | 75% | 15.0 |
| Development plan | 15% | 100% | 15.0 |
| Total | 100% | 100.5% |
A total of 100.5% means the person broadly met expectations with a strong retention result and a partial miss on escalations. The value of the table is not the decimal; it is that every number has a source and every weight was agreed in January.
Two calibration rules keep this honest. First, cap any single goal’s weight at 40% so one lucky outcome cannot carry the year. Second, require a written comment for any attainment below 80% or above 120%, because outliers usually mean the baseline or the target was wrong, not that the person was heroic or negligent.
What mistakes make performance goals fail?
- Writing goals in December. A goal created during review season is a justification, not a plan. If the goal did not exist in January, say so and use project evidence instead.
- Using only outcome goals. Outcomes depend on markets, dependencies, and timing. Pair each outcome with a behavior goal the person controls.
- Equal weighting by default. Four goals at 25% each implies they matter equally, which is rarely true and invites score inflation.
- No evidence owner. If nobody is responsible for producing the number, the number will not exist at review time.
- Changing the target mid-year without a note. Adjusting a goal is legitimate. Adjusting it silently destroys trust in the whole review system.
- Confusing activity with impact. “Ran 14 workshops” is a calendar fact. “Reduced onboarding defects by 31%” is an outcome.
How does Doitify help with review-ready goals?
The weakest link in most review processes is the twelve-month gap between setting a goal and evidencing it. Doitify closes that gap by keeping goals, tasks, and progress in one workspace: each goal can carry a numeric target, weekly updates roll into a trend line, and the review conversation starts from a report instead of a reconstruction.
For a manager running reviews across eight people, the practical benefit is that the evidence is already collected when review season starts. Goals, check-ins, and completion data live next to the work that produced them, so the January plan and the December evidence are the same record. It is not a compensation or calibration platform, and it does not replace judgment, but it removes the annual scramble.
FAQ
Conclusion
A performance review is only as good as the goals that feed it. Write each goal with a baseline, a target, an evidence source, and a past-tense sentence you would be comfortable saying out loud in December. Weight the goals before the year starts, express results as gap closure, and keep at least one behavior goal alongside the outcomes.
The 15 examples above are templates, not prescriptions. The structure is the durable part: specific behavior, measured baseline, defensible target, named evidence. Get those four right and the review conversation becomes a discussion about work rather than a debate about memory.
If this post on SMART goals examples for performance reviews was helpful, you might also enjoy Goals vs Milestones: What’s the Difference? and Goal Tracking Template.
Join Doitify Today
Move projects forward without the chaos: all your tasks, progress, and team reports in one unified workspace. Built for companies, startups, and remote teams — with a quick setup and a free trial.
