Streamline Sales Discovery with airSlate SignNow

How to create outlook signature

I'm Rohan and I'm a product manager on Juro product Discovery I have 5 years experience at atlassian working on Juro software and Juro product Discovery so I'm really excited to talk to you about this topic today most of you are already using jur software you know the value of having a single platform to plan and track your work but what about all the messy unstructured work that happens before it hits your J backlog where do you capture new feature opportunities start to scope them out and figure which ones you'll work on and in what order today I'll show you how you can do that in the jur platform using a new tool called jur Product Discovery and how you can seamlessly connect Discovery to delivery all in jira before diving in here let's align on a few terms what is product Discovery it's the process of continually identifying the problem to solve for your customers and finding a solution that solves the customer problem is feasible and meets your business goals what's delivery it's the process of breaking the solution into smaller pieces and delivering it in short Cycles to customers when you combine the two you get a continuous loop of identifying customer need and delivering customer value that mutually reinforce one another so why does this matter what happens if you don't have a unified process for Discovery and delivery well I'm sure most of you are familiar with with Jura for the delivery side of this and you use Jura to plan and track the work of your software team with Jura you get the ability to plan assign and track your work and organize it into releases and Sprints but what about the discovery work that I mentioned before all the work that happens before a feature hits your J or backlog where does this work happen for you for most teams the answer is either nowhere meaning prioritization decisions are made by gutfield or everywhere meaning that as a process but it exists across several different tools that aren't purpose built for this job so it's not very effective what if you brought this process into jir and applied the same rigor to it as you do with software delivery we developed a new tool dedicated to this work jur product Discovery before diving into what you can do in Juro product Discovery and how it can help your team let's discuss what we're going to cover in today's webinar we're going to cover collecting new ideas how to prioritize ideas to decide which ones you'll work on when creating road maps sharing them with stakeholders and gaining alignment with the rest of your organization we'll cover how you move to delivery building and deploying software using tools like Confluence jur software and jur plans and finally monitoring and communicating progress with your stakeholders while all the work is in Flight along the way I'll share the tips and tricks that have worked for us the team behind J product Discovery let's get started one of the biggest pain points we hear from product teams is that all your new featur ideas are scattered all over the place maybe you've created an epic in your jur backlog VI you to come back to later or they're in spreadsheets or they're in Confluence documents or notes somewhere on your laptop or forgotten after a whiteboard Workshop this makes it hard to identify Trends and figure out what you should be working on but this process of choosing what to work on is critical to your team's Effectiveness so many teams Chase marginal gains on trying to ship faster but shipping the right thing can have an even bigger impact let me show you ways that Duro product Discovery can help you bring structure and order to this process with Duro product Discovery you can easily add all your ideas and opportunities to a single place so that you don't lose track of them this means you keep a lean clean back log in Jer software that isn't cluttered with things you may not even do ideas in Jer product Discovery can represent product opportunities customer problems areas to explore Tech data initiatives whatever you want and can be at any altitude major initiatives that spend multiple teams projects that take a quarter down to minor optimizations you can add them all as ideas here in jur product Discovery in this example I've got major initiatives it's like the new Rewards program or an Express checkout for my online store I've got Tech debt like upgrading the Java library and small optimizations like landing page copy improvements or browser translations now these ideas that you have here aren't just going to come from you or your product management team they can come from anyone you have control over who can add ideas and even create forms so that they're created in a format that's useful for you in this example we're requiring that anyone who adds an idea needs to write it in the form of a user story so that when we look at this later we have enough context for example you want to gather ideas from your engineering teams they're engaged with your product and are going to have ideas for features and be heavily involved in choosing Tech debt initiatives to support these occasional contributors Geo product discovery comes with two roles paid creators and free contributors and everyone with a J license is automatically a contributor with Discovery and delivery all on one platform that everyone has access to it brings your product and Engineering teams closer together here are all my ideas once you have ideas you can then enrich them with insights located in the insights tab insights are the data points that flush out your ideas and help you make a case in support of or against pursuing an idea they're really flexible you can put anything in here they can be notes from a customer meeting or perhaps your sales team's meeting with a customer there can be feature requests or support tickets from juror service management or whatever CRM platform you use you can have a link to an amplitude dashboard with analysis that you did showing customer Behavior or a monitoring dashboard showing errors for a service that you maintain these are just a few options Dural product Discovery also comes with a Chrome extension that allows you to add insights from wherever you are it's really easy to highlight on a web page and add an inside without leaving your tab let's say I found a great article online about translations here and how they help uh conversion rates for my digital online store with the Chrome extension I can just open this select which idea that this relates to this is relating to translations and I can also highlight text that's going to come saved in my insight it appears here I hit add and I'm done then when I come back here I can go to my insights Tab and see that that inside's there when you combine ideas and insights in J product Discovery there's an easy way to see all of your ideas in one place along with all of the supporting data to back up those ideas all of these ideas can then be filed and visualized in different views here I have a list view the list view is an easy way for you to see all the ideas in your project I'll show you more view types later now let's talk about how we as a jural product Discovery team solve for this ourselves we have a weekly rotation just move this here to get me out of the way we have a weekly rotation where a PM is responsible for reviewing and responding to inbound customer feedback for one week and then we rotate whenever we get feature requests or ideas from customers we add them to our Geo product Discovery project we have a few different channels for collecting these ideas we have an online community with thousands of customers where users ask questions and share best practice our product management team responds to questions and collect that feedback we have dedicated slack channels for all the teams within atlassian using our product to share their feedback we have slack Channels with our sales team and we join them on calls we have an in product feedback form that customers can fill out we're also all regularly meeting with customers and we gather all the notes and feedback from those calls and then add them to J product Discovery then we come together once a week as a team to discuss it share learnings and ask questions for a remote team investing in this ritual builds a shared language and understanding for the team that pays off when it comes to quarterly planning time dur of product Discovery is the one place where we gather all this information that's going to help us decide where we should be investing our time and resources for our team that list view that I showed you this is our long list of ideas we have hundreds in our project it's not perfectly curated some of them overlap a little there might be a few duplicates floating around but we add all our ideas in here so that nothing's forgotten and if we get a feature request for an idea we already have on the list we add the request as an insight to an existing idea it gives us a good feel for how often certain issues are bubbling up the ideas with the most insights are a good starting point for where our customers need the most help so here I can add a field that shows me the number of insights that each idea has and this gives me a feel for where I should be directing most of my energy I can then create more fields to help organize these ideas let's say I'll create a goal field to show themes on our team we use the themes to represent the area of the product like growth Integrations core jobs to be done or Tech de and then we also use fields to represent size we use boulders to represent large initiatives and rocks to represent small improvements when we eventually form our road map it ends up being a combination of some Boulders and some rocks now that you've got a long list of ideas and connected insights but how do you decide what you should be working on and when so often this is decided by the loudest voice in the room or the most senior team member or simply Gutfeld when there should be a process applied to this that allows you to prioritize them Based on data and what's most impactful to your organization and customers Duro product Discovery has many features to help you do this with j a product Discovery you can be as Artful or as scientific as you want it to be you choose the prioritization method that works with you it all starts with Fields fields are the different criteria that you can use to compare your ideas against one against one another there there are many different field types that come out of the box we have radial Fields like impact rating it's as simple as rating something out of five or number Fields like this Revenue estimate field here you can also create custom fields of your choice you can also create a custom formula field to apply math functions to existing fields for example you can create a rice custom formula or value versus effort I've created value versus effort here I just had to write a simple math function on which Fields I wanted to use in this calculation this allows you to adjust your approach depending on the data that you have there are growth teams at atasan who are able to put a specific Revenue estimate on their opportunities based on rigorous data analysis and in other scenarios you're making a bet that the opportunity will have a big impact so a rating out of five is more appropriate a lot of our customers love using the Matrix view to visually compare ideas against each other let's look at the Matrix view here which is comparing Impact versus effort in this example I've got impact on this axis 1 to five and effort on this axis 1 to five you might look at this View and think hold on a second I don't think this idea here should have a higher impact than this idea here this then Spurs a conversation with your team that allows you to align on how the ideas compare against each other it's great to surface opinions about why people think ideas should be scored differently it unearths our assumptions about the problem the opportunity and the solution this discussion helps us build a shared understanding and Alignment in Juro product Discovery you can also use votes and reactions to help build this alignment let's show our voting and reaction Fields so I did a voting exercise here and I can see my reactions here so here's an example you might want to run a workshop with your team and allocate each person three votes to use across 10 different ideas or use reactions with emojis to gather feedback on ideas there's the positive emojis and you can also have the slightly less positive ones as well it's up to you it's very flexible depending on how you want to do it but these votes and emojis are a great opportunity to turn feedback to turn prioritization into an activity to gather the feedback of your wider team for example teams in engineering so that it's not just product managers making decisions in isolation it always pays off to bring product and Engineering closer together and have the wider team involved in the process that comes before delivery it means that once development begins The Wider team has already been talking about these ideas and have an understanding of the what and the why this results in Faster execution when you're in delivery mode we like to say that Juro product Discovery is a canvas for building alignment we believe the process needs to be inclusive and collaborative but that you also need to have a directly responsible individual to make final decisions now let me tell you a bit about how our team the team behind Juro product Discovery does prioritization for our quarterly planning we group our ideas by theme like acquisition adoption or improving on the core jobs to be done reliability and security things like that we then put together a short list of ideas that we think are going to have the biggest impact towards these goals and then as a PM and Engineering leadership team we Spar on those different ideas we'll go away and get more data we'll review our strategy and see what's feasible for example there's no point prioritizing an Enterprise feature unless we're also planning on having all the security features that Enterprise customers require as well without it we'll have no impact we then spar with our engineering and marketing teams to get everyone's feedback it's not an activity only for product managers we need engineering input to find the right balance with tech debt as well to ensure that we're not also drowning in maintenance and ensure that we have the marketing activities to complement our product initiatives this prioritization is a really messy process and that's okay because we end up with the priorities that everyone has had input into now that you know what you want to work on and in what order you need to share this with the broader team like sales and Leadership so everyone understands the product Vision you're working towards to often making road maps means building unique slide decks for each individual stakeholder that quickly gets out of date Road mapping is a Time suck rather than an opportunity to achieve alignment and get everyone excited about your vision let me show you how you can do this more easily in Jor product discovery here's a road map that I've created the goal here of our road map isn't to try and say when you'll do something it's an artifact to communicate your priorities we recommend the now next later format that we have here when you're in front of your sales team or other stakeholders there are times when it's better not to have any dates on the road map you don't want to create a false sense of precision where the sales team thinks that a feature will ship exactly for months and 10 days from now this doesn't help them set the right expectations with customers but this now next later format allows you to keep the information at the right altitude to have a conversation about why things are prioritized in the way that they are in Juro product Discovery you can create different types of road maps and as many road maps as you like to help you tow your product story to stakeholders this is my road map but then I can also group it by by goal like this so I can see which initiatives are contributing towards increasing Revenue winning Enterprise customers and we have quite a few for delighting users I can also group my road map by team as you can see it's really flexible in how you can create these road maps I've got two teams Team Alpha and team beta and I've been able to split the road map based on them so we can see what team Alpha is going to do and what team beta is going to do alternatively I can also create a filtered version of the product road map here I filtered for Team Alpha and I've got a view just for team Alpha's road map and I've done the same for team beta over here here I filtered for team beta now I've got Team level road maps and a product level road map if you want to visualize the sequencing of your work you can also create a timeline view here's a timeline view that I've created earlier the timeline view is powered by dates but with the flexibility of using dates months or quarters depending on how precise you want to be I know when I'm going to start the Express checkout project so I've picked a specific ific date I've got a project start with a precise date but alternatively I could have chosen month or quarter for when I finish I only know about as much as the quarter that I'm going to finish it in that's why I chose quarter here for a smaller project like landing page copy improvements I know exactly when I'll start and I know it's going to take me roughly a month to deliver so I chose to do it month there now that you've got a road map you'll need to share it with your stakeholders we're in the process of rolling our published views to J product Discovery customers with published views you can choose which view to share and who to share with let's show the published view of our product road map so we'll come back here hit publish choose who I'm going to share it with and then I've got setting to configure exactly which fields that my stakeholders are going to see and then I can publish here's a preview mode of the published view you can choose who you're going to share this road map with it could be stakeholders across the business or even customers and it's all down in a restricted environment in a readonly state you can use published views to share progress on a highly requested feature with your sales and support team by sending them a view of your road map you could use it to share an update on your product strategy with your senior leadership team it'll give you a bird's eye view of your focus areas you can use it to share your product Vision with priority customers with a dedicated view just for that customer highlighting the features that they care about stakeholders always have the latest and greatest because information inter a viw gets updated in real time that means no more time spent creating manual spreadsheets or multiple decks no more crowded calendars filled with road map update meetings now let's talk about how us the team behind Juro product Discovery does this process we use our road maps to get alignment both within our individual product teams and with the organization as a whole we use the now next later format just like this to keep conversations focused on goals outcomes and tradeoffs rather than ship dates we have road maps for the product as a whole and one for each team just like this layout here a product road map and a road map for Team Alpha and team beta we use the product level road map when communicating to our stakeholders like sales support and Leadership and our team level road map for internal discussions when creating our road maps and choosing how much we take on each quarter we don't commit all our capacity to these road map items we always dedicate capacity towards addressing bugs and minor enhancements not just filling it up with big projects so that we have the flexibility to quickly address bugs and enhancements with our road map going off track now that you've got a road map it's time to build these amazing features and get them in the hands of customers as you start your Discovery work a lot of steps start happening in parallel product managers are in Confluence writing requirements Engineers are defining technical architecture and doing spikes in jira designers are inigma it's hard to keep track of everything and then bring it all into jira for delivery and once you're in jira it can be hard to break all your work into epics and stories because you need to track down files and links scouted across from different tools and then manually copy them over with everything when everything is on a single platform it takes the manual work out of it let me show you how in J product Discovery we provide templates to help you get started with flushing out your ideas let's cre a new ID here and then there'll be templates to help me get started we have templates for hypothesis testing problem definition solution definition and more I can put in the hypothesis testing template here and it helps me get started on our team we call these one Pages their purpose is to define the problem we're looking to address connected to our strategy and pull together our customer research we typically do this process in Confluence and leave a brief summary back here in Juro product Discovery in J product Discovery we'll just leave a little tweet length summary we have our own template and you can create your own templates as well through this button here when we're in the phase of defining the solution there are a lot of things that you need to get done and these can be planned and track with action items these are action items here it's a really lightweight way to create a list of tasks that need to be completed assign them and track them for example your action items might be to define the problem in alignment with company strategy and goals to validate the problem with five customers to consult with sales to get figma designs and proposed experience approved by the leadership team or to get required technical architecture approved by engineering leadership and then as you go you can just take you can just check them off action items can be used in a very lightweight way to track tasks while some of our customers have preferred to use it much more rigorously for instance some customers prefer to set up a process where all these tasks need to be completed before development can commence this approach helps teams ensure that projects have got undergone sufficient due diligence ensuring that there is enough certainty around requirements experience and approval before any engineering time is wasted you can incorporate these tasks into your idea template so that all your projects adhere to the same Del adhere to the same rigorous process when you're ready to start development you can do so right here from the delivery tab of your idea this means you've got a consistent thread connecting your idea all your relevant documentation to the project for the project through to your tickets in jira from the delivery Tab in a jira product Discovery idea you can create an epic select create a delivery ticket choose which project you want the Epic to go in and the name of the Epic we pre-fill this for you you can name it anything that you want this epic has now been created in that J Project and then you can start creating stories and assigning them to developers and then putting them in Sprints alternatively you can link to an epic that you've already created let's say I already created an epic for the iOS side of this work to complement the Android Epic I can select out a delivery ticket paste that link and now it's stop can remove this placeholder one and I can see that for Express checkout I've got two epics that I need to complete for it iOS work and Android work and they'll be broken down separately one idea in a j product disco one idea in J product Discovery can link to as many juror issues as you like and from any level this model allows for maximum flexibility when you're creating ideas you don't know how big they're going to be at the time that they're going to be ready for development you might have a small optimization that's only a story in that scenario you'd link the idea to the story this model allows you to break down the work depending on whichever way your team chooses to work for example you might like to break up work by the team responsible like having separate epex IOS and Android work like I did before or you might want to create different epics for M dos so there would be one Epic for your V1 release and then you create a separate epic for your V2 release once you have these Jura issues created all the context of the idea is readily available for engineers working on the task in jira you can add a link to the idea in the jir software description and this will embed all the pin fields from the idea in jur into J software here's an example here let's go again create a delivery ticket epic let's make this a new one and this time we'll check for box for embedding the idea description now when I've got my epic injura software I can see all the context from the idea including all of its pin Fields as well coming soon we're going to do do this automatically for you this means that from jur software you've got a live view of the idea in jur product Discovery so if priority changes or other information gets updated for example we've reprioritized an initiative and it's moved from now to later Engineers won't have to get this information um there will be no double handling all the information is going to be at their fingertips with all our work now in jir it's time to plan how we're going to deliver this we can't just throw it all into our backlog and hope for the best shipping value to customers in fast Cycles requires careful planning and tough prioritization decisions with jura's powerful planning and tracking capabilities this is a breeze I'm going to show you how to do this in Jor timelines and plans let's start with jur timelines in Juro timelines you can visualize the sequencing of your work and estimate when you complete it I've got this bar to represent when I'm expecting to do my Android uh Express checkout work and my iOS work is going to start later because there's some other work that's been uh that's uh that needs to be completed beforehand These Bars can then be dragged uh based on your preferred planning time frame not everything you you work on will have gone through the process of Duro product Discovery there are going to be bugs and small things that you didn't plan for that's totally fine those epics and stories should still be tracked here in jir you don't need to add them to jur product Discovery as well and if you have the jur Premium Edition then you have jur plans will you have access to more powerful features for planning delivery here's my J plan to get the most out of using Juro product Discovery and Juro plans together use J product Discovery for your high level prioritization and Road mapping once you've chosen what to prioritize jump into plans and then plan how you'll deliver it with plans you have the option to control the scope of your plan so you can plan out delivery for a single idea which is what I've done here with Express checkout or your teams hold road map or across multiple teams as well with Juro premium you can create custom levels of hierarchy above the Epic this works well when you have a particularly big project to break down in this example we've made Express checkout an initiative which is the parent of Android and iOS work which are epics here my initiative these are my epics which have been broken down here in jur plant you can map dependencies for the complex projects that you have here let's say I've got a dependency on task to uh if I want to be able to start Task 4 so I can drag this afterwards and then also add this dependency here so I'm saying this is blocked by task two and I can put in cst2 here and now that dependency is visualized you can also set your capacity for Sprints and make sure your teams aren't overloaded you can model different scenarios in jurop plans and you can also see all of your work rolled up across multiple projects you can filter and group these group on these views to slice and dice to get a high level View and also drill down into the details I'm in the details here but then I can roll this up to an epic level or even an initiative level everything you do here is in a sandbox environment when you're ready to commit review changes here and then commit your plan to jir so all the changes I've made was creating a dependency and I made some modifications to task two I changed three Fields start date due date and the dependency I hit save changes and now those changes have been committed to jir currently ideas unsupported in jur Plants coming soon you'll be able to visualize and group by ideas in the plan let me show you what it can look like in this example I have an idea and epics underneath it and then I can group and Collapse by the idea so I can visualize that relationship between ideas and epics for now our recommendation is that you create a onetoone relationship between your idea and an issue in jur software in this case I created a corresponding Initiative for my idea with a uh Initiative for Express checkout and then I had epics underneath it the initiative is the parent of these epics and it allowed me to then still Group by initiative back in my plan now how does the Geo product Discovery team go about this on our team we like to use the idea as a central place for all the core information for our project let's take a look at the example from before our idea might look something like this any links to key requirement docs or designs or anything like that I either put in the description over here I've got links to my one pager my my product requirements or my decision log or alternatively I can have them in Fields as well so I've got a field for my figment designs I've also got a checkbox field to be able to communicate when my designs are ready so when my designer feels that these are ready for engineering to pick up they would check this check box over here this is really helpful for our team to stay on the same page and brings our product and Engineering teams closer together while these ideas aren't ready to be worked on all our Engineers are contributors in the Juro product Discovery project so they can come in and take a look at the items that are on the road map at any time they can learn more about upcoming projects to get up to speed and share their feedback this helps our team have a shared understanding of what we're working towards rather than operating like a factory line where product just hands things over to engineering for delivery when we want to get this into Jura most Big Ideas are linked to an epic and if it's small we link it straight to a story our J product Discovery idea contains the why and the what and all the links to requirements and designs so in jur software our epics and stories have very little documentation they used exclusively for task tracking we all know to follow the link back to Juro product Discovery or use the embed to find all the important information and links relevant to that stream of work this avoids us having two different sources of Truth for information that needs to be kept in sync we know to go to the idea and find the links in there this is really important to us while projects are in development requirement and scope will change based on new technical challenges we run into or learning more from customers about what will make a better solution that's why we have that decision log to keep track of the decisions that we made and why we made them at atlassian most teams have their own jur project when we have a particularly complex project that spans across teams we use Juro plant because of its ability to pull in Jura issues from across all of these projects then we use plans to break down all the work into initiatives and epics and stories and then assign them to teams and map out all the sequencing and dependencies it's really helpful for us to get a high level view of the work but then also drill down into the details once planning is done work is in progress Sprints are happening stories are moving from to-do to done the backlog is slowly being worked through of course even then your plans can change you get more customer feedback and realize the solution needs to change you find out that some parts of the solution will take longer than expected so you cut them from scope so you can get the value to customers faster and there's always Tech debt and bugs that need to be urgently prioritized ahead of the feature work this is all part and parcel of shipping software monitoring and communicating these changes can be really hard how do you get a bird's eye view of this and communicate your progress and updated plans to your stakeholders without having to extract the data and create slides that are immediately out of date as soon as you make them or running endless status update meetings let me show you how you could do this in jira in J product Discovery you can create a view like a delivery status view then you can use delivery progress and delivery status fields which come out of the box here I've got delivery progress and delivery status now showing in my view these give me a rough idea of how much work is completed and remaining for my initiatives without needing to get into the weeds of jur software you can include these fields in any View and use it for your own for your own monitoring or for sharing with stakeholders here I'm creating a dedicated view for delivery and I also want to see the goals they contribute to so I just add the goals field here and I can also add these to my road map with the progress visible for my initiatives that are in Flight I go to my product road map view and I can just add in the delivery progress field here now I can see that I've made some progress for Express checkout that there have been delivery tickets created for upgrading the Java Library and landing page copy improvements but they're still in the to-do phase I can also add these fields to another view like my timeline view here we go I've added the delivery progress in and now that it's visible there are different options for calculating delivery progress so you can choose which one is most suitable for your delivery process let's come back into my delivery status View and have a look here when I look in my delivery tab I can configure this first you can choose between default and simple calculations with the default calculation we look at the children of Link delivery tickets I link to epics so with the default calculation this progress bar is based on the children of those epics if I changed it to simple then I would be looking at the epics themselves and you can see how this affected my delivery progress bar alternatively you can switch between issue count and story points if that's what your team uses this means that your progress is going to be weighted by the story points of the issues that you have once I see my default view I can see how that bar changed because my stories had um story points on them we prefer to use the default view just with the issue count now all the dates that you've planned for your work can also be reflected back in J product Discovery for example you may have used J plans to estimate when you'll start and complete your repits which is what we did here for any date field you have you can pull in those dates let's remove my goal field from here and delivery status and now I want to pull in the dates so I can get my project start and project Target dat all right there we go these are the dates that powered my timeline view that we had before that's this one here these are the same dates but now I want those dates to be powered by uh what I planned here in my timeline view so I can go in and edit the field for project start select autofill dates I'm now pulling for my link delivery tickets and because it's the project start I don't want to be using the due date I want to be using the start date and I want to pull in the earliest date as you can see we've got dates from J software for these two initiatives here for Express checkout and upgrade upgrading the Java Library so now the dates are coming from there we can do the same for the project Target I go into edit I order fill dates again and this time I do want the due date and I want the latest of the due dates and it's been updated and I'm pulling from there now this is all on the jro platform so if you change your plan or update any of the dates in Juro software you're going to be seeing the live view here back in Juro product Discovery this gives you a high level view of your progress all in a view that you can configure to to your preference you can visualize this in different ways with views and choose which Fields you want visible we can easily add these fields to all the views created before now my product timeline is powered by the dates from jira and I I can see these dates and also I can do the same in my product road map if I want to as well add in my project start and project Target so now they're visible here this gives you a high level view of your progress all in a view that you can configure to your preference and as I showed you before you can use the publish feature so that your stakeholders will also have this information at hand without you needing to have status update meetings or having to update PowerPoint slides same as before I hit publish I can see a preview of that now how does our team and J product Discovery do this on my team we use the delivery progress bar based on issue count to give us a rough idea of progress and then each week we reestimate when we think we're going to finish we'll start with a really rough estimate like a quarter or a month and then as we get closer to the Finish Line we can narrow it down to a date these dates are really important to us for planning we want to know when a developer is going to finish on a project so that we know when they're available to pick up the next item on our road map today I've shown you how you can use this single platform to do all your product Discovery and software delivery together in a unified way with the best practices I showed you and J product Discovery and J software working together you can drive more impact for your customers and your business if you've not yet signed up for GE product Discovery you can do so for free just follow the URL on the screen or go to the resources tab of the web player thanks for joining and now I'll take some questions thank you hello everybody uh my name is Chris Hall and I'm one of the product marketing managers on Juro product Discovery and I'm joined by our presenter today Rohan um and yeah rohan's gonna answer a few of the questions that you all posed um during the session so first one for you Rohan who can be a contributor and and what can a contributor do into your a product Discovery so a contributor can be any atlassian user so they just need to be a member of your site so they need to have their an atlassian account um be part of your site they don't necessarily need to have access to jir or any other product it's a free role um but you just have to have the atlassian ID that'll be a part of your site you can add them to your J product Discovery project and that means that the contributor can then add ideas add votes add reactions um this works really well for anyone in your organization when you want to work with people in um engineering for example they might be regularly in jira but sales support marketing you can create at lassan accounts for them without being charged and they can be contributors as well so it's a great way to pull in everyone from your organization uh and have that shared brain in J product Discovery wonderful uh next question here is about insights uh so in J product Discovery is it possible to have insights without them being linked to an idea so at the moment the way that we've set things up is uh you have ideas and insights are attached to them insights don't operate uh independently of ideas um we've got a lot planned on our road map to improve our insights capabilities in the future so we'll have more to share um but right now that's that's how things work okay next question is about um best practices so uh what is the best practices to group or organize ideas for example using hierarchies hierarchies um we recommend solving through through Fields so uh ge product Discovery you can put ideas from any level really small or big uh and then I'd recommend creating a field for example a a parent field or a initiative field and that's a way of grouping or organizing these ideas uh to represent some level of hierarchy um again we've done it that way to keep it really simple and flexible for you at the moment um in the future we will have more improvements for for hierarchy um yeah there'll be more to share in the future about this great next question does jur prodct Discovery work with Jura data center if you're currently a Jura data center customer you can absolutely use Jura product Discovery so you'll have your data center product for Jura um in Data Center and Juro product Discovery will be in the cloud Juro product Discovery is exclusively in the cloud so there's absolutely nothing stopping you um from using both Juro data and and your product Discovery and we encourage that um the limitation there is that you wouldn't necessarily be able to uh link to the delivery progress or some of those uh linked um VI ability to link an idea to um jur tickets that I showed you in some of the demos before but it still presents tremendous value for you um to use J product Discovery as a dedicated space for um for uh collecting and prioritizing your ideas and creating road maps and we've got many customers who are currently using Juro data center who use it for that purpose okay next question what do you do if you have lot of ideas and how do you go about avoiding uh duplicates so this one is very relevant to our team our project has a lot of ideas and there are a bunch of duplicates in there as well um there's a few little things that we do to make life easy here so first of all there's a search function um in J product Discovery so you can always search your ideas and find out you know if I've got uh a new one can i s you can first search your existing ideas to see if there's something similar uh like that already uh and if you do end up with a duplicate that's fine you can merge any ideas that you have and that's what we commonly do we'll realize that there's two that may not necessarily be a duplicate but they're overlapping and we want to group them together we want to recategorize them and in that scenario we would um typically use the merge function okay when it comes to customers how would you go about collecting ideas from them uh well in this scenario I would strongly recommend creating a juros service management CU so jur service management is another product from atlassian and it allows you um to essentially have like a a portal for your customers where they can share uh feedback bugs and things like that um this is exactly what we've done in J product Discovery so uh on our team on our product in the bottom left corner we have a little button that says add feedback and that's wired up to a Jos service management cue that goes to the product management team and we review and look at everything that comes from there and uh what we do is we review the ideas that we get from customers and then uh we typically use the Chrome extension that I demoed for you earlier to add them either as insights or new ideas to our project uh we find this works well for us because it means we're not going to have a lot of um I guess duplicates that come in straight from our customers that we've got that level of uh PMS reviewing um inbound feedback and then carefully categorizing it as an idea as an Insight great and then final question here um who can a publish view be shared with um how can you share a publish view with customers so I have great news to share about this um in the demo I said that we're in the Pro in the process of rolling out uh published views to all our customers as of today um we've rolled it out to all customers so any product discover customers is going to have this um available to you uh with this capability you can share it with anyone who has a atlassian account so they don't need to be a member of your site but that um that customer needs to have an atlassian account so you can ask them to create one for free um and that essentially allows us uh to provide the right security layer so we verify who they are through that at lassan account and that allows us to um it allows you to then publish and share it with them um so yeah with the published views you do not have to share it with people who are on your site they just need a atlassian account wonderful well thank you so much Rohan and thank you everybody for joining today um as a reminder this presentation will has been recorded and will be shared with you via email after the event um and be sure to check out our resources tab before leaving today for more best practices from the juror product Discovery team information on how to to sign up for jur product Discovery Etc and have a wonderful day