Beginner6 min read
Was this chapter helpful?
Share
The cheapest, fastest way to make your app better — and you're probably ignoring it.
When you build something on your own, you fall in love with it. Every button is in the "obvious" place. Every word makes perfect sense. Every feature is exactly what people want.
Then you show it to a real person and they immediately get stuck on something you never noticed. That moment is worth more than a week of solo work. It tells you what to fix.
96%
of unhappy users never complain — they just leave and never come back
5×
more usability problems found by watching ONE person use your app than from your own testing
15 min
of asking people questions can save you weeks of building the wrong thing
You don't need fancy tools. Pick one of these and start today.
After someone signs up or uses your app, send a personal email a few days later. Just: "Hey, you tried [my app] last week. I'd love to hear what you thought — even one sentence helps. Hit reply." Half the magic is that it feels personal, not automated.
Short surveys
A Google Form, Typeform, or Tally form with 3-5 questions max. Share the link in your newsletter, tweet it out, or add it to a button on your site. Long surveys get abandoned — short ones get answered.
User interviews (calls)
The most powerful one. 15-30 minute call with one user. Ask open questions and let them talk. You'll learn more in one call than 100 surveys. Offer a $10-25 thank-you gift for their time.
Casual chats
Friends, coworkers, family. Show them your app over coffee and ask "what would you do here?" Then shut up and watch. The hardest part is not jumping in to explain — let them struggle so you see exactly where it's confusing.
Watch the stats
Even basic analytics tell a story. Where do people leave your site? What page do they spend the most time on? Which button do they click? Numbers don't replace conversations, but they show where to look.
The biggest mistake is asking questions that have a built-in answer. "Do you like my app?"is useless — they'll say yes to be polite. The trick is asking open questions that get real stories.
❌ Useless questions
All yes/no. People will be polite. You learn nothing.
✅ Useful questions
Open-ended. People tell stories. You learn what to fix.
There's a famous book called The Mom Test by Rob Fitzpatrick. The whole idea is that if you ask the wrong way, even your mom will lie to you to be nice. Three rules from the book:
1. Talk about their life, not your idea
Don't pitch. Don't describe. Ask them about how they currently do the thing your app helps with — what they use, what frustrates them, the last time they tried.
2. Ask about specific past behavior, not generic opinions
"Would you use this?" gets a polite yes. "The last time you needed to do X, what did you do?" gets the truth.
3. Talk less, listen more
Your job is to ask one short question, then shut up. The best feedback comes when you're uncomfortable with the silence and the other person fills it.
You don't need a system or a tool. You need 5 conversations. Here's how to set them up this week:
Pick 5 people who match your target user — friends, coworkers, online communities, your email list. They don't have to be strangers.
Send them a short message: "I'm building a tool for [their problem]. Could I show it to you for 15 minutes and get your reaction? I'd love your honest take — even if it's 'this is bad.'"
Schedule a 15-minute call. Show them your app. Don't explain anything. Watch them try to use it.
Ask: "What were you trying to do? What was confusing? What would make this useful for you?"
Take notes. Look for patterns across all 5 people. The same complaint from 3 different people = your top priority fix.
Collecting feedback is the easy part. Acting on it is where most people fail. Don't fall into these traps:
Building everything anyone asks for
Wait until 3+ people ask for the same thing. One-off requests usually come from edge cases. Patterns matter, single voices don't.
Defending your design when they don't like it
Don't argue. Don't explain why it's "actually" right. Just say "Tell me more." You're trying to learn, not win.
Ignoring negative feedback because it stings
The hardest feedback is the most valuable. The people who care enough to complain are the ones who care enough to come back if you fix it.
Letting feedback pile up unread
Every Friday afternoon, spend 30 minutes reading the week's feedback. Sort into bugs, ideas, and vibes. Pick the top 3 things and add them to next week's work.
Before you spend another month polishing your app, do this: find 5 real people in your target audience and watch each of them try to use your app for 15 minutes. You'll find more problems in those 75 minutes than in three months of solo work — and you'll fix the right ones, not the ones you imagined existed.
Build this with AI
"I want to add a small feedback widget to my app — a floating button bottom-right that opens a simple form. The form should ask one question: "What were you trying to do?" with a textarea, plus an optional email field if they want a reply. Save submissions somewhere I can read later (use the simplest option you can — a database table or even an email to me). Don't over-engineer it."
ADD A SIMPLE FEEDBACK BUTTON
"Add a small feedback button to my app, in the bottom-right corner. When clicked, it opens a tiny form asking "What's on your mind?" with a text area and a Send button. After they hit Send, save the message somewhere I can read it later and show a friendly "Thanks!" message. Don't make it complicated — keep it as simple as possible."
EMAIL ME WHEN SOMEONE SENDS FEEDBACK
"Whenever someone sends feedback through my app, automatically email me the message at [your email]. Include the time they sent it and (if they're logged in) their name and email. That way I see new feedback the moment it comes in instead of having to check a dashboard."
ADD A POST-SIGNUP SURVEY
"Right after a new user signs up to my app, show them a one-question survey: "What are you hoping to do with [my app]?" with a text area. Save their answer with their account so I can read it later. Make it skippable — don't force anyone to answer."
