Try : Insurtech, Application Development

AgriTech(1)

Augmented Reality(20)

Clean Tech(8)

Customer Journey(17)

Design(43)

Solar Industry(8)

User Experience(66)

Edtech(10)

Events(34)

HR Tech(3)

Interviews(10)

Life@mantra(11)

Logistics(5)

Strategy(18)

Testing(9)

Android(48)

Backend(32)

Dev Ops(11)

Enterprise Solution(29)

Technology Modernization(7)

Frontend(29)

iOS(43)

Javascript(15)

AI in Insurance(38)

Insurtech(66)

Product Innovation(57)

Solutions(22)

E-health(12)

HealthTech(24)

mHealth(5)

Telehealth Care(4)

Telemedicine(5)

Artificial Intelligence(143)

Bitcoin(8)

Blockchain(19)

Cognitive Computing(7)

Computer Vision(8)

Data Science(19)

FinTech(51)

Banking(7)

Intelligent Automation(27)

Machine Learning(47)

Natural Language Processing(14)

expand Menu Filters

How to Prepare a User Interview Questionnaire?

5 mins 10 secs read

The User Interview is a qualitative, non-binary, open-ended process that is a crucial contextual inquiry research method. And creating a good questionnaire is like sharpening your weapon to make the best impact.

A well-prepared, well-rehearsed user questionnaire is a must for an insightful interview.

Why make a questionnaire before a User Interview?

To avoid Response Biases*!

Seven-eight response biases influence user interviews greatly; understanding the user persona objectively is crucial for good design decisions. A thorough understanding of the response biases will help you use them or avoid them to get functional responses from the user.

*Note: There will be an upcoming blog on Response Biases and how to use or avoid them in research. Keep following Mantra Labs’s blog posts.

To make interviews more relevant to the research goals:

Planning an interview questionnaire keeps the facilitator on track during interviews. What does this mean? Multiple probing questions are asked during any user interview to gain more information and a deeper understanding of the participant’s behavior. Due to the probing, three situations occur.

1. The facilitator gets carried away in probing and deviates from the central questions under the influence of the participant’s response.

2. The facilitator asks questions spontaneously under the influence of their biases that might not be relevant to the research goals.

3. There is a chance of losing track of interview goals and shifting off-topic. Sometimes it’s a good idea to check all the possibilities that could influence the user’s behavior. However, there should be a clear line at which to stop and come back to the main questions.

To make sure questions are open-ended and revised/reframed before interviews:

“Details are in the story,” and Open-ended questions allow participants to tell the story of their experience. Since participants’ responses should not be influenced or bound to respond in a certain way, it is crucial to plan open-ended questions.

E.g., a pet product company is researching the possibility of their product entering the market and developing some pet grooming products for millennial pet owners. Let’s look at some 

questions to understand how open-ended they are.

Q 1: Would you use shampoo to make your dog smell better?

Q 1.1: What shampoo would you use to make your dog smell better?

Problem with these questions: 

Q 1: It’s a Yes/No question that will not give any qualitative insights.

       This question has little scope to know all the products the participant uses for grooming the dog.

Q 1.1: This is better than Q.1 because it has the scope of answering about shampoo products, but more is needed to know every detail of the pet cleaning-care habits of the user.

This can be a follow-up question to dig deeper, but not the main question.

What would be an excellent open-ended question?

Q. 1: What does your pet grooming process look like, and what products do you use while grooming?

Now this question has scope for the participant to tell the story of their pet’s grooming, including their process, the product they use, and how everything impacts their pet’s grooming pattern.

To avoid repetitive/similar questions:

If the questions still need to be pre-prepared and revised, the facilitator often asks questions similar to prior questions. This scenario causes a waste of time, sometimes irritating the participants as well.

