When should we consider JPD Premium?

[Apoorv Sahai]

Hi all,

We currently have multiple product teams onboarded onto their own JPD spaces. As a result, while a few views and fields remain standardized, many aspects of each space have become customized to suit individual team needs.

For example, the Status workflow has been customized by almost every product team to align with their specific processes. However, the Roadmap field continues to follow the standard structure of Now, Next, Later, and Won't Use.

Additionally, for a couple of teams, we have introduced Feedback River, and Design as item types alongside Ideas, allowing them to manage all pre-delivery work within a single platform. As adoption scales, I am concerned that we may eventually run into platform limits, whether around ideas, custom fields, item types, or other constraints.

We originally adopted JPD to address two key challenges:

1. Keeping fragmented pre-delivery work centralized in one place. This objective has largely been achieved.
2. Providing a CIO/CPO-level portfolio view across all product teams.

It is the second objective that I am currently evaluating.

I'd love to hear from teams that have adopted JPD Premium. How compelling has the upgrade been for you? How are you creating a consolidated cross-product leadership view? Are you standardizing certain global fields or columns across teams? If so, which ones have proven most valuable?

Any insights, best practices, or lessons learned from experienced JPD Premium users would be greatly appreciated.

Thanks in advance!

[Daniel Pierce]

Hi @Apoorv Sahai

So far, we haven't been able to justify the jump to JPD Premium. Mostly becayse we don't require the admin features that make up most of the difference. 

As for CIO/CPO level porfolio views, we are using a marketplace app called Released Hub for that. It gives us the portfolio Roadmap views without the need to upgrade to Premium. 

As for the fields and columns, initially different teams used different fields because JPD didn't support global fields early on. We've since standardized most of the fields where it made sense. 

The columns and fields we show depend on the audience. Different departments care about different information, and we create roadmaps tailored for each one. The setup wasn't really the hard part, but working out what exact data we should show to each group is what surprisingly took the most effort. But my advice would be to go that extra mile, as it makes a huge difference in the conversations we have with different stakeholders now. Much more focused on what's important. 


Hope this helps and let me know if you want more detail on any of the above. 

[Vronik]

Hi 

Look at this post, maybe can help you

https://community.atlassian.com/forums/Jira-Product-Discovery-questions/Exploring-whether-JPD-Premium-can-consolidate-multiple-spaces/qaq-p/3283149

Regards