Setting Goals for a Team That Doesn't Love Goal-Setting

You announce it's goal-setting season. The room goes quiet. Then one person says it: "We did this last year and nothing happened."

Nobody argues with them. A couple people nod slightly. Someone checks their phone.

And now you understand, in real time, the actual problem. It's not that your team doesn't care about doing good work. It's that they've been through goal-setting cycles that turned out to be theater: OKRs written for the HR system, quarterly targets forgotten by week six, "stretch goals" that somehow never stretched anyone, and review cycles where everyone got rated "meets expectations" regardless of what they actually did.

The skepticism isn't laziness. It's institutional memory.

Your job isn't to enforce the process. It's to make the process worth trusting again.

Key Facts: What the Research Says About Goal-Setting

• Locke and Latham's Goal-Setting Theory, built on 400+ studies over 35 years, found that specific and challenging goals lead to higher performance than vague "do your best" goals in roughly 90% of cases studied.
• Gartner research found that only 16% of knowledge workers say their goals are clearly defined and connected to company priorities — meaning most teams operate with fuzzy or disconnected targets.
• Gallup reports that only 40% of employees strongly agree their manager holds them accountable to performance goals, and just 30% strongly agree their manager involves them in setting those goals.
• Deloitte's Global Human Capital Trends survey found that only 8% of companies believe their performance management process is highly effective at driving business value — the #1 cited fix is shifting from annual cascaded goals to continuous, team-owned ones.
• MIT Sloan research on OKRs shows that participation in goal-drafting (not just goal assignment) is the strongest predictor of commitment — when people co-author their goals, follow-through roughly doubles.

