> For the complete documentation index, see [llms.txt](https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/readme.md).
# Public Service Innovation Booster
The **Public Service Innovation Booster** is a hands-on, modular toolkit designed to support public servants in applying human-centred approaches to service design and delivery. Built around real-world challenges and constraints, it offers **practical tools, templates and guidance** for those working at the frontline of public service.
## What the Booster offers
The Booster is structured around a **seven-step human-centred innovation process**.
Each step reflects a key phase in human-centred service design—from understanding the challenge to communicating the solution—with a key question and suggested tools.
| Step | Key question | Key tools |
| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [🎯 1 Scope](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing.md) | What challenge are we addressing? | [Service Challenge](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing/service-challenge.md) |
| [👫 2 Engage](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for.md) | Who are we designing for? | [Stakeholder Map](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for/stakeholder-map.md), [User Characteristics](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for/user-characteristics.md) |
| [🔍 3 Understand](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why.md) | What is happening now, and why? | [Discovery Planning](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/discovery-planning.md), [Interviews](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/user-interview.md), [Observations](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/user-observation.md), [Persona](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/persona.md), [Today’s Journey,](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/todays-user-journey.md) [Today’s Process](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/todays-business-process.md) |
| [💡 4 Re-frame](/publicservicebooster/design-steps/4-re-frame-what-is-the-real-challenge-we-need-to-solve.md) | What is the real challenge we need to solve? | [Re-framing Canvas](/publicservicebooster/design-steps/4-re-frame-what-is-the-real-challenge-we-need-to-solve/re-framing.md) |
| [🎨 5 Design](/publicservicebooster/design-steps/5-design-what-ideas-could-address-the-challenge.md) | What ideas could address the challenge? | [Crazy 8](/publicservicebooster/design-steps/5-design-what-ideas-could-address-the-challenge/crazy-8.md), [Service Concept](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing/service-challenge.md), [Tomorrow’s Journey](/publicservicebooster/design-steps/5-design-what-ideas-could-address-the-challenge/tomorrows-user-journey.md), [Tomorrow’s Process](/publicservicebooster/design-steps/5-design-what-ideas-could-address-the-challenge/tomorrows-business-process.md) |
| [🧪 6 Test](/publicservicebooster/design-steps/6-test-would-the-idea-really-work-in-the-real-world.md) | Would the idea really work in the real world? | [Testing Plan](/publicservicebooster/design-steps/6-test-would-the-idea-really-work-in-the-real-world/testing-plan.md) |
| [📣 7 Communicate](/publicservicebooster/design-steps/7-communicate-how-do-we-gain-support-for-the-new-solution.md) | How do we gain support for the new solution? | [Storytelling](/publicservicebooster/design-steps/7-communicate-how-do-we-gain-support-for-the-new-solution/storytelling.md) |
## **Why use the Booster?**
Public services work best when they start from people’s real experiences. The Booster gives you a simple, step-by-step way to look at a service through people’s eyes, understand what is really going on, and design practical improvements with them—even if you (and your team) are new to human-centred design.
***
### [Share Your Experience](https://padlet.com/opsi/innovation-booster-collaboration-lmuadp5wornnbo86)
We'd love to hear how you're using this tool! Please share your examples and feedback to inspire others and help improve the Booster. Submit your example today and be part of our community.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/readme.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.