Enterprise modernization · Part 3 of 4 · BHz Advisory Insight

Modernize the Process, Not Just the Platform

Use enterprise modernization to simplify how the business operates, with clear ownership, deliberate process design, and controls that serve today’s requirements.

← All Insights

By Brian Hertz · November 9, 2026

One of the easiest ways to waste a modernization investment is to move an old process onto new technology without questioning how the work gets done.

The system changes. The same approvals, handoffs, reports, and exceptions remain. Eventually, the new platform begins to look remarkably similar to the environment it replaced.

In Part 1, Cloud First Is a Strategy—Not a Decision, I explored why a technology direction does not resolve the business decision. In Part 2, Protect the Requirement, Not the Customization, the focus was separating a legitimate business need from the historical solution built to support it.

Part 3 takes that discipline into the operating model: once the requirement is understood, leadership has to decide how the work should happen in the future.

Continue reading Show less Read the full BHz Advisory Insight

A new platform does not automatically create a better process

A migration can be necessary and valuable. Replacing unsupported software, improving resilience, or reducing infrastructure risk may justify an investment on its own. But those benefits should not be confused with changing how the business operates.

If a transaction still passes through the same unnecessary reviews, if employees still reconcile the same information outside the system, and if decisions still wait for the same unclear authority, much of the original complexity survives.

That is migration. Process modernization requires another set of decisions.

A modern platform running a legacy process is still a legacy operating model.

The opportunity is to use the transition to examine the work itself: which activities create value, which protect the business, and which persist because no one has revisited them.

Protect the control objective. Reconsider the workflow.

In the Oracle engagement discussed in Parts 1 and 2, structured discovery helped make the business requirement visible beneath years of accumulated customization. The same distinction applies to the steps in a process.

An approval may exist to control financial exposure. A reconciliation may establish that information is complete and accurate. An exception may address a legitimate operational need. Those objectives deserve careful attention.

The historical workflow is one way of meeting them. It may no longer be the best way.

Consider an illustrative purchasing process. Every request goes through several sequential approvals, regardless of value or risk. A new system could reproduce that sequence exactly—and make it easier to track.

Or leadership could examine whether defined authority limits, appropriate segregation of duties, budget checks, and routing based on risk would meet the control objective with fewer routine handoffs. Higher-risk purchases could still receive the review they require.

That is a design question for the business, Finance, IT, and the relevant control owners to resolve together. Faster processing is useful only if the redesigned process still meets its obligations.

Ask why before deciding how

Current-state documentation is necessary. It shows how work happens today. The mistake is treating that documentation as an automatic specification for the future.

Before rebuilding a process in a new ERP environment, ask:

  • Why does this step exist? Identify the outcome, control, or decision it supports.
  • Does this approval still reduce meaningful risk? Understand what the reviewer actually decides and whether the authority is clear.
  • Can a handoff be eliminated? Look for duplicate entry, repeated validation, and work that moves between teams without adding information or judgment.
  • Is this exception still necessary? Separate current business needs from accommodations for an old system or organizational structure.
  • Can standard functionality meet the requirement? Evaluate the capability against the business need before designing a workaround.
  • If we were designing this process today, would we build it this way? Make inherited practices a subject for evaluation.

These questions should lead to explicit decisions: retain the step, simplify it, redesign it, or retire it. Record the rationale and the accountable business owner. Otherwise, an unresolved discussion can quietly become another configuration requirement.

Process redesign requires business leadership

Technology teams can explain platform capabilities, integration constraints, data requirements, and implementation tradeoffs. Implementation partners can translate agreed decisions into configuration.

Neither should be left to decide, by default, who may authorize a transaction, which organizational variations matter, or which activities the business is willing to stop performing.

Those choices affect decision rights, controls, responsibilities, and sometimes roles people have owned for years. They require business leadership.

A practical starting point is an accountable owner for the end-to-end process. That person needs enough authority to resolve competing departmental preferences, with Finance, IT, operations, and control owners involved where their responsibilities are affected.

Without that ownership, each function can preserve its own steps while the overall process remains slow, expensive, and difficult to manage.

Cross-functional alignment becomes concrete when leaders agree on what work will change, who will make the decisions, and what must be true before the new process is accepted.

Simplify deliberately, then prove the design works

Process modernization does not require redesigning everything at once. Start with a bounded process where the business problem is clear: repeated rework, long approval queues, manual reconciliations, or exceptions that consume disproportionate attention.

Establish a baseline before changing it. Depending on the process, useful measures might include elapsed time, manual touches, error and rework rates, exception volume, or the effort required to produce reliable information.

Then evaluate the proposed design against real operating scenarios, including exceptions. Validate the controls, data, integrations, responsibilities, and training the process depends on. Involve the people who perform the work; a diagram that looks efficient can conceal a difficult day-to-day experience.

Some variation will remain justified. A regulatory obligation, a material operating difference, or a genuine source of competitive value may require a distinct approach. Make that choice deliberately, with its cost and ownership visible.

The aim is a simpler process that the organization can operate, control, and sustain.

BHz Perspective

The first two parts of this series challenged premature platform decisions and automatic preservation of legacy customization. The next step is to challenge the assumption that the way work happens today is the way it should happen tomorrow.

That requires more than a technology plan. It requires leaders to make decisions about the business they intend to run.

Before asking, “How do we move this process to the new system?”, ask:

If we were designing this process today, would we build it this way at all?

That question connects platform capability to operating change. It also sets up the final discipline in the series: measuring whether the investment delivers the business value it promised.

Clarity before commitment

Align strategy, economics, and execution before the decision becomes expensive to reverse.

BHz Advisory provides confidential, independent, solution-agnostic executive counsel—without a software, vendor, or implementation agenda.

Independent perspective. Informed decisions. Shared success.

Contact BHz Advisory