Before announcing a change, map how the work will differ for each role. A polished all-staff email is not a change plan. Before you announce a new system, process or policy, ask a more practical question: who will have to work differently on Monday morning? A project can be approved, a system can be nearly ready and a training session can be booked, while the people doing the work still do not know what will change for them. The problem is not always that communication arrived too late. Often, the project moved to communication and training before it understood the operational impact. A simple change-impact map makes that impact visible. It compares today’s way of working with the future way of working for each affected role or group, then connects the difference to a practical support action. Why this matters A change can look small in a project plan but feel large to the person doing the work. Replacing a shared mailbox with an online form may sound like a technology chang...
Raf Sanga’s notes on project management, technology-enabled change, Lean Six Sigma, process improvement, analytics, and building practical systems that help teams deliver measurable results.