Have a question about Productboard? Ask here.
- 223 Topics
- 679 Replies
In some cases, especially roadmaps, it’s hard to show a roadmap when the entire hierarchy (including components- representing the opportunity tree). So I’m showing only features.The issue with that, when someone is looking at a feature on the roadmap and asking themselves for the user need driving this solution, how can they get to the component parent from there? The hierarchy field of the feature seems trivial for this, but that field is used to change hierarchy, not as a breadcrumb to get to the component.Thoughts?
I am working on an integration with inSided + Zapier + Productboard and I’m wondering if there is a possibility to populate the company field in Productboard when adding a new note through the Zapier integration?The only thing I seem to be able to add is customer user name and email, but not the company itself.
We’re defining our detailed releases either by sprint or by month. I see that we can align the specific features to a release, and then associate that release with a date / timeframe. This will work perfectly when we generate internal timeline-based roadmaps.I’m unsure how to leverage the ‘now’-’next’-’later’ capability since that should roll with the calendar. We’d like to leverage this vagueness when communicating roadmaps outside the organization. Therefore, ‘now’ = this quarter; ‘next’ = next 1 or 2 quarters & ‘later’ is after that. And then sometimes, next might be 4 months vs. 6 depending.I see that we can use release groups to define more than one ‘bucket’ for each feature to assign it to the specific sprint release & also to a release called “now” & ‘next’. I thought maybe we could do this by using release groups & moving the monthly or sprint release from one group to the next as the dates roll, but this doesn’t seem possible.Is the answer that we assign
Hi everyone!We are using productboard for high-level roadmap with Now / Next / Later / Finished / Parked releases. We do not really need status information, because the assigned release makes the status clear already (e.g. Now = in progress).On the other hand we are using emoji to indicate a dependency or some special attribute. The red sign means “this item depends on the work of another team (of another company)”. It works well, because on roadmap views these items stand out nicely.I was wondering I should rename statuses roughly like “regular item”, “dependent on this other team”, etc. and remove the emoji. So, I would use status more like a tag or so, because it does not take much space on roadmap views, and currently status field does not add any value for is, it just creates work.What do you think?Thanks a lotMartin
Product Makers, as our favorite Productboard enthusiasts, we wanted you to be the first to know about our exciting new learning platform! 👀 Productboard Academy teaches our customers how to harness Productboard to become better at their jobs. Over the years, many of you have created your own internal resources to deliver Productboard onboarding at scale. Meanwhile, our Customer Success Managers and Coaches were developing a wide breadth of resources which were only available through 1:1 sessions. We realized we needed we needed to address our own job to be done: Onboard our users and help them grow their careers - at scale. Ever wanted to deep dive into Productboard - at your own pace? Ever thought, “I understand how to do this in Productboard, but I’m not sure how I should do this in Productboard? How do other companies set this up? Am I doing it right?” Ever wish you had time to onboard new members of your team to Productboard properly?If so, the Productboard Academy is for you! Wh
Hello, Product Makers! Diana from Customer Education here, with this month’s exciting array of hands-on clinics, live trainings, drop-in office hours and more.NOTE: Did you hear the news? Live trainings have been moved to our brand new Productboard Academy! Learn about it here. We recommend logging into Productboard before accessing the Productboard Academy for the first time. Weekly events Every Tuesday: Productboard 101Formerly known as “Getting Started with Productboard”New to Productboard? Get started with our 30 minute webinar covering the basics, with an optional 15 minutes for Q&A. We’ll show you how to turn customer feedback into actionable data, make quick feature prioritization decisions, and create simple roadmaps for your colleagues.Europe session: 10 AM Ireland Standard TimeNorth American session: 10 AM Pacific Standard Time Every Thursday: Productboard Coaching Office HoursFormerly known as “Live Productboard Coaching”Want to ask our team of Customer Success experts
Hi,I am in conversation with the team that administers our Salesforce implementation around getting it integrated with Productboard. From my basic understanding all that is required on the Salesforce side is to setup the connected application credentials, and that all the field mapping is done on the Productboard side.Can anyone confirm this please, roughly how much time does it take to configure the Salesforce side of this integration, and how much involvement is required from the Salesforce admins?I would like be able to confidently tell the Salesforce team how much of their time I need to implement this, is it a 15 min job or closer to a few days worth of time?Thanks for your helpRegardsDarren
Hi there, we are using Now/Next/Later/Finished/Parked column roadmaps a lot and we are using “releases” for this. This works fairly well.Additionally, we are maintaining the status of each item (New Idea, Candidate, … Release), but for no real reason, just to keep it clean. We are not using roadmap view based on status.I am annoyed by double the effort, I would ideally just turn off the status field (and colors) at all.Another idea, shouldn’t we stop using the releases field (and maybe use later for real releases) and only use status, and rename them to Now/Next/Later/Finished/Parked ?Sorry for this rather unstructured thoughts? Our main pain point is the doubled effort of maintaining releases and status but they are currently mean basically the same for us.Thanks for your input!Martin
Hey!I wanted to share the success I have had using PB for capacity planning. I’m not sure how it is for everyone else, but in addition to all of the functionality which PB offers, our Product directors and VPs need very detailed views of how much investment we are putting into each product domain for the upcoming quarters, and if we have met our predefined goals.In order to make this work, beyond the basic feature columns PMs need to planning, I also added “product goals” (custom dropdown), “KPIs” (objectives), “constraints” (release group) and “market segment” (release group). Using the integration with Jira, I had the PMs push their features into Jira, where our R&D Team Leads updated the story points (which auto-populated in PB in our effort column via the bi-directional integration). This was awesome, because it helped us circumvent the licensing issue - we only want PMs and Product Leads in as Makers in the PB space; R&D are only Contributors. This of course means that R&
If you’re on the product team, have you had more luck using the extension yourself? Or have you tried equipping folks on sales/support/success with the extension to facilitate submitting product insights? Do you tend to use the extension for submitting feature requests? Or capturing ideas/inspiration as you browse other sites/products/social media? Either way, would be interested in hearing any successes you’ve had!
Hello there, On March 30 we will be sharing a talk about how Productboard uses Productboard. We have shared the views that Productboard leverages in our every day work, but we are also curious how each of you best leverage Productboard? Sharing any relevant views will help our entire community get inspiration and up-level their practices as well :)
Hi - so I’m hoping this is a temporary problem.MissionMy new Marketing and Sales team members planning our initial application launch with me have asked for a document that lists every feature with the “What” and “Why”. It would be great if they would just go into Productboard and I could just share the feature views I have created. But so far all the collaborative work they want to do is in Word docs and Google Sheets, etc.Rough RequirementsI don’t want to write this all twice or manually copy and paste all the feature descriptions. I don’t really want to maintain two documents I want to preserve links and images I want to minimize the steps it takes to do itFirst TryMy Tools arePB Pro Excel Notepad++ with the MarkdownViewer++ plugin WordProcess Use the Features export end point (It’s in the help docs) to get my CSV that has all my stuff Highlight everything and make a Table in Excel Filter to match my Release-based Views Insert a column to build my content. In this case I’m ju
Hello, Product Makers! Diana from Customer Education here, with next month’s exciting array of hands-on clinics, live trainings, drop-in office hours and more. Weekly events Every Tuesday: Getting Started with ProductboardNew to Productboard? Get started with our 30 minute webinar covering the basics, with an optional 15 minutes for Q&A. We’ll show you how to turn customer feedback into actionable data, make quick feature prioritization decisions, and create simple roadmaps for your colleagues.Europe session: 10 AM GMTNorth American session: 10 AM PST Every Thursday: Live Productboard Coaching Want to ask our team of Customer Success experts about how to set up your Productboard account? Need to bounce a few ideas off of someone about your strategy? Live Productboard chats are open-ended conversations with Customer Success Coaches and other users. Stay for the entire session – or just swing by during a free moment!Europe session: 10 AM GMTNorth American session: 10 AM PST Special
Daily / weekly summary for users that just gives them the updates of the tickets that they are following in Productboard?
Is there a way for us to set up a daily / weekly summary for users that just gives them the updates of the tickets that they are following in Productboard? It seems there are instances where some users feel they are now receiving too many updates and they just want a summary to be sent to them. I myself receive the below summary on a daily basis. However, I have found that a lot of the updates on this summary are for tickets that I have not followed directly in Productboard. It's a summary for a lot of the tickets don't directly relate to what I'm working on. I don't mind having exposure to what other teams are working on, but it might be good to have some summaries that are perhaps more targeted to the intended audience?
Create an account
You can create an account below using either single sign-on or a username/password. Already have an account? Login.
Join or Login
No account? Create an account
Single sign-onEmployee login Log in with Productboard
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.