Senior Director, Enterprise Program and Change Management

We need to output HTML fragment with sections: About the role? Actually the posting includes "Company Overview", "Why Work at Brother?", "Role Overview", "Duties & Responsibilities", "Experience & Qualifications", "Additional Details For This Role", "Our Benefits", "Our Mission, Vision & Culture", "About Where We Work". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate like EEO etc. Also remove navigation/legal etc. We need to preserve all substantive information. So we need to extract content and format accordingly. We need to decide which sections to include: - About the role: could be "Role Overview" and maybe "Company Overview"? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map "Role Overview" to About the role. Also "Company Overview" maybe part of About the role? Could include as prose. - Responsibilities: from "Duties & Responsibilities". Use that. - Requirements: maybe from "Experience & Qualifications" (education, experience, licenses, certifications). Could be Requirements. - Qualifications: maybe overlapping; but we can separate: Requirements (experience, education) and Qualifications (skills, certifications). However we need to avoid thin sections. We could combine into one Requirements section that includes education, experience, licenses, certifications, skills. But the instruction says we can have multiple sections but prefer few substantive sections over many thin ones. We could have About the role, Responsibilities, Requirements (including education, experience, licenses, certifications, skills), Benefits, Pay. Schedule: we have hybrid role details (up to two days remote). That's schedule info. So include Schedule. We must not include sections with filler like "commensurate with experience". We have actual pay range: $195,000 - $235,000 per year. Bonus details. So Pay section. Benefits: we have description of benefits package. Schedule: hybrid role details. We should not include "Our Mission, Vision & Culture" or "About Where We Work" unless we map them to allowed headings. Those are not in allowed list; we should drop them (they are not required headings). The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should only use those headings. So we should omit other headings. So we will not include sections for Mission, Vision, Culture, About Where We Work. We also need to drop boilerplate like EEO statement. Now we need to format content. Let's extract substantive content: Company Overview: Brother is a leading provider... etc. We'll include as prose under About the role maybe. Why Work at Brother? includes recognition, policies, hybrid schedule, casual dress, flexible Fridays, facilitated courses, certificate programs, self-paced learning. This could be part of About the role or Benefits? But we have Benefits separate. Could include under About the role as prose. Role Overview: description of Senior Director responsibilities. Could be part of About the role as well. Duties & Responsibilities: detailed bullet-like paragraphs. We'll turn into

  • items. Experience & Qualentials: Education, Experience, Licenses and Certifications, Software/Technical Skills, Other Skills/Knowledge/Abilities. We'll turn into lists. Additional Details For This Role: hybrid role schedule (up to two days remote). We'll put under Schedule. Base Salary: pay range. Bonus details. We'll put under Pay. Our Benefits: description of health, vision, dental, 401k match, educational assistance. We'll put under Benefits. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep specifics like numbers, percentages, etc. Let's craft. Structure:

    About the role

    Company overview paragraph + Why Work at Brother? + Role Overview paragraph(s). We'll combine into prose. But we need to ensure we don't lose any specifics: mention legacy 115 years, award-winning printers, sewing machines, P-touch labelers, BIC established 1954, 70 years US, HQ Bridgewater NJ, wholly owned subsidiary of BIL founded 1908 Nagoya Japan, operates 30+ countries, Americas subsidiaries in Canada, Mexico, Brazil, Argentina, Chile, Peru. Why Work at Brother: recognized as best place to work, values inclusive, collaborative, customer-centric, socially responsible, work-life balance, flexibility, hybrid office schedule, casual dress code, flexible Fridays, facilitated courses, certificate programs, investment in self-paced learning resources. Role Overview: Senior Director, Enterprise Program and Change Management responsible for program and change management services supporting strategic objectives, establishing and overseeing governance frameworks for Program and Organizational Change Management, ensuring enterprise-wide adoption, building team managing enterprise-level projects and programs and OCM from planning through completion, hypercare, adoption, partnering with stakeholders to define success criteria, gain executive alignment, allocate resources, establish roles/responsibilities, develop communication and change management plans, assemble and lead high-performance project teams, lead post-project reviews from project execution and business case retrospective perspective. We'll put that in

    maybe multiple

    but okay. Then Responsibilities: we need to list each duty as

  • . The Duties & Responsibilities section includes several bullet-like paragraphs each starting with a bold heading (Executive Leadership, Enterprise Project Management Office (EPMO), Organizational Transformation, Change Management, and Process). We'll turn each into
  • with the content. We need to preserve all details: For Executive Leadership: Provide strategic leadership and alignment for the enterprise project management and change management teams fostering a culture of operational efficiency, innovation, and transformational efforts; Oversee program and project governance and successful execution on a daily basis. This includes staffing and managing a team of professional employees and external consultants to support a broad range of organizational projects; Serve as a trusted advisor to the executive team, providing insights and strategic guidance for project execution and successful adoption of organizational readiness across the Americas; Support Portfolio Management with maintaining the Enterprise Project cost center, in partnership with finance and key stakeholders, to ensure consistency, accuracy and visibility across all project budgets and forecasts; Partner with the VP of ETEO to guide the continued transformation and alignment of the teams within the ETEO department as a whole, including creating department-wide roadmaps, resource assessments and standard ways of working, as well as providing leadership and coaching across all levels within the organization. Enterprise Project Management Office (EPMO): Develop and implement standard project methodologies as well as a EPMO governance structure across the organization; Build strong relationships at all levels across the organization, while facilitating needed stakeholder engagement and performance; Identify potential risks and develop mitigation strategies to minimize project or program disruption to ensure success; Act as the main point of contact between various project team stakeholders and the organization’s executive and other relevant governance committees; Drive data-driven program management practices by defining program performance metrics, establishing consistent reporting standards, and using insights from dashboards, financials, risks, milestones, adoption measures, and resource data to improve transparency, prioritization, and executive decision-making; Partner with project teams, sponsors, Finance, and Portfolio Management to ensure program data is accurate, timely, actionable, and connected to business outcomes, enabling proactive issue resolution, benefits tracking, and continuous improvement across the enterprise project portfolio. Organizational Transformation, Change Management, and Process: Oversee the build out of a Organizational Change Management (OCM) function to support Brother Americas transformation needs; Build standard OCM processes, methodologies and templates to create a consistent approach to OCM delivery; Develop a high functioning OCM team, leveraging a mix of employee and external consulting to drive a scalable, multi region support function; Drive stakeholder awareness and adoption of core OCM Brother Americas scope and approach; Assess business readiness and change impact needed to execute proposed projects and initiatives. Quantify these factors for project sponsors and executive leadership through ongoing prioritization, approval, review, and post-audit discussions; Partner with project owners & sponsors to develop and execute organizational change management plans; Assess processes related to organization initiatives for optimization and efficiency purposes. Work with key project stakeholders/participants to map “as is” and “to be” processes, and assist with the change and adoption associated with the transformation. We'll put each as
  • . Then Requirements: we need to include Education, Experience, Licenses and Certifications, Software/Technical Skills, Other Skills/Knowledge/Abilities. Could be separate sub-sections but we can combine into one Requirements section with lists. Education: Bachelor's Degree (or equivalent experience) in Business, Project Management, Organizational Development, or related field; Master's Degree (or equivalent experience) Business, Project Management, Organizational Development, or related field - Preferred. Experience: 15+ years of experience spanning the following areas: Proven experience managing large projects and programs with significant executive interaction; Demonstrated success in leading EPMO improvements and establishing governance structures within mid-to-large organizations; Expertise in creating and enhancing program and project management methods and standards; Experience overseeing business transformation, continuous improvement and process excellence initiatives; Experience managing project financials; Experience in implementing change management and adoption strategies, establishing a trusted advisor role with business stakeholders. Licenses and Certifications: PMP - Project Management Professional - Preferred; Agile Certification - Preferred; Organizational Change Management Certification - Preferred. Software/Technical Skills: Intermediate Jira, Workfront, or other PPM tools and software; Intermediate Microsoft Office (Outlook, Word, Excel, PowerPoint). Other Skills/Knowledge/Abilities: Strategic thinker with the ability to build strong relationships and work collaboratively across several business functions to gain buy-in to new processes; Strong communication skills (written/verbal), with demonstrated ability to effectively present to and influence senior executives; Strong understanding of Project Management Methodology (Agile & PMP techniques); Proven ability to effectively lead and manage teams, providing guidance, mentorship, and motivation; Ability to manage simultaneous projects through to completion, achieving all targets; Ability to monitor vendor performance and ensure compliance with contract terms; Ability to implement new technology, processes, and techniques; Knowledge of risk management; Finance, accounting and budget management; Six sigma/business process improvement - Preferred. We'll put each as
  • under appropriate subheadings? But we cannot add extra headings beyond allowed. We could just have a single
    with all items, but that may lose categorization. However we can embed headings inside
    • ? Not ideal. Perhaps we can have multiple
      each preceded by a

      heading? But we cannot add extra headings like "Education". The instruction only mentions using

      for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using

      for subheadings inside a section. So we can have

      Education:

      then

      etc. That's acceptable. Thus under Requirements section we can have

      Education:

      ... etc. Similarly for Experience, Licenses and Certifications, Software/Technical Skills, Other Skills/Knowledge/Abilities. We need to decide whether to also have a Qualifications section. Could combine Requirements and Qualifications but we have both allowed. Could put Requirements for education/experience, Qualifications for skills/certifications. But we already have many details; we could split: Requirements: Education and Experience. Qualifications: Licenses/Certifications, Software/Technical Skills, Other Skills/Knowledge/Abilities. That seems reasonable. Thus:

      Requirements

      Education:

      • Bachelor's Degree (or equivalent