# 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](<https://devfeed.tech/articles/how-we-conduct-user-interviews-and-user-tests-at-clue-part-one-24566.md>)

Original publisher: [Read original article](<https://medium.com/bleeding-edge/how-we-conduct-user-interviews-and-user-tests-at-clue-part-one-1e4ba424d91d?source=rss----d8ebe85cdc0f---4>)

Author: Caro Hardy

Published: 2018-05-11T13:25:25Z

Content type: article

Language: en

Sources: [Bleeding Edge - Medium](<https://devfeed.tech/sources/bleeding-edge-medium.md>)

Topics: [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [Usability](<https://devfeed.tech/topics/usability.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [design](<https://devfeed.tech/tags/design.md>), [interviews](<https://devfeed.tech/tags/interviews.md>), [product-design](<https://devfeed.tech/tags/product-design.md>), [prototype](<https://devfeed.tech/tags/prototype.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>), [usability](<https://devfeed.tech/tags/usability.md>), [user-interviews](<https://devfeed.tech/tags/user-interviews.md>), [user-research](<https://devfeed.tech/tags/user-research.md>), [user-testing](<https://devfeed.tech/tags/user-testing.md>), [ux](<https://devfeed.tech/tags/ux.md>)

## 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