Agreeing with the decision, disagreeing with how it was communicated

A peer conflict escalated to the CEO, who decided to split a team into two specialized functions — implementation and support. The assignment of people was never discussed with me beforehand, and I was direct with my own leader about disagreeing with how it was communicated, though I recognized the underlying decision was right for the business. That specialization ended up measurably accelerating new-client onboarding speed, and became the operational base that gave the company confidence to expand beyond Mexico.

The conflict: two peers, a different assumption

A new team member arrived assuming he would lead the whole team, when in fact he was my peer — the rest of the team reported to me. His leadership style generated real conflict, which ended up escalating to the CEO.

What do you do when you weren't consulted on a decision that affects you?

The CEO's decision was to split the team into two specialized functions, giving the new member his own group dedicated to implementations, while my team focused on ongoing support. The problem was that the assignment of people — who would report to whom — was never discussed with me beforehand. I was direct with my own leader about disagreeing with how it was communicated, while recognizing that, fundamentally, the decision was the right one: separating implementation from support let each function develop real depth, instead of one team doing both superficially.

How do you handle team resistance?

I had one-on-one conversations with the people now reporting to the new leader, framing the change as a growth opportunity: that new leader brought deep knowledge of microfinance and banking that I didn't have at the time, and working under him was a real chance to develop that expertise, not just a forced reorganization.

What was the outcome of that specialization?

The team gave the new leader and the new structure a genuine chance, and the specialization paid off fast. With implementation operating as a dedicated function, new-client onboarding speed improved measurably, because the team could focus entirely on integration quality and speed without also carrying ongoing support tickets. That faster, more reliable implementation process became one of the company's strongest sales arguments, and gave the company the operational confidence to start thinking beyond Mexico.

The lesson I take

You can disagree with how a decision was communicated without disagreeing with the decision itself — and saying that out loud, upward, doesn't weaken your position. What would fracture it more is staying quiet and letting the team's resistance become the real problem.

Frequently asked questions

What do you do when you agree with a decision but not with how it was made? Say it clearly upward, separating the two: disagreeing with how it was communicated isn't disagreeing with the decision. Staying quiet lets the team's resistance become the real problem.

How do you handle a leadership change the team didn't ask for? With one-on-one conversations that frame the change as a growth opportunity — naming the concrete expertise the new leader brings — instead of presenting it as a forced reorganization.