A calendar invite lands with two words in the title: "development goals." Behind it is a blank page, and somewhere ahead is a manager who will ask, "What do you want to work on?" You want an answer that sounds real, fits the job you actually do all week, and gives you something to point to later.
Four short examples from very different jobs show the idea.
- In an office: "I will give three short project updates and ask for one comment after each."
- On a shop floor or on shifts: "On two shifts a month, I will practice the new stock process and write down questions for the supervisor."
- With a tool you already use: "I will learn two functions of our software and use them on two real tasks."
- In a meeting-heavy week: "I will run four meetings and check that the decision and next steps were clear."
To pick yours, think of one task you repeat every week and ask which skill would make it easier. Choose one or two goals, no more. A small goal is a perfectly good goal.
- Pick one task choose the skill that would make a repeated task easier
- Show it say how progress will be visible
- You control skills and habits, not promotion or pay
- Keep a log a few lines a week turn into achievements
- Ask plainly one specific request, one date
Goals you can borrow, by kind of work
Your job might not look like anyone else's, but most development goals fall into a few groups. Each one below comes with a way to show it, because a goal you can point to is easier to talk about at a review.
Speaking up and writing updates. Rewrite your weekly update so it always names a decision, an owner and a next action, then go over six of them with a manager or a colleague. Or summarize what a person asked for before you answer, in five regular meetings.
Learning a tool. Learn the core functions of a program your team uses and apply them to two real tasks. Or rebuild one existing report in the new tool and ask a colleague to check it. Afterward, write a one-page guide for the team.
Working with other people. Agree a handoff checklist with a partner team and use it on five shared tasks. Or ask two colleagues for feedback on one specific habit, such as how clearly you pass work along, and pick one thing to change.
Managing your time. Write down competing requests for four weeks, then suggest a priority rule to your manager. Or find one low-value task and propose a safe way to stop it, automate it or hand it on.
Trying out a next role. Read three job descriptions for a role you might want and pick two skills that keep coming up. Then practice those in your current job, or volunteer for one temporary project that gives you something to show.
| Goal | Where it fits | How progress shows |
|---|---|---|
| GoalGive three project updates, asking for one comment after each | Where it fitsOffice or remote work | How progress showsThree updates delivered and three comments written down |
| GoalLearn two functions of a software tool | Where it fitsAny job that uses one | How progress showsTwo real tasks done with the new functions |
| GoalRun four meetings | Where it fitsTeam leads and anyone who organizes meetings | How progress showsNotes on whether the decision and next steps were clear |
| GoalPractice the new stock process on two shifts a month | Where it fitsShop floor, warehouse, shift work | How progress showsQuestions for the supervisor, with answers noted |
| GoalAgree a handoff checklist with a partner team | Where it fitsWork that passes between teams | How progress showsChecklist used on five shared tasks |
| GoalShadow a colleague for six sessions | Where it fitsAny workplace | How progress showsDates, what you watched and what you tried afterward |
What fits where you are right now
The right goal depends on where you stand. Each one comes with a low-cost way to practice.
Starting out. "Over six months, I will learn the team's reporting process, complete three reports with review, and write a checklist for the next new starter." Shadowing, asking for feedback after routine tasks and reading internal documents all cost nothing.
A few years in. "This review period, I will lead one workstream that involves another team, write down two decisions for senior colleagues and ask the project sponsor for feedback." A stretch task or a peer mentor can stand in for a course.
Managing people. "For the next quarter, I will hold a development conversation with each person on my team and ask what support would make progress easier." Practice giving feedback in your regular one-to-ones.
Part-time or shift work. "On two scheduled shifts each month, I will practice the new process and record questions for the supervisor." A task checklist and a few minutes of shadowing during paid time, where that is agreed, are enough to start.
Changing roles. "Within four months, I will name three skills common to the role I want, complete one work sample and ask someone who does that work for feedback." Job descriptions and short conversations with people in that role are free.
Your employer pays for nothing. "For eight weeks, I will use free materials to learn the basics of a tool and apply it to one example that contains no confidential information." Try a public library, open course materials, a professional association or a colleague who will review your work.
What employers offer differs a great deal by size of business, sector and country, and a gap in support is not your fault. A smaller, work-based step still counts. Keep confidential material out of your practice, and check whether any learning you do is meant to happen in paid time.
If you are looking for life goals rather than work goals, the guide to personal development goals is the better starting point. And if you are not sure what you want from your work at all, a way to think through what you want can come before any goal.
Wording a goal so progress shows
"I want to get better at leadership" is a fine wish and a hard thing to check. "I will run four meetings and note whether the decision was clear" gives you something to do, something to look at, and something to say at the review.
A goal that shows progress has six parts. Start with the skill you want to build and where you will practice it, then say what you will do and how progress will show. Finish with when you will look at it again and what help you need.
Put together, it can sound like this: "By the end of next quarter, I will improve my project updates by writing six in a decision, evidence and next-step format, going over two with my manager and noting the feedback."
That one sentence is also the answer to how to describe a professional goal to someone else.
Formats like SMART goals can help when a result is easy to name. They are not magic, though. A rigid target can push you to tick boxes, and for work that is complicated or new to you, a goal about learning or behavior often fits better. CIPD's guidance on performance management makes the same point about goals for people who are still learning a complex task.
What you control and what your employer decides
A development goal is something you can practice: a skill, a habit, a piece of work. Promotion, pay and ratings are decisions that other people make, so a goal cannot promise them.
That does not mean you have to leave "get promoted" out of the conversation. You can turn it into things you can do and show: a work sample, a project you took on, a skill you used on a real task. Then ask your manager what the employer looks at when it decides, and aim your goal at that.
The difference matters at review time. "Receive a promotion" is something you hope for. "Run the weekly planning meeting for three months and keep the notes" is something you can finish.
Keeping a simple record, and turning it into achievements
Most people forget what they did in March by the time a review comes around in November. A few lines after a work day or a work week will fix that. Jot down the date, what you did, what shows it, what anyone said about it and what you will change next time.
| Date | What you did | Evidence | Comment | Next tweak |
|---|---|---|---|---|
| Date12 May | What you didLed project update | EvidenceAgenda and decision log | CommentManager asked for a shorter opening | Next tweakLead with the recommendation next time |
| Date26 May | What you didRan the Monday team meeting | EvidenceMeeting notes with the decision written at the end | CommentA colleague said the next steps were clear | Next tweakSend the notes within an hour |
| Date9 June | What you didPracticed the new stock process | EvidenceChecklist with two questions marked | CommentSupervisor answered both | Next tweakTry the process unsupervised next shift |
When review time comes, turn three entries into two or three short achievement lines. For example: "Led four team meetings; the team now ends each one with a written decision and next steps." Or: "Learned two functions of our reporting tool and used them on two live reports."
A course certificate is stronger when it comes with something you did with it. Pair the course with a task you finished, a template you built or a comment from a colleague.
Keeping track along the way also helps. CIPD's review of the evidence on feedback says that tracking progress during the year is more useful than waiting for the end of it.
1. Which goal is easiest to show progress on?
2. Your employer has no training budget. What is a reasonable first step?
3. Your manager is too busy to talk. What helps most?
4. Which part of a promotion do you control?
What to say to your manager
Sometimes the hardest part is the first sentence. These three scripts are ready to adapt. Change the words so they sound like you.
To agree on a goal and a date. "I'd like to use part of this review to agree on one development goal connected to my current work. I want to get better at [skill]. I would practice by [action] and show progress through [evidence]. Could we agree on what good looks like and look at it again on [date]?"
To ask for support. "To make this realistic, I need [time, access, shadowing, feedback or a project]. What support is available, and what could wait while I do this?"
To ask for one specific comment. "Over the next month, could you watch for [one behavior] and give me one example of what worked and one thing to adjust?"
If your manager is busy or your workplace has no formal process, send a short note afterward: "Thanks for talking. To confirm, I'll [goal], show it with [evidence], and we'll check in on [date]." Then keep the goal tied to what you can do yourself.
In a very busy week, use the low-effort version. Send one message with the goal and a date, and add one line asking for a comment on one thing. That is enough to keep it alive.
When a goal stalls
Goals drift. It rarely means you did something wrong, and each stall has a fix.
No protected time, or a goal that is too big. Shrink the goal to one skill and one visible use at work, and ask what could be paused while you do it. Swap "improve leadership" for one behavior, like running a meeting or handing off a defined task.
Waiting on other people. If you are waiting on another team, set a shorter check-in, such as two weeks, instead of waiting for the next review. If a course is not available, replace it with shadowing, a review from a peer or a work sample.
A course with no follow-through. If you finished a course and never used it, apply it to one real task this month and ask a colleague to look at the result.
Changed priorities or irregular shifts. When priorities change, write down what changed and agree a new date. Pausing a goal on purpose is a decision, not a failure. If your shifts vary, pick a practice that fits any shift, such as a note to yourself after each one, rather than a weekly slot.
For a busy month, keep a minimum version: one practice session, or one request for feedback. It keeps the goal warm until you have more room.
Sometimes a different kind of help fits better. A career adviser can help if you are thinking about a change of direction. HR or a union representative can answer questions about paid learning time, your rights or unpaid training, which vary by country and employer. And if constant exhaustion or distress is affecting your work, a doctor or counsellor is the right person to talk to, not a development plan.
One step before your next review
Pick one goal from the examples above. Write it with the six parts: the skill, where you will practice it, what you will do, how it will show, when you will look at it again and what help you need.
Then send your manager one short message with the goal, the evidence you will keep and a date to check in. That is the whole step.
For more guides on work and growth, see career growth. Every guide lives in one place on Motivation Facts, and if you have a question or an idea for a guide, send us a note through the contact page.
Questions people ask
What are some examples of professional development goals?
Good examples are small and tied to your actual job: give three project updates and ask for a comment after each, learn two functions of a tool and use them on real tasks, or run four meetings and note whether the decision was clear. The examples by area of work above have more, with a way to show each.
How do I describe my professional goals?
Say the skill, where you will practice it, what you will do, how progress will show, when you will look again and what help you need. The wording section above has a full sentence you can copy and change.
How do I show progress on a goal at my review?
Keep a short log with the date, what you did, the evidence and any comment you received. Before the review, turn three entries into two or three achievement lines. The record-keeping section has a sample log and example lines.
How do I ask my manager for support?
Name what you need and what could wait: "To make this realistic, I need [time, access, shadowing, feedback or a project]. What support is available, and what could wait while I do this?" The scripts section has two more for agreeing on a goal and asking for feedback.
What if my employer has no training budget?
Choose a smaller goal that lives inside your work, like shadowing a colleague, asking for feedback after routine tasks or taking on a stretch task. Free materials from a library or a professional association can fill gaps. Ask your employer or a union what paid learning time applies to you, because it varies.
What are short-term professional goals?
A short-term goal runs for four to eight weeks and covers one small skill. For example: "For six weeks, I will send a written decision summary after each project meeting and ask one colleague whether it was clear."
Development goal. A skill, habit or piece of experience you want to build, such as learning a tool or running meetings.
Performance goal. A result or standard expected in your current role, such as finishing projects on time.
One-to-one. A regular private meeting between you and your manager.
Individual development plan. A written plan for your growth at work, including the support you need to follow it.
Stretch assignment. A task or project slightly beyond your usual work, taken on to build a skill.
Shadowing. Watching a colleague do a task so you can learn how they do it.
Evidence. Anything you can show that your work or practice happened, such as a document, a log entry or a comment from a colleague.
