Example context. Preview only. Nothing is submitted.
When to sendA customer wants to do something your product does not yet support.
- 01
Help shape your product
Capture the problem and desired outcome together, before introducing a solution.
See the questions
- What are you unable to do today?
- Start with the situation the customer cannot resolve.
- What would a good outcome look like?
- Describe success before asking for a particular feature.
- 02
A little context
Ask about the workaround and impact, then leave room for an idea. No yes/no gate is needed for an optional suggestion.
See the questions
- How do you handle this today?
- Learn how the customer copes today; an existing workaround can reveal the actual job.
- What does this problem prevent or make harder?
- Understand the cost of the problem before treating a feature request as a priority.
- How might we make this better?
- Keep proposed solutions optional and distinct from the original problem.
Using the answers
Group requests by the underlying problem and who it affects. A proposed solution is a starting point for investigation, not a delivery commitment.
When to choose another form
A feature is broken. A bug report should capture observed and expected behavior instead.
Before you publish
Choose who will review requests and how they will follow up. This form does not promise a roadmap date.
Keep evidence about the problem and its impact separate from votes for a proposed solution.