Executive Director of Product Management , Resiliency

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description (role summary) which could be About the role. Responsibilities are listed. Requirements: Required Qualifications. Preferred Qualifications maybe part of Qualifications. Skills maybe from required qualifications like communication, organizational, etc. Benefits: not mentioned. Pay: Estimated Salary: $150,000 - $214,000 plus bonus. So include Pay section. Schedule: Travel is as needed (approximately 25%–50%), including on-site pilot customer visits. That's schedule/travel. So include Schedule. Benefits not mentioned, so omit. Skills: we could extract from required qualifications: ability to clearly communicate; work in team environments; people management; software development experience; strategic planning; interpersonal, communication, presentation; organizational and time management. Could be a Skills section. But we need to ensure not to repeat content. Could put Skills as a subsection under Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate Skills section. Ensure we don't create empty sections. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from posting, but we can reorganize into sections. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, disclaimer, privacy policy, etc. Also remove navigation, cookie, legal, scam-warning. So we cut out the EEO paragraph and disclaimer etc. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

... summary ...

Responsibilities

• ... each bullet ...

We need to include all responsibilities bullet points. There's a long list. We'll need to capture them. Responsibilities paragraph: "Working with a broad group of stakeholders and partners — across GHX product pods, Forward-Deployed Engineering, current and prospective pilot customers, and the executive leadership team — the Executive Director develops and leads GHX Product Management execution for the Supply Resiliency use case. Responsibilities also include identification and qualification of future use case prioritization. Specific responsibilities include:" then list. We'll convert each line after "Specific responsibilities include:" into

