No incoming CEO arrives with more institutional knowledge than one who has spent a career building it. That knowledge is the foundation of everything you will do. And it creates a specific, predictable blind spot — one that no amount of internal data, no executive team briefing, and no board conversation will resolve.
The blind spot is not strategic. It is not operational. It is structural — the accumulated patterns of how the organisation actually functions beneath the surface of the one you have always known.
The first 90 days as CEO are the only window in which those patterns can be seen clearly and changed without the full political weight of tenure. After that, the organisation adapts to you — and the window closes.
The specific risk for an insider CEO →This is not a criticism of insider succession. It is a structural reality that applies to every leader promoted from within — and it is most acute at the CEO level, where the stakes of not seeing clearly are highest.
Twenty-five years of earned trust is an asset. It is also a filter. The organisation has observed, over decades, what you reward, what you ignore, and what makes you uncomfortable. By July, it already knows how to manage you — before you have made a single decision as CEO.
The organisation grants a new CEO a brief period of genuine openness — before it learns your patterns, before the political alignments crystallise, before people decide what is safe to tell you. That window is not defined by your intentions. It is defined by theirs.
Establish the baseline. Before the role fully absorbs your attention, a diagnostic can begin mapping the structural patterns that will most affect your first decisions.
The organisation is watching closely. What you ask, who you meet, what you signal — all of it is being interpreted. A parallel diagnostic runs beneath that without interference.
The window when genuine structural change is still possible without it being read as crisis management. The diagnostic is complete. The picture is clear. The decisions are yours.
Not a survey. Not a cultural assessment. A structured diagnostic — conducted across functions, across levels, across the informal dynamics that never appear on any report — designed to give the incoming CEO a picture of their organisation that no one inside it can provide.
BHP is entering its copper growth phase under a new leader at precisely the moment when geopolitical complexity, capital allocation pressure, and a generational shift in mining strategy converge. The organisation that delivered the last decade's results was shaped for a different set of priorities.
The structural and relational patterns that are currently invisible — because they have been stable and functional — will become visible under a new strategic agenda. The question is whether they become visible on your terms, or on the organisation's.
The logic that governs project-level value optimisation is sound: define scope, establish visibility, measure leakage, surface the problem to the decision-maker. It is the same logic that would, applied at the organisational level, resolve the structural inefficiencies that compound silently across every function and every reporting line.
The reason it has never been applied is structural, not intentional. At the project level, the boundaries of the problem are defined. At the organisational level, the boundaries are the problem. No one inside them has the authority — or the visibility — to see the whole.
Scope is defined. Authority is clear. Every inefficiency is a problem to be solved.
Scope is diffuse. Authority is ambiguous. Inefficiencies become structural features — accepted as normal because no one has visibility across the whole.
Problem awareness is the starting point. The team cannot optimise what it cannot see — so visibility is built into the methodology.
Problem awareness requires crossing boundaries that most people do not have authority to cross. The problems that persist longest are precisely the ones that sit between scopes.
The framework defines the contribution. Human talent operates within an agreed set of tools, methods, and constraints.
The same constraint that ensures delivery discipline at the project level becomes the mechanism by which organisational dysfunction is preserved. People cannot name what their role does not permit them to see.
Value leakage is measured. Rework, delay, scope drift — each is tracked, attributed, and surfaced to the decision-maker.
Value leakage at the organisational level is rarely measured and almost never attributed. It appears instead as friction, attrition, decision latency, and execution gaps — without a clear owner or a visible cause.
"The discipline you have applied to optimise value at the project level is precisely the discipline that, applied to the organisation as a system, would surface what no internal review, no engagement survey, and no executive offsite has been able to find. The difference is not methodology. It is the vantage point."
A single conversation — before July, before the role fully consumes the available attention — is enough to determine whether this diagnostic would be valuable. There is no commitment involved. There is only the question of whether the picture it provides is one worth having.