Employee goal setting means agreeing two or three goals with each person — typically two outcome goals that serve the team’s objectives plus one development goal — in a conversation rather than a handout. Each one needs a measure, a date, and a clear answer to “what do you need from me to hit this?”
This is the bottom layer of the cascade, and the one where good goal systems most often fall apart: the company and team goals are sound, then individual goals get assigned in five minutes and quietly ignored. Below is how to run it properly for a small team — the two kinds of goals, the 1:1 conversation, and the awkward question about performance reviews. For the layer above, see how to set team goals →
Where individual goals sit
A personal goal exists to move a team goal, which exists to move a company priority. That chain is the whole justification for individual goals — and the test for any you’re about to agree: if you can’t name the team goal it serves, don’t set it. The mechanics of drawing those lines are in how to align team goals with company goals →
Two kinds of employee goals
Most managers set only the first kind, and wonder why goal conversations feel transactional. People need both.
Outcome goals — move the work
A number the team cares about, and the person’s slice of it: conversion from 6% to 10%, response time under two hours. These are what the team is counting on this cycle.
Development goals — grow the person
A capability, not a metric: run the weekly meeting solo, ship a feature end to end, take over the customer calls. These are what makes someone want to stay.
Two outcome goals plus one development goal is a good default for a cycle. The development one is what turns a goal conversation from an assignment into a career discussion.
How to run the goal-setting conversation
Six moves. The order matters more than anything else here — especially that they draft before you do.
Share the team’s goals first
Send the team’s two or three goals ahead of the conversation. Nobody can write a sensible personal goal without knowing what the team is trying to achieve.
Ask them to draft, not to receive
Have the person propose their own goals before you offer yours. What people write themselves, they own; what they’re handed, they merely comply with.
Shape it together in the 1:1
Your job is to sharpen, not to overwrite: is it the right slice of the team goal, is it measurable, is the bar honest? Push back on vagueness, not on ambition.
Agree the measure and the deadline
Every goal gets a number and a date — “from 15 to 25 demos a month by September 30.” If you can’t say how you’ll both know it’s done, you haven’t finished the conversation.
Name what they need from you
Time, budget, access, a decision, someone else’s help. A goal handed over without the means to hit it isn’t a goal, it’s a setup — and this is the question managers skip most.
Book the check-in rhythm
Agree when you’ll look at it — usually the existing 1:1, every week or two. Goals reviewed once at year-end are performance theatre, not management.
Once you’ve agreed what the goal is, write it tightly — the format that does this best is in how to write SMART goals →
A worked example: one person’s quarter
Say Chloe works on lifecycle marketing, and her team’s goal is to turn more trials into paying customers. Her quarter might look like this.
Lift email-to-trial conversion from 6% to 10% by the end of Q3.
Publish and promote 6 customer stories by the end of Q3, one per fortnight.
Run the weekly growth meeting solo for the last six weeks of the quarter.
Three goals, each with a number or an unmistakable finish line, two of them visibly serving the team goal and one building Chloe. That is a whole quarter for one person — not eight bullet points nobody revisits.
Employee goals and performance reviews
Here’s the tension nobody enjoys naming: the moment a goal decides someone’s rating or bonus, they will set a target they’re confident of hitting. You get safe goals, healthy-looking numbers, and no information. But it’s also unrealistic to pretend goals never touch reviews.
Separate the two kinds. Committed goals — ones you both genuinely expect to be met — are fair to discuss in a review. Genuinely ambitious stretch goals stay out of it and stay unscored, so aiming high costs nothing. If you run OKRs, this is exactly why OKR scores belong away from appraisal.
What goes wrong
Six patterns account for most individual goals that die by week three.
Handing goals down
The fastest way to get compliance instead of commitment. Bring the team context and let the person draft first — then shape it together.
Too many per person
Five or six “priorities” means everything gets partial attention. Two or three per cycle, and one of them can be development.
Measuring activity
“Send 200 emails” is effort, not result. Measure what the effort is supposed to produce, or a busy quarter can still change nothing.
Goals nobody can trace upward
A personal goal that serves no team goal is local busywork with a deadline. Draw the line explicitly, in writing.
No support agreed
Setting the target and walking away. If the person needs a decision, a budget, or someone’s time, that belongs in the goal conversation.
Only development goals
Courses and conferences with no outcome attached. Growth matters, but a whole cycle of pure learning leaves the team’s work untouched.
Keeping them alive afterwards is a rhythm problem, not a goal-writing one — use the goal check-in template in your existing 1:1.
Celorly is built for draft-then-shape: a person can propose their own goal and their lead reviews and approves it, so ownership starts with the people doing the work. Every goal carries one owner and connects to the team goal above it, visibility settings let a development goal stay private if it should be, and progress lives on one screen — so your 1:1 starts from the numbers instead of trying to remember them.
Employee goal setting — quick answers
What is employee goal setting?+
It’s agreeing two or three goals with each person — usually a mix of outcome goals that serve the team’s objectives and one development goal — in a conversation rather than a handout. Each goal gets a measure, a deadline, and an agreement about what the person needs in order to hit it.
How do you set goals with an employee?+
Share the team’s goals first, ask the person to draft their own, then shape them together in a 1:1: check that each is the right slice of the team goal, make it measurable, agree the deadline, name what they need from you, and book a regular check-in. Draft-then-shape is what produces ownership.
How many goals should an employee have?+
Two or three per cycle, one of which can be a development goal. More than that and everything gets partial attention — an individual has less room to spread focus than a team does.
What’s the difference between performance goals and development goals?+
A performance or outcome goal changes a number the team cares about — conversion, revenue, response time. A development goal grows a person’s capability, like running a meeting solo or shipping their first feature end to end. Most people should carry both: two outcome goals and one development goal is a good default.
Should employee goals be tied to performance reviews?+
Be careful. The moment a goal decides someone’s rating or bonus, they will set targets they know they can hit — so you get safe goals and honest-looking numbers. If goals must feed a review, use committed goals you both expect to be met, and keep genuinely ambitious stretch goals separate and unscored.
What if an employee sets goals that are too easy?+
Treat it as information, not defiance. It usually means either the stakes feel unsafe — missing looks punishable — or the person can’t see how their work connects to anything that matters. Fix the safety and the context first; the ambition tends to follow.