Why Your New CFO Is Useless for Ninety Days, and Whose Fault That Is

A new finance chief starts in January. By April the board is quietly wondering whether the hire was right. By July the same person is visibly effective and the doubt is forgotten.

That pattern is so common it is treated as natural law. It is not. It is a cost the organisation imposes on every senior hire, and most of it is removable.

Where the first ninety days actually go

Weeks one to three: orientation. Meeting people, learning territories, finding out where things are. Little of this is optional and none of it is productive in itself.

Weeks three to seven: data archaeology. Requesting reports, discovering two systems disagree, learning which numbers are trusted internally and which are quietly known to be wrong. The largest block and the most wasteful, because every answer they reach was already known by someone in the building.

Weeks six to ten: informal mapping. Learning how decisions actually get made, as distinct from how the org chart says they do. Conducted entirely through conversation, because it has never been written down.

Weeks ten onward: first independent decisions. Acting on their own judgement rather than deferring to whoever has been here longest.

Roughly two thirds of that is reconstruction of existing knowledge. It is not thinking time. It is retrieval, conducted inefficiently because there is nothing to retrieve from.

You did not hire them to spend a quarter finding out what your company already knows. But that is what you bought.

Why it is not a talent problem

The diagnostic test is simple: the ramp is roughly the same length for strong hires and weak ones. A strong hire is better during the ramp — better questions, faster synthesis — but they do not skip it, because the constraint is not their processing speed. It is the rate at which the organisation can supply context, and that rate is set by how many people they can talk to per week.

The artefacts that collapse it

A definitions register. Every metric in a board pack, with its precise definition, owner, source system, and any known disagreement about it. The disagreements are the valuable part — they are what a newcomer otherwise spends weeks discovering by accident.

A decision log. The significant decisions of the last two years: what was chosen, what was rejected, what would trigger revisiting. The single artefact that most shortens a ramp, and almost nobody keeps one.

A real map of how things get decided. Written honestly, including the informal parts. Which forum actually settles things. Whose agreement is required in practice.

A live state-of-the-function summary. Not a snapshot prepared for the arrival. What is working, what is not, what is in flight, what is deferred and why.

Why nobody maintains them

These are cheap to maintain, expensive to create, and the benefit lands on someone who has not been hired yet. No incumbent has an incentive to build them, which is exactly why they do not exist anywhere.

That makes it a leadership decision rather than an operational one. The practical version: make the decision log a standing output of whatever forum already makes decisions, so it is a byproduct rather than a project. Ten minutes at the end of a meeting that is already happening.

Then measure the ramp. Time from start date to first independent decision, tracked for every senior hire. If it is not shortening, the artefacts are not being maintained, whatever anyone says.