Telling the Board a Transformation Is Not Working
This is the conversation most CTOs hope they never have to have — and the one that, when it arrives, separates the CTOs who govern from the ones who manage perception.
A transformation program has been underway. Investment has been committed. Milestones have been communicated. The board has been updated regularly, and the updates have been positive — or at least not alarming. And now the CTO knows, with sufficient clarity to state it, that the transformation is not working. The hypothesis is not proving out. The investment is not returning what was projected. The system being built is not the one the organization needs.
The board does not yet know this. The CTO must decide whether to tell them.
That decision — whether to surface a failing transformation before the board sees it independently — is the most consequential credibility decision a CTO will make.
What makes this conversation hard
The pressure against having this conversation is enormous and comes from multiple directions simultaneously.
The CEO may not share the CTO’s assessment. Surfacing a transformation failure before executive alignment risks damaging the CEO relationship and creating the impression that the CTO is operating outside their lane.
The board has been receiving positive updates. A sudden shift in assessment — from progress to failure — will raise questions about why the earlier updates were not more accurate. The CTO is not just delivering bad news. They are acknowledging that previous communications were incomplete.
The investment committed to the transformation is significant. Acknowledging failure triggers questions about accountability, about what was missed, and about who was responsible for the decisions that led here. The CTO who surfaces the failure is not insulated from those questions simply by being the one who raised the issue.
And the CTO’s own judgment is implicated. In most cases, the CTO had a role in designing or endorsing the transformation hypothesis that is now not proving out. Telling the board it is not working is, in part, telling them that earlier judgments were wrong.
What is actually at stake
The immediate question is whether the board receives an accurate assessment of the transformation’s status. That matters, but it is not the primary stake.
The boundary being tested is whether the CTO’s commitment to honest governance holds under the pressure of organizational reputation, executive alignment, and personal accountability. A CTO who manages the board’s perception of transformation progress rather than giving the board the information it needs to govern is not operating as a structural leader. They are operating as a communications function.
The mandate boundary is this: the board’s ability to govern the technology investment depends on receiving accurate information from the CTO. That is not contingent on the information being comfortable. A CTO who withholds or softens material information about transformation progress because the conversation is difficult has compromised the governance relationship that everything else depends on.
The long-term consequence of managing perception is worse than the short-term consequence of the honest conversation. A board that discovers a transformation has been failing — through external signals, through financial performance, through a crisis — and simultaneously discovers that the CTO knew and did not communicate it clearly, has no reason to trust the CTO’s subsequent assessments. The credibility required to lead through the recovery has been spent on managing the narrative of the failure.
How to prepare
This is the conversation where preparation is most consequential and most often absent — because the instinct when facing a transformation failure is to continue managing the situation rather than preparing to communicate about it honestly.
Three things must be in place before the conversation.
First, the assessment must be honest and complete. Not “the transformation is facing headwinds” — a characterization that every board has heard and learned to discount. The assessment must be specific: which elements of the hypothesis have not proven out, what evidence supports that conclusion, and what the financial implication of continuing on the current trajectory is. Vagueness in this conversation is not diplomacy. It is what damages credibility most.
Second, the CTO must have a position on what happens next. A board told that a transformation is not working and offered no path forward will fill that vacuum with their own conclusions — about management capability, about investment decisions, and about what should happen next. The CTO who arrives with an honest assessment of what is not working and a clear recommendation for what to do about it is in a fundamentally different position than one who arrives with only the bad news.
Third, the CEO alignment question must be resolved before the board conversation. If the CEO shares the CTO’s assessment, the conversation should happen jointly. If the CEO does not yet share it, the CTO faces a harder sequence: first, bringing the CEO to a shared assessment, and then, together, communicating it to the board. Going to the board before the CEO is aligned creates a governance crisis on top of a transformation crisis. It is almost never the right sequence.
How to hold the position
The pressure point in this conversation is the board’s desire for a recovery plan that preserves the original investment thesis. Boards do not easily accept that capital has been misallocated. The instinct is to find a way to make the original thesis work — to adjust the timeline, add resources, or reframe the objective in a way that allows the investment to be characterized as on track.
What cannot be traded is the accuracy of the assessment. The board can determine the response — they can choose to continue the investment on adjusted terms, redirect capital, or accelerate the exit from the current approach. That is their governance prerogative. But they must make that choice with accurate information. A CTO who adjusts the assessment to make the recovery plan more plausible is not helping the board govern. They are making a capital allocation decision on the board’s behalf, without the board’s knowledge.
When board members push back on the assessment — challenge the evidence, question the methodology, or suggest that the CTO is being too pessimistic — the CTO must hold the position on the evidence while remaining genuinely open to new information. The distinction matters. Holding the position on the evidence means not softening the assessment because it is uncomfortable. Being genuinely open to new information means being willing to revise the assessment if the board surfaces evidence that was not in the CTO’s analysis.
Defensiveness closes that distinction. Clarity keeps it intact.
What failure looks like
The most common failure is the managed narrative that delays the honest conversation until the board sees the failure through external signals. The CTO continues to report progress in terms that are technically accurate but structurally misleading — the delivery milestones are being met even though the hypothesis is not proving out, the investment is being deployed even though the return projections are no longer realistic. The board continues to approve capital on the basis of an assessment that the CTO knows is incomplete.
When the failure becomes undeniable — through financial results, through a competitive event, through a platform failure that is visible externally — the board’s first question is not about the transformation. It is about why they were not told earlier. The CTO who managed the narrative has not protected the organization. They have protected the narrative at the organization’s expense.
The second failure mode is the honest conversation that is poorly timed or poorly sequenced. A CTO who surfaces the transformation failure without CEO alignment, without a position on what happens next, and without evidence that is specific enough to be evaluated, will produce a governance crisis rather than a governance conversation. The board will lose confidence not just in the transformation but in the CTO’s judgment — and that loss of confidence will make the recovery significantly harder.
Honesty without preparation is not courage. It is a different kind of failure.
Five Circles reference: Circles I & IV — Strategic Clarity and Capital & Execution Engine