. Let's extract list: - Own end-to-end product development lifecycle (PDLC) for GHX Orchestration, from forward-deployed pilot and prototype through GA commercialization, across both use-case tracks (Procure-to-Pay and Order-to-Cash). - Design, govern, and continuously refine the pilot selection engine: Layer 1 binary hard gates (data access, SME time, on-site access, feedback cadence, executive sponsor) and the Layer 2 weighted scorecard used to rank and select pilot candidates. - Own pilot cohort selection and all stage-gate decisions (entry, mid-pilot, exit), including go/kill/reallocate calls on stalled accounts. - Partner directly with the Forward-Deployed Engineering team to scope on-site pilot engagements, define track-specific entry criteria and success metrics, and translate pilot learnings into a repeatable deployment playbook. - Own product-level success criteria and report progress against exit bars: P0/P1 issue resolution, GA-candidate certification, referenceable-logo targets, and quantified ROI proof points, by persona and by track. - Lead product's input into the GTM execution plan, keeping the commercial (pricing/packaging), pilot delivery, and marketing workstreams synchronized against the shared milestone schedule and dependency chain. - Define and evolve the tiered commercial model (Foundation / Agentic / Outcome-Premium) and the hybrid pricing approach (base subscription plus metered/outcome layer); partner with Finance and Deal Desk on SOW structure, platform-level contracting, and pilot-to-GA conversion terms. - Translate persona- and value-based requirements (executive sponsor, operational champion, SME end-users, technical/integration owner, data steward) into a technical roadmap in partnership with Engineering. - Drive product-boundary clarity across adjacent and overlapping offerings (e.g., Price Workbench, Industry Data Alignment, Data Connect, Managed Services, and Resiliency Center capability) and own the resulting customer-facing positioning, flow documentation, and sales-enablement materials. - Analyze market trends and the competitive landscape — including well-funded, AI-native point-solution entrants — to defend and advance GHX's “orchestration” category positioning, and to win head-to-head competitive evaluations. - Build and sustain executive-level relationships with pilot customers and internal sponsors to unblock data access, named SME time, on-site access, and rapid structured feedback. - Lead through influence across Sales, Marketing, and Professional Services to execute and deliver the roadmap and optimize product efficiency for implementation, supportability, and system reliability. - Develop and mentor Product Owners and Product Managers supporting the platform. - Utilize effective change management practices to execute the product roadmap and communicate progress, risks, and decisions to the executive/steering committee. Now Requirements: maybe we separate Required Qualifications and Preferred Qualifications under Requirements and Qualifications headings? The instruction lists headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need both Requirements and Qualifications sections. Likely Requirements = mandatory qualifications; Qualifications = preferred? Or we could put Required Qualifications under Requirements, and Preferred Qualifications under Qualifications. Let's do that. Requirements section: list required qualifications bullet points. Required Qualifications list: - A minimum of 10 years of Product Management experience. - Experience leading Product Management initiatives within the healthcare space is required. - Demonstrated experience designing or running structured pilot programs, forward-deployed engineering models, or similar early-access/co-development customer AI engagements. - Experience developing or executing usage-based, outcome-based, or hybrid commercial pricing models for enterprise software. - Ability to clearly communicate; work in team environments, with a minimum of 3 years people management experience. - Proven software development experience managing product planning milestones from business concept through launch. - Competency at developing strategies and execution plans for new businesses or new platform offerings. - Demonstrated ability to manage cross-functional project teams spanning Product, Engineering, Sales, Marketing, and Professional Services. - Strategic planning skills, including experience building and defending a go-to-market roadmap with executive stakeholders. - Excellent interpersonal, communication, and presentation skills (oral and written communication). - Outstanding organizational skills and time management skills. - Travel is as needed (approximately 25%–50%), including on-site pilot customer visits. Note travel maybe schedule, but it's also a requirement. We'll keep it in Requirements? But we also have Schedule section for travel. Might duplicate. Better to put travel in Schedule section, not Requirements. However the required qualifications includes travel. We could keep it in Requirements but also mention in Schedule? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we put travel only in Schedule, we still preserve it. It's okay to move it. We'll put travel in Schedule section. Thus Requirements will exclude travel line. Now Qualifications section: Preferred Qualifications bullet list. Preferred Qualifications: - 5+ years of healthcare software product management experience. - Experience managing healthcare supply chain products and services (Procure-to-Pay and/or Order-to-Cash) desirable but not necessary. - Experience launching or commercializing agentic AI or AI-enabled product capabilities. - Experience building pricing models that incorporate a metered or outcome-based component alongside a base subscription. - Experience showing ability to drive customer adoption of emerging technologies and solutions. - Track record winning head-to-head competitive evaluations against market challengers in enterprise or healthcare software. Now Skills section: Could extract from required qualifications: ability to clearly communicate; work in team environments; people management; software development experience; strategic planning; excellent interpersonal, communication, presentation; outstanding organizational and time management. But we already have many of those in Requirements. To avoid duplication, maybe Skills section can be omitted if content overlaps. But we need to include a Skills section only if there is real specific content not covered elsewhere. The posting does not have a separate "Skills" bullet list; skills are embedded in qualifications. Could still create Skills section summarizing those skills, but that would be summarizing/inventing? It's extracting from existing content, not inventing. It's okay to pull out skills. However we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we can omit Skills section and let Requirements cover skills. But the headings list includes Skills as optional; we only include if posting has real specific content for it. Since there is no dedicated Skills heading, we might skip Skills. Benefits: none. Pay: Estimated Salary: $150,000 - $214,000 plus bonus. Schedule: Travel is as needed (approximately 25%–50%), including on-site pilot customer visits. Now About the role: need to capture the initial paragraph(s) before "Why this role matters" maybe. The posting starts: "The Executive Director, Product Management – Supply Chain Resiliency reports to the VP, Product Management and owns the full product development lifecycle and go-to-market execution for GHX's Supply Resiliency Platform — the cross-application layer spanning two use-case tracks: Procure-to-Pay (hospital) and Order-to-Cash (manufacturer/supplier) workflows. This is a build-and-commercialize role: the Executive Director owns the platform requirements, product launch, and forward-deployed pilot through general availability, driving pilot customer selection and execution, product requirements and roadmap, commercial packaging and pricing, and cross-functional GTM alignment across Engineering, forward-deployed teams, Sales, Marketing, Implementation, Professional Services, Customer Care and Finance. Areas of focus include, but are not solely limited to: pilot program design and stage-gate governance; product definition, roadmap execution, and technical alignment; commercial packaging, pricing, and profitability; competitive positioning; cross-functional consensus building; and executive/steering-committee reporting." Then "WHY THIS ROLE MATTERS Healthcare supply chain resiliency is now a contested category: well-funded, AI-native challengers are selling point solutions directly to hospitals. This role is chartered to win that fight — turning GHX's two-sided network of 600+ connected providers and their suppliers into a resiliency platform that out-executes single-sided competitors on speed, breadth, and proven customer outcomes. The Executive Director owns that competitive outcome end to end, from platform definition through GA and beyond." We can combine these into About the role section. Should we include "WHY THIS ROLE MATTERS" as part of About? Yes. Thus About the role paragraph(s) will contain all that descriptive text. Now we need to ensure we don't include boilerplate like EEO, disclaimer, privacy policy, etc. We'll cut those out. Now produce HTML:

About the role

The Executive Director, Product Management – Supply Chain Resiliency reports to the VP, Product Management and owns the full product development lifecycle and go-to-market execution for GHX's Supply Resiliency Platform — the cross-application layer spanning two use-case tracks: Procure-to-Pay (hospital) and Order-to-Cash (manufacturer/supplier) workflows. This is a build-and-commercialize role: the Executive Director owns the platform requirements, product launch, and forward-deployed pilot through general availability, driving pilot customer selection and execution, product requirements and roadmap, commercial packaging and pricing, and cross-functional GTM alignment across Engineering, forward-deployed teams, Sales, Marketing, Implementation, Professional Services, Customer Care and Finance. Areas of focus include, but are not solely limited to: pilot program design and stage-gate governance; product definition, roadmap execution, and technical alignment; commercial packaging, pricing, and profitability; competitive positioning; cross-functional consensus building; and executive/steering-committee reporting. Healthcare supply chain resiliency