Setting career goals for the year: a plan that survives February

Three goals, not eleven

January lists fail because they are long and vague. "Get better at leadership", "network more", "earn more" and eight others compete for the same evenings, and by February most have quietly gone. Three goals you actually pursue beat eleven you forget.

Make each one specific enough that you would know if you had achieved it. "Lead a project from start to finish by September" works. "Develop leadership skills" does not. Then write down the first step, something you can do in the next two weeks, such as asking your manager about the next project that needs a lead.

A few examples show the difference:

• "Get better at data" becomes "Build and present one Power BI dashboard the team uses, by June".
• "Earn more" becomes "Take a market comparison and three results into my pay review in October".
• "Move up" becomes "Be acting team lead for at least one month before December".

Share the three with your manager early in the year. Most managers are glad to help with goals they know about, and a goal your manager has agreed is far easier to get time, funding and opportunities for. It also means the goals are already on the table when your review comes around.

Pay, skills and position as the three lanes

One goal in each of three lanes keeps the year balanced:

• Pay: a specific outcome, such as reaching a salary figure or a band, or checking your pay against the market before your review.
• Skills: one capability that makes you more valuable next year, such as a certification, a tool or a kind of work you have not done before.
• Position: where you want to sit by year end, such as a promotion, a new title, a bigger remit, or a move to a different team or employer.

The lanes reinforce each other. A new skill supports the case for a new position, and a new position supports the case for more pay. Our guide to professional development covers how to get the skills side funded.

Quarterly checkpoints in the calendar

Put four short checkpoints in your calendar now, one a quarter, before the year gets busy. At each one, spend twenty minutes on three questions: what moved, what stalled, and what is the next step for each goal. Adjust if something has changed. Dropping a goal on purpose is better than letting it fade.

The checkpoints also stop the year from slipping away. A goal due in September needs to be well under way by June, and a quarterly look is what tells you that in time to act.

Turning goals into wins journal entries

Progress on a goal is only useful at review time if it is written down. Each time something moves, such as a course finished, a project delivered or a piece of feedback received, write a line about it: what happened, the number it moved if there is one, and which goal it serves. Our article on keeping a wins journal covers the habit.

Over a year, those lines become the evidence for your pay case, your promotion case and your CV. Without them, the achievements of March are forgotten by November.

Reviewing before the performance review

A month or so before your performance review, go back to your goals and your wins. Mark what you achieved, what you learned from what you did not, and what you want next year. Take that into the review as a short summary, so the conversation starts from your evidence rather than your manager's memory. Our guide to performance reviews covers how to prepare.

In jobtracker.co.nz, Your Career keeps each goal with the role it leads to, a date and where it is up to, and the wins you log alongside, with reminders six weeks and two weeks before your pay review. An optional fortnightly check-in asks for one thing you finished, fixed, learned or were thanked for, and an open goal can become a draft promotion case. You can see a goal, wins and a review date in the demo, which needs no account.

Keep the goals where you will see them