WORLD WIDE PLUS JOURNAL
Business change2 min read

Make business change work for the people doing the work

A practical approach to business change: understand today's workflow, involve the right people, introduce change in useful steps, and learn after launch.

A new system can be live while the old workarounds continue. That gap usually says less about people's willingness to change than about how the change was planned. Better outcomes begin with understanding the work, involving the people affected, and making the new way genuinely easier to use.

Find the friction in today's process

Follow a real piece of work from start to finish. Note where information is re-entered, approvals stall, and people rely on informal messages to keep things moving. Those details reveal what a change needs to improve.

Ask people in different roles what happens on an ordinary day and when something unusual occurs. Their answers may be different, and both matter.

Define a result people can recognize

A broad goal such as becoming more digital is hard to act on. Describe a specific improvement: fewer handoffs, clearer ownership, quicker access to reliable information, or a simpler customer task. Agree on how the team will recognize progress without reducing every experience to a single number.

Build the transition into the plan

Include time for training, support, and updating the surrounding process. If a new tool changes who makes a decision or where information lives, write that down. People need to understand the new responsibility as well as the new screen.

  • Choose a clear owner for the change.
  • Explain what is changing and why.
  • Give people a place to report confusion or problems.
  • Make the fallback process clear during rollout.

Start where learning is possible

Introduce the change to a manageable group or workflow first when practical. Watch whether the intended task is easier, where users hesitate, and which assumptions need revision. A small release should create useful evidence, not merely a smaller launch announcement.

Keep improving after launch

Review feedback with the people doing the work. Fix the friction that prevents adoption, update guidance, and check whether the original problem is actually improving. Change sticks when the operating process and the technology evolve together.