Template

User Research Interview Guide + Question Bank

Why User Research Fails in Indian Startups

Many Indian startups treat user research as a mere formality. A Product Manager hops on a 15-minute Zoom call, shows a user a shiny new Figma prototype, and asks, "Do you like this? Would you pay for it?" The user, acting out of typical societal politeness, says, "Yes, it looks very nice." The PM takes this as validation, the engineering team spends three months building the feature, and upon launch, absolutely nobody uses it.

This happens because humans are terrible at predicting their future behavior. Good user research does not ask users what they will do; it asks them to prove what they have already done in the past. To gather accurate data, you need a rigorous, standardized script that focuses on past behavior, workarounds, and existing friction.

1. Pre-Interview Setup & Logistics

A. The Screener Survey

Never interview random users. You must recruit users who represent a very specific behavioral cohort. Use a tool like Typeform or Google Forms to screen candidates.

• Bad Screener: "Are you interested in personal finance?" (Too broad, everyone says yes).
• Good Screener: "Have you abandoned a mutual fund SIP setup flow in our app within the last 14 days?" (Highly specific, targets a broken UX flow).

B. Indian Compensation Norms

Your users' time is valuable. If you do not compensate them, you will only attract users who have nothing better to do, skewing your data.

• B2C Consumer App Users: Offer a ₹500 to ₹1,000 Amazon or Flipkart gift voucher for a standard 45-minute call.
• B2B SaaS / Professionals: A ₹500 voucher is an insult to an enterprise sales manager's time. Offer ₹2,000 to ₹5,000, or a highly valuable perk (e.g., 3 months of your Pro tier software for free).
• Payout Timing: Always state explicitly: "The voucher will be sent to your email within 2 hours of our call concluding."

C. The Platform & Recording Consent

Use Google Meet or Zoom. Always ask for permission to record immediately at the start of the call. Explain that the recording is "Strictly for my internal notes so I don't have to type while we talk, and will not be shared publicly." If they decline, respect it and take manual notes.

2. The Core Interview Script (45 Minutes)

Copy and paste this script structure into your Notion or Confluence document before the call.

Phase 1: The Warm-Up (5 Mins)

Goal: Build rapport, establish context, and make them feel comfortable. Transition to Hindi or a regional language here if you sense they are struggling with English. Comfort yields better insights than forced English.

• "Hi [Name], thank you so much for joining. As promised, your ₹500 Amazon voucher will be sent right after this call."
• "Is it okay if I record this just for my internal notes?"
• "To start off, could you tell me a little bit about what you do day-to-day?"
• "What does a typical weekday look like for you when it comes to [Broad Topic, e.g., managing your team's tasks]?"
• "If you look at your phone right now, what are the top 3 apps on your home screen?"

Phase 2: Problem Exploration / Discovery (15 Mins)

Goal: Dig deeply into the pain points BEFORE mentioning your solution. You are hunting for their 'Job to Be Done' and their current workarounds.

• "Talk me through the last time you tried to [Perform Specific Task, e.g., reconcile vendor payments]. Walk me through it step-by-step as if you were doing it right now."
• "What was the hardest or most frustrating part about that entire process?"
• (Apply the '5 Whys' Technique here. When they give an answer, ask 'Why was that frustrating?' until you hit the root cause).
• "How much time or money would you estimate that specific problem cost you last month?"
• "What other tools or methods have you tried in the past to fix this issue?"
• The Golden Question: "You mentioned using a custom Excel sheet to track this. Can you share your screen right now and show me exactly how you built that sheet?"
• "What do you absolutely love about the current tool you use to solve this?"
• "If you had a magic wand and could fix exactly one thing about this process, what would it be?"
• "Are you the person who actually makes the purchasing decision for software in your team, or does someone else have to approve it?"

Phase 3: Solution Validation (15 Mins)

Goal: Show them a Figma prototype or the live staging environment. Do NOT pitch the product. Observe their behavior silently.

• "I'm going to share my screen and give you mouse control. Without clicking anything yet, just look at this page and tell me what you think this software does."
• "If you wanted to [Perform Core Action], where would you click first?"
• (After they click) "Was that what you expected to happen? Why or why not?"
• "Is there any information missing from this screen that you would need to feel confident making a decision?"
• "Was anything on this page confusing, overwhelming, or unnecessary?"
• "How does doing it this way compare to how you do it today on [Competitor App]?"
• "If this product was available today, would you pay ₹[X] per month for this specific workflow?" (Note: Take pricing answers with a grain of salt. People say yes easily, but parting with actual money is harder).
• "If this product completely disappeared tomorrow, how disappointed would you be?" (The Sean Ellis PMF Question).

Phase 4: Wrap-Up & Referrals (5 Mins)

Goal: Gather final thoughts and build a continuous feedback loop.

• "Is there anything else I should have asked you about [Topic] that we didn't cover today?"
• "Would you be open to me reaching out in a few months to show you the updates we make based on your feedback?"
• "Do you know anyone else in your network who faces this exact same problem? I would love to speak with them as well."
• "Thank you again for your time. Your voucher is on its way."

3. Specialized Interview Question Banks

Sometimes you aren't doing general discovery; you are investigating a specific metric failure. Use these specialized questions.

A. The Churn Investigation (For users who canceled)

• "Take me back to the day you decided to cancel your subscription. What exactly triggered that decision?"
• "Did the product lack a specific feature, or was it a pricing issue?"
• "What are you using right now instead of our product?"
• "What is one thing we could have done differently that would have convinced you to stay?"

B. The Activation Investigation (For users who signed up but never used it)

• "I saw you created an account on Tuesday but didn't finish setting it up. Did you run into a technical bug, or did you just get busy?"
• "When you first signed up, what were you hoping the product would do for you?"
• "At what exact point in the setup process did you feel confused or lose interest?"

4. Post-Interview: The Synthesis Template

Do not dump a raw 45-minute Zoom recording or a messy 5-page transcript into your team's Slack channel. Nobody will watch it. It is the Product Manager's job to synthesize the data into actionable insights.

Create an Insight Card in your Wiki (Notion, Confluence, or Dovetail) for every interview. Use this exact format: