# User Interview

## Overview

Semi-structured interviews are one of the most powerful tools in human-centred research, but poorly planned interviews can lead to vague or biased data. Once you have clarified your research objectives and identified the user groups you wish to engage, the next step is to prepare your interview guide. This tool helps structure conversations that go beyond superficial answers to uncover what truly matters to people – their goals, frustrations, workarounds, and emotional responses. Well-designed guides are especially important in public services, where power dynamics and formality can inhibit open conversation.\
A thoughtful guide ensures that each interview supports your learning goals, while giving space for authentic user perspectives to emerge.

{% embed url="<https://docs.google.com/presentation/d/1Fnqy4CVJJR4uNYqWE5-yhh_XFm6kwiWBgX7neqfpn2w/edit?usp=sharing>" %}
[Open in Google Slides](https://docs.google.com/presentation/d/1Fnqy4CVJJR4uNYqWE5-yhh_XFm6kwiWBgX7neqfpn2w/edit?usp=sharing)\
[Open template in Google Docs](https://docs.google.com/document/d/13oETnuScNIuQfSiru9NEwAg6WTboDdg2GS7Ious13pI/)
{% endembed %}

{% hint style="info" %}
**⏱️ Time:** 45–60 minutes

👫 **Participants:** 1–2 team members who will conduct the interviews

🛠️ **Materials:** Interview guide template, notepad, recorder or transcription tool (optional)
{% endhint %}

## Input

Before completing this canvas, ensure you have completed the following steps:

{% content-ref url="/pages/7afK8CiAQ1DpqChZLbb5" %}
[Service Challenge](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing/service-challenge.md)
{% endcontent-ref %}

{% content-ref url="/pages/INg38Ka6W9AMTlzU6TdH" %}
[Stakeholder Map](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for/stakeholder-map.md)
{% endcontent-ref %}

{% content-ref url="/pages/vzD81w9xTqaraoct2ycr" %}
[User Characteristics](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for/user-characteristics.md)
{% endcontent-ref %}

## Context

Use this tool during the planning of your discovery research. It is suitable when planning semi-structured interviews with users, community members, staff, or stakeholders. Especially helpful when your team needs consistency across multiple interviews conducted by different people.

## Recipe

{% stepper %}
{% step %}

#### Clarify your research focus

Before drafting interview questions, use the first worksheet to map out your key **themes** (topics you want to explore) and related **research goals** (what you need to learn). This helps translate the [initial service challenge](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing/service-challenge.md) and findings from [user characteristics](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for/user-characteristics.md) to specific research question, ensuring your interviews are targeted and grounded in what you need to learn.
{% endstep %}

{% step %}

#### Design your opening

Move to the second worksheet, and plan how you will introduce yourself and the purpose of the interview. Explain clearly how the information will be used, and how participants' privacy and consent will be respected. This helps build trust.
{% endstep %}

{% step %}

#### Prepare context questions

Start by asking about the interviewee's background: “Could you tell me a bit about yourself?” (e.g. where do you live, what do you do?)
{% endstep %}

{% step %}

#### Write open-ended exploratory questions

Group your questions under your key research themes. Use formats such as:

* “What motivates you to…?” Why?
* “What do you find difficult when you try to…?”
* “How do you feel about…?” Why?
* “Can you describe a good/bad experience with…?” What happened?
* “What do you hope will happen when…?”
  {% endstep %}

{% step %}

#### Close the conversation with reflection

Invite the interviewee to share their ideas or suggestions: “What would you change?” “How?” “Why?”
{% endstep %}

{% step %}

#### Test and iterate

Review the guide with a colleague or test it with a mock interview to check for flow, clarity, and bias.
{% endstep %}
{% endstepper %}

## Results <a href="#results" id="results"></a>

A ready-to-use guide tailored to your topic and user group. It supports meaningful, consistent, and inclusive interviews that feed directly into insight development and problem reframing.

## Tips

* Avoid leading or yes/no questions – ask “how” and “why.”
* Leave room for unexpected stories – don’t over-structure. Remember: this is not a questionnaire but an interview guidance. It’s a conversation.
* Ensure your language is accessible to all user types.
* Practise active listening – what is said between the lines is often more revealing than direct answers.
* Consider how power dynamics may affect the interview. Neutral locations and non-hierarchical introductions help.
* When conducting an interview, always agree how you will **circle back** – how you will get back to people, by when, and what you will share. This builds trust and shows that their time and experience matter.

***

### [Share Your Experience](https://padlet.com/opsi/innovation-booster-collaboration-lmuadp5wornnbo86)

We'd love to hear how you're using this tool! Please share your examples and feedback to inspire others and help improve the Booster. Submit your example today and be part of our community.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/user-interview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
