On transitions
The team didn't choose you
Daphne Bernicker · 4 min read
A CEO hired by investors arrives with the title and not much else. The board chose them, but the team didn't. Whatever the résumé says, the people in the building are still loyal to the founder: to their habits, their relationships, and their way of getting things done. The new CEO walks into a company that has already formed opinions about who belongs.
I have worked with CEOs in this position, and the hardest part is rarely the strategy. Most incoming CEOs can see what the enterprise needs. The harder part is the people work in the first months, because that is when the team decides how much influence the new CEO will have, often before the CEO has made any major decisions.
The first job is the team
An incoming CEO arrives with a plan. The first months are when it gets tested, against the business and against the people who will carry it out, and what the CEO learns about the people usually changes it.
Evaluating a team you have just inherited is difficult. You are judging people you barely know, often on incomplete or conflicting information, while you are also learning the culture, building trust, and deciding who belongs in which role. Move too quickly, and you risk losing people you need; wait too long, and informal leaders fill the gap and people start deciding without you.
One thing I watch for is whether the team sees discipline. The team notices whether the CEO makes decisions when promised, and what the CEO does when the plan changes. A CEO who explains why the plan changed keeps the team's confidence. People can follow a change of course when they understand the reason for it. When the plan changes every time pressure rises, and no one explains why, the team learns that the plan is negotiable. People stop committing to it and start waiting for the next version.
Seeing people as they are
When I am working with a CEO in the first months of a transition, the people come up in our conversations before the strategy does. We go back through what they saw in the meetings: who pushed back, who went silent, what was said in the hallway afterward.
As humans, we have a natural tendency to believe that other people think the way we do, or that they should. We watch others' actions and reactions, and we infer their motives based on what our motives would be if we acted that way: if I had done that, I would have been thinking this, so that must be what they were thinking. A CEO who values speed may read deliberation as indecision, and a CEO who leads through intensity may read a colleague's calm as disengagement. This happens even when people have worked together for years.
For an incoming CEO the risk of misreading is higher because you don't yet know the team. You have not yet learned anyone's rules, so your own are the only ones you have. Getting to know your team means learning what each person believes and reading their actions through that. It happens in ordinary moments, by paying attention to how each person works.
With an incoming CEO, I help build that understanding: listening for what each person believes, and checking my own assumptions as carefully as theirs.
While you are reading the team, the team is reading you: how you treat the people who were loyal to the founder, how you respond when someone contradicts you, and whether what you said on Monday happens by Friday. Trust builds in those small exchanges.
The communication that keeps people with you
An incoming CEO may be tempted to say nothing until the plan is complete. But when people don't know what is happening, they explain it to themselves, and their explanations are usually worse than the truth. People who feel uncertain for long enough start to pull back, and the strongest people, who have other options, start looking at them.
I have watched a CEO hold a team together with very little to give them. “We are working on this, and I will have more for you at the next meeting” is enough, said consistently and backed up each time. What people rely on is the cadence. The CEO who shows up on schedule with a little more each time builds more trust than the one who waits until the whole answer is ready.
The part that is personal
Deciding who fits and who doesn't means accepting that some people will be hurt by your decisions, and that some of them have been in the enterprise longer than you have. You may be disliked for a while. What you can keep is their respect, by being consistent and fair while things settle.
It's tempting to delay or soften these conversations to avoid hurting people or being disliked. But putting them off doesn't make the issue go away, and it usually makes it more expensive. Meanwhile, the team can see that nothing has been decided.
If this goes on too long, the team starts to feel that you never really committed to them, and they stop committing to you. The team didn't choose you. Hesitation tells them you haven't chosen them either.
The question worth sitting with
Are the people waiting on your decisions hearing from you often enough, and when they aren't, what are they deciding on their own?
Keep reading
© 2026 Bernicker Leadership Advisory. All rights reserved.