Dominic Jainy is a distinguished IT professional whose career spans the complex intersections of artificial intelligence, machine learning, and blockchain technology. With a deep focus on how these emerging tools reshape industrial landscapes, he has become a leading voice on the structural challenges of modernization. His insights move beyond the technical “how-to,” focusing instead on the organizational architecture required to sustain long-term innovation. In this conversation, we explore the persistent gap between strategic design and operational reality, examining why most transformations lose their footing after the initial excitement fades and how leaders can build systems that actually survive the rigors of delivery.
The discussion delves into the subtle erosion of momentum that plagues large-scale programs, the pitfalls of oversimplifying complex value chains, and the “illusion of agility” that often masks rigid, traditional operating models. We also look at the critical role of the “people system”—including incentives and career progression—in ensuring that digital change is not just a temporary spike in performance but a permanent evolution in capability.
While over half of organizations initially meet their transformation goals, only 12% sustain those gains long-term. Why does momentum typically erode after the first three years, and what specific metrics should leadership track to identify when benefits are beginning to slip?
The erosion of momentum is rarely a sudden crash; it is a subtle, structural fragmentation that occurs when the initial “honeymoon phase” of budget approval and high-level alignment ends. After three years, many organizations find that the early clarity of their strategy has dissolved into a mess of disconnected projects and KPI dashboards that no longer reflect the original intent. We see this frequently in large public sector programs where execution becomes a game of task completion rather than outcome realization. To catch this slippage early, leadership must look beyond simple project milestones and track “translation health”—measuring how consistently intent is being converted into real-world decisions across different departments. They should monitor the rate of benefit realization against the original business case and look for rising friction in upstream or downstream dependencies, which usually indicates that the strategy is no longer surviving real operating conditions.
Strategy is often handed over as a finished document rather than an evolving process. How can teams bridge the gap between high-level leadership narratives and the technical constraints faced by delivery squads, and what does a successful “translation” of intent look like in practice?
Bridging this gap requires moving away from the sequential model where strategy is a “discrete phase” handed over to a delivery team. There is a profound cognitive gap between senior leaders who think in abstract narratives and delivery squads who live in the world of technical specificity and hard constraints. Successful translation looks like a continuous feedback loop where strategic intent and operational reality are held together simultaneously. In practice, this means strategy is treated as a living document that evolves as delivery teams uncover new constraints or opportunities on the ground. When translation is done well, a developer at the keyboard understands the “why” behind a feature just as clearly as the CEO, ensuring that trade-offs made during a sprint don’t inadvertently undermine the long-term vision.
When organizations ignore the end-to-end value chain, optimizing one department often creates friction elsewhere. What are the risks of simplifying complex systems too aggressively, and how can managers maintain strategic fluidity while managing upstream and downstream dependencies?
The biggest risk of aggressive oversimplification is the creation of fragility; you remove the vital context needed to make informed decisions, leaving the system unable to handle the inherent complexity of a digital shift. When you optimize a single function in isolation, you almost inevitably create bottlenecks for other departments, which slows down adoption and erodes the value you were trying to create in the first place. Managers must develop a “multi-level fluency,” meaning they have to understand how a change in one part of the value chain ripples through the entire organization. Maintaining strategic fluidity requires a shift in mindset: instead of trying to eliminate complexity, managers should focus on navigating it by ensuring that communication channels between upstream and downstream teams are wide open. This ensures that the transformation cuts across functions rather than getting stuck in them.
Many firms adopt agile rituals like stand-ups without changing their underlying operating models. How do these “superficial” ceremonies hinder real progress, and what structural changes to roles—such as product or service ownership—are necessary to enable faster, decentralized decision-making?
Adopting rituals like stand-ups or retrospectives without changing the core operating model creates an “illusion of agility” that can be more dangerous than traditional waterfall methods because it masks deep-seated inefficiencies. These ceremonies become superficial theater when the power to make decisions remains centralized at the top, leaving delivery teams with accountability but no actual control. To enable true enterprise agility, roles like product and service ownership must be treated as core capabilities rather than administrative add-ons. We need a structural shift where these owners have the mandate to prioritize customer needs and make rapid-fire decisions without waiting for layers of senior approval. This decentralization reduces dependencies and allows the organization to respond to market shifts in real-time, rather than moving at the speed of the next board meeting.
Transformation frequently fails because the “people system,” including incentives and career progression, isn’t designed alongside the technology. How can organizations move beyond senior sponsorship to create an actionable mandate for employees, and what role does a lean project management office play in this alignment?
You cannot expect sustained behavior change if your “people system”—the roles, incentives, and career paths—is treated as an afterthought to the technology. Senior sponsorship is a great signal of intent, but it creates a bottleneck if it doesn’t translate into an actionable mandate that empowers every employee. One effective way to bridge this is through a lean project management office (PMO) that serves as a connective layer rather than a bureaucratic watchdog. In one central government organization, such a PMO brought together strategy, delivery, and HR functions into a single layer to ensure continuity. This setup ensures that the mandate isn’t just a memo from the top, but a set of practical tools and incentives that align an individual’s daily work with the organization’s strategic goals.
What is your forecast for digital transformation strategies?
I believe the era of the “grand strategy document” is coming to an end, and we will see a shift toward “adaptive architecture” where strategy and execution are permanently fused. In the coming years, the most successful organizations will be those that stop viewing transformation as a project with a start and end date, moving instead toward a model of continuous evolution. We will see a decline in centralized “command and control” leadership and a rise in organizations designed as interconnected networks of empowered product teams. My forecast is that the 12% success rate we see today will only improve when leaders stop trying to design the “perfect” strategy and start focusing on designing the organizational conditions—the culture, the incentives, and the data flows—that allow a strategy to survive, adapt, and thrive in an unpredictable world.