Stop rewriting your roadmap and publish it
How one Atlassian PM replaced status updates with a live system of truth
Every product manager knows the feeling. You’re deep in a sprint review or halfway through a strategy session when a Slack message lands: “Hey, can you send me the latest version of the roadmap?”
It’s never just one request, either. Marketing wants the roadmap grouped by launch moment; your VP requests a slide format; and legal needs their must-review items. Each request means rewriting the same information in a different way – and by the time you hit send, the content is dated.
Jensen Fleming, Principal Product Manager on Atlassian’s Rovo Agents team, leads about 40 engineers and four PMs to build the custom AI agent platform inside Atlassian Studio. She described this exact spiral during a recent webinar.
“One of the things that brought Jira Product Discovery (JPD) to life for me was how many times I was asked to write a new roadmap page, but in some different format, in some different way, by some different team,” she says.
It’s when she turned to Jira Product Discovery to create a live source of truth that the rewrites stopped. Luckily, building that system didn’t require starting from scratch.
Static roadmaps don’t scale
The core issue is that static roadmaps create more work than clarity.
“My problem with roadmaps and writing things down on pages is that the content is always stale,” says Jensen. “It’s not up to date unless I link back to Atlassian projects.”
This is the trap: You write a roadmap on Monday. By Wednesday, two dates shift and there’s a new project. But the page still says what it said on Monday. Stakeholders read it, make decisions, then discover it’s wrong. Trust erodes, and the next time they need an update, they ping you again – because the last page you sent was unreliable.
Make the roadmap the source, not the summary
Jensen’s breakthrough was deceptively simple: Stop rewriting and start sharing.
She built what she calls her “mega board,” a comprehensive Jira Product Discovery view organized by workstream (Admin, Maker, Platform, Quality, Service) with fields for timeline, delivery quarter, engineers, Atlassian project links, design status, and more. Then she published it as a live, read-only view.
Axel Sooriah, Atlassian’s Product Management Evangelist and Jensen’s host for the webinar, notes that this read-only, always-live view is one of Jira Product Discovery’s most celebrated features. Stakeholders can bookmark the URL and check it anytime.
“Sending the JPD link works 85% of the time,” says Jensen. Each visit shows the current state – not a snapshot from last Tuesday – and updates automatically as dates shift or projects change. “That saves me 15–20 Slack messages a day.”
When a link isn’t enough
Of course, not everyone is satisfied with a link to a board. Jensen estimates that about 15% of the time, a leader wants a consolidated, written view they can read linearly. For those cases, she has two tactics:
Always link back. Every written page she creates links back to the relevant JPD ticket or Atlassian project, so readers can move seamlessly from the summary to live data.
Let Rovo do the writing. Jensen uses Atlassian’s AI assistant to turn a Jira Product Discovery view into a Confluence roadmap in minutes. “I just copy the link, send it to Rovo, and it builds the page for me.” She’s even handled whiteboard requests the same way, pasting in the link instead of rebuilding the roadmap from scratch.
From status reporter to system owner
This shift went beyond time savings to cultural change: Instead of answering roadmap questions, Jensen now redirects them.
“If somebody has a question about the roadmap, I just send them the link,” she says. She admitted this initially rubbed some people the wrong way: “People were like, ‘Jensen and her JPD,'” she admitted. “But then they realized it was actually valuable.”
Over time, the dynamic shifted. Instead of pushing updates, Jensen maintained a system stakeholders could use on their own. The roadmap stopped depending on her, and her team had direct access to the same, current view.
What happens when maintenance stops running your day
Before Jira Product Discovery’s published views, Jensen was stuck as her own assistant — maintaining updates, rewriting content, fielding status pings. Now, she invests that time differently.
“I was so bogged down in the chaos of maintenance and answering questions all the time that I wasn’t there for my engineers,” she says. “Now I’m more available, can think more strategically, and look ahead more than two months in advance.”
Meetings improved, too. Jensen now uses the Jira Product Discovery view as the agenda for triad discussions. The work is already laid out, so the team can make decisions instead of dancing around what to discuss.
If you’re still rewriting roadmaps, start here
Jensen’s playbook is straightforward:
- Publish your main roadmap view. Set it to read-only and share the link with your most frequent requesters.
- Send the link, not the content. When someone asks for an update, send the live URL. Let them bookmark it.
- For the exceptions, link back. If you must write a page, link every item to its JPD ticket so the page stays connected to live data.
- Automate the exceptions. Use Rovo or similar AI tools to generate Confluence pages from your Jira Product Discovery data in minutes, not hours.
- Track the shift. Notice how many status pings disappear when stakeholders can self-serve.
If your roadmap only works when you’re narrating it, it isn’t doing its job. A published, live view shifts the role of the PM from status reporter to system owner. Instead of waiting for updates, stakeholders pull what they need from a single source of truth.
Jensen built a roadmap her team could trust without asking her to translate it every week. And once that system was in place, the Slack question stopped showing up.
Explore Jira Product Discovery‘s view publishing to turn your roadmap into something that updates itself – so you can get back to building what’s next.