Upon successful completion of this program, participants will be able to:

• Apply structured change management frameworks (e.g., ADKAR, Kotter) specifically to technical initiatives.
• Identify and proactively address the unique sources of resistance within engineering and development teams.
• Design effective communication strategies for complex technical shifts (e.g., microservices migration).
• Foster a culture of psychological safety essential for continuous change and learning.
• Develop a comprehensive stakeholder analysis and sponsorship strategy for technical transformation.
• Measure the success and adoption rate of technical changes using quantifiable metrics.
• Coach technical team members and managers through the personal transitions of adopting new tools and skills.
• Structure a Change Management Office (CMO) that works in harmony with Agile and DevOps practices.

• Engineering Managers and Directors
• Technical Program and Project Managers
• Product Managers leading platform changes
• IT and Infrastructure Leaders
• Scrum Masters and Agile Coaches
• Enterprise and Solution Architects
• Change Management Specialists focused on IT

• **Scenarios:** Role-playing a difficult conversation with a senior engineer resistant to adopting a new programming language or platform.
• **Case Studies:** Analyzing large-scale technical change failures (e.g., major system replacements) and identifying change management gaps.
• **Group Activities:** Developing a comprehensive communication plan for a shift from an on-premise data center to a multi-cloud environment.
• **Individual Exercises:** Drafting a Change Impact Assessment for a team moving from waterfall development to Agile sprints.
• **Mini-Case Studies:** Evaluating different reward mechanisms to incentivize technical training and new skill adoption.
• **Syndicate Discussions:** Debating how to balance the need for speed (DevOps) with the need for stability (Change Management).
• **Simulation:** Participants lead a simulated technical kick-off meeting for a major platform change.

Unit 1: The Unique Challenge of Technical Change

• Why technical professionals resist change (loss of autonomy, expertise).
• Distinguishing between tactical and strategic technical changes.
• Integrating change management into Agile and DevOps sprints.
• The importance of "The Why" for intellectually curious engineers.
• Identifying key transition stages and the emotional curve of change.
• The impact of continuous change on team bandwidth and burnout.

Unit 2: Change Frameworks and Stakeholder Strategy

• Applying the ADKAR model to individual developer transitions.
• Conducting a thorough technical stakeholder analysis and impact assessment.
• Building an effective sponsorship roadmap for the Chief Technology Officer (CTO).
• Developing a compelling case for change that addresses technical debt.
• Creating a network of technical change agents and champions.
• Measuring sponsor engagement and accountability.

Unit 3: Communication and Technical Buy-in

• Designing communications tailored to different technical audiences (e.g., executives vs. developers).
• Techniques for effective technical roadshows and town halls.
• The role of hackathons and internal challenges in driving hands-on adoption.
• Communicating technical failures and pivoting strategies transparently.
• Establishing two-way feedback channels for technical concerns and suggestions.
• Using visual mapping (e.g., value stream mapping) to communicate process change.

Unit 4: Sustaining Momentum and Adoption

• Designing effective, bite-sized training and upskilling programs (e.g., internal dojos).
• Coaching managers and tech leads on supporting team members through transitions.
• Building performance support tools (PSAs) for new technologies.
• Strategies for recognizing and rewarding successful early adopters.
• Integrating change metrics into MBOs and performance reviews.
• Developing a technical transition sustainment plan post-go-live.

Unit 5: Change in Architectural and Platform Migration

• Managing the change associated with shifting from monolithic to microservices architecture.
• Change management for cloud migration and infrastructure as code (IaC) adoption.
• Addressing the people-side of adopting new data governance models.
• Leading the team through security culture shifts and DevSecOps integration.
• Managing vendor-related change and third-party tool adoption.
• Communicating the risks and dependencies of complex technical programs.