# Page Not Found

The URL `files/upfZebnoVFAZGdQ2Oxn0` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [2 ENGAGE: Who are we designing for?](https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/design-steps/2-engage-who-are-we-designing-for.md)
- [1 SCOPE: What challenge are we addressing?](https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing.md)
- [3 UNDERSTAND: What is happening now, and why?](https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why.md)
- [User Observation](https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/user-observation.md)
- [Persona](https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/persona.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/design-steps/2-engage-who-are-we-designing-for.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.

### Option 2 — Browse the documentation index

Full index: https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/publicservicebooster/design-steps/2-engage-who-are-we-designing-for.md`).

You may also use `Accept: text/markdown` header for content negotiation.