OCM Change Strategy & Execution
Change strategy, governance and roadmap, from planning through delivery.
Go live is not success. Success is when the organisation actually adopts the new way of working.
When a company implements Salesforce CRM, Microsoft Dynamics 365, ERP or another core system, the real challenge is rarely only technical. It is the change to process, the adjustment of roles, the shift in how people work and how the business is managed. A large system implementation is, at heart, a change to the operating model. Once processes are redesigned, accountability is reallocated and information becomes more transparent, the way employees work, the way managers manage and the way departments cooperate are all affected. So a system project has to answer more than whether the software runs. Is the organisation ready? Which roles are affected? Do people understand why this is happening? Do managers know how to lead their teams through it? After go live, will users genuinely use the new process and the new system? Through organisational change management, we work across organisation, people, process and management mechanisms in parallel, lowering resistance, lifting adoption, and turning the new system into real operating capability.
Everything works. Nobody uses it.
Old and new run in parallel, which adds work rather than removing it.
The process breaks at the hand off, and nobody considers it theirs to fix.
Reports need manual patching, and decisions go back to being made verbally in meetings.
Long after the project closes, the manual chasing and clean up continue.
Confirm transformation goals, scope, key stakeholders and the change governance model, and build a change roadmap that runs in step with the system project.
Analyse how each department, role and management level is affected across workflow, responsibility and authority, system interaction, access to information, cross functional working and decision making, then tailor the change approach to the level of impact.
Map as is and to be processes and settle who owns what after go live, what work disappears, what gets reassigned, what data must live in the system and how departments hand over, reducing the resistance that comes from unclear roles and broken hand offs.
Design layered communication for each stakeholder group, covering leadership messaging, the change story, milestone updates, key user and change champion networks, handling of concerns, and workshops that involve employees, so people understand why this is happening, what is changing and what it means for them.
Build role based, key user and end user training around real work situations, with SOPs, quick guides, workshops and a readiness assessment, so users have the knowledge and the skill before go live.
Go live is not the end of change management. Adoption tracking, user feedback, adoption KPIs, issue and resistance tracking, manager reinforcement and continued education confirm that the new way of working has genuinely become part of daily operations.
Scope is designed around company size, system complexity, user population and how much the organisation has to change.
The work was never only about implementing software. It was about making a global system into a management tool the local business could actually run on. Change management connected global strategy, business process, roles and responsibilities, system and data, communication and training, and user adoption into one framework, carrying the transformation past go live and into genuine business adoption.
The group was standardising its core systems worldwide and rolling Microsoft Dynamics 365 out across its Asia Pacific operations. The Taiwan site spans sales, sales operations, finance, customer service, production and supply chain. Beyond adopting the global template it had to accommodate local commercial practice, tax and regulatory requirements, customer transaction models and manufacturing needs. Four challenges dominated. The global template did not match how Taiwan actually operated. Cross departmental processes were tightly coupled, so a change to one role could affect several teams at once. A great deal of existing work ran on manual effort and spreadsheets. Roles and responsibilities needed realigning.
We joined at the front of the project and ran change management alongside the implementation. We established the change roadmap and governance, analysed the impact on each department and role, mapped as is and to be processes to settle accountability and hand offs, designed layered communication and a key user network, planned role based training and a readiness assessment, and after go live tracked adoption, user feedback and adoption KPIs with continued reinforcement from managers.
Multiple vendors were coordinated within a limited schedule and budget to create an efficient, flexible and comfortable mobile working environment. Open collaboration areas and well-planned storage improved cross-department communication, space utilization and the everyday workplace experience.
A multinational beauty group with 25 brands and more than 2,600 employees needed to relocate its headquarters to another district. Over half of the workforce had more than 15 years of service and their digital skills needed strengthening. An aging office and a traditional brand image also made it harder to attract and retain younger talent.
Led the planning of the seven floors of the group headquarters, bringing 60 years of brand identity into the workplace so that both the market and employees identified more strongly with the brand. Planned digital transformation across the whole site and built a new office environment combining space and technology, while running change management and training for the organization and its people, reshaping the employer brand and improving employee wellbeing.
Change strategy, governance and roadmap, from planning through delivery.
Role and process mapping that makes the real difference between as is and to be explicit.
Pre implementation diagnosis and stakeholder analysis, identifying where resistance will come from and how ready the organisation is.
Layered communication, the change story and the mechanisms that bring employees in.
Adoption management and role based training for CRM and D365.
It depends less on the size of the system than on the size of the change. If the implementation also changes process, roles, accountability, ways of working or the management system, change management belongs in scope. The larger the change, the greater the risk of handling only the technology.
An IT team and a system integrator make sure the technology, the functionality and the deployment land. Change management handles organisation, process, people, communication and adoption. The roles are different, and on a large transformation both usually need to run at once.
No. Training is one part of it. Complete change management also covers change strategy, stakeholder management, change impact assessment, communication, leadership involvement, organisational readiness, user adoption and reinforcement after go live.
Resistance is rarely simple unwillingness. It usually comes from not understanding why, from a role being affected, from more work, from too little information, or from low confidence in a new skill. We identify the source first, then respond through communication, manager involvement, process adjustment or training as appropriate.
Yes. An adoption assessment looks at actual usage, process design, user behaviour, what management asks for and data quality, and an improvement plan follows. Very often the gap is not missing functionality but a management mechanism that was never put in place.
Yes. We work alongside your IT team, system integrator or software vendor and focus on change management, process, organisational communication, training and adoption.
Fees reflect programme size, system scope, user population, departments involved, implementation timeline and the change management workload. After an initial discussion we propose scope and pricing against the actual complexity of the change.
Go live is a milestone. The result comes from adoption. People need to know why the change is happening and how to work the new way, so the process and the system become part of how the business runs.
Book a system adoption and change management diagnosis