Template 4 — Transformation Reset Briefing
Written Pre-Board Briefing
Technology Transformation Reset Briefing | Prepared by: CTO | For: Board of Directors | Distributed: 5 days before board session | Prepared jointly with CEO
Executive Summary
This briefing addresses a material change in the technology transformation program. The current trajectory is not producing the outcomes the board approved investment for, and continuing on it would compound the cost of correction. A reset is required.
This briefing covers: what is not working and why, what assumptions proved wrong, what changes now, what the capital implications are, and what the board should expect next. It was prepared jointly with the CEO. The assessment it contains reflects a shared executive view, not a technology-only perspective.
Section 1 — What Is Not Working
Stated specifically, not generally.
The platform migration program — designed to consolidate four customer data systems into a single shared platform — is eighteen months behind schedule and has consumed $2.1M of the $2.8M approved budget without reaching the consolidation milestone. Two of the four systems have been migrated. The remaining two are significantly more complex than the original assessment indicated, and the current team configuration cannot complete them within the remaining budget.
The delivery velocity impact is measurable and compounding. Teams building on the unconsolidated data model are absorbing 23% of their engineering capacity in reconciliation work — work that disappears when consolidation is complete but is consuming capacity that was supposed to be available for product delivery.
The AI initiatives planned for H2 depend on the consolidated data model. They cannot proceed until consolidation is complete. This blocks $1.4M of planned AI investment.
Section 2 — What Assumptions Proved Wrong
Assumption 1 — Migration complexity was underestimated. The original assessment classified two of the four systems as low-complexity migrations. Direct examination of the legacy code revealed custom business logic that was not documented and cannot be migrated without rebuilding. This was not visible in the discovery phase.
Assumption 2 — Team velocity was overestimated. The program plan assumed the migration team could maintain projected velocity while absorbing the complexity of the legacy systems. In practice, the team has been operating at 60% of projected velocity for three consecutive quarters. The root cause is the undocumented complexity, not team performance.
Assumption 3 — Downstream dependency was underestimated. The AI investment was approved on the assumption that the data foundation would be complete by Q2. It was not. The dependency was known but the timeline risk was not adequately communicated to the investment decision.
Section 3 — What Changes Now
Three changes, in order of priority.
Change 1 — Scope reduction. The program will migrate three of the four systems rather than all four. The fourth system — the legacy order management data layer — will be isolated rather than migrated. Isolation means it will continue to operate as a standalone system with a defined integration interface. This removes the highest-complexity migration from the critical path and allows the program to complete within the remaining budget.
Change 2 — AI investment sequencing. The two AI initiatives blocked by data foundation dependency will be deferred until Q3 of next year, when the revised consolidation timeline is complete. The $1.4M of planned AI investment will not be deployed until the foundation is confirmed ready.
Change 3 — Revised governance. The program will operate under a revised governance model with quarterly board visibility into consolidation progress against a milestone-based plan. The CTO will personally own the milestone reporting rather than delegating it.
Section 4 — Capital Implications
| Item | Original approval | Current status | Revised requirement |
|---|---|---|---|
| Platform migration program | $2.8M | $2.1M spent, $700K remaining | $700K remaining sufficient for revised scope |
| AI initiative investment | $1.4M planned for H2 | Deferred — not yet deployed | Deferred to Q3 next year |
| Additional remediation cost | Not in original scope | $180K — legacy isolation work | Requires board approval |
| Total program cost | $2.8M | $2.28M to completion (revised scope) | $180K additional approval required |
The program can be completed within the revised scope for $180K above the original approval. The alternative — continuing on the current trajectory — is projected to require an additional $800K–$1.1M and will not produce a materially better outcome given the legacy complexity discovered.
Section 5 — What the Board Should Expect Next
A revised program plan with milestone-based progress tracking will be distributed within 14 days. Quarterly board updates will include a consolidation progress dashboard alongside the standard governance update. The next board session will include a 30-minute deep dive on the revised program plan and the milestone criteria.
If the revised program encounters material obstacles — complexity discoveries, team velocity issues, or dependency changes — the board will be notified within 30 days, not at the next quarterly cycle.
Verbal Presentation Structure — Transformation Reset Briefing
Recommended time: 40–50 minutes | Format: Joint presentation with CEO, structured discussion
Transformation Reset — Verbal Structure
Opening — CEO (3 min) The CEO opens to signal executive alignment. A reset presented only by the CTO will be interpreted as a technology problem. A reset presented jointly signals shared ownership and a shared response.
What is not working — CTO (8 min) Specific, factual, without qualification. Numbers, not descriptions. State the impact in business terms: what is not being delivered, what investment is not returning, what future capability is blocked.
What assumptions proved wrong — CTO (8 min) The hardest segment and the most important for governance trust. Name each assumption specifically, explain why it was wrong, acknowledge the impact. A CTO who cannot articulate what they got wrong has not earned the board’s confidence in what they propose to do next.
What changes now — CTO (10 min) Three changes, clearly stated, with a rationale for each. Invite challenge here — the board’s strategic judgment on the scope reduction decision is genuinely valuable.
Capital implications — CTO + CFO (5 min) Present the table. State the request. Give the board the comparison: the cost of the revised approach versus the projected cost of continuation. Do not present only the revised approach cost.
What to expect next — CEO (3 min) The CEO closes the substantive content to reinforce joint ownership of the path forward.
Questions (10 min) Reserve genuine time. A transformation reset briefing that does not allow adequate question time signals the board is being managed rather than governed.