Individual Development Plan Template That Actually Works

The CORE model

A simple structure that holds the whole thing together:

Clarity
What are you trying to improve, in plain terms

Ownership
Who is responsible for making it happen, including the manager

Rhythm
How often progress is reviewed and adjusted

Evidence
What proves this is working

Miss one and the plan collapses.

Build a one-page IDP that people use

1. Employee context

Name, role, manager, review period.

No fluff. Just enough to anchor the plan in time and ownership.

If there is no review window, it drifts.

2. Career goals that connect to reality

Split into two horizons.

Short term (6 to 12 months)
Concrete outcomes tied to current work.

• Lead two cross-functional projects end to end

• Run weekly stakeholder updates and improve feedback scores

Long term (2 to 3 years)
Direction, not detail.

• Move into a leadership role

• Become a domain expert in a defined area

If the business cannot support this path, deal with that early.

3. Strengths and gaps

Break it into three:

Technical
What you can do today vs what needs work

Soft skills
How you communicate, influence, lead

Business knowledge
How well you understand the wider system

Be honest. This section drives everything else.

4. Development activities that actually happen

Most plans fail here.

“Improve leadership” is useless.

Replace it with actions that can be scheduled:

Mix it up:

• Real project ownership

• Targeted courses

• Mentorship

• Stretch assignments

If it is not in the calendar, it will not happen.

5. Success measures that remove doubt

Every goal needs a clear signal.

Bad:

• Get better at communication

Good:

• Achieve stakeholder feedback score of 8 or higher within 3 months

Tie each goal to:

• A measurable outcome

• A deadline

No ambiguity. You either hit it or you did not.

6. Support that is actually defined

Development is not solo.

List:

• Courses or training

• A mentor or coach

• Tools

• Manager commitments

Manager commitments matter most.

• Bi-weekly feedback

• Shadowing key meetings

• Removing blockers

If this is missing, the plan is one-sided.

7. Check-ins that keep it alive

Set a rhythm.

• Monthly quick reviews

• Quarterly deeper sessions

Track:

• What moved

• What stalled

• What changes

Keep it tight. Keep it consistent.

What this looks like in practice

Someone wants to step into leadership.

They do not write “improve leadership.”

They:

• Own a cross-team initiative

• Run weekly updates with senior stakeholders

• Get direct feedback from their manager after key meetings

• Measure success through delivery and stakeholder ratings

Three months in, they have proof. Not intentions.

Where most plans go wrong

• Written once, never revisited

• Goals that cannot be measured

• Too many activities, no focus

• Managers absent from the process

• Stored in tools no one checks

Fix the structure and most of this disappears.

Templates decide behaviour

A template is not a document. It is a system.

It forces clarity. It makes progress visible. It keeps people honest.

Bad templates create busywork. Good ones drive action.

Where Assemble fits

This is where most teams fall apart. Not in intent, in execution.

Plans live in docs. Updates happen in Slack. Feedback sits in someone’s head.

Assemble pulls it into one place.

You build a template that:

• Forces specific goals and measurable outcomes

• Connects activities to timelines

• Makes progress visible without chasing

• Keeps managers involved by default

It stops development from slipping through the cracks.

The point

If your development plans are not changing behaviour, they are admin.

Tighten the structure. Make it actionable. Put it somewhere people actually use.

Or accept that nothing will move.

Build your IDP template in Assemble and make it stick.