DROPCustomer Discovery Questions: From a Public Post to an Interview
Map an observed task to eight non-leading discovery questions and separate evidence from assumptions.
Short answer. Use a public post to identify a task worth understanding, then ask about past behavior and constraints with permission. Customer discovery questions should clarify what happened, what the person tried and what remains difficult before testing your product idea.
Eight questions grounded in behavior
For an illustrative post about reconciling bookings manually, use the questions selectively rather than reading an entire script.
- When did you last reconcile the bookings?
- What triggered that task?
- Which sources did you use?
- Walk me through what you did.
- Where did the process slow down or fail?
- What did you try to change it?
- What prevented that approach from working?
- What happened when the reconciliation was delayed?
Fill the evidence gap
Illustrative record; no interview is claimed.
| Field | Entry | Interpretation |
|---|---|---|
| Observed statement | Manual reconciliation happens each evening | A public statement, not verified time tracking |
| Unknown | Sources, error cost, frequency and permissions | Ask about actual behavior |
| Hypothesis | A supported import might reduce work | Test after understanding constraints |
| Avoid | “Would you buy my automation?” | A hypothetical yes does not establish demand |
Ask permission for a longer conversation
Start with a useful response to the original question. If a follow-up would help, explain the topic and ask whether they want to continue.
Use the follow-up interview workflow to record consent and stopping conditions.
Find a research question
Illustrative exercise — not a real customer result.
Worth checking: “I reconcile bookings manually every night” suggests asking what cannot be automated today.
Do not count: A profile describing someone as a founder does not tell you their current problem or buying authority.
Next step: Record the workflow and one unknown to ask about. A conversation can invalidate your idea as well as support it.
Try it step by step
- Collect the author’s stated task and exact obstacle before assigning a persona.
- Check which capability of your product addresses it and identify anything you still need to ask.
- Use a relevant, permission-respecting conversation to test that interpretation. Track learned constraints as well as positive responses.
Using DROP for this task
DROP is a social listening and customer discovery tool for product makers and content creators. Paid monitoring supports 4 platforms: X, Reddit, LinkedIn and Threads. Focus includes up to 500 post reads per paid period; Growth includes up to 3,000. Reads are not guaranteed leads. The initial logged-in preview samples X and Reddit.
Inspect a product example · Inspect a creator example · Pricing and limits. Both examples are fictional and need no login. Read a real DROP snapshot with original-source excerpts and limitations.
Can a profile replace an interview?
No. A public post provides context; it cannot establish unstated needs, private attributes or a future purchasing decision.
How should I measure discovery quality?
Count distinct relevant conversations and what you learned from them. Keep raw posts, reviewed opportunities and paid conversions as separate measures.