What makes a great product feedback post
Hello all! Sara from Asana’s implementation team, with a few tips about writing great product feedback in the community.
We get such rich information from all of you about what’s most important, alongside invaluable insights about use cases and pain points. When we forward this feedback on to product, the most compelling stories contain all the detail needed to understand and prioritize the request. To that end, consider including the following information in your post:
- Outline your use case. How do you and your team use Asana? Be specific.
- Frame the feature request in context of how your team is using Asana. The better we can understand how the feature request/bug fits into the workflow, the more streamlined it is for us to help sort and prioritize in our Voice of Customer process.
- Help us understand the impact this is having on your team. We want to know – is this having a critical workflow impact that’s affecting your team’s ability to use Asana? Is this driving work outside of Asana, or causing roadblocks in adoption? Or, does this feel like more of a nice-to-have?
- List any workarounds you may have employed. We’re interested in what you may have already tried in lieu of seeing a product change, and to what degree this is solving for the issue.
- Our marketing team has moved to a Board view for incoming requests. Each Task in the Project is a request for the Marketing Operations team to fulfill for another cross-functional Team. We also use Custom Fields for Priority and Status, which helps our team prioritize our work.
- Being able to see Custom Fields on the Board View would save time for our team, as well as help with adoption of Asana.
- Clicking into each card to see the Priority in order to put the card in the correct column takes a long time, and frustrates some of our reluctant adopters.
- We tried the same view in a List, where we could see the Custom Fields, but we prefer the Board view for ease of use and clarity of stages.
The above testimonial can easily be categorized with product component and workflow impact, and empowers our customer operations team to specifically prioritize (and advocate for!) this change. In addition, it helps enrich the conversations in the community, as other members can read and learn from your workflows, workarounds and creative requests.
As always, thanks for your partnership and thoughtful feedback Looking forward to continuing to read and learn from all of you!