I had the opportunity to attend numerous meetings and conference calls involving Zulfi and Kamal during my time in Allstate IT. What struck me repeatedly was not the depth of strategic discussion, but the lack of it.
I vividly remember meetings with dozens of attendees where significant time was consumed by basic IT and UI-level questions that a senior technology executive should already have understood. Rather than driving architecture, engineering, and business outcomes, conversations often stalled on fundamentals.
One example that has stayed with me was the decision not to perform a full ASC data conversion because of the associated cost, which was said to be in the hundreds of millions of dollars. Instead, the organization layered batch processes and relational-system workarounds onto the existing environment. The result was an architecture that was repeatedly described as "microservices" but remained burdened by complex legacy dependencies.
What is particularly troubling is that data conversion costs and complexities are neither unexpected nor unusual. A technology leader operating at that level should account for those realities at the outset of a transformation program. Data conversion is frequently one of the largest line items in any modernization effort, and its cost should be incorporated into the business case, architecture strategy, and long-term financial planning from day one.
Instead, the organization appeared to choose short-term cost avoidance over long-term architectural integrity. In practice, this meant placing a modern microservices front end over a foundation of legacy batch processing and relational systems. To many technologists, that looked less like genuine modernization and more like applying a cosmetic layer over fundamental architectural limitations.
The irony is that avoiding a major data conversion does not eliminate costs; it merely shifts them elsewhere. The technical debt created by maintaining hybrid architectures, integration layers, duplicate processing, reconciliation logic, and operational workarounds can persist for years. Those costs appear in maintenance budgets, project delays, reduced agility, increased complexity, and ultimately in the total cost of ownership.
This raises a broader question of leadership accountability. If hundreds of millions of dollars in conversion costs were foreseeable, why were they not adequately incorporated into the modernization strategy from the beginning? Effective technology leadership requires evaluating the full lifecycle cost of architectural decisions, not merely the initial implementation expense.
Meanwhile, departments were consolidated, headcount was reduced, and careers were disrupted in the name of efficiency. Yet many of the underlying architectural problems remained unsolved. Over the years, thousands of employees were affected by repeated reorganizations, outsourcing initiatives, and failed or incomplete transformation efforts, while the organization continued to struggle with many of the same core technology challenges.
Among architects and technical professionals, there was a widespread belief that these issues were understood internally, even if they were not openly discussed at the highest levels. Many hoped that senior leadership would eventually recognize the pattern and bring greater technical accountability to IT decision-making.
After nearly a decade, the consequences of those decisions are becoming increasingly difficult to ignore.