Transformation is an operating model decision

Data, Analytics & Transformation · Intlex Technologies · October 2026 · 2 minute read

Technology modernization programs often start with systems and treat people and processes as a later workstream. The programs that deliver their business case usually do the opposite: they treat transformation as an operating model decision from the first day.

Three elements, designed together

• Process: how work should flow once the new capabilities exist, including what stops being done.
• Architecture: the target landscape, how systems connect and where data is mastered.
• Organization: the roles, skills, ownership and decision rights the new way of working needs.

Designing these separately produces familiar failures: a new system configured around an old process, a process redesign the system cannot support, or a capability nobody has the skills or authority to run.

Decide what changes for people

For each major process, write down plainly what will be different for the people who do the work: which tasks disappear, which are new, which decisions move. That description becomes the basis for training, communication and the measures used to track adoption. If it cannot be written, the design is not finished.

Track value, not only milestones

Milestone reporting tells leadership whether the program is on schedule. It does not say whether the business is better off. Agree a small set of operational and financial measures at the start, establish the baseline, and report them alongside delivery progress. When value tracking starts at the beginning, it shapes priorities; when it starts at the end, it becomes an argument.

Govern decisions, not just progress

Program governance often concentrates on status: milestones, budget and risk logs. The more useful role of a steering committee is to make decisions quickly: resolving design disputes between functions, approving scope changes and stopping work that is no longer worth doing. Give the forum a short list of the decisions it owns, bring each one with a recommendation and its consequences, and record the outcome. A program that waits weeks for decisions loses more time than one that occasionally makes the wrong call and corrects it.

Plan for the organization after go-live

Transformation does not end at go-live. Someone has to own each new process, keep its data clean, maintain the reports and decide on future changes. Name those owners, and give them the time and skills to do the job, before the program team steps back. Many benefits are lost in the months after a launch simply because nobody was made responsible for keeping them.

Sequence for learning

Large programs benefit from early releases in a limited scope, a region, a business unit or a product line, that test process, system and organization together. Each release should teach the program something it applies to the next.

Related service: Transformation & Operating Model