How to Talk to Users When You're a Developer, and Find It Deeply Uncomfortable
If talking to potential users feels uncomfortable, that is completely normal, especially for developers, who are often drawn to building because it is something they can do independently, without the uncertainty of other people's reactions. But user conversations are not optional if you want to build something people will actually use. The good news is that there is a specific structure that makes them much less intimidating.
Why developers tend to avoid user conversations
Building gives you control. You define the problem, design the solution, and produce a measurable output. User conversations are the opposite: you give up control, you ask open-ended questions, and the outcome is often ambiguous. For someone who thrives on clear problems and definable solutions, this feels deeply uncomfortable.
There is also a specific fear of rejection, of describing something you have built or are about to build, and hearing that it is not what people want. But this fear is based on a misunderstanding of what user conversations are for. You are not presenting your work for judgement. You are learning about their experience.
The structure that removes the discomfort
The most effective user conversations follow a simple structure: ask about the past rather than the future, focus on behaviour rather than opinions, and listen far more than you talk.
Specifically, ask people to walk you through the last time they experienced the problem you are researching. Not "would you use a tool that did X?" but "what did you do the last time this came up?" Past behaviour tells you what people actually do. Hypothetical questions tell you what they imagine they would do, which is almost always more optimistic than reality.
This structure also takes the pressure off you. You are not the one being evaluated. The conversation is about their experience, not your idea.
What to do with what you hear
Take notes during or immediately after each conversation. Look for patterns across multiple conversations: what phrases come up repeatedly? What frustrations are universal? Where do people describe the same workaround?
Those patterns are your product insight. They tell you what to build, what to prioritise, and how to describe the problem in your marketing in language that will immediately resonate.
Keep reading
Making it a habit
The founders who build the best products are not always the most technically skilled. They are the ones who talk to users consistently, not just before launch, but throughout the product's life. Starting before you build is the best time to start building that habit.
From Passion to Product covers user research methods as part of a structured app strategy process. It is free, and the next cohort starts May 25, 2026.
