Roadmapper

The problem

Nobody could say what R&D was building, why, or when it would launch. Execution lived in the work tracker: tens of thousands of tickets with no shared rules for how teams used it. The planning roadmap lived in a spreadsheet that drifted from reality within weeks. Go-to-market teams found out about releases after they shipped, and leadership couldn't tie R&D spend to outcomes. Every quarter ended in a slide rebuild and an argument about what had actually been committed.

The solution

A living roadmap generated from the work tracker itself. Every big bet and initiative shows a named product, engineering, and design owner, a decision date, its linked OKRs, and real story completion. Claude writes a plain-language go-to-market summary for each one from the ticket descriptions. Quarters lock at the start, so slips show up as drift instead of quiet re-planning. An investment view shows where R&D effort goes each quarter against a benchmark range. A present mode turns the customer-facing part of the roadmap into a ready-to-send deck, with the positioning and product visuals written by Claude. That same idea now runs on the customer side, in a pipeline I helped the product marketing team shape: when work ships, agents draft the release note, the help article, the team-chat announcement, and a short product video for a public what's-new page, and a product marketer approves before anything goes live.

How it works

1. Initiatives, epics, and stories sync from the work tracker every 30 minutes. No one maintains the roadmap by hand.
2. Every initiative carries a product, engineering, and design owner and a decision date. Commitments lock at the start of each quarter, and anything that slips is flagged as drift with its owner and original date.
3. Claude drafts a go-to-market summary for each initiative from the ticket descriptions, and an owner can override it. Present mode turns the customer-facing initiatives into a full-screen deck with a launch timeline, role-tagged pitches, and generated product visuals, and exports it to PDF.
4. Work is classified by type of investment and measured in days of active development per quarter, against a benchmark range over the last six quarters. Untagged work is shown separately so it can't skew the mix.
5. Every sprint, shipped work becomes a launch pack: release note, help article, chat announcement, and a video rendered from code. A product marketer approves it before it publishes to the what's-new page.

The results

• One live roadmap replaced the quarterly slide rebuild and the drifting spreadsheet.
• Every initiative has a named owner, a decision date, and a progress number pulled from real work.
• Go-to-market teams see what's launching before it ships and can present it the same day, then get a ready-to-approve launch pack, video included, when it does.
• Customers get one public page for every release, built from the same data as the internal roadmap.
• R&D investment mix is visible by quarter against a benchmark, which turned "are we spending on the right things" into a number leaders can review.
• I built the first version. The R&D operations team now owns and extends it as a working product, and its present-mode idea grew into the product marketing team's launch pipeline.