# 3 UNDERSTAND: What is happening now, and why?

## 1. Why this step matters

Before solving a problem, we need to understand what’s really happening—and why.\
Too often, teams rush to fix a surface issue without seeing the full picture. This step helps you uncover the lived experiences, behaviours, and underlying systems shaping today’s reality.\
By listening, observing and investigating with curiosity, you build the foundation for more relevant, effective and human-centred solutions.

## 2. What this step helps you do

* Understand how users currently experience the service or problem
* Identify pain points, workarounds, unmet needs and constraints
* Spot patterns, assumptions and systemic factors that influence the current state

## 3. How to approach it

Go beyond opinions and assumptions. Spend time with people—observe what they do, listen to what they say, and reflect on what that tells you.\
Before you start, write down what you think is true about your users and the service. Then use interviews and observations to see where your assumptions are right, and where they might be wrong. Stay open to being surprised: you may discover the problem isn’t what you thought. This helps you design with people, not just for them.

## 4. Suggested tools

| Tool                                                                                                                                                                                                                                                      | Outputs                                                                     |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| [**Discovery Planning Canvas**](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/discovery-planning.md)                                                                                                                      | A plan for why, how, where and with whom to conduct research.               |
| [**Interview Guide**](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/user-interview.md)                                                                                                                                    | A structured but flexible set of questions to explore people’s experiences. |
| [**Observation Notes**](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/user-observation.md)                                                                                                                                | Records of what you see and hear in real-world contexts.                    |
| [**Persona Canvas**](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/persona.md)                                                                                                                                            | A composite profile of a key user type, based on real insights.             |
| [**Today’s Journey**](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/todays-user-journey.md) **/** [**Process**](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/todays-business-process.md) | A visual map of the current user or operational experience.                 |

***

## Share your thoughts 💭

We'd love to receive your feedback on this step! Click [here](https://padlet.com/opsi/breakout-room/d6AO26l836b3vojL-B8nYzL4y4Gg1zV4L) and share your comments and suggestions. Your input is valuable to us and will help improve the Booster.


---

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