Head of Product

The Head of Product owns product practice for Orchestration Works: the intake funnel that feeds the portfolio, the ROI thesis discipline that every initiative must carry, and the operating cadence that keeps the 120-day model honest. Every problem that enters OW arrives with a documented hypothesis about automation lift, operational improvement, and financial return — this role is the keeper of that discipline, from intake through gate decisions through outcome reporting.

This is end-to-end initiative ownership across the pod portfolio: product leadership, outcomes, testing, and the reporting rhythm that keeps executive governance informed. The Head of Product runs the gate review cadence for the General Manager, owns portfolio reporting into Control Tower, and sets the product and design standard that pod Product Managers and Designers work to. The role is the interface to Ensemble's Product organization, ensuring OW's portfolio stays connected to the enterprise roadmap without duplicating it.

• The intake funnel: Manage the single intake through which prioritized operational and clinical problems enter, and prepare initiatives for portfolio admission — problem framed with Operations, ROI thesis documented, pod composition defined.

• ROI thesis discipline: Every initiative enters with a documented hypothesis about automation lift, operational improvement, and financial return, and is measured against it. No thesis, no admission.

• The operating cadence: Run the three-gate rhythm — portfolio admission, lock-or-kill at the concept gate, and production readiness — preparing decision materials for the General Manager and the four-leader validation team.

• Kill discipline: Initiatives that cannot deliver against their thesis are killed quickly, deliberately, and without stigma. Own the learning capture so killed concepts still return value.

• Portfolio reporting: Own outcome measurement against baseline and the reporting interface into Control Tower for OW agenda items.

• Product practice across pods: Set the standard pod Product Managers work to — scoping, prioritization, validation planning, and initiative ownership from problem to adoption — within Ensemble's existing toolchain (Aha).

• Design and human-AI interaction: Oversee the interaction design standard for OW outputs, ensuring AI is designed to work alongside operators, not around them.

• Interface to the Product organization: Keep OW's portfolio aligned with Ensemble's enterprise product roadmap and the 15/30/50 automation trajectory.

Required

• 10+ years of product management experience with progressive leadership responsibility, including leading product managers.

• A track record of taking zero-to-one products from concept through validated, deployed solutions — and of killing concepts that did not earn their way forward.

• Experience running stage-gate, portfolio, or investment-review processes with documented business cases and outcome measurement.

• Healthcare domain experience; ability to engage credibly with operational leaders on revenue cycle problems.

• Experience with AI-enabled products and rapid experimentation cycles.

• Executive-level communication; comfort presenting decisions and outcomes to C-level governance bodies.
• Must be inquisitive and demonstrate openness to innovation including AI to explore better processes and ways to alleviate friction and improve patient and client experiences.

Preferred

• Deep revenue cycle management knowledge (patient access, coding, billing, denials, AR, underpayments).

• Experience in an innovation lab, incubator, venture studio, or startup product leadership environment.

• Familiarity with Aha or comparable product portfolio tooling.

• Experience overseeing design or human-AI interaction work.

• 120 days, three gates: Every initiative moves from intake to deployment-ready in 120 days or less, through three decision gates. Killing a concept at the gate is a legitimate, expected outcome — that is the model working, not breaking.

• Multi-hat, startup-like team: Roles here are broader than their titles. Leaders operate hands-on, pods rotate in and out on initiative cycles, and everyone contributes beyond their lane.

• Validated on real work: Front-line Ensemble teammates use what we build on real workflow before anything is locked. Solutions are designed around validated work, not assumption.

• Built on Core: Same codebase, same CI/CD, same Ensemble engineering bar. OW proves it; Core scales it.

• Co-located in Austin: The dedicated team and active pod members work together in person at the OW office. Candidates must currently reside in the Austin area or be willing to relocate; relocation assistance may be available for eligible candidates.

#LI-KS1