Technology is often the most visible part of transformation. It is rarely however the only reason one succeeds or fails. More often, success depends on who is ready to make the hard calls, how priorities are set, and how quickly the organization is willing to move forward.
When a transformation struggles, technology usually gets the blame first. The ERP wasn't flexible enough. The data platform didn't deliver the promised insights. The rollout took twice as long as planned.
Sometimes that's a fair diagnosis, and a poor technology-fit adds cost, delay and complexity that shouldn't be there. But look closer at most struggling transformations. The real problem usually started earlier: a decision that got postponed, a priority that wasn’t ranked, an owner that was not actually named. By the time these issues become visible, they may look like technology problems even when the real cause is somewhere else.
Organizations today have access to more capable technology than at any point before. Modern ERP solutions, data platforms, automation tools, cloud services and AI can support major changes in how a business operates.
The harder part is deciding what the organization wants to achieve and which trade-offs it's prepared to make. A transformation usually starts with a clear vision and a solid business case. Then reality shows up as a long list of decisions that never made it into that business case:
Technology can support these choices but requires business decisions.
Every function has needs, every stakeholder sees opportunities, and every major transformation creates expectations.
The challenge is that not everything can be improved at the same time. When priorities are unclear, transformation turns into a collection of competing requests. Individually, each requirement, exception or new feature may seem reasonable. Together, they can dilute the original purpose and slow progress.
Successful transformations are the ones where someone is willing to say no. Not every requirement should have an equal weight, and not every opportunity needs to be pursued immediately. A smaller number of well-understood outcomes is often a stronger basis for progress than a long list of loosely connected ambitions.
Every transformation program has steering groups, workstream leads and RACI charts, but none of them create ownership by themselves. Ownership shows up in exactly one moment: when a hard decision must be made, and someone makes it instead of escalating it again.
When it's unclear who resolves a disagreement between business functions or who protects the business case when a deadline gets tight, decisions don't get made. Instead, they get passed around. The delivery team keeps working, but just without a fixed direction to work toward.
Many people can contribute to decision making, but accountability should still be clear. A transformation needs fewer people in the discussion and clearer accountability for decisions.
Business, operations, finance and technology will not agree on everything, and that is completely normal. The aim is not to remove every disagreement before moving forward. It is to make sure the right people have enough information to decide, and that the same debate is not reopened every few weeks.
Progress does not require everyone to agree. It requires a clear way to decide and move forward. The strongest organizations can discuss trade-offs openly, decide at the right level and avoid reopening the same question without a good reason.
Technology often reflects decisions made earlier. Unclear processes become visible when a system forces them into the open. Shifting priorities slow down even a strong delivery team, and unclear ownership does not resolve itself just because there is a new platform.
When business outcomes, priorities and decision rights are clear, requirements can be assessed against their value, trade-offs can be made consistently, and delivery teams can move forward with confidence. Technology then supports transformation instead of becoming the place where unresolved business questions are pushed.
The point is not to blame the business instead of technology. The point is to understand which problem the organization is really solving.
Before treating a transformation issue as a system or delivery problem, it is worth asking a few simple questions:
These questions do not remove the need for strong technology and delivery expertise. They help ensure that technical work is based on deliberate business decisions.
Technology is a real part of every transformation, but it works best when decisions, ownership and priorities are clear.
This is often where an outside perspective helps. At Maya, we work with organizations to make business goals, operating model choices and technology decisions clearer before and during transformation, so the work stays connected to real business impact.
Considering an ERP renewal or another major transformation? We help make the key business decisions visible before technology choices are locked in, so the work stays practical, independent and focused on business impact.