A great request explains what it is you're asking for, as well as the underlying reasons for the request. Why is this request needed, where does the product fall short today? It should provide the context of the request, i.e. how you were using a product or feature that led you to feel a gap. Make sure to add any use cases and how you're currently overcoming the problem.
Below are some useful pointers for when it comes to submitting a request
Title: This should be clear and to the point. Avoid vague language and jargon as this needs to be instantly understandable.
Description: This is the meat of the request, and should contain all the information that the Product team needs to make a decision. You should focus on the problem you experienced rather than possible solutions, any context that is necessary for understanding, examples and use cases, and how you currently solve the problem.
Files: Files should be uploaded to add clarity or communicate something that is hard to put into the description. Screenshots should be clear and high resolution.
Product Areas: If the request is only relevant to a certain product area, then make sure to assign it to the correct one.
Tags: Tags help organize the feedback, and so adding relevant tags is a massive aid for the Product team.
Effort: If you're in a position to accurately estimate the effort your request will require, then go ahead and add it in. If you're unsure, leave it for the Product team or Engineers to decide.
Visibility: If you're making a private request, then be sure to change the visibility of your request before you submit it.
- Always try to focus on the problem and not the solution - that's the Product team's job.
- Be specific. Talk about the exact feature or user experience where you felt a product gap. If you have multiple requests that relate to different aspects of the product, make sure to split these.
- If you have context about your use case that could be helpful but not specific to the request, add it in the comments section.