Why Goal-Setting Fails (and Why Yours Doesn't Have To)

Goal-setting fails for three main reasons. Gallup's survey of employee engagement found that only 40% of employees say their manager holds them accountable to their goals — meaning the majority of goal-setting exercises produce documents that don't drive behavior.

The goals weren't actually used. They got written, filed, and never referenced until the performance review. At that point they were artifacts, not tools. People learn quickly whether goals shape decisions, and if they don't, they stop taking them seriously. A prioritization framework is one way to make goals feel real: when people see how their targets connect to how the team decides what to work on each week, the goals start to have teeth.

The goals were too vague to fail. "Improve customer satisfaction." "Be a stronger communicator." "Support team initiatives." You can never miss targets like these because they don't have a concrete standard. They also don't give anyone direction. Vague goals exist to check a box, not to create accountability.

Goals were tied directly to performance ratings. This is the trust-killer. When people know that setting an ambitious goal risks a bad rating if they miss it, they learn to write safe goals they're guaranteed to hit. The whole system inverts. Instead of goals pushing people forward, they become a negotiation about what level of output is officially required. This dynamic is well-studied in management research: MIT Sloan Management Review research on OKR adoption shows that coupling ambitious goals directly to compensation or ratings is the most common design flaw in corporate goal-setting systems.

Rebuilding trust in the goal-setting process requires making goals visibly useful, not just procedurally correct.

Start By Co-Creating the Purpose

Before you ask anyone to write a goal, spend 15 minutes with your team talking about why you're doing this at all.

Not "because HR requires it." That's the answer that poisons the well before you start. Instead, ask:

"What would make goal-setting actually useful for us this quarter? What would have to be true for it to feel worth doing?"

Listen to what comes back. People will tell you what went wrong before. Let them. You're gathering signal about what they need the process to fix.

Common answers you'll hear:

• "We'd need to actually look at them more than twice a year"
• "They'd need to reflect what we actually work on, not what looks good in a report"
• "We'd need to be honest about what's realistic instead of writing what management wants to see"

Use those answers to shape the process. If people say they need goals that reflect actual work, your goal-setting session starts by listing the actual work and deriving goals from there, not the other way around.

Top-Down and Bottom-Up: Both Matter

The cleanest goal-setting process runs in two directions simultaneously. Harvard Business Review's research on employee goal alignment found that employees who understand how their individual goals connect to organizational priorities are 3.5 times more likely to report being engaged.

Top-down: You share the team's goals with everyone. What are you accountable for as a team this quarter? What does success look like from your manager's perspective? What does the company need from your team? This gives people the context to understand what their individual goals are feeding into.

Bottom-up: You ask each person what they can own within that context. Not "here are your goals" but "given what the team is trying to do, what feels like the right focus for you specifically?"

When both directions meet, you get goals that are connected to real stakes but feel personally meaningful. That combination is what makes goals drive behavior rather than just fill in a template.

The Ownership-First Goal Pattern

The Ownership-First Goal Pattern inverts the traditional cascade: the team member drafts the goal first, and the manager refines it afterwards. You supply the context (team priorities, company direction, constraints) up front, but the first written version belongs to the person who will actually own the work. The manager's job is then to sharpen the language, stress-test the success metric, and commit to the support the goal needs — not to author it. This one reversal is what turns a goal from a quota into a commitment, because people defend what they drafted far more reliably than what they were handed.

In your 1:1s during goal-setting time, try this approach:

"Here's what the team is focused on this quarter. Within that, what are one or two things where you could make the most impact? What feels like a stretch you'd want to take on?"

Then listen. Write down what they say. Help them sharpen the language. Don't replace their goal with your version of it.

Keep Goals Small and Specific

Three to four goals per person. Not ten.

When people have too many goals, they can't prioritize between them. Everything is equally important, which means everything is equally de-prioritizable when things get busy. The result is nothing gets full attention.

And each goal needs a concrete success metric, not a vague aspiration, but a specific thing that will have happened by the end of the quarter.

Use this goal-writing worksheet structure:

---

Goal: [One sentence describing the outcome]

Success metric: [How we'll know this is done: a number, a deliverable, a yes/no condition]

Why this matters: [One sentence connecting it to team goals]

Biggest risk or blocker: [What might prevent this from happening]

What I need from my manager: [Support, resources, clarity, a decision]

---

The "what I need from my manager" field is important. It makes goals a two-way contract rather than a requirement imposed from above. When you, as the manager, are accountable for providing support, the goal becomes shared.

Make Progress Visible Week to Week

Goals get abandoned when the only check-in is at the end of the quarter.

Don't make goals a quarterly event. Make them part of your weekly 1:1 rhythm. Not a formal review every time, just a quick temperature check.

In your 1:1s, you might add one question each week: "How are things going with your [specific goal]? Anything getting in the way?" Some teams pair this with weekly status updates that include a short goal-progress line, so the accountability is visible without requiring a separate check-in.

This does two things. First, it demonstrates that the goals are real. You remember them, you're tracking them, they actually shape your conversations. Second, it surfaces blockers early enough to do something about them.

When someone's goal is at risk, you want to know in week four, not week twelve. If it's week four and they're behind because a dependency hasn't come through, you might be able to fix that. If it's week twelve and the goal is unsalvageable, all you can do is document it.

Read Running 1:1s Your Reports Look Forward To for how to weave goal check-ins into 1:1s without making them feel like interrogations.

Revise Goals Out Loud When the World Changes

One of the most trust-building things you can do as a manager is publicly change a goal when circumstances change.

If the business direction shifts, if a project gets cancelled, if priorities change from above, say: "The goal we set at the start of the quarter no longer makes sense given what's changed. Here's what I think we should focus on instead."

When you do this explicitly rather than just letting the goal quietly die, you show that goals are tools that serve real work, not forms that just need to be completed. And you signal that the team's effort should track reality, not the version of reality from ten weeks ago.

The opposite behavior, ignoring a goal that's obviously irrelevant and still grading against it at review time, is one of the fastest ways to kill trust in the whole system.

The Goal-Setting Kickoff Agenda

Here's a 60-minute team kickoff to run at the start of each quarter:

Part 1: Where we landed (15 min) Quick review of last quarter. What did we finish? What didn't happen? What do we want to carry forward? Be honest. Don't spend 10 minutes explaining why things slipped. Just name them and move on.

Part 2: What matters this quarter (15 min) Share the team-level goals and context. What's the company focused on? What does your manager need from the team? What's the biggest opportunity or risk in the next 90 days? Give people the context they need to set useful goals.

Part 3: Individual brainstorm (10 min) Give everyone five minutes to write down: given what you just heard, what are two or three things you could focus on this quarter that would have real impact? Don't filter. Just brainstorm.

Part 4: Sharing and connection (15 min) Each person shares one or two ideas. The team reacts briefly. You note any natural connections: two people working on related problems who should coordinate, a goal that creates a dependency you need to flag, a goal that doubles up on something another team is doing.

Part 5: Next steps (5 min) Everyone writes up their goals using the worksheet format before the next 1:1. You'll review, sharpen, and finalize in their individual meetings.

---

This agenda gets people into goal-setting mode collaboratively rather than handing down a form to fill out. The social calibration, hearing what others are working on, also helps people write goals that connect rather than goals that silo.

Mid-Quarter Check-In Template

About halfway through the quarter, do a short structured check-in with each person. This is separate from the weekly 1:1 goal conversation. It's a slightly more formal reset.

Mid-quarter questions:

• Looking at your goals from the start of the quarter, what's on track?
• What's at risk, and what would need to change for it to be recoverable?
• Is there a goal that no longer makes sense given what's changed? Should we revise it?
• Is there anything I could be doing differently to help you succeed?
• Is there anything you need that you haven't asked for?

The goal is to catch problems while there's still time to fix them, and to update goals that have been made irrelevant by changes in circumstances.

What Good Looks Like

After a quarter of goal-setting done this way, you'll start to see something different. People will reference their goals in conversation, not just in review forms. They'll flag blockers without waiting for you to ask. Some goals will get hit early and you'll have a quick conversation about what to do next. Some will slip and you'll have an honest conversation about why.

That's what goals are supposed to do. Not optimize performance management paperwork. Actually shape what people work on and how they talk about it.

When your team reaches that state, goal-setting has stopped being a process imposed on them and started being something they use.

Read Your First Performance Review to understand how the goals you set together become the backbone of the performance conversation at year end.

How Rework Keeps Goals From Dying in a Doc

Most goal-setting systems fail at the same spot: the goals get written in one tool (a doc, a spreadsheet, an HR system) and the work happens in another. By week three, nobody opens the goal doc.

Rework Work Ops puts goals and the work that feeds them in the same place. Each team member's 3-4 quarterly goals live as trackable objectives with linked tasks and projects, so when you assign work during the week, you can see which goal it advances. Weekly check-ins are a built-in workflow — each direct report answers a short set of prompts ("what's on track, what's at risk, what do you need from me"), and the manager sees the rollup across the team in one view.

The point isn't more process. It's that goals stop being an artifact you revisit quarterly and become the spine of the weekly 1:1 and the team standup. Work Ops starts at $6 per user per month on Rework's pricing page — which matters for a first-time manager whose budget to buy tools is usually "whatever you can expense."

Learn More

• Your First 30 Days as a Manager
• Career Conversations That Don't Feel Scripted
• Running 1:1s Your Reports Look Forward To
• Your First Performance Review
• Team Prioritization Frameworks
• Weekly Status Updates That Work