Talent development planning is one of the most underinvested management activities. Most managers skip individual development plans because the structured thinking takes time they do not have. Claude accelerates the structured part. The commitment to follow through stays human. Here is the workflow.
Most individual development plans are written once at performance review time and never referenced again. The plan exists; the development does not.
The version that works: short (1 page), specific (named skills, named milestones), tied to current work (not aspirational), reviewed quarterly (not annually). AI helps with structure. The commitment stays manager + employee.
I am writing an Individual Development Plan for [EMPLOYEE] in [ROLE].
Where they want to be in 12-18 months: [SPECIFIC]
Their current strengths: [LIST]
Gaps between current and target: [LIST]
What is on their plate right now that could double as development: [PROJECTS]
What we discussed in the career conversation: [PASTE NOTES]
Our companys budget for development (course budget, time, etc.): [SPECIFIC]
Write a 1-page IDP:
1. Their stated 12-18 month goal (in their words)
2. The 2-3 specific skill or capability areas to develop
3. For each skill: how they will develop it (project, course, mentor, stretch assignment)
4. Specific milestones at 30, 60, 90 days
5. What I (manager) will do to support
6. Review cadence (quarterly minimum)
Voice: specific, action-oriented. No vague platitudes ("be more strategic"). Concrete actions only. The career conversation itself. AI cannot replace the manager listening to what the employee wants.
Resource commitment. Manager committing to support the plan is the foundation; without it, the IDP is theater.
Quarterly reviews. AI can synthesize progress; the conversation about progress is human.
Hard conversations. When the employee is not progressing or wants something the manager cannot support.