When someone didn't choose the role they were asked to lead

During a restructuring, a colleague moved from managing technical capacity to supporting the CEO directly as Chief of Staff — a change she didn't choose and that took her completely outside her known zone. The support wasn't about the new role's process, but about communication: helping her bring real concerns to the CEO clearly and without softening them out of insecurity. Under her leadership, commitment reliability and error-free delivery improved by more than 25% versus previous months.

The starting point: distrust and resistance

She arrived at that transition distrustful and resistant, especially about working closely with Product and with the CEO directly. It wasn't a role she had chosen, and it clearly stretched her beyond anything she had done before.

Where do you start supporting someone in a role they didn't ask for?

I didn't start with the new role's process — I started with how she communicated. At first she avoided bringing direct concerns to the CEO, softening messages or holding back worries out of insecurity, instead of stating them clearly. We worked through real situations together, not hypothetical ones, until she could bring a direct concern without it feeling like a risk to her.

What changed, measurable and not

She ended up taking full ownership of the process side of that role, and I kept supporting her through that transition. Under her leadership, commitment reliability and error-free delivery, among other KPIs, improved by more than 25% versus previous months. But what matters most to me isn't that number — it's that she learned to communicate frankly and directly with the CEO, without the underlying insecurity she brought at the start. That shift in confidence is, of the two, the one I'm proudest of.

The lesson I take

Supporting someone through a role they didn't choose isn't about teaching them the process as fast as possible. It's about identifying what's really costing them confidence, and working there first — the rest, including the numbers, usually follows.

Frequently asked questions

How do you support someone through a role they didn't choose? By first identifying what's costing them confidence (not what process they lack) and working on that with real situations, not hypothetical ones. In this case, the blocker was communication with the CEO, not the job's process.

What should you do when someone resists a role change? Don't force process adoption as the first step. Listen to what makes them insecure, work on that with real cases, and let mastery of the role come later — in this case, commitment reliability improved by more than 25% once the communication blocker was resolved.