You’ll run the machinery the product team delivers through. Sprints land because you planned them properly, implementation-raised items move because you triaged them, and the numbers leadership reads are numbers they can trust because you built the measurement behind them. You own the tooling the product org runs on, the reporting layer, and the instrumentation that tells us whether a module is working. You work across product, engineering, implementation and leadership, and you take on strategic projects that make the function faster. You report to the Head of Product.
What you’ll drive
Sprint & Delivery Operations
• Own sprint planning hygiene across the product team: scope committed is scope that can land, and slippage against commitment stays under 15%.
• Run the stage-gate cadence: every gate signed off before the next phase opens, with artefacts current.
• Unblock delivery before it becomes a delay. Escalate with a recommendation, not a problem.
Customer & Implementation Support
• Triage implementation-raised items into the sprint: severity, owner,
and a committed turnaround.
• Keep implementation informed on what made the sprint and what did not, and why.
• Be the routing point between implementation and the module owners, so nothing sits unowned.
Data, Reporting & Measurement
• Own the product team’s reporting layer. Reports that leadership acts on without re-checking the numbers.
• Build the instrumentation behind the KPIs the team is measured on: incident tracking, rework tagging, roadmap milestones, release quality.
• Close measurement gaps deliberately. Know which KPIs have a working system behind them and which do not, and have a plan for each.
Tooling & Platform
• Own the internal tooling the product team runs on: the project tool, the backlog, the integrations between them.
• Fix tooling issues before they spread into delivery.
Strategic Projects
• Take on projects beyond the running workload: a recent measurement system, a pro