Product·
Identity resolution
How getuserfeedback.com connects the dots when the same person shows up with different identifiers — across devices, sessions, and the login boundary.
Research, ideas, and posts on user feedback and the work of asking well.
End-users decide whether a piece of software belongs in the app they trust in roughly fifty milliseconds. The variable is whether it looks like it belongs.
A theming engine's job is to make the good outcome the default and the bad one hard to reach.
A dark mode is a sign a team cares how its product feels. A survey running in that product matches it automatically, for the same reason the dark mode exists.
Most churn is invisible. The users who leave quietly are the ones you most needed to talk to.
Every named product-market fit pitfall is a different label for the same mistake — building for someone who was not in front of you. The fix is the same too.
The famous engagement thresholds — Slack's two thousand messages, Facebook's ten friends in seven days — are symptoms of fit you already had, not levers you can pull. Using them as goals inverts cause and effect.
Every field you add to signup is a chance for someone to close the tab. Most products keep adding them anyway.
The 40% rule tells you when you have product-market fit. It does not tell you how to get there — that is a different kind of knowing.
Every ask in your product can now carry your name, your photo, and your title. The unit cost of a personal ask drops to zero clicks.
A handwritten Post-it note doubled survey response rates in one famous experiment. Online, the photograph and the first name do the same thing.
Building a survey used to mean filling out a form and imagining the result. Now you edit the survey itself — what you see is what your respondent gets.
For every user who tells you something is wrong, twenty-five say nothing. Some of them are already leaving.