📂Leadership & Organization⏱2-min read📊Beginner🔗7 related

What is a goal-setting meeting?

In one line
A one-on-one meeting early in the year where a team leader and team member agree on the member’s annual personal goals, success measures, and support, and document them. It is the starting point of the year-end review.
⚡ Summary in 3 lines
  • What you agree on in January becomes the basis for year-end reviews
  • The team member drafts, the manager refines
  • Goals with no success measure are the root of distrust in reviews

A well-run goal-setting meeting cuts the year-end review meeting in half. If you agree early in the year on what to do, how much, and how to measure it, December only requires checking against that standard. Without agreement, the December meeting starts with a fight over 'whether that was even my job.' The goal-setting meeting is not the back side of the review but the front side, and the wording agreed here becomes the basis for the rating a year later. Goals are not handed down by the team leader but written by the team member and refined by the leader, and that order determines buy-in.

The meeting usually flows in three steps. Team members draft personal goals based on the team goals from the team kickoff. In the meeting, the team leader and member refine them together, checking alignment with team priorities, the presence of success measures, and appropriate difficulty. Finally, they write down what the leader will do to support those goals. Many companies set 3–5 personal goals, one of which is a personal growth objective. For success measures, use numbers where they exist; where they do not, describe in a sentence what “done” looks like, so interpretations do not diverge at year-end. Difficulty should be reachable with real effort: an unachievable goal is abandoned in January, and one that is too easy fails to differentiate at review time. 30–40 minutes is enough for the meeting, but only if a draft exists beforehand.

The most common failure in practice is replacing the meeting with data entry in a system. When a team leader copies the company-wide KPI and sends the same goals to every member, no meeting happens, and by year-end no one treats those goals as their own. Leaving the success measure blank when writing the goal is another common problem. A goal without a measure, such as 'improve customer satisfaction,' gets filled in by the reviewer’s subjective judgment in December, which is the biggest cause of distrust in reviews. At the other extreme, splitting goals into tiny pieces to hit numbers leaves you juggling a dozen goals while the important work falls through. Teams that still have not finished their meetings after Q1 are the most likely to end up with a year-end review based on impressions.

Training that covers this term · HR & Leadership
Recommended courses · Recommended instructors · Quick quote
🧮 Mini quote · Based on instructor fees
About KRW 1.2 million (≈ US$900)2-hour talk · up to 20 people · Korean
Get a quote for these requirements →
💡 In plain English
It is like agreeing on where the finish line is before the race starts. If you draw the line after the run, no one accepts the result.
Why it matters in practice
Meetings must finish before the February deadline for entering goals in the review system, yet most team leaders just enter numbers without any meeting structure. Building meeting design into team leader training reduces year-end review disputes.
Origin and sources

The idea that managers and their teams should agree on goals instead of managers imposing them comes from management by objectives (MBO), proposed by Peter Drucker in The Practice of Management (1954). Locke and Latham’s goal-setting theory, which holds that specific, challenging goals raise performance, is also used as a basis for designing these meetings.

Sources · Drucker, P. F. (1954). The Practice of Management; Locke, E. A. & Latham, G. P. (1990). A Theory of Goal Setting and Task Performance
An example

Consider a hypothetical case. Company A, an education content firm with 270 employees, closes goal entry at the end of each February. Last year, according to a survey, only 31% of its 230 team members went through a meeting before entering goals. Of 19 year-end review appeals, 14 said, 'We never agreed on what my goals were.'

  1. At the January team leader workshop, HR Manager Shin tells leaders, "Team members write their own goals; you only edit them." Shin distributes a simple draft form for team members with three fields: 3–5 goals, success measures, and support requests.
  2. Team Lead Ryu of Content Team 1 schedules 35-minute meetings with each of eight team members in the third week of January. When one member’s draft goal reads 'improve lecture quality,' they rewrite it together with a measurable target: a learner rating of 4.3 or higher and a 20% re-enrollment rate.
  3. In the meeting, a team member says, "Five new courses is impossible for one person." Team Lead Ryu cuts it to three and lists securing filming support staff on the form as the leader’s support item.
  4. Manager Shin has the system record whether each meeting was held, so goals entered without a meeting count against the team leader’s evaluation. In the second week of February, Shin reports each team’s completion rate to the executive meeting.
  5. That year, the share of goals entered after these meetings rose from 31% to 89%, and year-end appeals of review results fell from 19 to 6. The average length of a review meeting dropped from 55 to 30 minutes.
Related terms
Training linked to this term
📚Understanding MBONanum Consulting corporate training · On-site/OnlineView Course →
Need in-house training on this topic?
Get a curriculum and quote tailored to your needs right away.
Ask About Training
Last updated 17 Oct 2026 · Reviewed by John Kim

FAQ

The rule is after the team kickoff and before the end of Q1; in practice, late January to mid-February is most common. Once Q1 has passed, that year’s goals are set after the fact and are hard to use as the basis for year-end reviews.
Three to five is about right, and many companies make one of them a personal development goal. With more than ten, managing the goals becomes the job and the important work gets left out. With only one or two, it is hard to differentiate performance at review time.
Describe in a sentence what “done” looks like. For example, 'Establish an onboarding system for new hires' becomes 'Document the onboarding checklist and mentor-assignment rules by March and apply them to all first-half hires.' Defining the finished state this way reduces differences in interpretation at year-end.
If you copy the same goals to every team member, no meeting takes place and no one treats those goals as their own. Company-wide KPIs must be translated into team goals and then split into personal goals that fit each person’s role. That translation is the core work of the meeting.