nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Nesting product objectives and product initiatives for a portfolio view

Jonathan Tari

We're hoping to use JPD for a product portfolio overview - so we can look at a roadmap or 10,000 ft view of our division objectives, laddering down to the related product initiatives and even sub-initiative "ideas".

I see in previous threads that nesting is not yet possible and some use fields to create a parent/child relationship - we do that ourselves and have a label to describe whether a JPD card is an initiative or an idea.

Are there any elegant ways to create this overarching objectives view?

Accepted answers

All comments

Tanguy Crusson

Hi Jonathan,

During this webinar we've demonstrated how the JPD team uses a roadmap at 2 levels: one for the overall team, with broad themes, and one for each squad, with more details about each theme. Here's how to replicate this:

Demo: a roadmap with 2 levels

Here's a follow-up to this video, showing how you can show the list of ideas for each boulder when you open the boulder:

Demo: showing the list of ideas when opening a boulder.

Jonathan Tari

Thanks @Tanguy Crusson

We try to use a similar method of filtered views (one for label=idea, one for label=initiative) but we have too many initiatives which change too often (what would be Boulders in your demo) to create different labels for each. Appreciate the suggestion, though.

Perhaps we can try to manipulate the new global fields and expand from a single global JPD project to several (eg: a different JPD project for each product division) but the ideal use-case would be nesting, so we could create more than 1 level. That way we could see objectives laddering down all the way to product initiatives without manually creating labels for each layer down.

Tanguy Crusson

Thanks @Jonathan Tari - That makes complete sense and it's something we're currently designing solutions for (both views with ideas across projects and the concept of hierarchies/laddering up). I'd love your feedback on this concept here (one of the concepts we're exploring):

Early concept: idea types and relationships

Tanguy Crusson

Note: on the "objectives" front, we do have this:

https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Upcoming-product-improvements-Atlas-integration-ready-for-early/ba-p/2195274

(2nd video in this post)

Jonathan Tari

Thanks @Tanguy Crusson , that nested view is fantastic, especially the tree view and the ability to customize the relationships (and add layers depending on the macro/micro specificity) used to define and prioritise our goals <--> initiatives <--> projects.

As for the objectives integration with Atlas - we're not on Atlas so haven't played with this yet. Is it possible to view in Atlas the JPD cards that are linked to this Objective? This would give us a 10k ft view of our objectives and the initiatives that compose each.

Tanguy Crusson

OK cool.

On showing ideas from within Atlas goals / projects: not yet, but it's something we have on the roadmap. For exactly the reason you mentioned

Jonathan Tari

Hi @Tanguy Crusson, if there is an early access program or a way to test out the nested JPD ideas and hierarchies, please count us in! 🙌 😃

Tanguy Crusson

Hi there: you can now start creating custom product hierarchies (e.g. Opportunities-Solutions, parent-child and more) using a feature from the Jira Product Discovery Premium plan.

About the feature:

Custom product hierarchies

About the JPD Premium plan:

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

initiative

product-management

objective

nesting

portfolio