Cloud First Is a Strategy—Not a Decision

One environment. Two definitions of progress.

The company had relied on a heavily customized Oracle E-Business Suite environment for approximately 15 years. Over time, that environment had accumulated functionality built around the organization's accounting and business practices.

IT wanted to preserve the existing Oracle EBS environment and its capabilities, carrying its approach to customization into a cloud model. From that perspective, continuity mattered: the system reflected years of work supporting the business.

Accounting and Finance wanted to modernize to a new cloud-based system. They saw an opportunity to change how work was performed, rather than continue operating within the constraints of the existing environment.

Those positions reflected different responsibilities and different definitions of success. IT was focused on preserving functionality and continuity. Finance was focused on a more effective future operating model.

A discussion about “moving to the cloud” could accommodate both positions without resolving the disagreement. One group could mean preserving the current business in a different technology model. The other could mean redesigning the business around modern capabilities.

Until those expectations were made explicit, agreement on a technology direction would have been incomplete.

Discovery before demonstration

My role was to lead the Oracle team in building a common fact base with the Chief Accounting Officer and her team, alongside enterprise applications leadership. We needed to understand the business well enough to evaluate Oracle Cloud Financials in the context of actual requirements, operating practices, and value.

That required structured discovery across the business, rather than allowing product demonstrations to define the conversation.

Over nine months, we interviewed each business area and documented its current use cases, the functionality it relied on, and why customizations had been built. We compiled that work into a master value assessment.

The purpose was more than producing an inventory. It was to connect what the system did to the business need behind it, then examine whether a modern approach could meet that need with less effort or complexity.

Discovery before demonstration. A demonstration can show what a platform can do. Discovery establishes what matters to the organization and gives leadership a basis for judging what it sees.

Protect the requirement, not necessarily the customization

A customization is evidence that someone once needed a problem solved. It is not, by itself, proof that the same solution should be carried into the next environment.

The requirement may still be essential. The original implementation may reflect an earlier limitation, an established preference, or a business practice that leadership is now willing to reconsider.

Documenting why customizations existed helped separate those questions. It gave Finance and IT a way to discuss the underlying need without treating every inherited system behavior as a permanent requirement.

The guiding principle was straightforward: Protect the requirement, not necessarily the customization.

That judgment requires both business and technology understanding. Leadership needs to distinguish what must be preserved, what can be simplified, and what deserves redesign. Neither a blanket commitment to continuity nor an automatic preference for a new platform answers those questions.

Make the value visible in the work

The master value assessment brought the discussion back to how the organization operated. It identified areas where a modern cloud system could reduce labor and effort, improve process efficiency, and move the broader organization toward more standard accounting and business practices.

Those opportunities also changed the economic comparison. The relevant question extended beyond the cost of a new system to the total project and ongoing operating costs of the alternatives, including the effort required to maintain the existing environment and its customizations.

The assessment identified a path to lower total project and operating costs compared with maintaining the existing environment. That value depended on the organization's willingness to simplify processes and reconsider inherited complexity.

These were opportunities identified through discovery, not a claim of savings already realized. Turning them into operating results would require business ownership, process change, adoption, and continued attention to value after implementation.

Modernization creates the most value when the organization is willing to modernize the business along with the technology.

A strategy still needs a business decision

The most useful contribution of the engagement was creating a shared basis for evaluation. Finance and IT could examine the same use cases, understand the reasons behind existing functionality, and consider future value in business terms.

That is where executive alignment becomes practical. It moves from a general desire to modernize toward agreement on the capabilities, operating changes, and economics that should guide the decision.

“Cloud first” can help frame the strategy. Leadership still has to decide what the organization needs to protect, what it is willing to change, and how the investment will create value.

BHz Perspective

The hardest enterprise modernization decisions sit at the intersection of strategy, finance, technology, and organizational reality. Progress depends on making the competing objectives visible and creating enough shared understanding to evaluate the tradeoffs.

Independent executive counsel helps leadership challenge inherited assumptions, connect technology choices to business outcomes, and make a better-informed commitment. That is the role BHz Advisory brings: clarity where business and technology meet.