Set Team Goals for a Quarter That Actually Steer Work
Turns strategy into a small set of team goals with real measures, named owners, and an explicit list of what the team is not doing — plus the review cadence that keeps them alive past week three. Use it at the start of a planning cycle.
0 likes
0 dislikes
Sign in to rate this prompt
Prompt
You are an experienced manager who has written goals that shaped a quarter and goals that were never mentioned again after the kickoff. The difference is whether they change what people say no to.
The team and what it is responsible for: {{team_scope}}
What the wider organization is trying to achieve: {{company_priorities}}
What my manager expects from us: {{manager_expectations}}
Team capacity, honestly — headcount, gaps, ongoing commitments: {{capacity}}
What we did last quarter and how it went: {{last_quarter}}
The period: {{time_period}}
Build the goals.
1. **Start from the constraint, not the ambition.** Given ongoing operational load, known absences, and unfinished work carrying over, how much genuinely new capacity exists? Most goal-setting fails here: goals are set against theoretical capacity and then quietly abandoned when reality arrives. State the realistic number before proposing anything.
2. **Propose three to five goals. No more.** For each: the outcome in one sentence, why it matters to the wider priorities, and a measure. Prefer a measure of the outcome over a measure of the activity — "reduce time-to-first-response to under four hours" rather than "improve support processes." Where an outcome genuinely cannot be measured this quarter, say so and use a clear deliverable instead of inventing a number, and flag it as such.
3. **Name an owner for each.** One person accountable, not a group. Say what the owner is accountable for — the outcome, or the effort — and be honest where the team does not fully control the result.
4. **Write the explicit not-doing list.** Goals only steer if they cause something to be declined. Name the work we are choosing not to do, the requests we will push back on, and what we will say. This is the section most teams skip and the one that makes the difference.
5. **Check for the failure patterns.** Flag any goal that is really a task with a date, that nobody will notice if it is missed, that depends entirely on another team, that measures effort rather than result, or that is so safe it was always going to happen.
6. **Set the review rhythm.** What gets checked weekly, what monthly, and what triggers an honest mid-quarter renegotiation rather than a quiet slide. Say what "off track" looks like for each goal early enough to act.
7. **Write the version I share with the team**, including how each person's work connects to at least one goal — and be honest about anyone whose work does not, because that is a finding.
Finish with the goal most likely to fail and what would have to be true for it to succeed.