# Guide 3: How to find themes and insights from user interviews

* [ ] 3.1 Synthesise what you heard
* [ ] 3.2 Write insight statements

This guide is part of The Catalyst PUNS Guide. It follows on from Guide 2: How to do user interviews. It has two parts that together make up one working session. Do both parts in one session.

The session might take you around 3 hours. Morning is the best time to do this work.

{% hint style="warning" %}

### What you need to have already done

For this guide to be useful you need to have already:

* Carried out user interviews
* Documented them onto post-its notes

You can do this by using Guide 2: How to do user interviews, or by other means you choose.
{% endhint %}

{% hint style="success" %}

### What you will have by the end

By the time you are done here you will have:

* A set of themes and sub-themes based on what you learnt in the interviews
* 10-20 insight statements
* Learnt how to carry out a synthesis session and write insight statements based on research
  {% endhint %}

### What to use

{% hint style="info" %}

### 🙋🏽What to use

**The synthesis and insight statements whiteboard you created in 2.4. 👈**

**Use advice and guidance from the steps overleaf and the links you find.** 👉
{% 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-3-how-to-find-themes-and-insights-from-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.