Take two managers with the same headcount, the same budget and the same tools. One holds development conversations and writes plans that change what work people get. The other means to, and does not.
For a long time they look identical. Both ship. Both have people who like them. The difference is not visible in a quarter, which is most of why it persists, and it is not caused by one of them caring less.
The manager who doesn't isn't lazy, they're busy
Almost nobody skips development because they think people don't matter. They skip it because development is the work that has no deadline, sitting next to work that has nothing but deadlines.
Delivery arrives every week and asks loudly. A person's growth arrives once and asks quietly, and it can be postponed indefinitely without anything appearing to break. So it gets postponed, honestly, by managers who would tell you with a straight face that their people are their first priority. They are describing their intentions accurately and their calendar inaccurately.
That is why exhortation does not fix this. Telling a busy manager that development matters adds a feeling of guilt to a schedule that already has no room in it. What changes behaviour is when the absence of a plan starts costing something this quarter, and the rest of this piece is about the three places it does.
What differs first: who can be given the hard work
This is the earliest visible symptom, and it almost never gets diagnosed correctly.
A manager who has not had a real development conversation in a year has a mental model of their team frozen at the moment each person was hired. Ask them who could take the difficult piece of work and they will name the same two people they named last time. Not out of favouritism. Out of a shortage of information: those two have demonstrated it, and nobody else has been given the chance to.
So the difficult work goes to the same two, who eventually leave or burn out, while the other five slowly stop being considered for anything. From the outside it looks like a strong team with a couple of stars. From the inside it is a team where five people learned that effort does not change what they get asked to do.
The manager with plans is not being nicer here. They are better informed. They know who has been deliberately stretched on what, so when the hard piece appears they have four candidates instead of two, and the answer to who is ready is a matter of record rather than a guess.
What differs second: what a promotion conversation is made of
Promotion season is when the two managers stop looking the same, and it happens in a meeting neither of their teams attends.
The manager without plans arrives with advocacy. They believe in their person, they say so with feeling, and everything they offer is an impression formed recently. Whoever is in the room can only weigh that against another manager's equally sincere impression, so the decision gets made on who argued better or who is more senior.
The manager with plans arrives with a record: what this person could not do eighteen months ago, what they were deliberately given, what happened, what they can do now. That is not a stronger opinion, it is a different category of thing, and it is very hard to argue with because it describes events rather than feelings.
Their team notices this before they can explain it. People work out fairly quickly which managers can get things done for them and which ones can only be enthusiastic, and that reputation travels faster inside a company than almost anything else.
What differs third, and this one is new: what happens when the work changes underneath you
The first two costs have always existed. This one has grown teeth recently, because the shape of a lot of jobs is now moving faster than the people in them are being reassessed.
When parts of a role start being done by a machine, the question is not whether the person is good. It is what else they are close to being good at, and that is exactly the question a manager who has never had a development conversation cannot answer. They know their team's current output. They have no picture of anybody's edges.
So the two managers find out at different speeds. One has been having small conversations about what people want to move toward, and gets a year of warning, in fragments, cheaply. The other finds out in a single week, at the moment the capability is already needed, when the only remaining options are hire someone or hope.
This is the part I would push back on if someone told me development is a nice-to-have. It stopped being one when the half-life of a job description got shorter than the gap between performance reviews.
Most development plans deserve their bad reputation
Everything above describes plans that do something. Most of them do not, and pretending otherwise is how this topic lost its credibility with the people who have to do it.
The typical plan is written during review week, contains three goals phrased so that nothing could ever falsify them, and is opened again eleven months later so it can be copied into the next one. It is a document about a person rather than a change in what happens to them. Everybody involved knows it, which is why the exercise is quietly resented at every level.
There is one test that separates the two, and it is worth applying honestly to whatever your organisation currently produces: did anybody's work change because of this? Not their intentions. Their actual assignments, their reviews, who they sit with, what they are trusted with. If the answer is no, the plan was a document, and the hours spent on it were spent on paperwork rather than on a person.
What the version that works actually looks like
It is smaller than most people expect, and the size is the point: a plan that needs a quiet quarter to execute will never be executed.
- One thing at a time. A plan with six development goals is a wish list, and the reliable outcome of a wish list is that none of it happens.
- It names the work, not the quality. Not "become more strategic" but "you run the vendor evaluation, I review before it goes out". Strategic is a verdict, and a verdict cannot be practised.
- It has a real assignment attached within weeks. This is the load-bearing part. A plan whose first concrete step is more than a month away is a plan that will be overtaken by delivery, every single time.
- It says what the manager is doing, not only what the person is doing. Somebody has to give up the work, make the introduction, or sit through the first attempt going badly. If nothing is asked of the manager, nothing was actually planned.
- It gets revisited when something happens, not when the calendar says so. The useful moment is right after the stretch assignment, while the evidence is fresh.
- It survives a change of manager. Something has to be written down somewhere a successor will find it, or every reorganisation resets every person's development to zero, which is the single most common way years of this work gets thrown away.
The uncomfortable part: nothing bad happens quickly
The honest reason this pattern is so stable is that the manager who skips development is not punished for it. Not this quarter, and usually not this year.
Their team still delivers, because most teams do. The cost arrives later and lands somewhere else: on the person who inherits a team where nobody was ready, on the successor filling a role that has no internal candidate, on the individual who gave four good years to someone who never once put them in the way of something harder. The manager who caused it has often been promoted by then, on the strength of the delivery.
Which means this is not really a question about who cares. It is a question about whether an organisation can see a cost that shows up two years away from the decision that caused it. Most cannot, and the ones that can are usually the ones that made development legible: written down, visible to somebody other than the manager, and awkward to skip.
If you are the manager, the smallest honest version of this fits in an afternoon. Take your team list, and next to each name write what harder thing that person could plausibly do next, and what would have to happen first. If you cannot fill it in for someone, that is not a gap in the exercise. That is the finding.
