User Interview Template
Capture relevant details from discussions with current or potential customers. The user interview is a great tool to gain insights and improve your product.
About the User Interview Template
The user interview template is where you can keep track of your user interviews, adding the questions, answers, and any other information you might find helpful to build a profile of your user and conduct user research.
What is a user interview?
User interviews are a UX research technique where researchers ask users questions about a topic. You can use the user interview template to prepare your questions and take note of the interviewee’s responses. It allows your team to quickly and easily collect user data, and it’s also a great way to learn more about who uses your product.
When to conduct user interviews
Product teams, UX designers and writers gather background data to understand how people use technology. It’s a way to take a snapshot of how users interact with a product, understand user objectives and motivations, and find users’ pain points.
It’s an important step when developing or iterating an existing service or product. That’s why marketing, business, and development teams often find it helpful to conduct a user interview to gain insights and develop better strategies and solutions.
Benefits of conducting user interviews
There are many advantages to conducting user interviews, especially if you are developing a product or improving a service. It allows researchers to understand the user experience, gives a clear picture of a product’s usability, and enables companies to gather demographic or ethnographic data that can be used to create user personas.
Who should implement the user interview template
Two UX researchers, product managers, or other product team members generally conduct user interviews. That doesn't mean that other people can’t join the process; marketing researchers and strategists may also take part in the interview as listeners and take notes to develop a user persona.
How to structure your user interview
Start explaining the purpose of the interview. Tell the interviewee what you plan to cover and what you’re trying to accomplish in the interview. Then explain how user data will be used afterward.
Afterward, start your interview. Make sure you’re not priming the interviewee at any point during the conversation. For example, if you’re trying to figure out how people are using your podcast app, ask them, “Do you use any podcast apps?” rather than “How often are you using our podcast app?”
A good practice is to create space for answers to flourish, and by that, we mean asking open-ended questions so they can elaborate on their answers. Another tip is to try keeping the interview short, under an hour.
At the end of the interview, thank the user for coming and give them the opportunity to ask any questions of their own.
Common user interview questions
Tell me about your background.
How often do you use [similar products in our space]?
When you are using these products, do you encounter any challenges?
What are the most important tasks you perform while using these products?
Is there anything you wish you could do with these products which is currently not possible?
Are there any ways these products do not support your current needs?
Set up your own user interview template
The user interview template is designed to capture the most relevant information from your user interviews. In addition to the details of the interview and interviewee, you may want to include questions asked and topics covered, as well as user observations and feedback and key takeaways or action points for your team.
The user interview template can also be referred to later and used as a strategic tool to develop a complete customer journey map. Share your user interview template with your team and stakeholders and ask for feedback or brainstorm based on your findings to gain insights.
How do you create user interview questions?
Depending on what you are trying to discover, you can direct your interview differently. When creating user interview questions, some standard practices include asking open-ended questions that require more than a single word answer and questions that make you understand your user’s tasks. Another important thing to remember is to ask about their feelings, opinions, and pain points regarding a specific topic. You can also ask them to compare services or explain how they compare to another similar experience.
How many participants do you need for user interviews?
You can conduct the interview yourself, but UX and research teams commonly gather together to observe and make notes. Ideally, you would have one more person with you at the interview.
Get started with this template right now.
HEART Framework Template
Works best for:
Desk Research, Project Management, User Experience
Happiness, Engagement, Adoption, Retention, and Task Success. Those are the pillars of user experience — which is why they serve as the key metrics in the HEART framework. Developed by the research team at Google, this framework gives larger companies an accurate way to measure user experience at scale, which you can then reference throughout the product development lifecycle. While the HEART framework uses five metrics, you might not need all five for every project — choose the ones that will be most useful for your company and project.
Service Blueprint by Hyperact
Works best for:
Research & Design
The Service Blueprint template is perfect for visualizing the orchestration of service components. It maps out frontstage and backstage elements, helping you analyze and enhance customer experiences. Use this template to align teams, identify pain points, and streamline processes, ensuring a seamless service delivery. It's ideal for creating a shared understanding of service dynamics among stakeholders and collaborators.
FMEA Analysis Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
When you’re building a business or running a team, risk comes with the territory. You can’t eliminate it. But you CAN identify it and mitigate it, to up your odds of success. Failure Modes and Effects Analysis (FMEA) is a powerful tool designed to help you manage risk and potential problems by spotting them within a process, product, or system. And you’ll spot them earlier in your process—to let you sidestep costly changes that arise late in the game or, worse, after they’ve impacted your customers and their experience.
Product Hypothesis Canvas
Works best for:
Product Management, Planning
The Product Hypothesis Canvas template assists product teams in formulating and testing hypotheses effectively. By defining assumptions, success metrics, and validation experiments, this template guides teams through the hypothesis validation process. With sections for articulating problem statements, proposed solutions, and expected outcomes, it ensures that hypotheses are clear, testable, and aligned with strategic objectives. This template serves as a framework for hypothesis-driven product development, enabling teams to validate ideas and make data-informed decisions.
Product Backlog Template
Works best for:
Agile Methodology, Kanban Boards, Product Management
Development teams are often juggling many products at once. A product backlog is a project management tool that helps teams keep track of projects in flight as they build and iterate, so you can store everyone's ideas, plan epics, and prioritize tasks. The highest-priority tasks are at the top of the product backlog, so your team knows what to work on first. Product backlogs make it easier for teams to plan and allocate resources, but it also provides a single source of truth for everyone to know what development teams are working on.
Scenario Mapping Template
Works best for:
Desk Research, Mapping, Product Management
Scenario mapping is the process of outlining all the steps a user will take to complete a task. The scenario mapping template helps you create a visual guide to what different personas are doing, thinking, and feeling in different situations. Use scenario mapping to outline an intended or ideal scenario (what should happen) as well as what currently happens. If you’re trying to outline the ideal scenario, user mapping should take place very early on in a project and can help inform user stories and the product backlog. If you’re just trying to get a better sense of what currently happens, you can do user mapping when conducting user interviews or observation.