Don't start from blank.
Start from proven.

Letting users and internal teams propose product improvements, in a way that yields the underlying user problem and its cost rather than a bare feature spec.

A periodic deep-dive with users of a product, feature, or experience: satisfaction, real usage, likes, dislikes, friction, and gaps, ending with where they'd spend your next improvement cycle.

Collecting actionable bug reports from customers or internal testers: what broke, how to make it happen again, how bad it is, and the environment it happened in.

A general-purpose qualitative interview about how users actually work, grounded in recent concrete examples.

A jobs-to-be-done discovery interview run before you build: the situation that triggers the need, how people cope today, what they've tried, and the forces that would govern a switch.

A structured market-research survey showcasing the full question-type palette.

Screening volunteers for usability tests, interviews, diary studies, or beta programs: role, experience, real behaviors, tools, availability, and contact details, all in filterable structured answers.

The follow-up conversation after a participant attempts tasks in a product or prototype: completion, difficulty, confidence, and a deep dig into every confusing moment while it's still fresh.

Testing a product, feature, or business concept with target users: comprehension, perceived value, fit, concerns, and honest likelihood of use, with the reasoning behind every judgment.

Willingness-to-pay research in the Van Westendorp style: current spend, perceived value, the four price anchors from suspiciously cheap to out of the question, and the reasoning behind each.

Post-play feedback after a playtest, demo, or early-access build: how someone played, whether they'd come back tomorrow, what stuck with them, and the moment that nearly ended the session.