Thought Leadership

Every new business requirement presents CIOs with an important decision: build another standalone solution or invest in a shared platform that makes the next solution easier to deliver.
The difference can have an enormous impact on return on investment, adaptability, and long-term operating costs.
When organizations develop solutions independently, they often duplicate the same investments in security, integrations, workflows, and infrastructure. Each solution may satisfy an immediate business need, but every new application can introduce more complexity, more maintenance, and more operational risk.
Platform Thinking takes a different approach. Rather than treating every business requirement as an isolated development project, organizations build on a shared foundation of reusable capabilities.
New solutions become easier to deliver. Existing solutions become easier to adapt. And IT leadership gains greater transparency into how applications, data, processes, and people work together.
The objective isn't simply to build solutions faster. It's to make every investment in technology more valuable than the one before it.
This isn't just a theory promoted by software companies. CIOs in transportation, manufacturing, financial services, and healthcare are already demonstrating why Platform Thinking matters.
In an April 2026 CIO interview with Rahul Jalali, CIO of Union Pacific, he describes a philosophy shaped by his experience at Walmart and now applied to one of North America's largest railroads.
“The most successful companies think like platform companies.”
His argument is straightforward. Rather than developing disconnected capabilities, organizations should invest in platforms that support multiple products, services, and business processes.
At Union Pacific, that approach has helped establish foundations for improved operational efficiency, customer transparency, and data-driven decisions.
Consider what this means for a railroad.
Customer service, freight operations, equipment maintenance, scheduling, and supply chain management are deeply interconnected. A change in one area can quickly affect another.
Building independent solutions for each function may address individual problems, but it can also make it harder to understand how those problems are related.
Shared platforms create opportunities to connect those processes, reuse operational capabilities, and give employees and customers better visibility into what is happening. They also make it easier to respond when the business changes.
For CIOs, this is an important distinction.
Adaptability isn't just about how quickly a new solution can be built. It's about how easily the organization can change the solutions it already depends on.
In manufacturing, Platform Thinking has a very practical financial benefit: stop paying to solve problems you've already solved.
Raman Mehta, then CIO of automotive supplier Visteon, described this approach in a CIO interview about the company's transformation.
Visteon was moving toward increasingly software-driven automotive products. Rather than rebuilding common features for every new product, the company invested in reusable, well-tested capabilities that engineering teams could assemble into new solutions.
As Mehta explained:
“They no longer need to put significant engineering energy into already-proven features”
Think about how this applies to enterprise application development.
Every business application needs some combination of authentication, data access, security, user interfaces, reporting, and workflow.
Why should an organization repeatedly invest in these capabilities every time a department needs a new solution?
A shared platform allows development teams to concentrate on the business problem rather than rebuilding the infrastructure around it.
The financial benefits extend well beyond initial development. Shared capabilities can also reduce duplicated maintenance, simplify upgrades, and provide a more consistent security model.
Over time, the cost of delivering additional applications can decline because each new solution builds on previous investments.
That's how Platform Thinking turns individual technology projects into investments that compound in value.
In a June 2025 MIT Center for Information Systems Research study, researchers examined how ANZ Institutional, a division of one of Australia's largest banks, transformed its business by investing in reusable enterprise platforms.
The results offer an interesting example of what Platform Thinking can accomplish.
ANZ Institutional had historically operated with disconnected processes across business units and geographies. Different parts of the organization maintained their own systems and processes, making it harder to provide consistent services to customers.
Working with CIO Peter Barrass, ANZ developed shared capabilities that could be reused across the organization.
One particularly interesting example involved lending.
By connecting customer onboarding, identity verification, credit, and lending systems through a shared digital backbone, ANZ moved toward real-time lending processes. Information collected during onboarding could be reused across other systems rather than entered repeatedly.
The result was a 70% reduction in manual data entry, along with lower processing costs and reduced operational risk.
The broader business transformation delivered substantial financial results.
Between 2016 and 2024, ANZ Institutional doubled its return on equity from 7% to 14%. Revenue from its payments platform offerings also grew from AUD$187 million in 2021 to AUD$468 million in 2024.
Those results reflect a multiyear transformation involving business strategy, organizational change, and technology. They shouldn't be attributed exclusively to the platform investment.
But the underlying lesson is clear.
ANZ didn't simply automate existing processes. It built reusable business capabilities that could support multiple services, connect previously fragmented operations, and create new revenue opportunities.
For CIOs, this represents an important shift in how technology investments are evaluated.
The value of a platform isn't limited to the first solution built on it. It grows as additional business processes reuse the same capabilities.
New solutions become easier to develop. Existing solutions become easier to adapt. And the organization gains better visibility into processes that previously operated in silos.
That's how Platform Thinking turns technology investments into a foundation for long-term business improvement.
If ANZ demonstrates the financial benefits of shared platforms, U.S. Bank illustrates why the same approach is becoming essential for enterprise AI.
In an October 2026 Metis Strategy interview, Dilip Venkatachari, Chief Information and Technology Officer at U.S. Bank, discussed the challenge of moving AI beyond isolated experiments.
His observation gets to the heart of the problem:
“The hard part here isn't proving that AI works. The hard part is industrializing it.”
Many organizations have already demonstrated that AI can solve individual problems. The challenge is deploying those capabilities across the enterprise without creating another generation of disconnected technology.
At U.S. Bank, the strategy involves common technology foundations, reusable components, and shared governance.
The bank has also developed an internal AI marketplace where teams can discover capabilities created by other teams and reuse them rather than starting from scratch.
Importantly, reuse is encouraged rather than blindly mandated. Teams maintain flexibility while benefiting from investments made elsewhere in the organization.
This is Platform Thinking applied to AI. Consider the alternative.
One business unit develops an AI agent to analyze customer information. Another builds an agent to support compliance. A third develops an assistant for operational exceptions.
Each project may succeed individually. But if every team independently builds its own data integrations, security controls, deployment infrastructure, and workflows, the organization quickly accumulates an expensive collection of AI solutions.
Now multiply that problem by hundreds of AI-assisted development projects.
The technical cost of creating applications may decline dramatically, while the cost of operating and governing them continues to grow.
U.S. Bank's approach illustrates a better path: provide shared infrastructure and governance while allowing business teams to innovate.
The opportunity isn't simply to scale the number of AI applications. It's to scale business value without scaling complexity at the same rate.
Perhaps one of the strongest arguments for Platform Thinking comes from healthcare.
In an April 2026 Becker's Hospital Review article, CIOs from several major health systems discussed the growing importance of enterprise platforms.
Lisa Stump, chief digital information officer at Mount Sinai Health System, identified a problem that should sound familiar to almost every CIO:
“Without a platform, health systems are forced to repeat an intake process”
That process includes security reviews, contract negotiations, and integrations for every new standalone solution.
Think about the cost of that repeated work.
Each new application requires evaluation. Someone needs to determine how it will connect to existing systems, how data will be protected, who will have access, and who will maintain it.
Even when the application itself is inexpensive, the organizational cost of putting it into production can be substantial.
Now imagine what happens when AI makes it possible to develop new applications in hours instead of weeks or months.
A department that previously requested one application might soon have the ability to create ten.
An individual employee might build an application without involving the IT department at all.
Each application could introduce new integrations, new data access requirements, new dependencies, and new security concerns.
The cost of generating the application may be approaching zero, but the cost of evaluating, securing, integrating, and maintaining it certainly isn't.
AI could dramatically increase the number of applications entering the enterprise while leaving CIOs responsible for the operational risk of every one of them.
Without a platform strategy, organizations risk creating an enormous backlog of security reviews, integration projects, and maintenance obligations.
The problem Mount Sinai describes could become far more difficult to manage.
This is where Platform Thinking provides an important advantage.
Instead of treating each AI-generated application as an entirely new technology investment, organizations can establish shared foundations for application development, data access, security, workflow, and governance.
Applications still require appropriate review and testing, but teams can reuse approved capabilities rather than repeatedly starting from scratch.
Importantly, the healthcare CIOs weren't arguing that every organization should abandon specialized applications.
Terri Couts, chief information and digital officer at Sharp HealthCare, described the right balance as treating the enterprise platform as “a foundation, not a ceiling.”
The lesson is that new solutions should be compatible with a broader enterprise architecture.
A platform should enable innovation, not restrict it.
There is another benefit of Platform Thinking that becomes increasingly important as organizations adopt AI: transparency.
Consider a supplier disruption.
An AI agent identifies a potential delivery problem and recommends switching to an alternative supplier.
Procurement needs to investigate. Operations needs to assess the production impact. Finance needs to understand the cost. Quality needs to approve the alternative.
If these activities occur across disconnected applications, it can be difficult to establish what happened, who made each decision, or whether the issue was actually resolved.
Now imagine those activities being coordinated through applications built on a shared platform.
Each participant has an appropriate view of the problem. Business rules determine which actions are permitted. Approvals are routed to the right people. Authorized AI agents can assist with defined tasks.
The organization can maintain a record of decisions, actions, and outcomes throughout the process.
For a CIO, this means more than better reporting.
It creates the foundation for understanding how solutions operate, identifying process failures, enforcing accountability, and evaluating whether technology investments are delivering their intended results.
Transparency becomes an architectural capability, not something reconstructed after a problem occurs.
This philosophy is central to Process Tempo Jupiter.
Jupiter provides a shared environment for developing governed enterprise applications, bringing together data connectivity, dashboards, forms, workflows, and AI capabilities.
Rather than developing every solution as an independent technology project, organizations can build on common application services and reusable components.
Business teams can address their own requirements while IT maintains the controls needed to support applications across departments and roles.
Jupiter also works with existing enterprise data platforms and applications. Organizations can introduce new solutions and workflows without necessarily replacing the systems they already depend on.
With Jupiter's AI and MCP capabilities, AI-assisted development can accelerate the creation of applications within a shared enterprise framework.
The opportunity isn't merely to build applications faster.
It's to develop solutions that are easier to manage, adapt, secure, and extend as business requirements evolve.
And importantly, it gives organizations a practical way to bring AI into existing business operations without creating an entirely new collection of disconnected applications.
Before approving the next application development project, consider three questions.
ROI: Will this investment create capabilities that can be reused, or will the organization pay to build and maintain them again?
Adaptability: When the business changes, how easily can this solution change with it? Will changes require coordinating multiple independent applications?
Transparency: Can we understand how the solution operates, what data it accesses, who is responsible for decisions, and what actions are being taken?
These questions become especially important as AI accelerates the pace of application development.
The organizations that benefit most from AI won't necessarily be those that produce the largest number of applications.
They will be the organizations that can turn those applications into coordinated, governed business solutions while controlling the cost and complexity of their technology portfolios.
Platform Thinking changes the economics of enterprise application development.
It transforms technology investments from a collection of isolated projects into a foundation for continuous business improvement.
And for CIOs, that may be one of the most important opportunities of the AI era.
Build on a shared foundation. Discover how Process Tempo Jupiter helps organizations build governed enterprise applications that connect data, people, processes, and AI.
See how Jupiter connects your data, applications, AI, and people in one governed platform.