.
- Requirements: Might be qualifications? Actually they have "Qualifications" heading. Could treat "Qualifications" as Requirements? But they also have separate "Qualifications" heading. The list includes education, experience, etc. We'll put under Qualifications.
- Skills: Could extract skills like "Strong written, verbal, facilitation, stakeholder management, and relationship-building skills." Also "Ability to translate complex technology concepts..." etc. Could be placed under Skills.
- Benefits, Pay, Schedule: Not mentioned, so omit.
- About the role maybe also include location? Already in first sentence.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, accommodation, etc.
We must preserve all substantive information.
Let's extract content:
First paragraph: "Milacron is looking for a Change Management Specialist to join our team in Batavia, OH. In this position, you will be responsible for leading organizational change initiatives with a strong focus on technology-enabled transformation, including AI, automation, digital tools, and enterprise systems. You will partner across business, technology, HR, and functional teams to drive adoption, build workforce capability, and ensure sustainable business outcomes."
That's About the role.
Responsibilities (Work You'll Do): list each sentence starting with a verb.
- Develop and execute change management strategies for enterprise-wide business, process, organizational, cultural, and technology initiatives.
- Partner with business leaders, technology teams, HR, and functional stakeholders to translate change initiatives into new workflows, capabilities, and behaviors.
- Conduct stakeholder analyses, change impact assessments, workforce readiness evaluations, and role-based skills assessments.
- Build implementation roadmaps that include communications, training, sponsorship, champion networks, pilots, feedback loops, and sustainment activities.
- Support the adoption of AI, automation, digital platforms, and enterprise systems by preparing employees and leaders for changes in ways of working.
- Design and deliver role-based training programs that strengthen digital and AI literacy, technology proficiency, and employee confidence.
- Develop communications that clearly explain the purpose, impact, benefits, and support resources associated with organizational changes.
- Monitor adoption, proficiency, utilization, employee experience, and business outcome metrics to measure success and value realization.
- Identify and address resistance, capability gaps, risks, and barriers that may impact successful adoption.
- Coach leaders and managers to effectively sponsor change, model desired behaviors, and reinforce adoption throughout the organization.
Qualifications: list bullet points.
- Bachelor’s degree in Business, Human Resources, Organizational Psychology, Information Systems, Communications, or a related field.
- 3-5 years of experience in change management, digital transformation, organizational development, technology adoption, or a related field.
- Experience supporting AI, automation, enterprise systems, digital workplace tools, or other technology-enabled change initiatives.
- Working knowledge of generative AI capabilities, limitations, business use cases, and responsible-use principles.
- Familiarity with structured change management methodologies such as Prosci, Kotter, or similar frameworks.
- Experience working within agile, product-based, or iterative implementation environments preferred.
- Ability to translate complex technology concepts into clear, practical guidance for diverse audiences.
- Experience developing enterprise communications, training programs, adoption plans, and success measures.
- Strong written, verbal, facilitation, stakeholder management, and relationship-building skills.
- Experience with AI assistants, analytics platforms, SharePoint, Smartsheet, or similar technologies preferred.
- Knowledge of responsible AI practices, data privacy considerations, security requirements, and digital risk awareness preferred.
Skills: Could extract some overlapping but we can separate: maybe "Strong written, verbal, facilitation, stakeholder management, and relationship-building skills." and "Ability to translate complex technology concepts into clear, practical guidance for diverse audiences." and "Experience developing enterprise communications, training programs, adoption plans, and success measures." and "Experience with AI assistants, analytics platforms, SharePoint, Smartsheet, or similar technologies preferred." and "Knowledge of responsible AI practices, data privacy considerations, security requirements, and digital risk awareness preferred." But many are already in Qualifications. To avoid duplication, we could put skills separate: maybe list skills like "Strong written, verbal, facilitation, stakeholder management, and relationship-building skills." and "Ability to translate complex technology concepts into clear, practical guidance for diverse audiences." and "Experience developing enterprise communications, training programs, adoption plans, and success measures." and "Experience with AI assistants, analytics platforms, SharePoint, Smartsheet, or similar technologies." and "Knowledge of responsible AI practices, data privacy considerations, security requirements, and digital risk awareness."
But we must not invent content; we can take from qualifications but it's okay to list under Skills as they are skills. However we must preserve all substantive information; duplication is okay? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be redundant. Better to avoid duplication by placing under Qualifications only, and maybe Skills not needed if no distinct skills beyond qualifications. However we need to include a section only when posting has real, specific content for it. The posting does have skill statements; we could put them under Skills. But they are also in Qualifications. To avoid duplication, we could treat Qualifications as the list of requirements (education, experience, knowledge) and Skills as the abilities (written, verbal, facilitation, etc.). Let's split:
Qualifications (education/experience):
- Bachelor’s degree in Business, Human Resources, Organizational Psychology, Information Systems, Communications, or a related field.
- 3-5 years of experience in change management, digital transformation, organizational development, technology adoption, or a related field.
- Experience supporting AI, automation, enterprise systems, digital workplace tools, or other technology-enabled change initiatives.
- Working knowledge of generative AI capabilities, limitations, business use cases, and responsible-use principles.
- Familiarity with structured change management methodologies such as Prosci, Kotter, or similar frameworks.
- Experience working within agile, product-based, or iterative implementation environments preferred.
Skills:
- Ability to translate complex technology concepts into clear, practical guidance for diverse audiences.
- Experience developing enterprise communications, training programs, adoption plans, and success measures.
- Strong written, verbal, facilitation, stakeholder management, and relationship-building skills.
- Experience with AI assistants, analytics platforms, SharePoint, Smartsheet, or similar technologies preferred.
- Knowledge of responsible AI practices, data privacy considerations, security requirements, and digital risk awareness preferred.
That covers all.
Now About the role: we have the intro paragraph.
We also have "Who We Are" description about Milacron. Could be considered About the role? Actually About the role is about the position; Who We Are is company description. Could we add another section like "About the company"? Not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings. Where to put company description? Could incorporate into About the role as a brief description? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. But we should only use those headings. The company description could be placed under About the role as part of the role context? Might be okay to include a paragraph under About the role that includes both role and company overview. However the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include company description in a
under About the role.
Thus About the role section will have two paragraphs: first about the role responsibilities overview, second about Milacron.
Let's craft:
About the role
Milacron is looking for a Change Management Specialist to join our team in Batavia, OH. In this position, you will be responsible for leading organizational change initiatives with a strong focus on technology-enabled transformation, including AI, automation, digital tools, and enterprise systems. You will partner across business, technology, HR, and functional teams to drive adoption, build workforce capability, and ensure sustainable business outcomes.
Milacron is a global industrial leader in the manufacturing and distribution of highly engineered and customized injection molding and extrusion solutions, and aftermarket parts and service for the plastics processing industry. The company’s 1,900+ associates worldwide collaborate to serve a diverse range of end-markets, such as automotive, construction, medical, telecommunications, material handling, packaging, and much more. With expertise in plastics spanning nearly 60 years, Milacron holds longstanding relationships with more than 27,000 customers around the world. The original equipment provider of plastics manufacturing solutions is the largest US-owned and globally served of its kind. Headquartered in Batavia, OH, Milacron’s global footprint is also serviced through regional facilities in Asia, Europe, and South America.
Now Responsibilities:
Responsibilities
- Develop and execute change management strategies for enterprise-wide business, process, organizational, cultural, and technology initiatives.
- Partner with business leaders, technology teams, HR, and functional stakeholders to translate change initiatives into new workflows, capabilities, and behaviors.
- Conduct stakeholder analyses, change impact assessments, workforce readiness evaluations, and role-based skills assessments.
- Build implementation roadmaps that include communications, training, sponsorship, champion networks, pilots, feedback loops, and sustainment activities.
- Support the adoption of AI, automation, digital platforms, and enterprise systems by preparing employees and leaders for changes in ways of working.
- Design and deliver role-based training programs that strengthen digital and AI literacy, technology proficiency, and employee confidence.
- Develop communications that clearly explain the purpose, impact, benefits, and support resources associated with organizational changes.
- Monitor adoption, proficiency, utilization, employee experience, and business outcome metrics to measure success and value realization.
- Identify and address resistance, capability gaps, risks, and barriers that may impact successful adoption.
- Coach leaders and managers to effectively sponsor change, model desired behaviors, and reinforce adoption throughout the organization.
Qualifications:
Qualifications
- Bachelor’s degree in Business, Human Resources, Organizational Psychology, Information Systems, Communications, or a related field.
- 3-5 years of experience in change management, digital transformation, organizational development, technology adoption, or a related field.
- Experience supporting AI, automation, enterprise systems, digital workplace tools, or other technology-enabled change initiatives.
- Working knowledge of generative AI capabilities, limitations, business use cases, and responsible-use principles.
- Familiarity with structured change management methodologies such as Prosci, Kotter, or similar frameworks.
- Experience