When the context changes, you change.

Authority is not conferred with the title. It is built through how you show up: whether you have genuinely inhabited the responsibility the position requires, or whether you are still leading from a previous version of yourself. The functional head who became a senior leader but is still solving functional problems. The experienced operator who moved into a strategic role but remains more comfortable in the detail.

The leaders who build authority fastest resist the pressure to prove themselves through activity. The traditional urge to do more is usually a trap. What the role requires is the discernment to know which tool to leave in the drawer, and the discipline to read the situation you are actually in rather than the one you expected to find. Knowing which version of your authority the moment requires, and being fully there rather than just being the person in the chair, is what makes the difference.

Longer than most organisations plan for. We have reached a point where the job is no longer a fixed destination but a state of perpetual motion. Even without a title change, the ground is constantly shifting.

The 90-day framework is useful for orientation. It is not a realistic measure of being settled. The leaders who navigate this fastest are not those who move quickest. They are those who invest time early in reading the system they have stepped into: understanding the conditions, the terrain, and what the situation is actually asking of them before they start trying to change it. Speed is not the same as momentum. The organisations that move fastest over time are usually the ones whose leaders were willing to move more slowly at the beginning, long enough to bring people with them rather than ahead of them.

Because the ground has moved. Transition creates a gap between the situation you are in and the habits you have relied on to succeed. What got you here was credibility in your domain, delivery, and leading a team with clear outputs. Senior roles ask for something different: reading and managing the system, the room, and yourself, often simultaneously, with less certainty and more visibility.

At this level it is rarely about what you know. It is about how you show up and apply your experience to what the situation requires. The instincts that served you well before can become the thing that holds you back. The room you think you are in and the room you are actually in are not always the same. Feeling out of your depth is a reasonable response to a genuine shift in what the role requires. The problem is not capability. It is that the old autopilot responses no longer fit the new situation, and that gap does not close by itself.

Usually because the organisation lacks the capacity to absorb the movement. A strategy can be clear at the top and still stall because one or more of the conditions required for it to move are not in place. A lack of clarity in what the strategy specifically demands feeds directly into how teams coordinate around it. Misalignment drains commitment as people disengage when effort feels purposeless or politically charged. All of that lands as headwinds in the organisation's ability to get things done, with the organisation consuming its own energy before it reaches the work.

A brilliant strategy landing in a system without those conditions becomes noise: or worse, another failed initiative that breeds cynicism. Building and maintaining the conditions in which an organisation can execute its strategy is not HR's job, or any single function's job. It is the work of leadership. It always has been.

Agreement is not the same as behaviour. A leadership team can commit to new ways of working and still revert to familiar patterns the moment the pressure is on. That is not bad faith. It is autopilot. When the ground moves, the temptation is to fall back on responses that worked in a different context. The space to think gets lost, and the system becomes noisy.

What you model, what you tolerate, and what you signal through your reactions are shaping the culture around you continuously, often invisibly. Getting a leadership team to behave differently requires more than a shared plan. It requires an honest read of the patterns currently operating in the team, clarity on what specifically needs to shift, and the sustained discipline of practising the new response in real situations rather than constructed ones. Presence is not performance. It is the condition from which everything else flows.

The first question is whether the leadership team has a genuinely shared and specific enough picture of what implementation requires of them collectively. A strategy that is clear at the level of intent can still fragment the moment the team leaves the room, if each member is working from their own interpretation of what it means for their function.

The second question is whether the conditions are in place for strategy to move through the structure without hitting bottlenecks: defined clearly enough that people can connect their daily work to the overall direction, aligned so that teams work across boundaries rather than defending their patch, and resourced so that effort converts to progress rather than being consumed by the same obstacles. Without those conditions, even a committed leadership team will find their effort absorbed by the system rather than translated into results.

Often because they are operating from different maps. Each member may have a clear picture of their own function and their own priorities. What they do not have is a shared picture of the terrain they are navigating together. You cannot navigate from different maps.

Behind most alignment failures are human dynamics that organisational design does not fix: the need to protect territory, the avoidance of conflict that lets misalignment quietly accumulate, the ego investment in outcomes that belong to a function rather than the whole. These are rational responses to environments that have taught people that self-protection is safer than collaboration. Strong alignment reflects people who feel secure enough not to need their patch, confident enough to share credit, and mature enough to handle the friction of genuine interdependence. That is built through leadership behaviour, not through reorganisation.

The constraint is rarely individual capability. Worth separating two questions first: whether the issue sits at the individual level (one or two members not performing) or at the collective level (the team as a whole not functioning as it should). Individual underperformance is a line management question. Collective underperformance is usually a question of conditions.

Most leadership teams are not real teams. They are a meeting: people who represent their function, come together regularly, and leave to lead their part. That works well enough until the strategy requires something that no single function can deliver alone. At that point the team needs to operate with genuine joint accountability for something none of them owns individually. That shift is one of the hardest in senior leadership. Diagnosing which you are dealing with is the right starting point before anything else.

Because agreement in a meeting and commitment to act differently are not the same thing. A team can reach apparent consensus without anyone having made a real decision to do something differently. This is often a pace problem as much as anything else: making deliberate choices about when to move, when to hold, and what the team is genuinely committing to, rather than what sounds reasonable in a meeting, is part of how a leadership team stays coherent rather than just busy.

It also requires honesty about what is actually being said and what is being left unsaid. A team that has learned what not to raise often mistakes ease for health. When everyone agrees readily and healthy conflict is rare, it is worth asking whether that reflects genuine alignment or whether the team has simply learned to avoid the conversations that matter most. Without the discipline to read the situation accurately and adapt, the pattern repeats regardless of how good the meeting was.

Because you cannot deploy AI into an unclear strategy, a fragmented structure, and a disengaged workforce and expect it to fix any of those things. It will produce a faster version of what was already not working. The problem is not the engine. It is the architecture. And the architecture is a leadership question.

What AI actually requires is what good leadership has always required: a clear strategy that people can connect their daily work to, teams that work across boundaries rather than defending their patch, people who feel genuinely invested, and the structures and decision rights to let effort convert to progress. AI cannot ask for conditions it has not been given. The organisations that get leadership right will be the ones that get AI right. Not the other way around.

Because AI does not create new problems. It removes the tolerance margin for existing ones. Before AI accelerated the pace of change, organisations could muddle through. Silos persisted because manual friction masked the cost. Unclear strategy survived because things moved slowly enough to correct course. Weak engagement was papered over by individual heroics. AI removes that buffer. It accelerates whatever conditions already exist.

The leaders finding it hardest right now are not, on the whole, the ones who lack technical fluency. They are the ones whose leadership is still built on expertise rather than the conditions that expertise was supposed to produce. When AI closes the knowledge gap in months, what was doing the work of authority becomes harder to see. The instinct under that pressure is to reach for a new tool, a new system, a new initiative. That is usually the mistake.