# Guide 2: How to do user interviews

* [ ] Recruit interview participants
* [ ] Run user interviews
* [ ] Document interview notes

This guide is part of The Catalyst PUNS Guide. It follows on from Guide 1: How to plan your project. 

Use it and Guides 3 and 4 for each user group you plan to create personas and user need statements for.

{% hint style="warning" %}

### What you need to have already done

For Guide 2 to be useful you need to have:

* Planned your project
* Decided which user group you will interview first
* Written research questions for your first user group

You can use Guide 1: How to plan your project to do this.
{% endhint %}

{% hint style="success" %}

### What you will have by the end

By the time you are done here you will have:

* A set of post-it notes capturing the most important things you heard in each interview, organised on a wall or whiteboard. These could be real or virtual.
* Learnt how to recruit participants, run user interviews and document your notes as post-its on a whiteboard
  {% endhint %}

{% hint style="info" %}

### 🙋🏽What to use

* **User research worksheet in 2.1 👉**
* **User research consent form in 2.1 👉**
* **Interview questions and notes template in 2.2** 👉
* Advice and guidance from the steps below and the links you find👉
  {% endhint %}

{% hint style="info" %}

#### 🔗🔗 [User interviews: why you must do them](https://www.thecatalyst.org.uk/blog/why-interviews)

{% endhint %}


---

# 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://wearecast.gitbook.io/catalyst-puns/guides/guide-2-how-to-do-user-interviews.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.