Does a feature request establish the underlying problem?
A public request for a larger search button may reflect difficulty finding search, a desire for a bigger touch target or simple visual preference. The proposed solution is explicit, but the underlying need may not be. Research should preserve the request while distinguishing documented task evidence from an analyst’s interpretation of the problem it might address.
Separate search-button requests from documented discoverability or tapping problems in supplied posts. Keep unstated motivations unknown and label alternative responses as analyst hypotheses.Capture the request faithfully
Record the exact feature or change requested and the context in which it appears. Include any stated reason separately. Exclude inferred motivations from the request field; an author asking for a larger button has not necessarily reported failed taps or difficulty seeing the screen unless the passage explicitly describes those experiences in relevant terms.
Extract supported problem evidence
Look for a task, obstacle and consequence in the same account or clearly linked context. If none is stated, label the underlying problem unknown rather than inventing one. Keep a public request useful as a solution preference while acknowledging that it does not, by itself, establish the mechanism or breadth of the need behind it.
Consider alternative responses
Where a problem is explicit, list plausible response directions as hypotheses rather than user-endorsed alternatives. Better placement might address discoverability, while larger targets might address documented tapping difficulty. Do not attribute these analyst suggestions to the author or claim their effectiveness without an appropriate evaluation of the actual interface and task under authorized conditions.
Deliver two linked inventories
Provide solution requests and documented problems with links showing where the relationship is explicit, inferred or unknown. Recommend further investigation where the proposed feature outruns the evidence. Avoid collapsing several different problems into one popular feature request merely because that makes a convenient roadmap item for the receiving product team to prioritize or implement.
Keep the boundaries clear.
- An explicit solution preference can coexist with an unknown underlying mechanism.
- Research-context badges do not promise source access, complete history or live verification.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.