Our leadership decided to migrate Yield Analytics into our core product, Monetize. This wasn’t just a technical move: Yield Analytics was generating over $3M in annual revenue, and any disruption risked client churn. At the same time, its workflows were outdated—key forecasting functions were scattered across disconnected pages, forcing publishers to jump between products for yield management, campaign planning, and troubleshooting. This created a clear design opportunity: preserve critical revenue features while modernizing the workflow to improve efficiency and retention.
I led research to understand how publishers actually used Yield Analytics. Key insights included:
To close these gaps, I interviewed internal experts and mapped the end-to-end user journey.
To complement this, I created a “Publisher Ad Agent” with Copilot Studio, anticipating common publisher questions and helping the team ground our design decisions in real user needs.
Using the mapped user journeys, I identified where Yield Analytics features naturally aligned with Monetize workflows. I created wireframes to visualize how those functions could be embedded into existing flows.
Through discussions with PMs and engineers, I facilitated alignment on which features to tackle first. We chose forecast builder because it had the highest user demand, delivered foundational business value, and was technically achievable in the near term.
I led multiple rounds of design iteration, testing, and alignment with stakeholders to refine the forecast builder experience. The solution preserved critical forecasting functionality while addressing key pain points: publishers can now continue directly into next-step actions from the same page, eliminating unnecessary context switching and saving significant task time.
Beyond the immediate solution, I created vision artifacts mapping where Yield Analytics features would live within Monetize. This helped leadership balance near-term delivery with a long-term roadmap.