An aging platform area needed a full revamp spanning four major flows: campaign management, campaign creation, an asset manager, and asset creation. Rebuilding all of it at once was a non-starter. The work had to be sequenced so each stage shipped something usable and de-risked the next.

I built a phased roadmap: discovery and foundation first, then a core MVP, the asset manager, the creation flows, analytics, and a final polish-and-scale phase. Every phase carried explicit scope lines and a success criterion, with named decision points between them so we validated each stage before committing to the next.

The platform served several distinct personas, from hands-on marketers to designers to developers to enterprise administrators, and they wanted fundamentally different things. A one-size-fits-all roadmap risked building for an average user who didn't exist.

I mapped the work into user stories grouped by persona and by phase, written in the standard "as a, I want to, so that" form so the underlying need stayed explicit and prioritizable. That made the divergence visible: where personas overlapped, where they conflicted, and where a feature served one group at another's expense. I grounded the priorities in direct customer input, including a design partnership with a major media publisher who co-validated the direction, so every sequencing decision traced back to a real need.

Roadmap decisions were being made without a clear read on where the product stood against the market, so it was hard to tell a genuine opportunity from table stakes we were simply missing.

I audited the major players in the category, comparing how each handled the standards in this surface area, from dismissal behavior to template systems. I benchmarked our strongest internal pattern against them and against published industry rates, then turned the findings into concrete opportunity areas that fed straight into the roadmap. Engagement campaigns here were already clearing industry benchmarks on click-to-install and click-to-open, which set the bar the roadmap had to protect while it closed the gaps.

A set of planned capabilities read as a scattered feature list instead of a direction. Leadership and customers needed a story that connected them: why these pieces, why together, what they add up to.

I shaped a connected vision for a modular system where each capability stands on its own and composes into something larger: suggestion, syncing, management, and measurement as four parts of one end-to-end loop. The narrative made each module independently valuable while showing that together they give teams the full visibility and control they're otherwise cobbling together across separate tools. The roadmap read as a direction.