# user-interviews Published articles for user-interviews. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How we conduct user interviews and user tests at Clue: Part Two DevFeed: [How we conduct user interviews and user tests at Clue: Part Two]() Original publisher: [Read original article]() Author: Caro Hardy Published: 2018-05-11T13:26:29Z Content type: article Language: en Sources: [Bleeding Edge - Medium]() Topics: [App](), [data]() Tags: [insights](), [interviews](), [product-design](), [software-development](), [user-interviews](), [user-research](), [user-testing](), [ux]() ### AI overview This article explains how Clue conducts user interviews, including introductory questions, baseline questions about app usage, questions about competing alternatives, and project-specific research questions. ### Source excerpt To learn about our process, read Part One. Illustration by Marta PucciInterview sessions Once we have someone in the office, on the phone or on Google Hangouts, how do we carry out user interviews? Ideally, an interview will teach us one or more of the following things: Teach me something about people. Who are they? What's important to them? What's their story? Teach me something about how and why people use Clue. When do they starting thinking about it? What motivates them to look for something like it? Do they do research? Who do they ask? Teach me something about competing alternatives. What does Clue replace? How is it perceived against what they were doing before? How do people weigh up different options? The typical questions we ask I break the interview questions down into three categories. Introductory questions I'll start off with some super basic questions to get people warmed up. Some people find the experience a little weird at first, so this is an opportunity to get them used to the process. Questions: Tell me about yourself? What do you do for a living? How long have you lived in Berlin? The standards questions After the breaking the ice, I'll move onto some questions to get baseline insights from them. To give examples, they include questions such as: Which device do you use? How long are you using Clue? What do you use Clue for? What categories do you track in Clue? How often do you track? I'll ask questions about how they searched for such solutions: How did you hear about Clue? Do you currently use other female health apps? What for and why? Did you switch from another app to Clue? Which one? Why did you switch? And I'll ask questions about usage: Beside your period, do you track any other options? Which ones? Why? Have you entered anything into Clue today? When do you usually do it? At what time of the day? Where? (I want to know if they mostly do instant data entry or a posteriori tracking) Can you show me how you do it? (and I would about look w ## How we conduct user interviews and user tests at Clue: Part One DevFeed: [How we conduct user interviews and user tests at Clue: Part One]() Original publisher: [Read original article]() Author: Caro Hardy Published: 2018-05-11T13:25:25Z Content type: article Language: en Sources: [Bleeding Edge - Medium]() Topics: [User interface design](), [Testing](), [Usability](), [App]() Tags: [app](), [design](), [interviews](), [product-design](), [prototype](), [testing](), [tests](), [usability](), [user-interviews](), [user-research](), [user-testing](), [ux]() ### AI overview Clue explains its practical process for conducting user interviews and prototype tests throughout product design. The article describes blank-page interviews, feature research interviews, and prototype testing, with the approach shaped by the organization's stage and research goals. ### Source excerpt Illustration by Marta Pucci I find it fun to see exactly how other organizations handle certain design processes. It's the small the little details that I find interesting. So, I thought I'd lay out exactly how we do work with users for research and testing purposes at Clue. Clue is a female health tracking app based in Berlin. We're now at the stage of about 50 employees, and we've raised over $30 million from VC firms such as Union Square Ventures. More than 10 million people use Clue. The reason I give these details is that I think your organization's stage will have a big impact on your approach to user research and user testing. To give a quick example, we're not at the stage where we test a single flow with hundreds of users to get quantitative data on the usability. But we are well beyond the stage where offering free coffee in Starbucks in return for chatting to us for 10 minutes is enough for our research and testing processes. In this two-part article, I'm going to focus on the practical, step-by-step process we use for talking to users, week-in, week out. The design process Our design process at Clue focuses both on designing a product that is scientifically-valid -- our app lets people know when they can expect their period and other menstrual cycle symptoms and stages -- and responds to the needs of the people using it. That means that the two product designers at Clue work closely with scientific researchers and data scientists. This is how we make sure that the product meets rigorous scientific standards. We also talk to the users at pretty much every point across the design process. Here's how I'd break up the stages of talking to users: Blank page interviews Even when we don't have a particular feature idea in mind, we'll carry out some user interviews. At this point we're just looking for interesting problems to dig into that could be the basis of future feature ideas. Feature research interviews When we have a feature idea, we'll kick off a round of