Three Conversations, Kept Apart

At a company where I ran a group of financial data products, I found that outside the annual review cycle there was essentially no structured development happening. Not because the company was neglectful — there were good self-paced learning resources sitting there unused. It was that nobody was connecting them to anything. Whether you grew depended entirely on whether your particular manager happened to take that on personally. Which means it was luck.

So I built something, and the first version was worse than I'd like to admit, for a reason I now think is the most common failure in people management: I was trying to do all of it in the weekly 1:1. Status, growth, and the occasional hard feedback, in the same thirty minutes, competing.

Those are three separate conversations with different time horizons, different emotional registers, and different owners. Running them together doesn't save time. It makes the weekly meeting into a status report, the growth conversation into a thing that never quite happens, and the performance conversation into an ambush.

The weekly 1:1 belongs to them

The single highest-leverage change I've made as a manager was giving up the 1:1 agenda. It's their meeting. They bring what they want to talk about. If they bring nothing, we talk about whatever's actually on their mind, and if that's frustration with a peer team or a decision they think I got wrong, good — that's the meeting working.

The reason this matters is that project status has other venues. Standups, reviews, the board, whatever the team uses. When status colonizes the 1:1, the only recurring private conversation you have with someone becomes a place where they perform competence. Nobody says "I'm underwater" or "I don't understand the strategy and I've been faking it" in a meeting where they're reporting on their tickets.

What I try to bring is one piece of specific feedback, most weeks. Small, concrete, close to the event. The idea that feedback should be saved up for a designated moment is one of the more damaging conventions in management — feedback decays, and a note about how someone handled a meeting three months ago is useless and slightly insulting.

I also protect these ruthlessly. Cancelling a 1:1 because something urgent came up communicates a ranking, and people are very good at reading rankings. If I have to move one, I move it rather than skip it, and I say why.

Career development is a separate, scheduled thing

Development doesn't happen in the gaps of a weekly meeting. It needs its own session, on a slower cadence — quarterly works — with its own preparation.

The structure I use is deliberately simple. What's the next level or next role you want? What does that level actually require, in behaviors rather than adjectives? Where's the gap between that and where you are now? And what specific work in the next ninety days closes some of it?

The part that makes it work is that the gap has to be named honestly and the plan has to be made of assignments, not intentions. "Get better at strategic thinking" is not a plan. "You'll own the discovery for this next initiative end to end, present the recommendation to the leadership team yourself, and I'll give you notes after rather than editing it before" is a plan, because it produces reps and evidence.

One example I think about often. I had a product manager who was exceptionally strong technically — the best person I had at program-managing a complex backlog and partnering with engineering. Engineers trusted him completely. And he wanted to move into management, but he had a real gap: he was working from an internal backlog rather than from customers, and his roadmaps were well-sequenced without being strategically grounded. He could tell you what was next and not why it mattered.

Nothing about that gets fixed by encouragement. What we built was a plan aimed precisely at those gaps: he ran customer discovery himself rather than receiving research, he presented to executives regularly instead of feeding slides to me, and he took on the cross-functional stakeholder work he'd been avoiding. It took time and some of it was uncomfortable. He became one of the strongest people on the team and was eventually promoted to Director.

What I'd want to extract from that is not that coaching works. It's that the plan was specific to his gaps relative to his stated ambition. A generic development plan is a document. A plan built from one person's actual delta to one particular next role is a tool.

Performance management is the third conversation, and it's kindness

The word has an unearned reputation, mostly because it's so often done late and badly. Done properly it's one of the more respectful things a manager does.

Two rules I hold to. No surprises — if a formal conversation about performance contains new information, I failed at the weekly cadence, not them. And separate the two failure modes: someone below the bar for their current role is in a fundamentally different situation from someone meeting their bar but not growing toward the next one. Those get conflated constantly, and conflating them is cruel in both directions. It tells a solid performer they're failing, and it tells a struggling person they're merely developing slowly.

When someone genuinely isn't meeting the bar, the useful version is specific and early: here is the behavior, here is the standard, here is what changed behavior looks like, here is the timeline, and here is what happens if it doesn't change. Vagueness in this conversation is not gentleness. It's a way for the manager to avoid discomfort at the cost of the other person's ability to actually respond.

I'll also say something less popular: sometimes the honest answer is a role mismatch, not a development need, and coaching someone harder against a fit problem wastes a year of their career. The kindest conversation I've had in this category ended with someone moving to a different function where they were excellent. That was a management success, even though it looked like attrition on a spreadsheet.

The caveats

Frameworks like this become paperwork with alarming speed. The quarterly session turns into a form, the form gets filled in the morning of, and the whole thing decays into compliance. The only defense I've found is that the manager has to prepare seriously — if I show up to a development conversation having thought about it for four minutes, the person knows, and they'll calibrate their own investment to mine.

Not everyone wants intensive development, either. Some people are at a stage where the job is a job and the growth is happening elsewhere in their life, and that's a legitimate choice. Pushing a development plan onto someone who hasn't asked for one is managing for my own sense of being a good manager rather than for them. The question "how much of this do you want right now?" should be asked out loud.

And scale strains all of it. Somewhere past six or seven reports the quality of individual attention drops whether you admit it or not. The move is to coach your managers on doing this rather than to try to do it for everyone yourself — which means the framework has to be teachable, not just something I do well.

What holds it together isn't the cadence or the structure. It's that people can tell the difference between a manager who runs a development process and one who is actually invested in where they end up. The structure exists to make sure that investment shows up on a calendar instead of only in good intentions.