Ad-product requirements
Contributed to Home Page Hero requirements and translated the advertising experience into scheduler needs, workflow logic, data requirements, and acceptance criteria.
Ad-product requirements, workflow design, testing, and enterprise systems integration for a major multi-year cross-screen advertising initiative.

TiVo One brought together teams across product, engineering, data, platforms, monetization, and operations. I participated in broader product discussions, helped define requirements for the Home Page Hero advertising experience, and led the operational and systems work needed to make the new product sellable, schedulable, testable, and supportable.
My primary ownership connected the Salesforce scheduler experience with targeting and forecasting, internal campaign-management workflows, Google Ad Manager, billing, reporting, and the people responsible for delivering campaigns.
Public language intentionally abstracts confidential internal system names and implementation details.

Contributed to Home Page Hero requirements and translated the advertising experience into scheduler needs, workflow logic, data requirements, and acceptance criteria.
Created visual mockups and experience specifications for new Salesforce Lightning Web Component pages; Engineering completed the coding.
Planned how information moved across targeting, internal systems, ad serving, delivery, billing, and reporting through two launch phases.
Drafted test cases, led end-to-end user testing and training, coordinated regression testing, and incorporated stakeholder feedback before deployment.
Two phases of TiVo One and Home Page Hero capabilities were successfully deployed across Salesforce and connected operational systems. The work established a clearer end-to-end path from opportunity and order to targeting, scheduling, delivery, measurement, billing, reconciliation, and cash—while preparing Sales and Operations to support the new premium advertising experience.
The ad experience could scale only when product behavior and operational execution were designed as one system.
Schedulers needed confidence without seeing every layer of system complexity.
Product quality depended on validating the complete journey—not only individual interfaces.
User testing, training, and stakeholder feedback improved functionality before each deployment.
The most valuable result was a clearer operational model that helped schedulers, product teams, engineers, and business partners understand how planning, targeting, delivery, billing, and reporting connected.