15 Performance Goal Setting Examples (With Templates)

Only 27% of leaders could back a rating with goal evidence. Performance goal examples by type, written to be tracked and provable.

Steven Macdonald
5 Mins read
September 2, 2026
15 Performance Goal Setting Examples (With Templates)

A performance goal has a second job most goals don't: it has to stand up in a review months later. Yet only 27% of people leaders say a manager could defend every rating with the goal evidence to back it, while 66% still trust those ratings. That gap is what separates a performance goal that holds up from one that's forgotten — and it comes down to how the goal is written and whether its progress was tracked all period, not how it sounded at the planning meeting.

Performance goal setting is the practice of writing individual goals that both drive the work and document it — so that when the review arrives, the rating rests on evidence rather than the manager's memory of the last few weeks. Done well, a performance goal points someone at a real outcome and leaves a trail of progress behind it. Done the usual way, it's a sentence written once, filed, and reconstructed from memory the night before the review.

This guide gives performance goal examples by type — outcome, behavioural, and development — each written to be measurable and trackable. The examples sit inside the wider practice of goal setting, and they connect directly to how those goals later inform a performance review.

Set performance goals you can prove

OKRs Tool keeps every goal owned, tracked weekly, and visible — so the review rests on evidence. Free for up to 5 users.

Start Free →

What Makes a Performance Goal Hold Up

The Performance Rating Benchmark Report surveyed 230 people and HR leaders and found a problem at the centre of most review cycles: ratings are trusted but not provable.

66% of people leaders trust their performance ratings, but only 27% say a manager could defend every rating with goal evidence.

Two-thirds of leaders trust their ratings, yet barely a quarter say a manager could back every one with the goal record to support it. The gap comes down to documentation more than trust: 65% have seen a rating the goal evidence didn't support, and 35% have to reconstruct an employee's goals from memory at review time. A performance goal only closes that gap if it was written to be measured and then actually tracked. The three types below are all built that way.

Outcome Goals: Move a Number

An outcome performance goal names a result the person is accountable for and a number that proves it moved. These are the goals that carry the most weight at review time because they can't be argued — the key result moved or it didn't.

Outcome Goals 5 examples
Goal 1
Performance GoalIncrease net revenue retention on your accounts from 104% to 115% by year-end.
  • Metric Net revenue retention across your book
  • Baseline → Target 104% → 115%
  • Owner The account owner, reviewed weekly
  • Deadline Year-end
Goal 2
Performance GoalCut average first-response time on support tickets from 6 hours to 2 hours this quarter.
  • Metric Average first-response time
  • Baseline → Target 6 hours → 2 hours
  • Owner Support lead on shift rota
  • Deadline End of quarter
Goal 3
Performance GoalRaise qualified pipeline generated from 12 to 20 opportunities per quarter.
  • Metric Qualified opportunities created
  • Baseline → Target 12 → 20 per quarter
  • Owner The individual rep
  • Deadline End of quarter
Goal 4
Performance GoalImprove the team's on-time delivery rate from 78% to 92% by cycle end.
  • Metric On-time delivery rate
  • Baseline → Target 78% → 92%
  • Owner Delivery manager
  • Deadline Cycle end
Goal 5
Performance GoalGrow feature adoption in your product area from 12% to 35% of active accounts.
  • Metric Feature adoption among active accounts
  • Baseline → Target 12% → 35%
  • Owner Product manager for the area
  • Deadline Cycle end


Each names a baseline and a target, so progress is visible all period and the review reads from a record rather than a recollection. In a scan of 20,952 key results, 52% turned out to be activity dressed as a goal — the outcome framing is what stops a performance goal collapsing into a to-do list.

Behavioural Goals: Change How the Work Happens

Not every performance goal is a metric. Behavioural goals capture how someone works — collaboration, communication, reliability — and the trick is to make them observable rather than vague. "Be a better communicator" can't be scored; a behavioural goal with a concrete signal can.

Behavioural Goals 5 examples
Goal 6
Performance GoalRun every project kickoff with a written brief circulated 48 hours ahead, all quarter.
  • Signal Written brief exists, sent 48h ahead
  • Target Every kickoff this quarter, no exceptions
  • Check Reviewed in the weekly check-in
Goal 7
Performance GoalRespond to cross-team requests within one business day, tracked across the cycle.
  • Signal Response logged within one business day
  • Target 90%+ of requests across the cycle
  • Check Sampled weekly
