How often should you reassess a professional development goal?
Reassess a goal at the end of the cycle you set for it, usually 90, 180 or 365 days, not every week. Checking in weekly is useful for tracking effort — did you do the agreed activity — but re-scoring the goal itself too often mostly measures noise. Research on measurement error shows that any instrument has a margin within which change cannot be distinguished from normal variation, sometimes called the minimal detectable change (PMC, 2018). Reassessing before that margin has had time to clear tells you little.
This matters because people often confuse the two activities. A weekly check-in answers "did I practise?" A reassessment answers "has anything actually moved?" Those are different questions on different clocks.
Why reassessing too often wastes effort
Skill and performance measures bounce around for reasons that have nothing to do with ability: a bad night's sleep, a noisy room, a harder client, an off day. The PMC review on measurement error explains that a single reading can swing within a known range purely from this noise. If you reassess weekly and the range is, say, four weeks wide, you will see "improvement" and "decline" that are really just the same underlying level, measured twice.
Locke and Latham's review of goal-setting research found that specific, moderately difficult goals work best when paired with feedback on progress (Locke & Latham, 2002). But feedback needs to be timed to when real change is visible, otherwise it teaches the wrong lesson — that effort doesn't work, when in fact nothing had time to show yet.
A reassessment rhythm that works
A simple way to separate the two clocks:
| Cycle | Check-in frequency | What the check-in tracks | When to reassess the goal |
|---|---|---|---|
| 90 days | Weekly, ~3 minutes | Did the first step happen, hours used against budget | At day 90 |
| 180 days | Weekly or fortnightly | Same as above, plus any if-then triggers used | At day 180 |
| 365 days | Monthly | Pattern of effort over the quarter | At day 365 |
Amabile and Kramer's research on workplace motivation found that noticing small, concrete progress day to day sustains effort far more than waiting for a big verdict (Amabile & Kramer, 2011). So the weekly habit still matters — it just isn't the moment for a scorecard.
Two examples outside the usual office setting
A sprinter working on start reaction time might record it daily, but a single session's number is affected by track conditions and sleep. A coach typically waits for a full training block, perhaps six to eight weeks, before concluding the start has genuinely improved rather than simply varied. The development plan for professional athletes we've written about separately follows the same logic: short-cycle feedback for effort, longer-cycle review for the measure itself (see /blog/development-plan-for-professional-athletes).
A founder tracking monthly recurring revenue faces a similar trap. One strong week from a single large client can look like a trend. Most operators wait for a full month, sometimes a full quarter, before treating a shift as real rather than one good week. The founder's plan we've covered elsewhere treats revenue as an outcome to watch, while the underlying capability goals — the actual skills being built — sit on their own 90-day cycle (see /blog/founder-development-plan-revenue-to-capabilities).
A short checklist before you reassess
- Has the stated cycle (90, 180 or 365 days) actually elapsed.
- Is the measure the same one you started with, not a substitute that creeps in.
- Is the observed change larger than the known or estimated margin of error for that measure.
- If it's smaller, record "held steady" rather than forcing a verdict (see /blog/measuring-professional-growth-honestly for more on why that's a legitimate outcome).
- Decide, separately, whether the goal itself still belongs in Live or should move to Later.
Where Jobulary fits
Jobulary, the Individual Development Plan platform from Bodhih Training, builds this rhythm in rather than leaving it to memory. Plans follow a practice-first 70/20/10 path sized to a stated weekly hours budget, running in 90/180/365-day cycles inside a longer 3–24 month horizon, so the reassessment date is set when the goal goes live, not guessed at later.
Check-ins stay to about three minutes and only track whether the agreed step happened. Growth is reported only when it is larger than measurement error — otherwise Jobulary records "held steady" — which keeps weekly noise from being mistaken for a verdict on the goal.
Related reading
Frequently asked questions
How often should I reassess a professional development goal?
At the end of the cycle you set for it, typically 90, 180 or 365 days. Check in more often on effort, but reassess the goal itself only once enough time has passed for real change to be visible above measurement error.
Is it bad to reassess a goal every week?
Weekly re-scoring usually captures day-to-day noise rather than genuine change. Weekly check-ins work better for tracking whether you did the agreed activity, not for judging whether you have improved.
What should I do if a reassessment shows no change?
Report it as held steady rather than forcing a verdict of success or failure. Held steady is a legitimate result, especially early in a cycle or when the measure has a wide margin of error.
Sources
- Measurement error and minimal detectable change (PMC)
- Locke & Latham 2002, Building a Practically Useful Theory of Goal Setting
- Amabile & Kramer, The Power of Small Wins (HBR, 2011)
- CCL, The 70-20-10 Rule for Leadership Development
Topics: Measurement · Individual Development Plan · Goal setting