To limit the number of questions and make them effective per the interview time limit.

  1. The time taken in an interview significantly impacts the qualitative information received from the participants. 40-45 minutes is the sweet spot for an interview. More than that, it starts becoming too much for the participant. If the facilitator continues to engage, the participant might get disengaged and be in a hurry to finish the interview.
  2. If it takes less than 40 minutes, you might not get a deep understanding of the question due to needing more probing in the response received from the participant.

How to make a good User Interview questionnaire?

Now that we know why, a good questionnaire is crucial before the research interview. There are some parameters and ways to write a good questionnaire.

Defining the business goal and user goal:

Keep stakeholder analysis as the first priority before writing the questionnaire. It’s crucial to know the business goals of the critical stakeholders to lay the foundation for your research interview. Also, try to understand and write the User Goal according to key stakeholders and their target personas.

Doing secondary research and gaining more information about the products, services, and business: 

It helps the facilitator make questions more relevant to the topic. The planning of the questions would be about the product and the service, which would help to find impactful insights. Here are some matters to focus on while doing secondary research:

  •  Analytics of the website (whatever possible, Google Analytics, Hotjar, Similarweb), target personas, user journey, pain points, what are your most trafficked pages, which site pages rank high in SERPs, visits from organic sources, traffic referrals from other sites and channels, Traffic from direct URL into the search bar, Devices used by the traffic ETC.)
  • Top performing keywords
  • How long do people typically spend on your website?
  • Page load time of the site?
  • Competitors analysis
  • User Personas
  • Geolocations of major user bases
  • Industry trends
  • The existing research paper regards the context
  • Existing customer journey map (If any)

Write the User Interview objective and key result properly:

This is the foundation of any research. Defining the OKR of the interview will keep your approach more constructive. The researcher should define why they are interviewing and what they want to achieve. Later, the questions should be formed in order to get the relevant information with regard to the interview objective.

The questions need to be framed in four categories that go in order one after another during the interview:

Intro Question and Ice Breakers

* Hi, How does your day/week go in Mantra Labs?

* Could you tell us about your role, followed by what your team does at Mantra Labs?

* How do you plan for your certain work to achieve your ‘X’ target?

Topic Specific Questions

* How do clients approach you and vice-versa? 

* Could you describe a couple of scenarios where you failed to perform the task and how it happened?

* How do you overcome obstacles when performing such tasks?

Opportunity specific questions

* What is making a good impact on existing clients during the project?

Opinionated questions

* In your opinion, where would you suggest this service should improve?

Conclusion

User Interview Research in UX is crucial to making informed decisions to solve complicated problems for any product or service. As it is essential, it needs to be understood. 

What does it mean? How should it be done? Also, when should it be done? But above all, the biggest problem with interviewers is a need for more technical and experiential knowledge of how to prepare Research Interview Questionnaires.

To do that, Interviews need to understand fundamental response biases, which can destroy the creation of the questionnaire and interview insights. Do thorough secondary research about the matter. Next, review the business goals and write the interview research goals and OKRs. And finally, have a structured questionnaire covering all types of questions. 

About Author,

Vijendra is currently working as a Sr. UX Designer at Mantra Labs. He is passionate about UXR and Product Design.

Cancel

Knowledge thats worth delivered in your inbox

Why Netflix Broke Itself: Was It Success Rewritten Through Platform Engineering?

By :

Let’s take a trip back in time—2008. Netflix was nothing like the media juggernaut it is today. Back then, they were a DVD-rental-by-mail service trying to go digital. But here’s the kicker: they hit a major pitfall. The internet was booming, and people were binge-watching shows like never before, but Netflix’s infrastructure couldn’t handle the load. Their single, massive system—what techies call a “monolith”—was creaking under pressure. Slow load times and buffering wheels plagued the experience, a nightmare for any platform or app development company trying to scale

That’s when Netflix decided to do something wild—they broke their monolith into smaller pieces. It was microservices, the tech equivalent of turning one giant pizza into bite-sized slices. Instead of one colossal system doing everything from streaming to recommendations, each piece of Netflix’s architecture became a specialist—one service handled streaming, another handled recommendations, another managed user data, and so on.

