Operator Note: Find Audience Evidence Before Product Ideas

A product idea is not evidence of demand. Before deciding what to build, collect the questions, workarounds, and desired outcomes that appear repeatedly in an audience. This note outlines a small, reviewable research process.

Start with observed behavior

Review recent comments, replies, direct questions, call notes, and the language people use when they describe a problem. Record the wording without translating it into a solution too early.

Look for repetition across different people and different moments. One enthusiastic comment may be useful context, but it is not enough to justify a product.

• The problem appears more than once.
• People already spend time or money trying to solve it.
• The creator has credible experience relevant to the problem.
• The desired outcome can be described without inventing a product format.

Build a simple evidence log

Use a small table with the audience statement, source, date, apparent need, and confidence level. Remove private information that is not needed for the decision.

Group similar statements only after reviewing them individually. The goal is to preserve nuance while making repeated patterns visible.

Choose the next smallest test

The next step may be a short interview, a waitlist with clear language, a paid workshop, or another reversible test. The right test depends on the audience, the creator's strengths, and the risk of the decision.

Do not treat sign-ups, likes, or survey enthusiasm as confirmed purchases. Define what the test can prove before running it, then record what actually happened.