When a large enterprise invited me to assess its enterprise systems landscape, the question seemed straightforward.

Oracle was showing its age. The company had recently acquired a new royalty management platform called Alliant, and leadership was trying to determine how everything fit together. Should they modernize Oracle? When should they implement a niche the niche rights and royalty software called Alliant? Should they tackle Human Resources at the same time?

Like many organizations facing significant change, they weren't looking for someone to validate a predetermined answer. They were looking for clarity.

My role wasn't to recommend software.

It was to understand the enterprise well enough to recommend what should happen first.

Before writing a single recommendation, I interviewed leaders across Finance, Human Resources, Business Technologies, Strategy, and Executive Management. I wasn't looking for technical requirements as much as I was looking for patterns—how the organization worked, where information flowed, and where it didn't.

Looking back, I don't remember a dramatic turning point.

I remember something much quieter.

Each conversation added another piece of the picture. Finance described one set of challenges. Human Resources described another. Business Technologies described a third. None of them contradicted one another. They simply reflected different parts of the same organization.

By the end of the interviews, the question itself had changed.

The issue wasn't Oracle.

Oracle had become the visible problem because it sat at the center of so many conversations, but it wasn't creating the organization's greatest friction.

The real challenge was fragmented information.

Critical data lived in multiple systems. Reporting relied on workarounds. Departments had developed effective ways of operating within their own worlds, but there was no cohesive approach to managing information across the enterprise. The report ultimately concluded that strengthening master data management and establishing a broader enterprise roadmap would create more long-term value than simply replacing software.

That realization changed the recommendation.

The discussion was no longer about whether Oracle should be replaced.

It became a question of sequence.

The newly acquired Alliant platform represented a foundational capability for the business. Trying to redesign the financial system, modernize Human Resources, and implement a new royalty platform simultaneously would have introduced unnecessary complexity at exactly the moment the organization needed focus.

The recommendation was intentionally measured.

Implement Alliant.

Allow Oracle to remain stable.

Strengthen the organization's information foundation.

Then decide what comes next.

The report wasn't recommending technology.

It was recommending sequence.

That recommendation proved remarkably durable.

Alliant became the immediate priority. Oracle remained in place. Years later, when the organization ultimately migrated from Oracle Financials to NetSuite, separating the royalty platform years earlier made that transition significantly more manageable. The sequencing had held.

Looking back, that's what stays with me.

Not the software.

Not the report itself.

The realization that even well-run organizations can lose perspective simply because they've been living inside the same systems for so long.

Sometimes leadership doesn't need more options.

It needs someone willing to step back, observe objectively, connect what different parts of the organization are experiencing, and help answer a simpler question:

What is the right next step?

That engagement became the beginning of a trusted advisory relationship that continued through multiple enterprise initiatives over the next decade.