Use case
Concept testing
Put an early idea in front of a category audience before you spend a sprint on it.
The problem
Why this is hard today.
The cheapest moment to learn that a concept does not land is before it is built, and that is exactly the moment you have no data. Internal debate fills the gap, the loudest opinion wins, and the first real signal arrives in a store rating six weeks after launch.
How userken does it
Four steps.
- Pick an audience: a whole category, a competitor's user base, or your own app.
- Write the concept as you would pitch it, one short paragraph.
- Run a concept test: userken samples every persona several times, weighted by how large that segment actually is.
- Read the distribution, then the segment split, then the verbatims that explain the split. Follow up on whichever segment surprised you.
run_concept_test
Score a concept across an audience, with segment breakdown.
ask_audience
Any single question, any format, against the same audience.
Concept test template
In-app template with the follow up drill down built in.
Tool names are the MCP tools and in-app templates. The same engines power both.
Illustration
What a run looks like.
Illustrative example, not a result we are reporting
Illustration: a news app considers a 'catch me up' daily digest
- Audience: the news category, all indexed apps, reviews from the last 12 months.
- Question: how interested would you be in a once a day digest that summarises what you missed?
- What you would read: the overall interest distribution, then whether the notification fatigue segment reacts differently from the commuter reader segment, then the verbatims from the people who said no.
Related
Next door to this.
Run a concept testing on your category.
Accounts are provisioned by hand during early access. Tell us the question and the category and we will set you up.