Individual Development Plan

People wanted to grow long before this document existed. The wish just wasn't written down anywhere. Managers and reports already sat down for a 1:1, but that weekly half hour filled up with whatever was blocked this week. With something urgent in front of them, the three-years-from-now conversation slid every time.

So the same scene repeated. In the spring a manager asks what someone wants to take on next, hears "let me think about it," and the topic closes. Then in December, during the annual performance review — the process of summing up a period's results and capabilities into a rating or written judgment — the person hears "you're not at the level we expect yet" for the first time. One side got the news eleven months late. The other had been thinking it since July and never found the right place to say it.

A career framework splits into four parts: how people are sorted (structure), which directions exist (paths), how someone moves (movement), and what helps them move (enablement). The individual development plan (IDP) belongs to the last one. If the level table and the tracks are a company-wide map, this document is the note that copies one square of that map onto one person's next three months. Without the note, people know which square they stand on but not which way to step.

Five things go on the page: the destination, the gap, this quarter's work, the support needed, and the date it gets reopened.

1. The destination — a cell in the job level table. A job level is a grade defined by scope and responsibility, and each step spells out in sentences what that person can do. Writing "level 4" and nothing else is half an entry. You also have to pick which sentence in that level description you can't do yet, or the next item has no input. The direction isn't only upward either, so this is also where you choose between staying on the individual contributor track, where depth of craft carries you up, and moving to the manager track, where people and teams do.
2. The gap — what sits between that sentence and today. "Needs stronger design skills" is an impression, not a gap. "Finishes solo features well, but someone else still sets the schedule when other teams are involved" is specific enough to write the next line from.
3. This quarter's work — one or two assignments inside real work that narrow the gap. Park them outside the job and they are the first thing dropped in a busy month. For the gap above, the assignment is "I own schedule coordination for the payments feature." A line like "study architecture" reads the same a year later.
4. The support needed — who has to do what for that assignment to be possible. Write it as actions the other person can actually take: leaving the meeting-chair seat open, making an introduction to a counterpart on another team. An empty box here turns the plan into a resolution.
5. The reopen date — one check mid-quarter and one at the end, scheduled in advance. A document with no date gets read only in the week it was written.

The report drafts it and the manager shapes it from the side. Reverse that order and the document changes character: a plan handed over pre-written is a task assignment, and the person receiving it never treats it as theirs. Writing it alone, though, usually stalls in two places. The next level's sentences are hard to interpret from below, and without knowing what the company is taking on this quarter you can't judge what support to ask for in item 4.

Two people read it — the author and their manager. It doesn't get collected by HR and it doesn't feed into evaluation. That boundary is what makes the document useful. The moment people believe it will be read as evaluation, they stop writing down what they can't do. Item 2 fills up with things they already do well, item 3 follows with practice they don't need, and the page gets updated every quarter while changing nothing.

"What's in your development plan and what's on your plate this quarter don't line up. Want to swap one in?"

The practice written down isn't inside the actual work, so the work should shift.

"That's a development plan conversation. Right now let's sort out this week's schedule."

Drawing a line between two topics inside the same 1:1.

"You wrote that you want to reach level 5, so I'll sit out this design review and you run it."

Handing over a real piece of work on the strength of what the document says.

At Pagedeck the file gets opened in the first week of the quarter. Theo fills in his own copy, sends it to Grace, and the two take thirty minutes on items 3 and 4. Last quarter Theo wrote that he couldn't yet do the line in the level 4 description about carrying multi-team work alone, and the assignment was to own the external integration schedule for payments. Grace's support came to two lines: introduce the vendor contact, and attend only the first meeting without saying anything.

At the mid-quarter check Theo wrote that he had chaired the meetings but Grace ended up assembling the schedule. So the remaining six weeks narrowed to "the next two times, my draft schedule circulates first." Plans shrinking mid-quarter like this is more common than plans running as written.

The most frequent mistake is reading the plan as an evaluation document. Sitting with a manager, writing goals, checking them each quarter — the shape overlaps with review closely enough to invite the confusion. But they point in opposite directions. A review sums up a finished period and connects it to ratings and pay. The plan picks something you can't do yet and clears space to practice it next period. Merge them into one document and the box for weaknesses empties first, leaving a list of things already done well.

Reading the page as a promise of promotion is almost as common. Promotion decisions happen in a room of several managers, argued from real examples out of the last two or three quarters. The plan schedules the practice that produces those examples; it isn't the scorecard. Treat it as a promise and the first person who completes a plan and doesn't get promoted stops trusting the document — and from the next quarter nobody writes down a real weakness.