Using SMART Goals to Create Clarity

SMART goals are a communication tool. Managers should use them when a conversation needs enough structure that both people can leave with the same understanding of the expectation.

The goal is not to create paperwork. The goal is to make sure both the manager and employee understand what success means, how progress will be evaluated, and what support is needed.

Use SMART goals as a shared reference point, not as a script. A good goal should make the next conversation easier because both people know what they agreed to.

When to ask for SMART goals

Managers should ask for SMART goals when:

• An employee wants to improve in a specific area.
• A project or responsibility has unclear ownership.
• Expectations are vague or misaligned.
• A performance concern needs clearer follow-up.
• An employee is preparing for more responsibility, career growth, or promotion.
• A recurring issue needs an explicit improvement path.

SMART goals are less useful when the expectation is already obvious, the issue is urgent enough to require direct action, or the conversation is mainly exploratory.

How to guide the conversation

Use questions that make the goal more specific without taking ownership away from the employee:

• What would success look like by the end of this period?
• How would we know this improved?
• Can we make this more specific?
• What is a realistic milestone for next week?
• What support do you need to make this achievable?
• How does this connect to your role, team priorities, or growth path?

The manager should guide the conversation toward clarity, but the goal should not feel imposed without context. If the employee disagrees with the expectation, resolve that first. A written goal will not fix misalignment that has not been discussed.

SMART goal checklist

A useful goal should be:

• Specific: the expected behavior or outcome is clear.
• Measurable: progress can be observed or evaluated.
• Achievable: the employee has a realistic path to complete it.
• Relevant: the goal connects to role expectations, team priorities, or growth.
• Time-bound: there is a clear date, period, or checkpoint.

If a goal fails one of these checks, keep refining it before treating it as an agreement.

Examples

Instead of:

• Improve communication.

Use:

• By the end of the next sprint, post a written status update in the project channel at least twice per week, including current progress, blockers, and next steps.

Instead of:

• Be more proactive.

Use:

• For the next four weeks, identify at least one risk or dependency before each planning meeting and share it with the team before work begins.

Instead of:

• Get better at code reviews.

Use:

• During the next month, review at least three pull requests per week and leave comments that identify risks, missing tests, or unclear implementation choices when relevant.

Review cadence

SMART goals need a review point. Without one, they become documentation instead of management.

Before ending the conversation, agree on:

• The next checkpoint.
• What evidence or examples will be reviewed.
• How the employee should ask for help before the checkpoint.
• What the manager will do to remove blockers or provide support.

What managers should avoid

Managers should not:

• Turn every conversation into a formal goal-setting exercise.
• Use SMART goals as punishment.
• Write the goal alone without employee input.
• Measure activity when the real expectation is an outcome.
• Create goals without discussing support, constraints, or tradeoffs.
• Keep goals rigid when business priorities change.
• Treat a missed goal as the whole performance conversation without understanding the context.

Manager responsibility

Managers own the clarity of the conversation. Employees may own the goal, but managers are responsible for helping define expectations, checking for alignment, and removing ambiguity before it becomes frustration.

When a conversation ends with a SMART goal, both people should understand:

• What is expected.
• Why it matters.
• When it will be reviewed.
• What support or constraints exist.
• How success will be recognized.