Why Pay and Development Can't Share a Conversation

The Moment Honesty Leaves the Room

Of all the structural mistakes I see in how practices run their performance conversations, one stands out as the most damaging and the most common. The conflation of pay and development into a single conversation.

It usually happens at the annual review. The form has a section on performance, a section on development needs, and somewhere — sometimes explicit, sometimes implied — a connection to the pay decision that follows. The leader believes they're being efficient by combining the conversations. The team member knows, from the moment they sit down, that whatever they say in the next hour will influence what they earn next year.

From that moment, honesty is gone. From both sides.

How Team Members Perform Competence Instead of Developing It

The team member can't say I'm struggling with this part of my role. Doing so might be heard as an admission that they don't deserve a rise. They can't say I'm not sure I'm in the right role. That sounds like notice. They can't admit to a gap, ask for help they need, or name a development area they want to grow into, because all of those, in a conversation tied to pay, get reinterpreted as weakness.

So they perform competence instead. They give a curated version of the year. They highlight what went well. They downplay what didn't. They wait to see what the leader does with the pay decision, and they leave the room slightly flatter than they went in, having had no real development conversation at all.

The leader is in the same trap from the other side. Anything they say that sounds like criticism will be heard as justification for a low pay award. So they soften the feedback. They wrap concerns in caveats. They mention development areas in language so general that nobody could act on them. Then they make the pay decision and move on.

An hour has been spent. A form has been completed. Nothing useful has been said.

The Structural Fix (That Isn't Complicated)

The fix is straightforward and it's structural. The two conversations have to be separated. Different time, different framing, different decision criteria.

The performance and development conversation is about growth. What's working, what isn't, what needs to develop, what support is required. The team member needs to be able to say I don't know how to do this part of my role without it costing them. The leader needs to be able to name a gap without it sounding like a punishment. That conversation is best held as part of the quarterly rhythm — twenty to thirty minutes, structured but not heavy, forward-focused.

The pay conversation sits elsewhere. Different month if possible. Its own logic. Pay should reflect role, market, contribution, and the practice's position. It shouldn't be the reward dispensed in the same room where you're asking someone to be vulnerable about what they need to learn.

What Happens When You Make the Separation

Some leaders worry that separating these will make the pay conversation feel cold or transactional. In practice, the opposite is true. When pay is its own conversation, with its own rationale, it actually feels fairer to both sides. The team member knows what the decision is based on. The leader can be specific about it. There's no awkward link between the criticism delivered ten minutes ago and the number being offered now.

More importantly, the development conversation can finally do its actual job. With the pay decision out of the room, the team member can be honest about where they're struggling. The leader can be honest about what needs to change. Real progress can be agreed, supported and tracked.

Practices that make this separation report the same thing. The development conversations become more useful, more honest, and more valued by both sides. The pay conversations get easier. The annual review, if it survives at all, becomes a much smaller event, because the work it used to try and do has been done elsewhere, more consistently, and to a higher standard.

Combining pay and development doesn't make either conversation more efficient. It makes both of them less honest. Separate them, and both improve.