For the teams that decide
For product teams
Kill the wrong idea on Tuesday instead of in the next release retro.
Why
Kill the wrong idea on Tuesday instead of in the next release retro.
Product decisions are made weekly and researched quarterly. userken closes that gap: put the concept, the flow, or the two competing defaults in front of a category audience in the time it takes to write the question down.
Where it fits
In the week, not the quarter.
Before the sprint
Concept test the idea against the category, not against the room.
During the spec
A/B/n the two defaults you cannot agree on, and see which segment each one serves.
After the ship
Ask the same question again and watch the distribution move.
On the roadmap call
Bring the segment breakdown, with quotes, instead of an anecdote.
Start here
The three that land first.
Concept testing
Concept testing
Put an early idea in front of a category audience before you spend a sprint on it.
A/B/n testing
A/B and A/B/n testing
Rank options against each other instead of scoring them one at a time.
Focus groups
Focus groups
Moderate a conversation with five to eight personas and follow the thread.
Put it in front of your team.
Early access accounts are provisioned by hand. Tell us what your team keeps arguing about and we will set you up.