Organizational Change Management (OCM) Analyst

We need to output HTML fragment with sections for headings where content exists. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to include sections only when posting has real specific content. We have details: Position Summary, Program Context and Scope, Key Responsibilities (with subcategories), Required Qualifications, Preferred Qualifications. Also contact info and apply button but we should remove application instructions and contact? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The contact info (Micah Andres) is application instruction? It says "For interested applicants, click the apply button or you may reach out to Micah Andres..." That's application instruction, so remove. Also "Details:" repeated? We'll drop. We need to preserve all substantive information: position summary, program context, responsibilities, required qualifications, preferred qualifications. Also maybe skills? The qualifications include skills like Microsoft Office. Could put under Skills section? But we have Qualifications and Skills separate headings. The posting includes "Required Qualifications" and "Preferred Qualifications". Could combine into Qualifications section? But we have headings for Qualifications and Skills. We could put required qualifications under Qualifications, and preferred under Qualifications as well? Or separate? The instruction: Use headings only when posting has real specific content for it. We have content for Qualifications (both required and preferred). Could make a Qualifications section containing both required and preferred bullet lists. Skills: The posting mentions "Advanced proficiency with Microsoft PowerPoint, Excel, Word, Teams, and SharePoint." That's a skill. Could put under Skills. Also "Excellent written and verbal communication skills in English." That's also skill. Could include. We have no explicit Benefits, Pay, Schedule. So omit those sections. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to avoid repeating job title. No need for etc. We need to output only HTML fragment. Let's craft:

  About the role

  maybe we can put position summary and program context under About the role. Or we could have separate sections: About the role (position summary), Responsibilities, Qualifications, Skills. We need to decide headings: About the role (position summary + program context). Responsibilities (key responsibilities). Qualifications (required and preferred). Skills (specific skills like communication, MS Office). Could also include "Preferred Qualifications" as part of Qualifications but we can separate. We must not create empty sections. Let's extract content: Position Summary: "We are seeking a highly organized and execution-oriented Organizational Change Management (OCM) Analyst / Coordinator to support a Global IT Service Management (GITSM) transformation program. The program is establishing standardized global ITSM processes and a unified ServiceNow platform across the Americas, EMEA, Japan, and EAGS. The contractor will work under the direction of the GITSM OCM Lead and collaborate with Program Management, Regional ITSM Leads, Global Process Owners, ServiceNow delivery teams, business stakeholders, and Accenture OCM advisors. The role will provide hands-on support for stakeholder engagement, communications, training coordination, readiness, adoption tracking, UAT, Go-Live, and Hypercare activities." Program Context and Scope: "Project Leap Includes Global Process And Platform Changes Affecting Both End Users And IT Support Teams. The Contractor Will Support Change Activities Associated With Rolling Out Of The Global IT Service Management Platform With The Following Capabilities: Incident, Problem, Change, Request, and Knowledge Management processes. Service Portal, Service Catalog, user feedback surveys, and AI-enabled self-service experiences. CMDB foundation, ITOM / AIOps capabilities, reporting, integrations, and automation. Global process standardization, regional adoption, and transition to the target GITSM operating model." We can combine these into About the role. Responsibilities: list bullet points from Key Responsibilities sections: Support execution of the GITSM communication and stakeholder engagement plan across regions and functions. Maintain the stakeholder register, communication calendar, audience segmentation, distribution lists, and engagement tracker. Draft leadership messages, project updates, email campaigns, FAQs, announcements, town hall content, and Go-Live communications. Coordinate reviews, translations where required, approvals, and distribution with global and regional stakeholders. Support regional change networks, change champions, and stakeholder feedback activities. Training and User Readiness: Coordinate training for end users, fulfillment teams, Service Desk personnel, process roles, and other impacted groups. Maintain the training schedule, audience roster, invitations, attendance records, completion status, and follow-up actions. Assist with training materials, quick-reference guides, job aids, FAQs, knowledge content, and recorded-session coordination. Coordinate updates to materials arising from UAT feedback, solution changes, or approved process decisions. Support preparation and maintenance of the Operational Readiness Guide for in-scope processes. Readiness, Adoption, and Reporting: Administer business and operational readiness assessments and consolidate results across regions. Maintain readiness dashboards and track communications, training completion, stakeholder engagement, user feedback, and adoption indicators. Identify gaps, overdue actions, regional dependencies, and OCM risks for escalation to the OCM Lead and PMO. Prepare concise weekly OCM status reports, leadership summaries, and decision or action logs. UAT, Go-Live, and Hypercare Support: Coordinate UAT awareness, participant communications, training alignment, reminders, and feedback consolidation. Support Go-Live readiness checkpoints, cutover communications, launch materials, and stakeholder briefings. Monitor and consolidate user feedback during Hypercare, identify recurring themes, and route actions to the appropriate owner. Support issue communications, frequently asked questions, office hours, lessons learned, and post-Go-Live adoption reporting. OCM Project Coordination: Maintain the integrated OCM workplan, deliverable tracker, RAID items, dependencies, meeting notes, and action log. Coordinate OCM workshops, leadership briefings, regional sessions, town halls, training events, and readiness reviews. Work closely with the GITSM PMO, Process Governance, Platform, Service Management, regional teams, and Accenture advisors. Ensure OCM activities remain aligned with design, build, testing, deployment, and Hypercare milestones. We can group these under Responsibilities as a list. Qualifications: Required Qualifications bullet list: Approximately 3-7 years of experience in organizational change management, change communications, training coordination, PMO, or enterprise transformation. Hands-on experience supporting a large-scale technology implementation or digital transformation. Demonstrated ability to create polished stakeholder communications, presentation materials, trackers, and status reports. Strong organizational skills, attention to detail, and ability to manage multiple deadlines and stakeholders. Excellent written and verbal communication skills in English. Advanced proficiency with Microsoft PowerPoint, Excel, Word, Teams, and SharePoint. Preferred Qualifications bullet list: Experience with ServiceNow implementations or IT service management transformation. Working knowledge of ITIL practices and ITSM processes. Experience supporting global, geographically dispersed, or multicultural teams. Experience in pharmaceutical, healthcare, life sciences, or another regulated environment. Exposure to UAT, Go-Live, Hypercare, readiness assessments, training operations, and adoption measurement. OCM certification or familiarity with a recognized change framework is beneficial but not required. Skills: Could extract communication skills and MS Office proficiency. But those already in qualifications. Might be redundant. Perhaps we can put those under Skills and keep Qualifications for experience years etc. But we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in original? But we should not repeat same info unnecessarily? It didn't forbid duplication, but better to avoid redundancy. We could split: Qualifications: experience and education etc. Skills: communication, MS Office, etc. However the required qualifications already include communication skills and MS Office. If we move them to Skills, we would be removing from Qualifications, losing some detail? But we could keep them in both places? Might be considered duplication but still preserving. Safer to keep them in Qualifications and not create Skills section unless we have additional distinct skills not covered. The posting does not list separate skills beyond those. So we may omit Skills section. Thus sections: About the role, Responsibilities, Qualifications. We need to use

  for each. Inside About the role: we can have

  containing position summary and program context (maybe two paragraphs). Use

  for prose. Responsibilities:

  • each bullet. Qualifications: we could have two sub-sections? Not required headings. Could just list all qualifications (required and preferred) as list. But we might want to separate required vs preferred using

    headings? Not allowed to create extra headings besides the specified ones. Could use

    to label "Required Qualifications:" and then list, then another

    for "Preferred Qualifications:" then list. That's okay as prose. Let's craft. HTML:

    About the role

    We are seeking a highly organized and execution-oriented Organizational Change Management (OCM) Analyst / Coordinator to support a Global IT Service Management (GITSM) transformation program. The program is establishing standardized global ITSM processes and a unified ServiceNow platform across the Americas, EMEA, Japan, and EAGS. The contractor will work under the direction of the GITSM OCM Lead and collaborate with Program Management, Regional ITSM Leads, Global Process Owners, ServiceNow delivery teams, business stakeholders, and Accenture OCM advisors. The role will provide hands-on support for stakeholder engagement, communications, training coordination, readiness, adoption tracking, UAT, Go-Live, and Hypercare activities.

    Project Leap Includes Global Process And Platform Changes Affecting Both End Users And IT Support Teams. The Contractor Will Support Change Activities Associated With Rolling Out Of The Global IT Service Management Platform With The Following Capabilities: Incident, Problem, Change, Request, and Knowledge Management processes. Service Portal, Service Catalog, user feedback surveys, and AI-enabled self-service experiences. CMDB foundation, ITOM / AIOps capabilities, reporting, integrations, and automation. Global process standardization, regional adoption, and transition to the target GITSM operating model.

    Responsibilities

    • Support execution of the GITSM communication and stakeholder engagement plan across regions and functions.
    • Maintain the stakeholder register, communication calendar, audience segmentation, distribution lists, and engagement tracker.
    • Draft leadership messages, project updates, email campaigns, FAQs, announcements, town hall content, and Go-Live communications.
    • Coordinate reviews, translations where required, approvals, and distribution with global and regional stakeholders.
    • Support regional change networks, change champions, and stakeholder feedback activities.
    • Coordinate training for end users, fulfillment teams, Service Desk personnel, process roles, and other impacted groups.
    • Maintain the training schedule, audience roster, invitations, attendance records, completion status, and follow-up actions.
    • Assist with training materials, quick-reference guides, job aids, FAQs, knowledge content, and recorded-session coordination.
    • Coordinate updates to materials arising from UAT feedback, solution changes, or approved process decisions.
    • Support preparation and maintenance of the Operational Readiness Guide for in-scope processes.
    • Administer business and operational readiness assessments and consolidate results across regions.
    • Maintain readiness dashboards and track communications, training completion, stakeholder engagement, user feedback, and adoption indicators.
    • Identify gaps, overdue actions, regional dependencies, and OCM risks for escalation to the OCM Lead and PMO.
    • Prepare concise weekly OCM status reports, leadership summaries, and decision or action logs.
    • Coordinate UAT awareness, participant communications, training alignment, reminders, and feedback consolidation.
    • Support Go-Live readiness check