Example context. Preview only. Nothing is submitted.
When to sendWith people who could use a specific feature but appear not to. Let them correct that assumption.
- 01
A question about {{feature}}
Establish the situation without assuming awareness. People who did not know the feature or already use it can finish here.
See the question
- Which best describes your experience with {{feature}}?
- Allow people to correct the assumption that they are not using the feature. Analytics may have misclassified them.
- 02
A little more context
Only the not-tried and stopped-using paths get another question. Lack of a need is a valid explanation, and a comment is optional.
See the questions
- What has kept you from trying it?
- Ask about the actual obstacle to trying, rather than predicting future adoption.
- What led you to stop using it?
- A person who stopped can describe what happened during real use.
Using the answers
Keep lack of awareness, lack of need, first-use friction, and discontinued use separate. Investigate each with product context; better communication may help where additional code would not.
When to choose another form
You have not defined the feature or eligible audience, or you plan to turn hypothetical interest into a demand forecast.
Before you publish
Choose a relevant cohort using observed behavior, and allow for missing or incorrect tracking.
Use the answers to decide whether to improve discovery, explain the feature, or investigate a usability problem. Do not treat disinterest as a defective response.