Feature Request Evidence Review
Test whether a requested feature is backed by real need.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Test whether a requested feature is backed by real need. Feature request: [FEATURE_REQUEST]. Who asked and how many: [REQUESTERS]. Evidence so far (tickets, interviews, usage data, lost deals, survey results): [EVIDENCE]. Product goals: [PRODUCT_GOALS]. Walk through this tree: 1. What problem is the requester trying to solve? Restate the request as a problem. IF the problem is unclear THEN list interview questions and stop. 2. How many distinct users or accounts have it, and how important are they (segment, revenue, strategic fit)? Distinguish volume from volume of complaints. 3. How often and how painfully does the problem occur? Look for current workarounds as proof of need. 4. Do usage data or behavior support the claim? Compare what people say with what they do. 5. Does it serve the product's goals and the target customer? 6. What is the cost to build, support, and maintain? Are there simpler alternatives (documentation, settings, integrations, services)? 7. What is the risk of not building it? Return a verdict (build, test cheaply, gather more evidence, decline) with the reasons, a table of evidence strength, a cheap validation experiment, and a polite reply template to the requesters. Don't invent evidence.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.