Framework · People leadership · 2 min read
Individual development plan
One page per designer with strengths, growth goals from the career ladder, actions, support and evidence of done, so growth becomes a plan you review together instead of a hope.
1Strengths
What they already do well, each with a real example.
e.g. clear flows for complex tables2Growth goal
One to three goals, each tied to a career-ladder dimension.
e.g. present to stakeholders (Impact)3Action
What they will actually do, and by when.
e.g. present at the monthly review4Support
What you, as their lead, will provide.
e.g. review the deck the day before5Evidence
How you will both know the goal is done.
e.g. a decision made in the meeting6Stretch
One real piece of work above their level each quarter.
e.g. lead a cross-team patternReview monthly in 1:1s · one page per designer
Use it when
- A designer says they want to grow but cannot say into what.
- You are preparing for review or promotion season and want evidence, not memories.
- Someone is ready for more, and you want to give them a stretch assignment on purpose.
How to use it
- Start from strengths, with evidence. Ask the designer what they do well and add what you have seen. Link each strength to a real piece of work. Output: two or three strengths with examples.
- Pick growth goals from the ladder. Compare their current level with the next level on the Career ladder. Choose one to three goals, each tied to one ladder dimension. Output: one to three goals, each linked to a dimension.
- Turn each goal into an action, support and evidence. Write what they will do, what they need from you, what "done" will look like and a date. Output: one row per goal in the plan.
- Add one stretch opportunity this quarter. Choose a real piece of work slightly above their level, such as presenting to stakeholders or a cross-team problem. Output: one named stretch assignment.
- Review it monthly in 1:1s. Use the monthly growth check-in in your One-on-one meetings to update progress and collect evidence. Output: dated notes on each goal.
Worked example
A Mid designer on an internal operations platform wants to reach Senior.
| Goal (ladder dimension) | Action | Support needed | Evidence of done | Date |
|---|---|---|---|---|
| Present design decisions to senior stakeholders (Impact) | Present the order-tracking redesign at the monthly product review. | Lead reviews the deck one day before and attends. | Presented; the product director made a decision in the meeting. | End of Q2 |
| Run design critique (Leadership) | Facilitate two cross-team critiques. | Lead co-facilitates the first one. | Two sessions run; feedback from attendees in the next health check. | Mid Q2 |
Watch out for
- Too many goals. Five goals means no focus. One to three goals per quarter is enough.
- Goals with no link to the ladder. If a goal doesn't map to a ladder dimension, it may not count at promotion time. Say so openly.
- Support only on paper. If the plan says "lead will introduce to stakeholders" and you never do, the plan fails because of you.
- Writing it for them. If you fill in the plan alone, they will not own it. Let them draft it, then refine it together.
Template
Ask the designer to draft this, then complete it together in a 1:1.
Designer: ___ Level: ___ Next level target: ___
Strengths (with evidence):
-
-
Growth areas (from ladder):
1. Goal — Action — Support needed — Evidence of done — Date
2.
3.
Stretch opportunity this quarter:
AI skill to build:
Monthly check-in notes:
(date) progress / evidence / next step
Saved only on this device.