An aging platform area needed a full revamp spanning four major flows: campaign management, campaign creation, an asset manager, and asset creation. Rebuilding all four at once was a non-starter; each stage had to ship something usable and de-risk the next.

I built a six-phase roadmap: discovery and foundation, core MVP, asset manager, creation flows, analytics, then polish and scale. Explicit scope lines, a success criterion, and named decision points in every phase meant each stage was validated before the next was committed, so the team never bet more than one phase of work on an unproven direction.

The platform served distinct personas, from hands-on marketers to designers, developers, and enterprise administrators, all wanting 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 phase, written in the standard "as a, I want to, so that" form to keep each need explicit and prioritizable. The divergence became visible: where personas overlapped, conflicted, or where a feature served one group at another's expense. Priorities were grounded in direct customer input, including a design partnership with a major media publisher that co-validated the direction, so every sequencing decision traced to a real need instead of an average user who doesn't exist.

Roadmap decisions lacked a clear read on where the product stood against the market, making it hard to tell genuine opportunity from missing table stakes.

I audited the category's major players on how each handled this surface's standards, from dismissal behavior to template systems, then benchmarked our strongest internal pattern against them and against published industry rates. The findings converted into named opportunity areas that fed straight into the roadmap. With engagement campaigns already clearing industry benchmarks on click-to-install and click-to-open, the roadmap had a clear bar to protect while it closed the gaps.

Planned capabilities read as a scattered feature list, not a direction. Leadership and customers needed the story connecting them: why these pieces, why together, what they add up to.

I shaped a connected vision for a modular system: suggestion, syncing, management, and measurement as four parts of one end-to-end loop. Each module stands alone yet composes into the full visibility and control teams otherwise cobble together across separate tools. The roadmap stopped reading as a feature list and started reading as a direction.