Talking to Real Humans About What You're Building

The scariest thing I've done in this whole process is not any of the technical stuff. It's not the databases, not the deployments, not the moment I nearly deleted production.

It's showing a half-built app to another human being and watching their face.

There is nowhere to hide in that moment. The thing you've been polishing for weeks, that lives in your head as nearly perfect, meets a stranger's actual eyes, and they immediately do not understand the button you thought was obvious. They tap the thing you didn't want them to tap. They ask a question that reveals the whole first screen doesn't say what you thought it said. You die a little.

Do it anyway. Do it early. Do it often.

Here's what I've learned about these conversations:

1. Show sooner than you're comfortable with.

The instinct is to wait until it's "ready." It will never be ready. If you show it at 40% done, the feedback will change the direction of the 60% you have left, and that's the whole point. If you show it at 95% done, the feedback is a threat rather than a gift — you're too close to the finish line to change anything meaningful.

2. Do not present. Watch.

The temptation is to walk them through it, narrating: "and then you click here, and this does this..." Don't. Hand them your phone or laptop, say "try to do X," and then shut up. Every word you say during their first attempt is a word that will make you miss what they actually needed to do without you.

3. Their confusion is the most valuable thing in the room.

When they hesitate, don't explain. Write it down. When they misunderstand a word on a button, don't defend the word. Write it down. When they say "wait, is this the same thing as that?" don't clarify. Write it down. Every point of friction is a bug report from the future, delivered for free.

4. Ignore compliments. Chase questions.

"This is really cool" is meaningless. It's what nice people say to their friends. What matters is what they ask after the compliment. "This is really cool — so does it also do..." That "so does it also" is where your next month of building lives.

5. You'll want to argue. Don't.

The first time someone tells you the thing you built is confusing, your whole body will want to explain why they're wrong. Every atom of you will want to say "well, actually, if you just..." Bite it back. Nod. Ask a follow-up question instead. "What made you tap that?" "What did you expect would happen?" You are not there to defend. You are there to learn.

Who to talk to: not other builders. Not your closest friends (they'll be too nice). Not your mother (God bless her). You want people who are close to the person you actually built this for. If you built a tool for small-restaurant owners, find one small-restaurant owner. Buy them coffee. Show them the thing. Ten minutes of that is worth a hundred hours of guessing.

What I'd tell someone in my shoes: this is the part of building that most makes you feel like you're not a real founder. Doing it anyway is exactly what makes you one. The willingness to be embarrassed in front of a stranger, on purpose, in exchange for the truth — that's the whole game.