The CFO Who Was Still the Controller

He had been promoted nine months earlier. His title had changed. His office had changed. His behaviour had not. He still owned the variance reports personally, still corrected the junior analyst's pivot tables, still arrived at the board with the granularity of a man who had something to prove. The board was beginning to notice.

The most common failure in senior transitions is not incompetence in the new role. It is excellence in the previous one. The executive arrives at the new role still carrying the toolkit, the metrics, and the satisfactions of the role he just left. He is doing the work of his former self, with more authority and a larger team, and he calls this attention to detail.

The board did not promote him to be a better controller. They promoted him to be a CFO. These are not the same job, and the difference is not seniority. The controller's job is to ensure that the numbers are right. The CFO's job is to ensure that the right numbers are being produced, and that the company's capital posture, its investor narrative, and its risk architecture are coherent. The first is internal-facing and exact. The second is external-facing and judgmental.

The new CFO, in this case, was anxious about the second role and competent in the first. So he stayed in the first. Each time the board tried to discuss capital strategy, he returned the conversation to working capital. Each time they tried to discuss the investor narrative, he returned to the gross margin reconciliation. He was not refusing the new role. He was unable to inhabit it, and the controller work was a credible-looking refuge.

The deeper problem was that he had not yet built the team that would let him leave the controller work behind. His former deputy was capable, but he had not delegated to her. He had, in fact, in the first six months, slightly undermined her by intervening in her decisions in ways that signalled he still owned the territory. She had begun to wait for his input rather than acting independently. The team had configured itself around his refusal to leave.

This is a recurring pattern at every senior level. The new General Manager is still doing sales calls. The new Chief Risk Officer is still writing the credit notes. The new President is still chairing operating reviews. Each is excellent at the work, and each is, structurally, a level behind where the role requires him to be. The organisation watches and waits, sometimes for years.

The correction is rarely self-initiated. The executive can usually see the problem in others and not in himself, because to him, the work feels like quality assurance. It is not. It is comfort eating.

What helps, when anything helps, is a structural mechanism. Some boards now ask new senior hires to articulate, in writing, what they will stop doing in their first ninety days. The list is reviewed at the six-month mark. This is more useful than asking what they will start doing, because starting is easy and stopping is hard. The list of stops is the real test of whether the executive understands the geometry of his new role.

The CFO in this case did not produce such a list. By month fifteen, the board was actively discussing whether to bring in someone alongside him. He sensed this, intensified his attention to the variance reports, and produced an even more granular monthly pack. The board read this as confirmation of their concern.

Doing the previous role at the next level is not loyalty to detail. It is the visible shape of an executive who has not yet promoted himself in his own head.