An individual development plan is useful when it creates evidence, not when it restates an ambition. Name the direction, choose one capability, attach it to real work, ask for specific support, and set a review date. Describe Course list with real evidence, then put the next experiment under Promotion wish. Macaron can retain that context while Project-based IDP keeps the next action visible. You can create a development project tied to evidence.

A working IDP connects career direction with assignments available in the current role. It describes observable capability, the project where it will be practiced, and the evidence that will show improvement. The Career Navigator interface is a useful reference for Course list. The embedded component on this page handles Project-based IDP.

Enter your role, twelve-month direction, skill, stretch assignment, and support request. Macaron can create a project for continuing reflections, while the page component immediately drafts a reviewable plan. Begin with the situation and constraints: Key points:
Ask for evidence before drafting: Begin with Course list and work you actually did. Put constraints beside Promotion wish, then let Macaron keep that context for a later revision. Use Project-based IDP for facts that still need research. Connect Course list to a dated source, and turn Project-based IDP into one practical next action rather than a permanent verdict.
Image description: Career Navigator development interface
Interface reference from Career Navigator
A manager can back an IDP when the project helps the team and the request is concrete. Ask for access, sponsorship, feedback, or time, then explain how the assignment will be delivered without hiding existing responsibilities. Key comparisons:
How to use the table: Connect Course list to evidence, test its relevance through Promotion wish, and turn Project-based IDP into a practical next step.
Quarterly review is usually more useful than discovering at year-end that the project never started. At each check-in, attach a work sample, stakeholder feedback, a result, and one change to the next practice cycle. Example: A customer success manager wants program-leadership evidence. Owning an onboarding pilot, with monthly sponsor feedback, produces a work sample and stakeholder evidence. The person checks Project-based IDP, updates Promotion wish, and keeps the revision beside Course list.
write a measurable work goal, compare longer-term career paths, prepare hiring-manager stories.
No, an IDP is a development agreement that clarifies growth direction, support, and evidence, not a promise of promotion or a guaranteed role change. Use it to connect your Course list, current work, and Promotion wish to specific experiments that can be discussed during a review.
An effective IDP usually focuses on one or two capabilities so the plan stays specific and usable. Choose skills that can be practiced in real work, then describe what evidence would show progress before adding them to a Project-based IDP.
A stretch project is useful when it gives you visible practice beyond your current comfort zone while still being realistic to deliver. Pick work with clear ownership, observable results, and a review date so your manager can evaluate progress from evidence rather than intention.
The plan should usually be reviewed by the employee and manager, with mentors, sponsors, or project leads added when they can offer relevant feedback or opportunities. Agree on what support is needed, when the plan will be revisited, and which work evidence should be considered.