I've written the same vague PD goal three years running: "improve student engagement through technology." I signed it in August, nobody mentioned it again until the June form asked me to reflect on it, and I had nothing real to say. The problem wasn't effort, it was that the goal was never specific enough to act on.
Why the vague version fails every time
"Improve engagement" isn't a goal, it's a wish. You can't tell in October whether you're on track, because there's no way to check. A goal you can't check in October is a goal you'll ignore until June.
What makes a PD goal actually usable
- One specific practice, not a category. Not "improve engagement," but "use a structured turn-and-talk protocol in at least three lessons per week."
- A way to see it happening. Something an observer, or you on video, could count. Frequency, a checklist, student work samples, something concrete.
- A checkpoint before the year is half over. November or December, not just May. If you don't look until spring, you can't adjust anything.
- Tied to something you actually chose, not a district initiative you're lukewarm on. The goal you'll follow through on is the one connected to a real problem in your room.
A prompt that gets you something usable
"I teach 6th grade science. My real classroom problem is that only the same 5-6 students talk during discussions. Help me write one measurable PD goal for this year, with a specific practice to try, a way to track it monthly, and a mid-year checkpoint question I can answer honestly." You'll get a goal with a built-in way to know if it's working, which is the entire point.
What to do with the goal once you have it
1. Put the checkpoint date on your actual calendar, not just the goal-setting form. If it's not calendared, it doesn't happen.
2. Keep one running note, three sentences a month, on what you tried and what changed. This becomes your evidence at year end, and it takes ninety seconds.
3. Revise the goal at the checkpoint if it's not fitting reality. A goal that gets adjusted mid-year is a sign you're actually using it, not a failure.
What to do when the goal isn't working by December
If your checkpoint honestly says "I haven't tried this consistently," don't quietly let the goal die until June, name the barrier out loud. Usually it's one of three things: the practice needed more prep time than you had, it needed a co-teacher or observer you didn't line up, or the real problem in your room shifted and the goal no longer matches it. Any of those is a legitimate reason to revise the goal at the checkpoint, in writing, rather than limping toward a June reflection that reconstructs a year that didn't happen the way the form assumes.
A goal is not a performance for your evaluator
It's easy to write PD goals aimed at what sounds good in an observation, rather than what would actually move your practice. The two usually overlap, but when they don't, pick the one that's true for your room. An evaluator reading a specific, honestly-tracked goal, even one you revised mid-year, gets more confidence in your practice than a polished goal you clearly never touched again after August.
Where this fits with evaluation
A goal like this also makes evaluation conversations easier, because you show up with actual evidence, not a reconstruction from memory in May. Our [PD plan generator](/pd-plan) builds a full-year plan from your goal, current role, and available time, with milestones and evidence points built in, so the mid-year checkpoint is already on the calendar before the year starts.