But microservices alone weren’t enough. What if one slice of pizza burns? Would the rest of the meal be ruined? Netflix wasn’t about to let a burnt crust take down the whole operation. That’s when they introduced the Circuit Breaker Pattern—just like a home electrical circuit that prevents a total blackout when one fuse blows. Their famous Hystrix tool allowed services to fail without taking down the entire platform. 

Fast-forward to today: Netflix isn’t just serving you movie marathons, it’s a digital powerhouse, an icon in platform engineering; it’s deploying new code thousands of times per day without breaking a sweat. They handle 208 million subscribers streaming over 1 billion hours of content every week. Trends in Platform engineering transformed Netflix into an application dev platform with self-service capabilities, supporting app developers and fostering a culture of continuous deployment.

Did Netflix bring order to chaos?

Netflix didn’t just solve its own problem. They blazed the trail for a movement: platform engineering. Now, every company wants a piece of that action. What Netflix did was essentially build an internal platform that developers could innovate without dealing with infrastructure headaches, a dream scenario for any application developer or app development company seeking seamless workflows.

And it’s not just for the big players like Netflix anymore. Across industries, companies are using platform engineering to create Internal Developer Platforms (IDPs)—one-stop shops for mobile application developers to create, test, and deploy apps without waiting on traditional IT. According to Gartner, 80% of organizations will adopt platform engineering by 2025 because it makes everything faster and more efficient, a game-changer for any mobile app developer or development software firm.

All anybody has to do is to make sure the tools are actually connected and working together. To make the most of it. That’s where modern trends like self-service platforms and composable architectures come in. You build, you scale, you innovate.achieving what mobile app dev and web-based development needs And all without breaking a sweat.

Source: getport.io

Is Mantra Labs Redefining Platform Engineering?

We didn’t just learn from Netflix’s playbook; we’re writing our own chapters in platform engineering. One example of this? Our work with one of India’s leading private-sector general insurance companies.

Their existing DevOps system was like Netflix’s old monolith: complex, clunky, and slowing them down. Multiple teams, diverse workflows, and a lack of standardization were crippling their ability to innovate. Worse yet, they were stuck in a ticket-driven approach, which led to reactive fixes rather than proactive growth. Observability gaps meant they were often solving the wrong problems, without any real insight into what was happening under the hood.

That’s where Mantra Labs stepped in. Mantra Labs brought in the pillars of platform engineering:

Standardization: We unified their workflows, creating a single source of truth for teams across the board.

Customization:  Our tailored platform engineering approach addressed the unique demands of their various application development teams.

Traceability: With better observability tools, they could now track their workflows, giving them real-time insights into system health and potential bottlenecks—an essential feature for web and app development and agile software development.

We didn’t just slap a band-aid on the problem; we overhauled their entire infrastructure. By centralizing infrastructure management and removing the ticket-driven chaos, we gave them a self-service platform—where teams could deploy new code without waiting in line. The results? Faster workflows, better adoption of tools, and an infrastructure ready for future growth.

But we didn’t stop there. We solved the critical observability gaps—providing real-time data that helped the insurance giant avoid potential pitfalls before they happened. With our approach, they no longer had to “hope” that things would go right. They could see it happening in real-time which is a major advantage in cross-platform mobile application development and cloud-based web hosting.

The Future of Platform Engineering: What’s Next?

As we look forward, platform engineering will continue to drive innovation, enabling companies to build scalable, resilient systems that adapt to future challenges—whether it’s AI-driven automation or self-healing platforms.

If you’re ready to make the leap into platform engineering, Mantra Labs is here to guide you. Whether you’re aiming for smoother workflows, enhanced observability, or scalable infrastructure, we’ve got the tools and expertise to get you there.

Cancel

Knowledge thats worth delivered in your inbox

Loading More Posts ...
Go Top
ml floating chatbot