IT Program Audit: $7M Project Halted, $20M in Future Losses Avoided

Situation

A large national insurance firm had been developing an enterprise-wide enrollment system for three years. The system was designed to capture new insurance business — a mission-critical platform that sat at the center of the company’s revenue generation capability. After three years of development and $7 million in investment, the project had produced very little that was usable.

The application that existed was slow, difficult to use, and painful to modify. Every change required a disproportionate amount of IT effort. Performance was poor. The user experience was frustrating. And the business teams who were supposed to benefit from the system had grown deeply skeptical that it would ever deliver what had been promised.

The business leadership — led by a senior vice president who had been watching the situation deteriorate — had reached the limit of their patience. They needed an independent, objective assessment of what was actually going on and a clear recommendation on what to do next. Full On Consulting was brought in directly by business leadership to conduct that assessment.

Challenge

The engagement presented a set of challenges that go beyond technical complexity. Conducting an independent audit of a failing IT program — inside an organization where the IT team has been employed for decades — requires a specific combination of technical expertise, political judgment, and the credibility to deliver findings that people do not want to hear.

Action

Full On Consulting began by conducting a structured series of interviews across the organization — the CIO, IT leadership, the project team, the infrastructure team, the development team, and the business stakeholders who had been waiting on the system. The goal was to build a complete picture of the situation from every perspective: what each group believed the problems were, what decisions had been made and why, and what the technical reality of the application actually was.

As expected, the IT organization was guarded. People who have been with a company for decades — and who know that an outside assessment of their work is underway — do not volunteer information that reflects poorly on their decisions. The assessment required going beyond what people said and evaluating what the evidence showed: the architecture of the application, the technology choices that had been made, the development practices that had been followed, and the performance characteristics of the system that had been built.

What the Assessment Found

The root cause of the failure was not the platform, the tools, or the framework — it was the team’s lack of experience with all three. The IT team had been with the organization for many years, had developed deep institutional knowledge of the company’s business, and had successfully maintained legacy systems for decades. What they did not have was experience with modern application development practices, current Java frameworks, and the architectural patterns required to build a performant, maintainable enterprise application on a modern stack.

The decision to develop the enrollment system internally using a modern platform was made with confidence — but that confidence was not grounded in demonstrated capability. The team had attempted to learn new tools, technologies, and frameworks while simultaneously delivering a complex enterprise application. The result was an application that had been stitched together based on dated instincts applied to modern technology: poorly architected, not following software development best practices, and not designed for the performance requirements of an enterprise-scale enrollment system.

The application was slow because the architecture could not support the load. It was difficult to maintain because the code did not follow the patterns and conventions that make modern applications maintainable. Every change required disproportionate effort because the technical debt embedded in the foundation compounded with each addition. Three years of work had produced a system that could not be fixed incrementally — the foundational decisions were wrong, and fixing the symptoms would not address the cause.

The lack of transparency from the IT organization to the business was not malicious — it was a symptom of a team that did not fully understand the nature of the problems they had created, and that had no framework for communicating technical debt and architectural risk in business terms. The business teams were frustrated because they were experiencing the consequences of decisions they had never been informed about.

Presenting the Findings

Full On Consulting prepared a comprehensive assessment report and presented it to the IT organization, the business leaders, and the CEO. The report identified the specific root causes of the failure, documented the technical evidence supporting each finding, and assessed the implications for the path forward.

In a one-on-one conversation with the CEO, the question was direct: what should we do next? The answer, based on the depth of the technical problems identified, was equally direct: the application as built was not salvageable. The architectural problems were foundational. Continuing to invest in the current codebase would produce more of the same results — more time, more money, and an application that still could not perform at the level the business required. The recommendation was to stop development, assess the true cost of what had been built, and make a deliberate decision about the path forward with full information rather than continuing to invest in a failing approach.

Result

The CEO accepted the findings and the recommendation. Development on the enrollment system was halted, preventing additional investment in an approach that could not be salvaged. The decision was not easy — $7 million had already been spent, and stopping meant acknowledging that investment would not produce the intended return. But continuing would have compounded the loss without changing the outcome.

The more significant outcome was what happened next. At the time of the assessment, the organization was preparing to embark on a new initiative: a $20 million effort to develop a policy administration system internally. Based on the findings of the enrollment system audit — and the clear pattern it revealed about the organization’s internal development capability — the CEO changed direction. The $20 million internal development initiative was redirected. What would have been another multi-year, high-risk internal development effort was restructured to avoid repeating the same mistakes.

Changes were also made within the IT organization to address the capability gaps identified in the assessment and to establish the transparency and communication practices that the business teams had been missing. The relationship between IT and the business — strained by three years of frustration and opacity — began to be rebuilt on a more honest foundation.

Summary of Outcomes

What This Engagement Illustrates

This engagement illustrates one of the most valuable — and most underutilized — forms of IT advisory: the independent program audit. When an IT initiative has been underway for years without producing results, the organizations most affected are often the least equipped to assess what is actually wrong. The people closest to the problem have the most invested in a particular narrative. Leadership has been receiving reports that do not reflect reality. And the business has been absorbing costs and frustration without understanding why.

An independent assessment — conducted by someone with no stake in the current state and deep enough technical expertise to evaluate what they find — cuts through that. It gives leadership the information they need to make real decisions rather than continuing to fund hope.

In this case, the value of the assessment was not just the $7M it stopped. It was the $20M it redirected. The return on a well-executed IT program audit is almost always a multiple of its cost — because the decisions it informs are almost always larger than the assessment itself.