Why Career Development Belongs in Every Manager's Toolkit, Not Just HR's

Most organizations design career development as something HR runs. An annual review add-on. A workshop scheduled once a year. An internal mobility portal that a handful of ambitious employees know how to use and everyone else forgets exists.

Meanwhile, ask any employee to name the conversation that actually changed how they think about their own career, and HR is rarely in the room for it. It's a manager who noticed something and said it out loud. A project debrief that turned into an honest conversation about what's next. An offhand comment in a 1:1 that stuck for months.

That's not a coincidence, and it's not a training failure on any individual manager's part. It's a design choice, usually made without anyone deciding it on purpose.

If your organization treats career development as an HR-owned event, the actual quality of career development any given employee receives depends almost entirely on luck: whether they happen to report to a manager who is naturally good at these conversations, was mentored by someone who was, or simply cares enough to make time for it without being asked. Most managers were never taught this. Most weren't hired for it, and most don't see it as a core part of the job description they were handed.

That's the real gap. Not a lack of career-development content or tools, most organizations have plenty of those sitting in an intranet folder somewhere, but a lack of design connecting those tools to the place where career conversations actually happen most often: the ordinary, unglamorous rhythm of the manager relationship.

This is the starting insight behind every manager development program I design, including a multi-year manager learning series I've run with a university partner. Each one is built on a deliberately two-sided premise. One side gives employees a simple, repeatable way to get clarity on their own direction. The other, just as deliberate, gives managers a shared vocabulary and explicit permission to have those conversations themselves, rather than deferring the whole subject to HR or to an annual cycle.

The second half is the one organizations tend to skip, and it's the one that actually determines whether career development reaches everyone or only the employees confident enough to go looking for it on their own.

The operating principle is simple: treat the manager, not the annual review cycle, as the real unit of career development. A manager equipped with a shared vocabulary and standing permission to ask where someone wants to go, more than once a year, does more for that person's trajectory than one polished, high-production conversation ever will. Career development that only happens in a scheduled event is, by definition, rare. Career development built into a manager's ordinary toolkit can happen every week.

None of this argues for removing HR from the picture. HR still owns the design, the tools, and the standards that make these conversations consistent rather than accidental. What it argues for is a specific design question worth asking before you build or rebuild a career-development function: is this happening to your best-supported employees by luck of the manager they got, or is it built into every manager's toolkit on purpose?

If you're asking that question about your own organization right now, I'd welcome the conversation. This is the exact design work I do.