One of the most common reasons employees leave isn’t pay. It’s the sense that their growth has stalled. In response, many companies doubled down on development plans, assuming the document alone would spark momentum. After years of watching these plans succeed, fail, and occasionally catch fire, here’s what I’ve learned.
Most development plans die in the wild. Not because leaders don’t care, but because the plans are too vague, too detailed, too aspirational, or too disconnected from the employee’s actual day‑to‑day reality.
September is the perfect month to fix that. Everyone’s back from summer mode, motivation is rising, and you still have runway before year‑end reviews begin. It’s the ideal time to reset expectations and build development plans that actually work.
1. Start With What the Employee Wants, Not What You Want
Hard, huh? Real development starts with the employee’s goals, strengths, and interests, not the company’s gaps or the manager’s wish list.
One of my favorite one‑to‑one questions is: “What do you want to do when you grow up?” Not what I want them to do.
Then ask: “What skills do you want to grow in the next 90 days?”
When employees choose the direction, they commit to the work. And 90 days is doable.
2. Make It 90 Days, Not 12 Months
Annual development plans are where good intentions go to die. A 90‑day plan is short enough to stay relevant and long enough to create momentum.
You can still include growth initiatives in the annual review. I recommend breaking them into 90‑day chunks.
Focus on:
- One skill to build
- One behavior to strengthen
- One stretch assignment to try
Anything more becomes a performance review in disguise.
3. Tie Development to Real Work
If the plan requires extra time the employee doesn’t have, it won’t happen. Period.
Instead, embed development into existing responsibilities:
- Leading a meeting
- Owning a small project
- Shadowing a cross‑functional partner
- Taking the first draft of something the manager usually does
Development should feel like growth, not homework.
4. Build Micro‑Milestones, Not Massive Checkpoints
Most development plans fail because the milestones are too big. “Improve communication” or “be more strategic” aren’t milestones, they’re wishes.
Micro‑milestones create traction:
- One improved handoff
- One documented process
- One proactive update
- One cross‑team partnership
- One decision made without escalation
Small wins build confidence, and confidence builds momentum. Micro‑milestones keep development visible, doable, and measurable without turning it into another form.
5. Celebrate Progress, Not Perfection
Real development plans evolve. If the employee learns something faster than expected, great. If they hit a wall, also great. That’s where coaching happens.
September is the month to reset development expectations: simple, human, and doable. When you build plans that honor the employee’s reality, you build teams that grow on purpose.