Oracle Cloud is evolving at an incredible pace. Every quarter brings new capabilities, while monthly security patches add another layer of change for enterprise teams to manage. Add the growing number of AI-powered features and agents, and the opportunity for businesses is significant.
But there is a question every Oracle customer should be asking: Are we keeping pace with what Oracle delivers, or are we simply keeping our existing systems running?
As a Gold Sponsor at Oracle AI World 2026, the Opkey team spent time with Oracle customers, partners, and technology leaders exploring how organizations can get more value from their Oracle investments. One theme stood out: the challenge is no longer just managing change. It is making sure organizations have the capacity, ownership, and operating model to turn that change into business value.
Here are the key takeaways that shaped my perspective.
The real challenge is not innovation. It is adoption.
Oracle continues to introduce new functionality across its cloud applications. Yet many organizations struggle to evaluate and enable the capabilities relevant to their business.
The reason is understandable. IT and functional teams are already occupied with regression testing, integrations, reporting, security, and business continuity. When a new release arrives, protecting existing operations takes priority. Evaluating new features often gets pushed aside.
Over time, this creates what I call the Oracle adoption gap: the difference between the capabilities Oracle delivers and the value an organization actually adopts.
The bigger issue is that deferred adoption does not always mean avoided change. Some opt-in features have expiration windows and can become enabled automatically in a later update. Without an owner, a testing plan, and user preparation, a decision to wait today can become an unplanned change tomorrow.
Release readiness needs to become a continuous business discipline.
The traditional approach to Oracle updates was largely focused on getting through the release cycle without disrupting operations. That is no longer enough.
With quarterly feature updates and monthly Critical Security Patch Updates, organizations have less room between changes. The same teams responsible for keeping systems stable are also expected to evaluate new functionality, understand its impact, and prepare the business to use it.
In our Oracle AI World session, we discussed how this pressure creates a recurring cycle: continuity work consumes the available capacity, adoption gets deferred, and the backlog grows with every release.
The answer is to move from reactive release management to a repeatable operating model. We outlined five decisions that teams should make during every release cycle:
- Regression test: Validate critical business processes and integrations to protect continuity.
- Assess and prioritize: Understand what changed, identify business impact, and build a prioritized backlog.
- Enable: Configure relevant new features in a lower environment.
- Validate and adopt: Test impacted processes and prepare users with updated training materials.
- Measure: Track how much of the available functionality the business has actually adopted and where value remains untapped.
The important shift is moving beyond the first three steps. Testing and stability are essential, but they should create the capacity for teams to evaluate, enable, and benefit from new functionality.
AI agents should absorb repetitive work, not replace human judgment.
AI agents can play an important role in helping lean teams keep pace with continuous change. But the opportunity is not simply to automate more tasks. It is to give people more time to focus on decisions that require business context and judgment.
Consider the work involved in a typical Oracle release: understanding changes, preparing configuration updates, building and executing regression tests, investigating failures, and updating training materials.
Much of this work is repetitive and high-volume. AI agents can help accelerate these activities. But decisions about which features make business sense, whether a risk is acceptable, and when a change is ready for production should remain with accountable people.
The operating principle is straightforward: Let agents carry the volume. Keep people on the decisions.
That means clear human approval points for configuration, test results, business sign-off, and user-facing training. Automation should strengthen governance and give teams better evidence for decisions, not remove accountability.
Automation Creates Capacity for Business Value
One example we shared at Oracle AI World was the transformation at TFG (The Foschini Group), an Oracle HCM customer.
Before automation, TFG’s quarterly regression testing involved 277 scripts, 11 people, and 825 hours of testing effort per cycle across 12 HCM modules. The team wanted to maintain full test coverage while reducing the manual workload and building the internal capability to manage automation independently.
Together, Opkey and TFG built approximately 300 automated scenarios within 12 weeks. In the first live patch cycle, TFG reduced testing effort by 73%, bringing the workload down from 825 to 225 hours per cycle. Testing required involvement from three people instead of 11, freeing team members to focus on other priorities. That translates to approximately 2,400 hours reclaimed annually.
What matters most to me is where those hours went. The team could spend more time learning new Oracle functionality, responding to business requests, improving its test strategy, and working on broader system improvements. TFG also built the capability to manage its automation independently, without ongoing external dependency.
This is the real business value of automation. It does not simply help teams complete the same work faster. It gives them the capacity to do work that was previously pushed aside.
Closing the gap between Oracle innovation and business value
Oracle’s pace of innovation will continue to accelerate. Organizations cannot control when new updates arrive, but they can control how prepared they are to respond.
The next phase of Oracle Cloud maturity will require more than a reliable release process. It will require clear ownership of adoption decisions, continuous validation, measurable outcomes, and a smarter use of automation and AI.
At Opkey, we believe organizations need a connected approach to managing the Oracle Cloud lifecycle, from understanding changes and configuring new capabilities to testing business processes and keeping users prepared.
Ultimately, the organizations that get the most from Oracle Cloud will not necessarily be the ones that enable every new feature first. They will be the ones that know what matters to their business, make deliberate adoption decisions, and have the capacity to turn innovation into measurable results.
