Two people can tap the same button for completely different reasons.
That’s a design question I’m exploring with Callout, a social debate app where opinions receive Based or Hot Take votes.
“Hot Take” might mean:
- I disagree.
- This is controversial.
- This is an unusual perspective.
If people interpret a vote differently, the total can look precise while its meaning remains unclear.
The test I want to run is simple: show someone the interface, ask what they expect each button to do, and compare that answer with the intended behavior.
Before adding a tooltip, I want to understand whether the label itself works.
How do you test UI wording in your projects?

Top comments (1)
Two answers, one on the test itself and one on what sits under it.
On the test: asking what someone expects a button to do invites prediction, and people are generous predictors. You'll get plausible answers that all sound fine. Ask for recall instead. Show the label and ask them to describe the last thing they read that they'd have pressed it on. Concrete memories disagree with each other much faster than hypotheticals do, and that disagreement is the signal you want.
On what sits under it: your three readings of Hot Take aren't really a wording problem. They're three different things the product could be counting, and the label is being asked to pick one after the fact. Worth writing the single sentence that says what a Hot Take vote means, then showing that sentence to whoever else is building Callout before you touch the button. If the sentence is hard to write, no label rescues it, and a tooltip just moves the ambiguity one tap away.
The precise-looking total you mention is the part I'd worry about most. A number that sums three meanings is worse than no number, because it survives review.