Roadmap App
An internal roadmap product replacing a workflow spread across Miro, Excel, and Power BI.
At ZES / Electrip Global, the roadmap was maintained across three tools: Miro for presentations, Excel for data, and Microsoft Power BI elsewhere in the workflow. Every change meant manual syncing, repeated formatting, and extra coordination across teams. This was not an assigned project. Instead of handing over the Figma file my supervisor expected, I proposed a working internal product that could replace the process itself.
Context & Problem
The roadmap served software product management, mobile platform leadership, and the group manager reporting to the CTO. It also needed to stay legible for executives and international investors. But updating it still meant editing three separate tools, reshaping the same data for different audiences, and manually keeping views aligned.
The same fragmentation existed upstream in backlog intake. Requests from country teams were collected across separate files without a consistent scoring, prioritization, or handoff path into the roadmap. The operational problem was not only visibility. It was the absence of one governed workflow from request intake to roadmap publication.
Approach
I designed the product around the workflow the company was already using rather than around a presentation artifact. Claude Code helped with architecture and structure, and Codex handled implementation. To keep the build coherent over longer development cycles, I also set up a custom memory and documentation system so product logic, permissions, and interface patterns could stay consistent as the scope expanded.
The roadmap editor brings Gantt and table views, quarter planning and custom date ranges, per-item health tracking, and progress analytics into one system. That turns roadmap maintenance from a presentation task into an editable product surface.
Gantt view with per-item health, milestone markers, and a quarter-based timeline.
Table view with item health panels and average progress analytics.
I also built the backlog side into the same product. Country teams can submit requests directly, the backlog can be locked for a scoring cycle, and approved items can move into the roadmap without being re-entered elsewhere. The scoring model was based on the weighted Excel method senior product management was already using, translated into a shared application flow instead of replaced with a new framework.
Backlog board where country teams submit and manage requests ahead of scoring cycles.
Around that core flow, I added the supporting systems the process needed in practice: roadmap comments, publishable live or snapshot links with optional password protection, role-based access for viewers, editors, and admins, an admin panel with user management, version history, and activity logs, plus Excel import and PNG or PDF export.
Outcome
I first showed the product to my supervisor, who was expecting a Figma file. The review started with a working web application instead. From there it was reviewed with the roadmap manager, the group manager, and the Platform and Mobile Applications Group Manager reporting to the CTO. Each review moved the product forward rather than sending it back as a concept.
The product has already been approved for internal production deployment under the company domain with company login and company-provided AI subscriptions. The frontend is complete. Backend planning is in progress and currently depends on internal hosting decisions.
The value is broader than consolidating three tools. Once live, backlog requests from country teams can enter through one interface, be scored against shared criteria, and move directly into the roadmap. A manual process spread across multiple files and handoffs becomes one controlled workflow.
Comments and discussion threads linked directly to roadmap items.