So happy this feature is coming out ! We'd love to join the treeview EAP ! I don't know how I'v missed the announcement 2 weeks ago, we've been waiting for it for the last year.
Our use case : We are starting to use the OST methodology to help in our decision making and internal process (quite close to Teresa Torres' original method). We have set up hierarchies and views as described in your tutorial as well.
I will make sure to gather feedback and send it after a few weeks. Thanks again for developping this !
We were starting to consider building an internal app use the export feature to have a tree view, I'm so glad this is coming out, it will be so much better than what we had in mind.
PS : I thought you switched to an AI team, are you doing both JPD and AI innovation ?
We would love to have the timeline view with high level initiatives. For each initiative we'd like to see all the child ideas and solutions that are in progress, and their placement on the timeline.
Thank you for sharing a great feature. We are now investigating how to work with Ideas in our intake process (which structure we will create), so having a three-view for consideration of what it will look like will help.
Hi Tanguy! We would like access too. We have made extensive use connections to build a hierarchy view and would love to see it depicted visually. We are very interested in leveraging the future design as well (e.g. embedded hierarchy in the Timeline view).
We'd love early access. Our site: lucidlink.atlassian.net
We run a three-level hierarchy in JPD: Opportunity → Initiative → Epic (and Experiment), with everything connected via connectors. The Connections feature has been essential for keeping those relationships intact, but visually, we can only surface one level of parent-child relationship at a time using groupings. To see the full strategic picture, we have to maintain multiple views and mentally stitch them together — which works fine for people who live in JPD daily, but creates real friction for anyone less embedded in the PDLC.
Tree view would solve this directly. Being able to show how a specific Epic connects up through its Initiative to the broader Opportunity, in a single view, without clicking around, makes the strategic narrative legible to stakeholders who aren't in JPD regularly. Right now, that story lives in multiple views plus our Confluence strategy documentation. Tree view would let JPD tell it natively.
On the List view hierarchy improvements mentioned in the article, those would compound the value further. The combination of Tree view and hierarchical List view would substantially reduce the number of views we need to actually manage the work, beyond showing the narrative.
Hi @Tanguy Crusson ! I am wondering if it's not too late to get early access to the Tree View. We are planning on using this to track and bring customer derived features or variations of a product feature back into our main product offering.
Thank you starting this feature, we would like to work with ideas , goals, and and roadmaps and how to have this in our process, would be lovely to have access concerning this to try it out. Thank you
90 comments