The change represents an unavoidable facet of integrating any novel ERP System. Employ the following tactics to guarantee a seamless and triumphant ERP implementation, embraced fervently by your workforce.
Navigating Change in ERP Deployment
Implementing a new ERP System, whether it's an initial adoption or an upgrade, invariably brings about change. Particularly in the public sector, where change can be met with resistance, preparing the organization and its personnel is imperative. The journey of ERP change management should kick off with the crafting of coherent communication strategies and change management methodologies well in advance of the actual software integration.
In our extensive experience aiding public sector entities with software integrations and ERP change management initiatives, we often encounter similar hurdles as they execute their plans. The ensuing strategies can direct your organization in proactively managing change, thus ensuring a smooth and prosperous ERP implementation and ERP change management.
1. Communication: Timely, Regular, and Cohesive
Effective communication serves as the cornerstone of proficient change management. Establish dedicated support or steering committees to delineate roles for staff, decision-making processes, and leadership in driving change. Designate individuals to act as the spokespersons for these committees, disseminating information about changes throughout the organization. Typically, these roles are filled by influential figures like city or county directors, mayors, CFOs, CIOs, or department heads.
Maintain consistency in the messages conveyed by the steering committee, as inconsistency can breed uncertainty and erode trust. Disseminate crucial messages widely and utilize communication channels that resonate with and engage the broadest swath of your workforce, employing both rational and emotional appeals. Messages that are logical and emotionally resonant are often better received by individuals.
Transparently communicate the current state of the organization to ensure successful change. Articulate the business needs propelling the change, such as growth, technological advancements enabling necessary functionalities, or the imperative to better serve constituents. Focus on elucidating the 'why' rather than fixating on the future state at this juncture.
2. Addressing Employee Apprehensions
Once it's been communicated to employees that organizational change is inevitable, leaders must aid them in envisioning the future state. A collaborative project kickoff meeting involving all stakeholders, especially end-users, is crucial. Thoroughly prepare to support employees through the transition, clarify their roles and responsibilities, and address how the changes will affect them individually.
Employees will inevitably ponder how their work will differ in the future state and may harbor concerns regarding job security or role alterations. Planning for these discussions ensures consistency in messaging when individuals seek answers to the question, "What does this mean for me?"
Emphasize changes in job roles and skillsets rather than job reductions whenever possible. In instances of resistance, engage in one-on-one conversations to address concerns and assuage fears.
Consistency, clarity, and alignment in messaging from leaders are pivotal. While organizational leaders wield influence, immediate supervisors hold the trust of their subordinates. Misalignment among supervisors can detrimentally impact staff morale.
While supervisors shoulder much of the communication responsibility at this stage, communication from the steering or support committee, often dubbed the "voice from the top," should not cease. Hearing from senior management demonstrates ongoing commitment and support from the organization as a whole.
3. Knowledge Transfer
As part of your change management strategy, assess whether your organization possesses the requisite expertise internally for your desired objectives or if external expertise is necessary.
In ERP implementations, much of the knowledge is sourced from the software vendor, and organizations must establish mechanisms (such as shadowing) to transfer that knowledge to their staff. It falls upon your organization to determine the most effective training approach. Note that interactive and hands-on training tends to yield better results than lecture-based training.
People learn at different paces, presenting an opportunity to identify individuals who quickly grasp the new software and processes. Leverage these early adopters as mentors for others. Mentors can work with individuals in small groups or one-on-one settings, reinforcing the new protocols within your organization.
User groups and forums can also serve as valuable platforms for staff to discuss issues and troubleshoot problems with the new system or processes, but they should not supplant a clear and formalized training plan. Ensure staff know who to approach when they have questions.
4. Recognition and Assistance
Recognize the accomplishments of team members when they adeptly embrace the new processes. Acknowledge progress and achievements even before changes are fully implemented.
Understand that meaningful recognition varies by individual — some prefer private acknowledgment, while others value public recognition. Recognition can take myriad forms, such as project email updates, posters, snacks, social gatherings, or casual dress days.
Experiment with various methods to express appreciation, as everyone responds differently.
If errors occur during ERP implementation, minimize negative repercussions. Individuals may resist adopting the process or system if they feel criticized for inadvertent errors.
Institute a system where staff can support each other's learning and hold each other accountable rather than relying solely on management corrections. Train-the-trainer approaches that foster knowledgeable advocates among staff can be advantageous. Additionally, staff within the same functional area can informally assist each other, reinforcing new processes or transactions.
5. Continuous Enhancement
ERP change management efforts shouldn't conclude once the system goes live. Plan to conduct a review approximately one year after implementation to identify additional areas for improvement, including further training needs. Starting from the go-live phase, management should regularly solicit feedback from employees on how their teams are utilizing the new system, pinpointing opportunities for additional efficiencies.
The work of ERP change management is an ongoing endeavor. Continuously follow the aforementioned steps to ensure the success of your ERP implementation and to realize the objectives you've set.
Comments