How Goals Connect to Feedback and Reviews

Goals aren’t just task lists — they’re a core part of performance management. Here’s how they connect to feedback, reviews, and ongoing development.

​

Goals provide performance criteria

One of the biggest challenges in performance reviews is subjectivity. Goals create objective criteria: Without goals:

• “Did this person do well?” is vague
• Reviewers rely on recent memory (recency bias)
• Accomplishments from months ago get forgotten
• It’s hard to distinguish between “met expectations” and “exceeded expectations”

With goals:

• “Did this person achieve their goals?” is concrete
• You can review progress over the entire period
• Execution is documented through goal updates
• There’s a shared understanding of what was expected

Goals make performance conversations more fair and grounded in reality.

​

Goals shape feedback

Feedback often relates to how someone is executing on their goals. Examples of goal-related feedback: Positive feedback:

• “You’re making great progress on the API migration — 3 weeks ahead of schedule”
• “The way you unblocked your goal by reaching out to the platform team showed great initiative”
• “Your goal updates are clear and helpful for understanding status”

Constructive feedback:

• “Your Q1 goal hasn’t been updated in a month — let’s discuss what’s blocking you”
• “I noticed your goal scope keeps expanding — let’s talk about focus”
• “You achieved the goal, but the quality wasn’t where we needed it — let’s discuss how to balance speed and thoroughness”

Goal execution provides concrete examples for feedback conversations.

​

Feedback informs goal setting

Feedback from one review cycle often becomes goals for the next. Example flow:

1. Performance review feedback: “Your presentations to leadership could be more concise”
2. Development goal: “Complete executive communication training and deliver 3 concise leadership updates this quarter”
3. Next review: Evaluate whether the goal was achieved and whether the skill improved

This creates a continuous improvement loop:

• Feedback identifies growth areas
• Goals create concrete development steps
• Reviews evaluate whether growth happened

​

Goals in performance reviews

Most performance reviews include goal-based evaluation: Common review questions about goals:

• Did the person achieve their goals?
• Were goals adjusted appropriately when priorities changed?
• How well did they execute (speed, quality, autonomy)?
• Were goals realistic and meaningful?

How goal data appears in reviews:

• List of goals for the review period
• Completion status for each goal
• Progress notes and updates
• Action items linked to goals
• Context from integrations (commits, tasks, etc. related to goals)

Reviewers don’t need to remember what happened — the goal history shows execution over time. Evaluating goal achievement fairly Not all goals are equal:

• A goal completed early exceeds expectations
• A goal completed on time meets expectations
• A goal adjusted due to shifting company priorities isn’t a failure
• A goal that missed the mark due to lack of effort or follow-through is a performance issue

Reviews should evaluate how goals were executed, not just whether they were checked off.

​

Goals create alignment

Goals connect individual work to team and company objectives. Cascading goals example:

• Company goal: Increase annual recurring revenue by 40%
• Sales team goal: Close $6M in new business this year
• Individual goal: Reach 120% of quarterly quota

During a performance review, you can see:

• Whether individual goals aligned with team priorities
• How individual execution contributed to team success
• Whether goals were adjusted when company direction changed

This alignment makes it clear how someone’s work contributed to larger outcomes.

​

Using Topicflow AI for goal-based review prep

When preparing for a performance review, Topicflow AI can help with goal-related questions: For managers writing reviews:

• “What goals did [person] complete this quarter?”
• “Which goals were adjusted and why?”
• “What progress did [person] make on their development goals?”
• “What feedback did I give related to their goals?”

For employees writing self-reviews:

• “What goals did I complete this review period?”
• “What challenges did I face with my goals?”
• “What accomplishments aren’t reflected in my goals?”

AI can recall the data, but humans interpret performance and make judgments.

​

Development goals

Not all goals are about delivering work — some are about building skills. Examples of development goals:

• “Complete the leadership fundamentals course and apply 3 learnings”
• “Shadow 5 customer calls and document insights”
• “Present at the engineering all-hands by end of quarter”
• “Mentor a junior team member on code review practices”

Development goals:

• Often come from feedback or career discussions
• Focus on skill-building, not just output
• Are evaluated based on effort and growth, not just completion

Performance reviews should assess both execution goals (what you delivered) and development goals (how you grew).

​

When goals don’t capture everything

Goals are important, but they don’t capture all performance: What goals measure well:

• Planned work and projects
• Measurable outcomes
• Long-term initiatives

What goals don’t always capture:

• Day-to-day responsibilities
• Helping others (mentoring, unblocking teammates)
• Responding to urgent or unexpected work
• Cultural contributions (e.g., improving team processes)

Performance reviews should consider both goal achievement and contributions beyond goals.

​

Best practices

Set goals collaboratively Managers shouldn’t dictate goals. Collaboration creates ownership and alignment. Reference goals in one-on-ones Don’t wait until review time. Discuss goal progress regularly. Give feedback on goal execution If someone is struggling with a goal, provide feedback early, not just at the review. Adjust goals when priorities change Sticking to an obsolete goal doesn’t demonstrate commitment — it shows inflexibility. Use goals to guide development Feedback should inform future goals, creating a continuous growth cycle.

​

What’s next