The OKR theater trap
You've set your team goals. They're specific, measurable, aligned with company objectives.
Your team hasn't done any of it. Because they were written by your manager, not you.
This is the team version of the rumination loop. Setting team goals is not the same as achieving them. You can hit every metric and still be in the same position.
The truth: Team goals are usually manager-mandated, not self-chosen. Your team's real growth happens when you choose your own goals within the constraints of your role.
The Name/Frame/Build method for team goals
Name it
What the team actually wants to achieve. "I want us to ship a better product" — not "increase quarterly deliverables."
Frame it
A shared project with deadline. "Ship the Q3 feature by end of quarter." Not "improve product quality."
Build it
One step in your next team meeting. "Propose a sprint plan for the feature."
The four things that keep team goals stuck
1. OKR theater over real growth. Hitting every metric is not the same as growing as a team.
2. Waiting for permission. Don't wait to be asked. Volunteer, apply, take the lead.
3. Setting instead of achieving. A team goal you don't act on is not a goal — it's decoration for your OKR doc.
4. Thinking quarterly instead of weekly. A 90-day goal is too far away to act on. What can you do this week?
The bottom line
Team goals are usually manager-mandated, not self-chosen. Your team's real growth happens when you choose your own goals within the constraints of your role.
Frequently asked questions
What are good team goals?
Name what the team actually wants to achieve (not the manager's metric), Frame it as a shared project with deadline, Build one step in your next team meeting.
Should team goals align with company objectives?
If they do, great. But don't let alignment become an excuse for vagueness.
How do I set team goals my manager won't like?
Pitch them as value-adds. "I want us to ship X because it will improve Y." Frame it in terms of business impact.