Technical Product Owner, Enterprise POS - Masco

Role Summary

The Technical Product Owner, Enterprise POS gathers POS demand and the owner of the prioritized Masco enterprise POS roadmap. This role translates business demand from Business Units, Functions, Centers of Excellence and other partners into defined, prioritized epics the build teams deliver. The Technical Product Owner bridges the "what and why" of business need to the "how and when" within enterprise platform delivery. The Technical Product Owner leads the intake, a cross-functional POS council, coordinates releases across the engineering and BI teams, and owns adoption of what ships. This role is central to ensuring the enterprise POS platform builds what the business needs most and provides transparency for where the enterprise platform is headed in the future.

What You'll Own

Demand Intake & Prioritized Roadmap

Own the single structured intake for POS needs across Business Units, Functions, Centers of Excellence and other partners

Own the prioritized enterprise POS roadmap, reconciling inbound demand with top-down enterprise and BU strategic priorities.

Proactively originate roadmap candidates from usage patterns, retailer data developments, and observed capability gaps.

Stakeholder Alignment

Establish and lead the cross-functional POS council, arbitrating priorities and relieving leadership of ad-hoc intake.

Represent all POS consumers across a variety of use cases and department-specific requirements.

Publish the roadmap and communicate status, tradeoffs, and decisions with clear reasons.

Escalate genuine priority deadlocks to the Data and Tech Leader with a clear recommendation.

Epic Definition, Acceptance & Design Handoff

Define epics — problem statement, business value, and success criteria — and maintain their priority order for the delivery leads.

Route prioritized work through the Enterprise Data Architect's design-authority checkpoint so approved work fits the enterprise model before build begins.

Accept completed epics against their success criteria and formally close roadmap items.

Release Coordination, Adoption & Change Communication

Own the release calendar and cross-team go-live coordination for releases spanning data engineering and BI.

Communicate master-data changes and historical restatements to consumers in advance, with clear "what will change and why" summaries.

Drive adoption of enterprise assets through training coordination, change communication, and usage follow-through.

Lead cross-team dependency and milestone management.

Demand Team Leadership & Capacity Allocation

Hire, develop, and manage the Business Data Analyst function within the demand organization.

Allocate BDA capacity across Business Units and functions as a prioritized, visible resource.

Act as project manager for work across the tech and data team to ensure accurate and timely delivery