A team goal is one number several people move together and nobody moves alone, like “bring median first response on customer questions from 7 hours to under 2 by the end of Q3.” Below are 24 examples grouped by the kind of outcome a team can genuinely share, plus the test that tells you whether what you wrote is really a team goal. Each one is a goal you could set, share, and score in Celorly.
For the session that produces these, see how to set team goals. For goals that belong to one person instead, see employee goal setting → And if you are looking for goals by function rather than by kind, the SMART goal examples by team → list is organized that way.
The test: could one person move it alone?
“Each engineer closes 20 tickets this quarter.”
“Cut time from bug report to fix in production from 12 days to 4 by December 31.”
The first one is five individual goals printed on one page, and it rewards closing easy tickets. The second cannot be moved by anyone working alone: it needs triage, the fix, review, and release to change together. That is the whole difference, and it is worth applying to every goal you are about to call a team goal.
Turning a company number into goals a team can own is lesson 6 of our free course. lesson 6 of 17 in From Zero to Goals: The cascade in practice. Break a company goal into area goals without producing tasks in disguise. You make the calls inside one realistic company, run the exercise on your own goals, and the course ends with a 15 question exam (12 to pass) and a certificate worth putting on your profile.
Team goal examples: delivery the team owns together
Ship the three roadmap items agreed for this quarter by September 30, with none carried over.
Cut the share of work that slips past its committed date from 45% to 15% by the end of Q4.
Reduce work started but not finished at quarter-end from 11 items to 3 by December 31.
Team goal examples: quality nobody can own alone
Cut bugs found after release from 24 to 8 per quarter by the end of Q4.
Raise the share of changes covered by an automated check from 55% to 85% by December 31.
Reduce repeat support tickets on the same root cause from 30% to 10% of the total by the end of Q3.
Team goal examples: speed of response
Bring median first response on customer questions from 7 hours to under 2 by the end of Q3.
Cut time from bug report to fix in production from 12 days to 4 by December 31.
Reduce the time a request waits before someone picks it up from 2 days to 4 hours by the end of Q4.
Team goal examples: one number two teams share
Lift trial-to-paid conversion from 14% to 22% by the end of Q4, owned jointly by product and sales.
Cut the share of demos that need engineering help from 40% to 10% by September 30.
Raise the share of new features used by 20% of customers within 60 days from 1 in 5 to 3 in 5 by year-end.
Team goal examples: customer outcomes a team can move
Raise week-one activation from 38% to 60% by the end of Q4.
Cut new customers who never complete setup from 22% to 8% by December 31.
Raise the share of customers who reach their second successful use within 14 days from 30% to 55% by the end of Q3.
Team goal examples: how the team works
Cut meetings on the team calendar from 14 to 8 hours per person per week by the end of Q3.
Get every goal in the team updated at least once a week for 12 consecutive weeks.
Reduce unplanned work from 40% to 20% of the team’s time by December 31.
Team goal examples: knowledge and coverage
Get every critical system down to no fewer than two people who can run it by the end of Q4.
Cut escalations that can only be handled by one named person from 18 to 5 per quarter by December 31.
Have all six team members complete one handover of their main area by September 30.
Team goal examples: a team that serves other teams
Raise internal satisfaction with the team’s turnaround from 3.1 to 4.2 out of 5 by the end of Q4.
Cut the share of requests that come back for rework from 25% to 8% by December 31.
Publish a decision or answer within 3 working days for 90% of internal requests by the end of Q3.
How to write a team goal that stays shared
Ask whether one person could move it alone
If the answer is yes, it is an individual goal wearing a team badge, and it will be quietly delegated to that person in week two. A real team goal needs at least two people to move.
Give it a single owner anyway
Shared does not mean unowned. One person is accountable for the number being current and for saying when it is slipping. Everybody responsible means nobody updates it.
Resist splitting it into per-person targets
Dividing a team number by five is the fastest way to lose it: people optimize their slice and the shared outcome falls between the slices. Keep the number whole and let the work divide instead.
Cap it at two or three per team per quarter
A team of six with five goals has none. Two is usually the honest number, especially when the team also carries routine work that never appears on the goal list.
Once they are set, the goals have to survive the quarter, which is a separate discipline: see how to track goals and the goal review meeting →
Where team goals go wrong, honestly
The most common failure is the one in the comparison above: a team goal that is really a stack of individual targets. The second is the opposite mistake, a number so far above the team that nothing they do this quarter visibly moves it. Company revenue is a company goal; the team goal is the thing this team can change that feeds it, which is what aligning team goals with company goals is for.
The third is worth naming because it is invisible until review season: a shared goal used as input to individual performance. The moment a team number decides one person’s rating, they start protecting their contribution to it rather than the number, and the honest weekly update stops being possible. Keep shared goals out of individual reviews, and if that is not an option in your company, do not pretend the goal is shared.
A shared goal only works if everyone can see the same number without asking. In Celorly a team goal names the company goal above it, carries one owner and one figure everybody on the team can read and update, and rolls into the quarter close with a score rather than a discussion. No performance reviews, no individual scorecards, and nothing that ties a goal to anyone’s pay. Free while it’s just you. See what Celorly does →
Team goal examples: quick answers
What is a good example of a team goal?+
“Bring median first response on customer questions from 7 hours to under 2 by the end of Q3.” It names one number the whole team affects, a starting point, a target, and a date, and no single person can move it alone.
What is the difference between a team goal and an individual goal?+
A team goal is one number several people move together and it is not divided up. An individual goal belongs to one person and appears in their own review. If a goal can be achieved by one person working alone, it is an individual goal, whatever the header on the document says.
How many goals should a team have per quarter?+
Two or three, including for teams of ten or more. The routine work does not disappear because a goal exists, so a team with five goals is really a team doing its normal job plus five side projects.
Should team goals be split into individual targets?+
Usually not. Splitting a shared number into per-person slices makes each person optimize their piece, and the outcome that mattered sits between the pieces. Divide the work, not the number.
Who owns a shared team goal?+
One named person, even though the goal is shared. Their job is to keep the number current and to raise it early when it starts slipping, not to do the work alone. A goal owned by everyone is a goal nobody updates.