Goal 8
Performance GoalGive structured written feedback on every design review, rather than verbal-only.
  • Signal Written feedback attached to each review
  • Target Every design review this cycle
  • Check Confirmed in the weekly review
Goal 9
Performance GoalClose each sprint with a documented retro and one committed change, every sprint.
  • Signal Retro doc + one committed change logged
  • Target Every sprint this cycle
  • Check Retro doc reviewed at sprint close
Goal 10
Performance GoalSubmit next-week priorities every Friday for the full quarter.
  • Signal Priorities posted each Friday
  • Target Every Friday for the quarter
  • Check Visible in the weekly check-in

Development Goals: Grow the Person

Development goals build capability for the next role rather than hitting this quarter's number. They're the easiest to let slide because nothing breaks if they slip, which is exactly why they need a deadline and a visible marker of progress.

Development Goals 5 examples
Goal 11
Performance GoalComplete the advanced SQL certification and ship one self-serve dashboard using it by Q3.
  • Milestone Certification passed + dashboard shipped
  • Deadline By end of Q3
  • Check Progress noted in the weekly review
Goal 12
Performance GoalLead three client presentations solo this quarter, with feedback captured after each.
  • Milestone Three solo presentations delivered
  • Deadline This quarter
  • Check Feedback logged after each
Goal 13
Performance GoalShadow two discovery calls a week and run your first solo discovery by cycle end.
  • Milestone First solo discovery call run
  • Deadline By cycle end
  • Check Two shadowed calls logged weekly
Goal 14
Performance GoalPublish four internal write-ups sharing a technique with the wider team this quarter.
  • Milestone Four write-ups published
  • Deadline This quarter
  • Check One tracked per fortnight
Goal 15
Performance GoalMove from contributor to reviewer: review and merge peers' work on ten pull requests.
  • Milestone Ten peer PRs reviewed and merged
  • Deadline By cycle end
  • Check Count updated weekly


Tie development goals to a cadence the same way you would an outcome goal. A development goal reviewed weekly gets the same completion lift as any other; one filed and revisited only at year-end is the one that never happens.

Why Tracking Decides More Than Wording

However well any of these examples is written, the Goal-Setting Benchmark shows the wording is the smaller half of the result.

Teams that set and track goals well hit them 51% of the time; a rough goal tracked well hits 33%, a polished goal left to drift 29%, and poor at both 18%.

A performance goal set well but left to drift lands at 29% — barely ahead of one set badly. Tracked closely, a goal reaches 51%. For performance goals the stakes are higher than completion alone: an untracked goal doesn't just miss, it leaves the review with nothing to stand on.

That's how a rating ends up trusted but unprovable. The fix is the same for all three types — one owner, a weekly check, and progress kept somewhere visible on one platform rather than reconstructed at review time.

Keep Goals and Ratings on Speaking Terms — Not Fused

One caution the data is firm on: writing sharp performance goals doesn't mean welding them directly to the rating. When a goal's score is the rating, people set targets they've already cleared.

Use goal evidence as the backbone of a fair review — the record 65% of leaders wish they had — while leaving room for judgement, so the goal stays a real stretch rather than a negotiated floor. Score on a 0.0–1.0 scale where a 0.7 is strong, and let the tracked history inform the rating rather than dictate it.

Put the Examples to Work

Pick two or three performance goals per person — a mix of an outcome goal and one behavioural or development goal usually fits a review cycle well. Write each with a baseline and target, give it one owner, and set the weekly check-in before the cycle starts.

Do that and the review months later has a record behind it instead of a memory. The examples are only the starting point; the goal setting habits underneath them are what make a performance goal hold up when it matters.

Make every performance goal provable

The OKRs Tool platform keeps goals owned, tracked, and visible all period — so the review rests on evidence, not memory. Free for up to 5 users.

Start Free →


Data: the Performance Rating Benchmark Report (230 People and HR leaders), the Goal-Setting Benchmark (280 operations and strategy leaders), and OKRs Tool platform data (876 organizations, 20,952 key results).

CEO Photo

Founder

Steven Macdonald│LinkedInX

Steven is the founder of OKRs Tool, OKR software built for senior operators inside growing companies. Trusted by 350+ teams to run OKRs that survive beyond the first cycle — with weekly check-ins, required KR ownership and a visual alignment map that shows how every goal connects.