Organizational Change Manager - MAM/MDM Implementation

Role Overview


The Organizational Change Manager (OCM) will lead the change management strategy and execution for the MAM/MDM implementation project. This role is critical to ensuring a smooth transition for end users and stakeholders as new mobile policies and device management protocols are rolled out. The OCM will work closely with project managers, cybersecurity, employee experience teams, and technical deployment leads to drive adoption and minimize resistance.


Key Responsibilities
• Develop and execute a comprehensive change management plan aligned with the MAM/MDM project timeline and goals.
• Serve as the primary liaison for communication and engagement across impacted business units, including Employee Experience and Cybersecurity.
• Lead stakeholder analysis, readiness assessments, and impact analyses to inform change strategies.
• Design and deliver communication campaigns, training materials, and support resources tailored to different user groups.
• Collaborate with the technical team to translate technical changes into user-friendly messaging.
• Monitor feedback channels (e.g., Teams, OneNote, Feedback/Support Channel) and adjust strategies based on user sentiment and adoption metrics.
• Coordinate with internal and/or external partners providing PM/OCM support.
• Report progress, risks, and mitigation plans to project leadership and Cybersecurity sponsors.


Qualifications
• Proven experience in organizational change management, preferably in IT or digital workplace transformation.
• Familiarity with MAM/MDM technologies and enterprise mobility policies.
• Strong communication, facilitation, and stakeholder engagement skills.
• Ability to manage multiple priorities in a fast-paced, cross-functional environment.
• Experience with Microsoft Intune, OneDrive policies, and enterprise collaboration tools is a plus.


Preferred Background
• Experience supporting enterprise-wide rollouts involving conditional access, mobile policy enforcement, or device compliance.
• Prior involvement in pilot-to-deployment transitions and lessons-learned documentation.