The Goal-Setting Playbook: A Recipe for Goals Employees Actually Chase
Most goal-setting sessions end with a list of objectives that get reviewed once at the end of the year , right before people scramble to rationalize whatever actually happened.
The problem isn't the goals themselves. It's the process. Goals set in a one-size-fits-all meeting, with vague metrics and no connection to what the employee actually cares about, are decorations. They signal that the company takes goal-setting seriously without producing the accountability or development that goals should create.
This playbook gives you a 5-step recipe for setting goals that stick. Goals that align with company priorities, connect to what employees actually want from their careers, and get reviewed often enough to course-correct when reality shifts.
The Recipe at a Glance
Outcome you're trying to achieve: A set of 3–5 goals per employee that the manager and employee both believe in, tied to measurable outcomes, with a built-in review cadence.
Ingredients:
- Company priorities for the quarter/half (you need these before you set individual goals)
- A career conversation with each employee (what do they actually want to get better at?)
- A structured goal-setting conversation
- A shared writing surface where goals live
- A 2-week review pulse to catch when goals become stale
When to use this: At the start of each performance cycle , quarter or half, depending on your cadence.
When NOT to use this: Mid-cycle goal pivots or urgent project additions. Those need a separate lightweight process. This recipe is for cycle kickoffs.
Step 1: Start With the Company Layer, Not the Individual Layer
The most common goal-setting failure: managers run goal-setting conversations without a clear view of what the company needs from this person's team right now.
The result is goals that feel meaningful in isolation but don't ladder up. You end up with five employees each hitting 100% on their individual goals while the team misses its targets.
Before every goal-setting cycle, get clear on:
- What does the company need from this team to succeed this quarter?
- What does this team need to do differently or better compared to last cycle?
- What capabilities does this team need to build that we don't currently have?
These three questions generate the team context. Individual goals should emerge from this context , not from a blank page.
If you don't have company priorities in written form, don't improvise goal-setting. Escalate the absence of direction before creating a cascade of misaligned individual goals.
Step 2: The Career Conversation , Before the Goal Conversation
Most managers merge the career conversation into the goal-setting conversation. Don't.
Career conversations and goal conversations are different. Career conversations are about what the employee wants , where they want to go, what they're trying to develop, what kind of work energizes them. Goal conversations are about alignment between what they want and what the organization needs.
Running them simultaneously collapses the nuance. The organizational priority dominates, and the employee feels like their growth agenda was an afterthought.
The career conversation (10–15 minutes, ideally a week before goal-setting):
Ask three questions and listen:
- "Looking back at last cycle , what did you work on that felt most meaningful or energizing? What felt draining?"
- "What do you want to be better at six months from now that you're not good at today?"
- "Is there anything you want to do more of, or anything you want to stop doing, in how you spend your time?"
Write down their answers. You need them in the goal-setting conversation to build goals that include a development component , not just output targets.
Step 3: The Goal-Setting Conversation , Structure and Sequence
The goal-setting conversation has four parts. If you skip any of them, you get weaker goals.
Part 1: Share the company context (3 minutes)
"Here's what the company needs from our team this cycle: [specific priorities]. That shapes what I think our team's goals should be. Let me share that before we dig in."
This frames the conversation. The employee understands why you're going to propose certain goals.
Part 2: Draft together, don't present and sign (15 minutes)
Share 2–3 goal themes based on the company context and your read of what this person should focus on. Ask: "What do you think is missing? What would you change?"
Goals created together have higher commitment rates than goals handed down. The employee needs to feel like they influenced the outcome.
Part 3: Incorporate the career thread (5 minutes)
Take at least one goal (or a component of one goal) and connect it to what the employee said in the career conversation. "You mentioned you want to get better at stakeholder communication. I think this project goal could be framed around that , does that feel right?"
Not every goal needs a development angle. But at least one should explicitly connect to their growth.
Part 4: Agree on what "done" looks like (5 minutes)
For every goal, establish: What would I see if this was completely successful? What's the minimum acceptable outcome? When will we check in on progress?
Goals without clear success criteria are opinions. Force specificity before you close the conversation.
Step 4: Write the Goals in a Shared System
Goals that only exist in a doc nobody revisits get abandoned. Goals in a system that both the manager and employee can see stay alive.
What a good goal record includes:
- The goal itself (one sentence, present-tense outcome: "Customer satisfaction scores above 90% by end of Q2")
- The "why" , one sentence connecting it to team or company priority
- The development thread , if applicable, what the employee is building through this goal
- 3 or fewer milestones , the specific checkpoints that signal progress
- Owner: who's responsible
- Review date: when you'll next explicitly discuss progress
Common formats that work: OKR tools, goal modules in performance software, a shared doc. Common formats that don't work: email threads, action items buried in meeting notes, verbal agreements.
In Confirm, you can write these goals directly into the platform and tie them to the employee's performance cycle. That way they appear alongside feedback, 1:1 notes, and review ratings , creating a connected record instead of a fragmented trail across tools.
Step 5: Build a Pulse, Not Just an End-of-Cycle Review
Goals reviewed only at the end of the cycle produce one of two outcomes: triumph or rationalization. Neither is a good feedback loop.
The alternative is a 10-minute pulse every two weeks. Not a status update , a brief, honest conversation about whether the goal still makes sense and what's in the way.
Pulse conversation questions (2–3 of these, not all):
- "Where are you on [goal]? Any surprises since we last checked?"
- "Is this still the right goal, or has something changed that makes it less relevant?"
- "What would help you move faster on this? What's in your way?"
- "Did anything happen since last time that we should acknowledge?"
Biweekly pulses catch three things: goals that became irrelevant because priorities shifted; goals that are stuck because of a blocker nobody surfaced; and goals where the employee is crushing it and deserves recognition before the cycle ends.
The last one matters more than managers think. Real-time acknowledgment of progress increases intrinsic motivation far more than end-of-cycle review scores.
Why Goals Fail Even When This Process Is Followed
"We set great goals but nobody looks at them again." This is a cadence problem, not a goals problem. Build the pulse into your 1:1 template. Make it automatic, not voluntary.
"Our priorities change every month. Goals become meaningless." Goals in fast-moving environments should have a shorter horizon (6–8 weeks, not 6 months) and explicit revision rights. Set the expectation upfront: "We'll revisit this goal at week 8 and adjust if priorities have shifted."
"Some people hit their goals on paper but clearly weren't that impactful." This is a goals quality problem. Goals that measure activity (shipped X reports) instead of outcomes (customers used the report and reduced errors by Y%) can be hit without real impact. Improve the metrics.
"My best people keep setting sandbag goals." Happens when goal ratings have direct compensation consequences. People optimize for achievable goals rather than ambitious ones. Decouple goal achievement from comp decisions, or weight stretch goals differently.
Using Confirm for Goal-Setting
Confirm's goal tracking is built to support this recipe end to end:
Goal visibility for both manager and employee. Goals live in a shared space. No "I thought we agreed on X" conversations six months later.
Progress updates without status-meeting overhead. Employees can log brief progress notes between 1:1s. Managers see the cadence of updates , silence on a goal often signals a problem before it surfaces in a conversation.
Goal history tied to performance cycles. When review season arrives, the history of goal revisions and progress notes is already in context with feedback and ratings. No retroactive reconstruction.
ONA data to inform goal alignment. Confirm's organizational network analysis can show you which employees are most central to company outcomes , helping you focus their goals on the work where their influence has the highest leverage.
The Bottom Line
Goal-setting done right isn't a form. It's a 45-minute conversation that connects what the company needs from this person to what this person is trying to become , with a system that keeps both parties honest throughout the cycle.
The recipe is: get the company context first, have the career conversation separately, build goals together, write them in a shared system, and check in every two weeks.
The first cycle using this process will feel slower. By cycle two, managers who run this protocol report significantly fewer end-of-cycle surprises , for them or their employees.
If you want to run this process in Confirm, start here →
