Tithi Mondal

Guide6 min readUpdated

User Research for Startups in India: A Practical Guide

User research for Indian startups: how to recruit on WhatsApp, interview in your user's language, what to ask and how to turn notes into decisions.

By Tithi Mondal, UI/UX Designer

What user research is and why founders skip it

User research is finding out how your customers actually behave: what problem they have, how they solve it today, and what would make them switch. It is different from market research, which looks at size and trends. User research looks at individual people and their daily reality.

Founders skip it for three reasons: it sounds expensive, it feels slow, and they believe they already know their customer. The third is the most dangerous. Founders usually know their own assumptions. Talking to ten real users almost always changes something.

You do not need a research team. You need a list of questions, a phone, and a willingness to listen more than you talk.

UX research methods: which one when

There are many UX research methods. A startup needs only a few.

MethodWhat it tells youWhen to use it
Customer interviewsWhy people do what they doBefore design, always
Usability testingWhere your product confuses peopleWhen you have a prototype
ObservationWhat people really do, not what they sayWhen you can visit their workplace or shop
Short surveysHow common something isAfter interviews, to check a pattern
Review miningWhat people complain about in competitorsAny time, free

Start with interviews. Add the others when you have a specific question. For testing, see my usability testing guide.

A step-by-step way to run customer interviews

There are six steps, from the question to the persona.

Step 1: decide what you need to learn

Do not start by asking "what do users think of our idea". Start with one sharp question.

  • How do shopkeepers currently track credit given to customers?
  • How do students in smaller cities decide which online course to trust?
  • How do farmers find out the day's price before they sell?

A good question is about a real activity, not your product. Write down two or three, and let them guide every conversation.

Step 2: recruit on WhatsApp

In India, WhatsApp is the easiest recruitment tool you have. Almost everyone is on it, and people reply to a personal message faster than to an email.

Here is how to do it.

  1. Start with your network. Ask friends, relatives and past colleagues: "Do you know someone who runs a small shop or teaches tuition? I would like 15 minutes of their time."
  2. Ask for introductions, not favours. A warm introduction from a person they trust beats a cold message.
  3. Join relevant groups, carefully. Trade, alumni or community groups can help, but read the rules and do not spam. Ask the admin first.
  4. Send a short, honest message. Say who you are, what you want to learn, how long it will take, and that you are not selling anything.
  5. Offer a thank-you. A UPI transfer or recharge for their time is fair. Say what it is up front.
  6. Aim for five to eight people from the same customer type, so patterns can appear.

A message that works: "Hello, I am building an app to help small shop owners manage credit. I am not selling anything. Could I ask you a few questions about how you do it today? It will take 15 minutes by phone or in person, and I will send 200 rupees on UPI as thanks."

Never use a person's answers or number for anything beyond the research without their permission.

Step 3: interview in the user's language

This is where many founder interviews quietly fail. If your user thinks in Bengali, Hindi or Marathi and you interview in English, you get polite, short and careful answers. In their own language you get stories.

  • Ask the person which language they prefer. Offer a choice.
  • Use a colleague who speaks it naturally if you do not. Brief them first so they ask neutral questions.
  • Do not translate your questions word for word. Rephrase them the way a neighbour would ask.
  • Keep notes in the original language as well. Translating quotes later is fine, but do not lose the exact words people used.
  • Watch for words they use for your idea. If they call it something different, use their word in your product.

I speak Bengali as my first language and work in English too, and I have seen how a single local word can explain something that three English questions could not.

Step 4: what to ask

The golden rule: ask about the past, not the future. People are poor at predicting what they will do, but they remember what they did last week.

Good questions

  1. "Tell me about the last time you [did the task]. What happened?"
  2. "What was the hardest part?"
  3. "What did you do next?"
  4. "How do you handle that today? What tools, people or apps do you use?"
  5. "Have you tried anything else? What happened?"
  6. "How much time or money does this take you?"
  7. "Who else is involved in the decision?"

Questions to avoid

  • "Would you use an app that does this?" People say yes to be polite.
  • "Do you think this is a good idea?" Same problem.
  • "Would you pay 500 rupees a month?" Opinions about price are unreliable. Watch what they pay for today.
  • Questions that already contain the answer, such as "Is it frustrating when it is slow?"

Follow every answer with "Can you tell me more?" or "Why was that?". Then stay silent. The best information often comes after the pause.

Step 5: run the conversation

  • Keep it to 15 to 30 minutes.
  • Ask permission to take notes, and to record if you want audio. Keep recordings private.
  • Start with an easy question about their day.
  • Let them talk. If you are speaking more than they are, change course.
  • Do not pitch your product. You are learning, not selling.
  • Write down your impressions within an hour while they are fresh.

Step 6: turn notes into a user persona

After five to eight interviews, read all your notes. Underline repeated things: the same frustration, workaround or phrase. Group them.

A user persona is a short profile built from these patterns: who the person is, what they are trying to do, what gets in the way, and how they currently cope. Keep it to half a page. Base it on what you heard, and do not invent a stock photo and a fictional hobby.

A useful persona changes decisions. If your main user is a shop owner who is on a budget phone with weak data, that persona will argue against a heavy, image-rich app. That is its job.

What to do with the results

  1. Write down the top three problems you heard most often.
  2. List what surprised you, since surprises are where the value is.
  3. Decide what to change in your plan, such as features, priorities or wording.
  4. Share the findings with your designer and developer in plain language, along with one or two direct quotes.

This is also the material that goes into a design brief. My guide on how to write a design brief shows where to put it. It is the first stage of my own process too: understand before you draw anything. When I worked on apps like a seller marketplace for Tanzania, the questions asked at the start shaped what the onboarding screens needed to do.

A closing thought

You can run a first round of user research this week with a phone and a few messages. It costs very little and tends to save a great deal of build time. If you would like to work with a designer who starts from understanding your users, you can read about my UI/UX design service or write to me through the contact section.

Frequently asked questions

How many customer interviews do I need?

Five to eight from the same customer type is a good start. When you hear the same things repeated, you have likely found the main patterns.

Should I pay people for interviews?

A small thank-you, such as a UPI transfer or recharge, is fair and improves response. State it up front and keep it modest.

Can I do user research without a designer?

Yes. Interviews need only good questions and careful listening. A designer helps later by turning what you learned into screens and flows.

What is the difference between a user persona and a customer segment?

A segment is a group defined by traits such as age or business type. A persona is a short, realistic profile of one typical person in that group, with goals and frustrations drawn from your interviews.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.