User Development and Buyer Research

User development is the first phase in the lifecycle of any new product or feature. It is your foundation — without it, your product decisions are guesses. The diversity of users today means that even within a seemingly uniform market, needs differ widely. Your job is to uncover those needs quickly and accurately.

This lesson teaches you how to do that at warp speed — getting the insights your team needs without sacrificing rigor. You will also learn how to find and engage buyers — the people who write the checks — whose problems can be quite different from end users. Finally, you will see how to synthesize your research to make it clear and compelling for your team.

User research is not optional — it is critical

Henry Ford supposedly said, “If I’d asked customers what they wanted, they would have said a faster horse.” Steve Jobs famously said, “It’s really hard to design products by focus groups. A lot of times, people don’t know what they want until you show it to them.” These quotes have led many to question the value of user and market research. “Jobs didn’t do it,” some say, dismissing research altogether.

Let me be direct: experienced product teams value user research as an indispensable tool. The problem is not whether to do research, but how to do it well and efficiently. User research is the compass for your decisions — without it, you are navigating blind.

User development at warp speed

Startups and product teams often complain they don’t have time for in-depth research. The pressure to ship features fast is real. So how do you get quality insights quickly?

I recommend an equal mix of these two approaches:

1. Extended, one-on-one, open-format interviews.
   Face-to-face if possible, or by phone/screen share. Prepare a list of questions designed to elicit detailed responses:

   • “Describe your needs in your own words.”
   • “How else would you solve this problem?”
   • “What do you like and dislike about our approach?”
     This is about panning for golden insights — the unexpected things users tell you that no survey or focus group would surface.
     If you do three of these a week, in 3-4 weeks you will know more about your customer base than anyone else.

2. Narrow, goal-directed, lean-startup style, single-issue research.
   Suppose you suspect prospects are struggling with your sign-up flow. You have several proposed fixes. Which works best?
   Pull a list of relevant customers or prospects. Send personal emails asking for 15-minute calls or screen shares. Confirm they fit your audience. Then ask targeted questions about what they were thinking or trying to accomplish at points of friction — without sounding creepy by parroting log data.
   This focused approach gets you the answers you need to unblock development quickly.

Avoid focus groups and online surveys unless your product is very simple and consumer-facing. Focus groups often waste time because a few participants dominate discussion, and the differences between individuals are often more interesting than group consensus. Online surveys miss the nuances and textures of user responses. You want to ask follow-ups, not pick from predetermined options.

Practical tips for user interviews

• Invite a selective group: current customers, potential customers, influencers, and even those unfamiliar with your product.
• Morning sessions are best — breakfast meetings are cost-effective and participants are more energetic.
• Compensate participants fairly — usually ₹1,500-₹1,600 for two hours in person; ₹400 for phone interviews to cover breakfast.
• Prepare rough wireframes and high-level specs to guide the conversation. Encourage questions and short conversations throughout to keep users engaged.
• Include usability and behavioral questions such as “Do you know where to click for this?” or “How would you open that?”
• Track time spent on each screen or task to identify design pain points.
• Conduct at least two sessions per research topic to get reliable averages.
• Debrief immediately with facilitators and scribes to capture insights while fresh.
• Deliver value to your developers by answering their real questions with real user input quickly — this builds credibility and trust.

Depth of research depends on context

How deep your research should be depends on:

• The goal of the research: Are you exploring new ideas or validating known problems?
• The type and stage of your product: Early-stage startups need broader discovery; mature products focus on optimization.
• The type and stage of your company: Risk tolerance and speed to market vary widely.

For web products, ask:

• Is it a consumer product or do you have a business stakeholder (partner/vendor)?
• Are you trying to learn about customer interests or determine user behavior?
• What’s the time horizon for decision making?

Research is an iterative process that starts with a germ of an idea — a feature request, competitor move, or inspiration from another industry. You define and refine that idea into a clear value proposition. Then you socialize it with product, technology, sales, and marketing teams for feedback and improvement. Finally, you size the market and opportunity, and write the press release as if launching tomorrow.

If your effort is low-risk and low-cost, throw it out there and test. If it’s larger effort, get customers lined up and sell the concept BEFORE you build it. Use research to refine your implementation.

Buyer research is not user research

In B2B and enterprise, users are only half the equation. You must also solve problems for the buyer — the person who signs the checks. Their needs and priorities can be very different.

Buyer research is harder:

• Buyers are often senior and protected from non-urgent meetings.
• Cold outreach is usually ignored or seen as a sales pitch.
• Travel and logistics are expensive and require approval.
• You must convince buyers to talk without triggering sales pressure, which invalidates honest feedback.
• Sales teams want to join calls and sell, which can conflict with your research goals.

The best way to learn about buyers is to sit with them and ask targeted, probing questions. Your goal is to understand their problems, needs, and goals deeply.

Spend most effort trying to talk to potential customers, not just existing ones. The most profitable segment is often those you haven’t sold to yet.

Getting access takes work:

• Source lists from CRM, LinkedIn, social channels, and your network.
• Prioritize contacts connected to you (2nd or 3rd degree). An intro dramatically improves response rates.
• Contact the rest by phone, email, or social outreach, expecting low response rates.
• Have a clear, succinct pitch: “As a VP of X, I believe you face Y because of Z. We are solving that problem and want your help.”
• If you get many rejections, reconsider whether the problem is painful enough.
• Once you secure interviews, plan what you want to learn. Focus on how they solve the problem today — even if it’s pen and paper or Excel.
• Stay on track — time flies in these sessions.

Balancing sales involvement is tricky. A product-focused CEO will support your buyer research; a sales-focused one might not. Make sure leadership understands this is long-term portfolio investment.

If done right, you will build a network of contacts, advisors, and new customers.

Synthesizing research: making your findings actionable

Conducting research is just step one. If you fail to synthesize and communicate your findings clearly, the effort is wasted.

Two tools I use repeatedly:

2x2 Matrix: The 10,000-foot view

A 2x2 matrix helps you simplify complex competitive landscapes into visual quadrants.

• Choose axes relevant to your market (e.g., price vs. feature richness, convenience vs. customization).
• Plot your product and competitors in the appropriate quadrants.
• Identify white spaces and opportunities for differentiation.

Steve Jobs famously used a 2x2 to position the iPhone against competitors, and again to focus Apple’s product portfolio in 1997.

Feature Gap Analysis: The 1,000-foot view

Feature gap analysis compares your product’s features against competitors in a table.

• List features or value propositions as rows.
• List competitors as columns.
• Use “harvey balls” or checkmarks to grade each feature’s presence or quality.
• Identify gaps where your product can uniquely excel.

This tool helps you focus marketing and branding on your unique benefits.

Empathy Mapping

Empathy maps help you organize qualitative insights on what users say, do, think, and feel. This humanizes your data and surfaces stories that inspire design ideas.

Use photos, quotes, drawings, and artifacts from your research sessions to bring your findings alive.

Test yourself: Prioritizing user research under time pressure

Where to go next

• If you want to deepen your user research skills: User Research Methods
• If you want to learn how to turn strategy into vision: Product Vision and Strategy
• If you want to master stakeholder interviews: Stakeholder Management
• If you want to improve your product analytics: Metrics and KPIs