What Are Good Personal Development Goals for Work?

Good personal development goals for work are the ones your coworkers would notice if you hit them. Not "improve communication." Something closer to "my team tells me about problems while they are still small." If nobody around you could tell the difference, it is not a goal. It is a phrase for the review form.

Every year, somewhere in America, a few million people sit down in front of a form that asks them for their professional development goals, and a few million people write down some version of the same four things. Improve communication. Be more strategic. Develop leadership presence. Grow my network.

I have written those. I have read hundreds of them. I have signed off on them.

And I can tell you that almost none of them changed anything, because none of them described a thing a human being could watch happen.

The Test: Would Anyone Notice?

Here is the only filter I use now. Say the goal out loud, then ask yourself: if I actually did this, who would notice, and what exactly would they see?

"Improve communication" fails immediately. Nobody notices improved communication. It is weather.

"People bring me bad news within a day instead of at the end of the week" passes. You would see it. Your team would feel it. You could point at a Tuesday in October and say, that is the day somebody told me early and we caught it.

Every one of your personal development goals should pass that test. If it does not, you have not written a goal yet. You have written a category.

The Three Hour Walkabout

I worked for a man I will call Steve Peterson. Steve ran what he called a walkabout. Every morning, three hours, walking the floor with a group of us, stopping at stations, asking questions, moving on.

Three hours. Every day. Multiply that by the people in the group and you are burning a serious piece of a workweek before anybody has touched a wrench.

And nothing came out of it. No decisions. No actions. Just a very visible display of engagement.

Meanwhile there was a problem we had been chasing for months. Labels kept falling off. Nobody could crack it. Then one day somebody finally asked a guy on the floor, in steel toed boots, who had been standing next to that machine the whole time. He knew. He told us. I checked, and he was right.

That answer had been sitting there the entire time, waiting for somebody to slow down long enough to ask a simple question. But if your mornings get eaten by three hour walkabouts that produce nothing, you never have that conversation.

That is the real cost of a bad meeting. Not the hours. The unasked question. The solution that stays in somebody's head forever because nobody made room for it.

Steve's development goal was probably "increase floor presence." He hit it. He was extremely present. It helped nobody.

Personal Development Goals for Work That Actually Mean Something

So here is what the same four tired categories look like once you make them real.

Notice what happened. Every one of them turned into a behavior with a time attached. That is the difference between a goal and a wish. A goal has a place to live on a calendar.

Notice something else. Every one of them costs you something. Ninety minutes. The satisfaction of answering first. That is how you know it is real. A development goal that costs nothing is decoration.

What About Development Goals for Managers?

If you run people, your development goals should mostly be about removing things, not adding them.

I ran huddles with my team, and underneath all the updates and task lists, what those huddles were really for was clearing obstacles. That is the actual job. Not creating friction. Not standing between people and the work they are capable of. Clearing the path.

So the good management goals sound almost negative when you write them down.

Cut one recurring meeting this quarter and give the time back. Stop being the approval bottleneck on one category of decision. Ask about somebody's family and actually listen to the answer, because people need to know the person in charge sees them as a human being and not a function on a schedule.

That last one is not soft. When people want to show up, everything else gets easier. When they do not, no process saves you.

How Do I Write This So It Survives the Review Form?

Two lines. Write the real goal, then write the corporate translation underneath it.

The real one is for you and it is specific and slightly uncomfortable. The translation is for the form, and it can say "improve cross functional communication" if that is what the system wants to hear.

That is not cynicism. Forms have their own language and fighting them is a waste of a good year. Just do not let the form's version become the one you actually chase, because you cannot chase a category.

Then pick one. One. Not four. When everything on the list is a priority, nothing on the list gets done, and the person doing the quiet deciding about what actually matters is not you.

Reflection Questions

1. If you hit your current work goal, who exactly would notice, and what would they see?
2. Which of your goals is a category pretending to be a goal?
3. What does this goal cost you? If nothing, is it real?
4. If you manage people, what could you remove instead of add?
5. Which one would you pick if you were only allowed one?

The Bottom Line

A good work goal is a promise about your behavior that somebody else could verify.

This week, do one thing. Take whatever is currently written in your development plan and rewrite one line of it as something a coworker could watch happen. Then put it on your calendar, because a goal without a time slot is a mood.

The guy in the steel toed boots knew the answer for months. Nobody asked. Whatever else you put on that form this year, consider making room for the questions you have not been slowing down enough to ask.

So here is my question for you. If I walked up to the person who works closest to you and asked what you are working on getting better at, what would they say?