Give the reviewer enough context to act
Start with the job you are trying to finish. Name the type of person affected without adding private customer details. Describe the point where the current workflow fails, how often it happens, and what you do instead.
The desired outcome should allow more than one solution when possible. “Reconcile this month’s account activity without copying each row” is more useful than insisting on a particular button before the team understands the problem.
Leave out what does not help the decision
- Do not include passwords, access tokens, personal records, or confidential customer material.
- Label guesses as guesses. A single observed problem is useful without claiming that everyone has it.
- Separate unrelated needs into different requests so each can receive a clear decision.
- Use the product’s support route for outages or account-specific problems that need a private response.
Search before you submit
Look for an existing idea that describes the same outcome. If it matches, add your context there instead of creating a second record. If it only sounds similar, explain the difference rather than treating it as an automatic duplicate.
A customer feedback board gives that search, discussion, and follow-up a shared home. For the team receiving requests, the review workflow keeps approval separate from a promise to build.