Skip to Content

Change management is a workstream, not a checkbox.

It needs a named owner, a budget line, and a metric of its own.
October 25, 2026 by
Change management is a workstream, not a checkbox.
Al Jawad

Change management is a workstream when it has a named owner, a budget line, a plan with dates and a metric that someone is accountable for. When it is a checkbox, it is a training session in the last fortnight before go-live. The first approach changes how people work. The second explains a system they have already decided how to avoid.

What does the workstream own?

  • The people impact. For every role, what changes in the day, what stops, what starts, and who loses a decision or a report they had before.
  • The decisions that precede configuration. Who approves what, and which local habits give way to the standard process. These are organisational decisions and they are made by managers, not by consultants.
  • Communication. A plan from announcement to day 91, in the language people work in, from the people they trust.
  • Training by role. Short, scenario-based, on the real data, close to go-live and repeated after it.
  • Support at the desk. Named super-users in each department who answer the first question before it becomes a workaround.

Who should own it?

A senior business leader whose own targets depend on adoption, supported by a project role with time allocated, not borrowed. If the only owner is the IT manager, the workstream will measure what IT can see: log-ins and tickets.

What should it measure?

Log-ins are not adoption. Measure whether the process runs in the system: orders entered by the person who takes them, approvals completed in the tool, reports used in the meeting instead of a spreadsheet. Count the workarounds that are still alive at thirty, sixty and ninety days, and ask why each one exists. Some will show a real gap in the design, which is information the project needs.

When does the work end?

Not at go-live. Most implementation contracts end at hypercare, around day 90, yet the behaviours that decide the return form afterwards. Plan the ninety days after the project team leaves with the same seriousness as the ninety before go-live, and write the adoption metric into the engagement from the start.

ERP governance after go-live.
The decision log is the asset. Most programmes throw it away at handover.