Author: Galaxy Pham
Live demo: https://roadmapping-tool-seven.vercel.app
Repo: https://github.com/Galaxypham/Roadmapping-Tool
Stack: React 18, Vite, Tailwind, @dnd-kit, jsPDF, localStorage
A product intake and roadmapping system built to make the full request pipeline visible and traceable - so nothing falls through the cracks and nobody has to side-channel engineering to get heard.
This page is the launch kit for that tool: the origin story, feature overview, pre-launch planning, launch execution, post-launch operations, demo script, and documentation standards I used to ship and hand it off.
During my time as a Product Manager at Meta, I owned the full enterprise tooling launch calendar across six global regional teams - triaging 100 to 150 requests per half across Security, Finance, Compliance, and Business Development, without direct authority over any contributing engineering team.
The intake process had a specific failure pattern I kept running into:
The instinct is to treat this as a prioritization problem. It is not. It is a visibility problem. Requestors do not bypass PMs because they disagree with the prioritization framework - they bypass PMs because they cannot see the pipeline and do not trust it.
The fix is not a better scoring formula. The fix is making the whole pipeline visible and traceable so that: