# 1 SCOPE: What challenge are we addressing?

## 1. Why this step matters

Every project needs a clear sense of direction. In this step, you’ll begin to shape the challenge your team wants to explore. Rather than jumping to solutions, this is your opportunity to ask: *What do we really need to work on—and why?*

## 2. What this step helps you do

* Translate everyday frustrations into a focused challenge
* Align your team or organisation around a shared goal
* Set a foundation for meaningful user engagement and discovery

## 3. How to approach it

You don’t need to get it perfect. Start with a working definition of the problem based on what you currently know.\
This first articulation helps you get started—and gives you something to test, reflect on, and possibly revise later. In Step 2, you will go deeper into **who** this challenge is for*—*your users and key stakeholders*—*and what matters most to them.

## 4. Suggested tool

| Tool                                                                                                                             | Outputs                                                                                                                                 |
| -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| [**Service Challenge Canvas**](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing/service-challenge.md) | A simple and shared definition of the challenge you’re exploring. It gives you a clear starting point for planning your discovery work. |

***

## Share your thoughts 💭

We'd love to receive your feedback on this step! Click [here](https://padlet.com/opsi/breakout-room/5Wkoqm3O6A3Q48pM-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/1-scope-what-challenge-are-we-addressing.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.