Practical Change Management for It Projects

1. Change Management is crucial for IT project success

"Just because the change has been implemented, this doesn't mean the work is done."

Change Management definition. Change Management is a set of activities, processes, and tools designed to help people successfully adopt change. It focuses on the human side of organizational change, addressing the emotional and practical challenges faced by employees during transitions.

Importance for IT projects. Change Management is critical for IT project success because:

• It addresses the "soft" factors like employee attitudes and corporate culture
• It helps overcome resistance to change
• It ensures that new systems and processes are actually adopted and used effectively
• It minimizes performance dips during the transition period

Key components. The five pillars of Change Management are:

• Sponsorship
• Organization design
• Stakeholder management
• Communication
• Training

2. Establish a framework for change with emotional and intellectual appeal

"No matter how much data you show to people to demonstrate that the change is good for them, they often still decide that they prefer the status quo."

Dual approach to change. Effective Change Management addresses both the intellectual and emotional aspects of change. This dual approach helps overcome resistance and encourages adoption.

Frameworks for change:

• See-Feel-Change: Focus on visual demonstrations and emotional appeals
• Rider-Elephant-Path: Address the intellectual side (rider), emotional side (elephant), and environment (path)

Practical application:

• Use data and facts to appeal to stakeholders' intellectual side
• Create visual demonstrations to evoke emotional responses
• Remove obstacles and provide incentives to make adoption easier
• Coordinate with other teams (e.g., Corporate Communications, Corporate Training) to maximize impact

3. Build a strong sponsorship network across organizational levels

"Remember that although the rider might seem to be in charge and does in fact, hold the reins, the rider is very small and weak compared to the elephant they are trying to control."

Sponsorship network components:

• Steering committee: Sets project direction and provides resources
• Executive sponsors: Advocate for the project and provide visible support
• Change agents: Act as "corporate cheerleaders" across the organization
• Super users: Become near-experts and provide front-line support

Key activities for sponsors:

• Actively and visibly support the change
• Communicate the importance of the change
• Participate in project events and activities
• Hold people accountable for adopting the change

Supporting sponsors:

• Provide clear information about the change and its benefits
• Offer tools and resources to help them fulfill their roles
• Recognize and reward their efforts
• Maintain regular communication and feedback loops

4. Identify and manage stakeholders through the change curve

"Real life change is much messier."

Stakeholder analysis. Conduct a thorough stakeholder analysis to identify:

• Who is impacted by the change
• Their level of influence and impact
• Current and required levels of support

Change curve stages:

1. Unawareness
2. Awareness
3. Understanding
4. Exploration
5. Adoption

Managing stakeholders:

• Tailor communication and support to each stage of the change curve
• Address both positive and negative impacts of the change
• Include end users in project activities (e.g., user acceptance testing, system demonstrations)
• Prepare for and mitigate performance dips before and after implementation

5. Develop a comprehensive two-way communication plan

"Communicate early. Communicate often. When you think you've communicated enough, communicate some more."

Communication plan components:

• Audience analysis: Identify stakeholder groups and their communication needs
• Vehicle analysis: Determine the best methods for communicating with each group
• Key messages by project phase
• Feedback gathering methods

Effective communication strategies:

• Use both push (e.g., email) and pull (e.g., intranet portal) communication methods
• Break through the noise with creative, mobile-friendly, and incentivized communication
• Ensure two-way communication to gather feedback and address concerns
• Tailor messages to different stakeholder groups and project phases

Writing good communication:

• Keep it simple and avoid jargon
• Use bullet points and clear calls to action
• Start with the most important information
• Include "What's In It For Me" (WIIFM) to engage the audience

6. Create a blended learning approach for effective training

"Never assume."

Importance of training. Training is crucial for:

• Ensuring efficient and effective use of new systems from day one
• Reducing frustration and increasing confidence among users
• Maximizing the utilization of new system capabilities

Blended learning approach. Combine multiple training types to cater to different learning styles and needs:

• Instructor-led training
• e-Learning
• Knowledge transfer
• Coaching
• On-the-job training
• Self-service training

Training development and delivery:

• Identify training audiences beyond end users (e.g., project team, super users, executives)
• Gather input from various teams to determine training topics
• Plan for adequate development time (e.g., 200 hours per hour of e-Learning)
• Coordinate logistics for training materials, facilities, and delivery

7. Continuously gather feedback and improve the change process

"If you ask for feedback, you must be prepared to respond and act on it."

Feedback methods:

• Dedicated email address
• General surveys
• Event-specific surveys
• Focus groups
• Suggestion boxes
• Change agents and super users

Responding to feedback:

• Thank people for their input
• Communicate how feedback is being used
• Explain reasons for not implementing suggestions
• Remain positive and professional, even when receiving negative feedback

Continuous improvement:

• Incorporate feedback into future communication and training plans
• Regularly update the Change Management plan based on stakeholder input
• Monitor adoption rates and address ongoing challenges
• Celebrate successes and share positive outcomes to reinforce the change

By following these key takeaways, organizations can significantly improve their chances of successfully implementing IT projects and ensuring long-term adoption of new systems and processes. Remember that Change Management is an ongoing process that requires constant attention, adaptation, and support throughout the project lifecycle and beyond.