Leading a team you did not build

Almost nobody chooses their leadership team. They inherit one, assembled by a predecessor for reasons that made sense at the time and were never written down.

This produces a specific and uncomfortable early period. The new leader is accountable immediately for the performance of people they did not select, whose histories they do not know, in a set of working relationships that predate them and will outlast their honeymoon.

The two failure modes

The first is moving too fast. A new executive arrives with a mandate, sees an obvious structural problem in week three, and reorganizes. Occasionally this is right. More often it turns out the odd reporting line existed to route around a conflict nobody mentioned, and removing it releases the conflict into the open with the new leader's name on it.

The second is moving too slowly, which is more common and less discussed. The leader spends six months listening, avoids every difficult call, and by the time they act the team has concluded that difficult calls do not get made here. That conclusion is expensive and slow to reverse.

What the first ninety days are actually for

The useful frame is that the early period is for building an accurate model of the system, not for demonstrating decisiveness or for withholding it. Some things are worth learning before acting on them.

• Which relationships in this team are load-bearing, and which are merely long-standing?
• What did my predecessor decide that everyone is still working around?
• Where does information actually travel, as opposed to where the chart says it should?
• Which problems am I being shown, and by whom, and what does that tell me about who wants what?

That last question is the one most new leaders skip. Early in a tenure, people bring a leader the version of reality that suits them, and they are not usually being cynical. They are telling you the truth as they experience it, from a position you cannot yet see.

Making small decisions early

The way through both failure modes is to make small, reversible decisions quickly while the large ones are still being understood. It gives the team evidence that decisions get made, without betting the structure on a model of the organization that is three weeks old.

Coaching is useful here mostly as a place to be wrong out loud. A new executive has nobody internal they can think aloud with, because every internal conversation is also a signal. That constraint is real, and it is why the first year is lonelier than the job description suggests.