Describe your stack. I have Slack, Jira, G-Suite, LucidChart and Notion.
I’d love to know what tools people use for feedback gathering and ideas storage; my roadmaps in notion are beautiful but I don’t love storing general ideas there for some reason.
@AngieGoodwin, what don’t you like about this use case’s notion? We are receiving input from a variety of sources, which I think is fantastic (Support, CRM, Surveys etc.). Therefore, all of ours are linked together via Zapier to an idea database, which nicely categorizes everything for us Additionally, Slack notifications are really useful.
@RobMartin, the two main pain points for me in this situation, in my opinion, are merging duplicates and “closing the loop” with idea creators. I’ve been considering canny for a larger public exhibition.
Oh, I know. You have any experience using them IRL? Aha is a lot and not particularly joyful without a lot of config; I’ve tinkered w product board but never heard very compelling use stories. I like Canny a lot, but worry just how publicly it positions your roadmap.
@KaranTrivedi, I used Aha and experienced the same thing. It was a pain to use. It kind of reminds me of SAP, and I detest that. I didn’t first see the benefit of product board, but after linking it to Intercom and the rest of my stack, it significantly reduced the amount of time needed to gather and organize feedback. Unfortunately, my employer/client at the time preferred to concentrate more on protecting customers’ privacy, thus we abandoned it in favor of feature upvote, an opensource but severely constrained and inferior alternative.
@PriyaVarma, Nice, thanks for the reply.
I’ve seen aha work incredibly well for a product czar with many product teams (my word, he was simply playing head over numerous PMs).
Product boards are intriguing, but I’m not sure if I should attempt them in the product I’m working on right now because I’m still in the early stages and can do whatever I want. However, I really want to design something scalable once.
Canny has been used by a couple of my role models, so I’ll definitely try it out.
Also, yes, Aha does give vibes of SAP or Atlassians less fun products
We use this for user feedback.
Productboard. Since they can detect trends automatically, their new feedback capabilities are quite amazing. You can utilize them to set priorities.
We have a dedicated #feedback channel on Slack where comments can be made by anyone.
I personally classify criticism based on its type. I’ll make a JIRA ticket for it if it’s a bug. I typically read feature requests but don’t act on them. Our brains are really adept at recognising patterns, so if something occurs frequently enough, my brain will typically send me a push notification. If I truly want to read one particular piece of feedback in that situation, I can still return to Slack and do so.
If it’s a feature request for something we’re already working on, I’d try to contact the user and request a user interview so I could delve deeply into the “why.”
Additionally, we have a public board where user requests can be seen and voted on. That’s a fantastic way of letting users know that they have been heard. The upvotes are also useful for identifying some low-hanging, temporary solutions you can roll out while working on more significant, strategic projects that might not be immediately apparent to the public.
I agree that bugs are swiftly added to the ticket board and prioritised.
I like to conceive of feature requests as reading material for design and treat them as ideas, keeping them saved and labelled. If I can link them to themes and high level user problems, and they can be easily surfaced when talking about them, they make up the requirements of other more fully considered projects, or they get designers moving on.
While it’s excellent when they can be accelerated, for the most part they operate around workflows and are only marginally helpful.
I like the idea of ideas coming in from both internal and external sources, having a fast track to get bugs and simple features added to the project board quickly, and having a lean “processing” stage for all ideas that allows them to surface quickly and doesn’t hurt my back while still getting the job done.
Curious, how do you evaluate whether the idea is good?
I only have a passing intuition about how to process it. I’ll draught it as a ticket if it’s instantly applicable to what we’re trying to do, simple to implement, and isn’t a workaround, but otherwise, it’s just material or design inspiration.
I don’t believe it’s a good method to think about ideas because excellent vs. bad has so much to do with what you’re trying to do as a business. They’re all excellent. However, some of them are feasible, impactful, and immediately actionable. Others are incredibly helpful in knowing what we should be constructing in the long run.
I’ve used Canny, Aha, ProductBoard, and ProdPad.
ProdPad was my personal favorite, it was the easiest to use, setup, and gain adoption through the org.
Aha has way too many knobs and switches making it a nightmare to administer and configure.
Nice, thanks. What made you say ProdPad over canny, specifically? Are there any public facing features like Canny on ProdPad?
The complete lifetime of comments and ideas is catered for with ProdPad. It includes an adaptable ideation pipeline that lets you know where an idea is in the process. The particular workflow feature, in my opinion, is what makes ProdPad stand out from the competition.
ProPad includes open feedback portals and customizable roadmaps that you can share with a client via url.
Currently working with a client where we are all in on O365. Teams / Planner / Outlook / Visio. We’re currently generating and storing documentation through Sharepoint.
I know a lot of people don’t like the MS stack that much, but I’m honestly so familiar with Work, Excel, and Visio, that I don’t mind it. Teams is… fine. It’s not great, but I don’t find it as painful as most people seem to, plus there’s pretty decent cross-application integration.
For another client it’s Slack / Jira / Confluence, and I’m using Word & Visio to create branded documents.
Slack / notion / g-suite / paper notes for general stuff
Lou for in app messaging
Segment / g analytics / fullstory for (mvp) analytics
Go links and chrome custom search engines for snappy finding of things
Superhuman for email (I know it’s pricey, but it makes me actually deal w e-mail properly where nothing else did
Greenhouse or lever for ATS - fetcher.ai to fill the funnel and karat to empty it
I know it’s mostly defunct now but I still love redash
Aha / G docs / Jira / Lucidchart / Slack / Typeform / Calendly
I believe TypeForm has hacked the best UI/UX for any form, it’s so sweet and smooth and good lord! I love that typeform and they know their value lol they tease you with just enough features to want you to want to go premium asap