# User Characteristics

## Overview

To design better public services, we need to understand the people who use them—but not all users are the same. This tool helps your team take a step back and think carefully about *which* users you want to focus on during your research.

By listing different characteristics (e.g. age, income, digital skills, location), you can build a simple user profile to guide your discovery work. This encourages inclusion from the start—making sure you’re not just hearing from the “easy to reach”.

{% embed url="<https://docs.google.com/presentation/d/1hyInyjB0vArFeUoQTYnTTidgW6ZZFCR3V05tw-1pGzg/edit?usp=sharing>" %}
[Open in Google Slides](https://docs.google.com/presentation/d/1hyInyjB0vArFeUoQTYnTTidgW6ZZFCR3V05tw-1pGzg/edit?usp=sharing)
{% endembed %}

{% hint style="info" %}
**⏱️ Time:** 30–45 minutes

👫 **Participants:** Core team members, ideally with service delivery insights

🛠️ **Materials:** User Characteristics template (printed or digital), sticky notes or whiteboard
{% endhint %}

## Input

Before completing this canvas, ensure you have completed the following steps:

{% content-ref url="/pages/7afK8CiAQ1DpqChZLbb5" %}
[Service Challenge](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing/service-challenge.md)
{% endcontent-ref %}

{% content-ref url="/pages/INg38Ka6W9AMTlzU6TdH" %}
[Stakeholder Map](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for/stakeholder-map.md)
{% endcontent-ref %}

## Context

Use this tool after you’ve identified the service you want to improve, and before you begin planning interviews or fieldwork. It helps you prioritise which kinds of users you want to engage with first.

## Recipe

{% stepper %}
{% step %}

#### Name your user group

Use [service challenge canvas](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing/service-challenge.md) and [stakeholder map](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for/stakeholder-map.md) to identify who the core, central users are. Start with a general group (e.g. residents applying for permits, parents using childcare services).
{% endstep %}

{% step %}

#### List key characteristics

List a few key characteristics that make this user group distinct. Consider the types of diversity that may affect their experience. You can use contrasts such as:

* Rural / Urban
* Low income / High income
* Older / Younger
* Low / High digital literacy
* Small / Large businesses
* Decision-makers / Non-decision-makers
* Native speakers / Non-native speakers
* Public transport users / Car users
  {% endstep %}

{% step %}

#### Select priority profiles

Discuss which types of users you most need to hear from. These might be:

* People who experience the most barriers
* First-time or infrequent users
* Users whose experience is often overlooked
  {% endstep %}

{% step %}

#### Use this to guide research planning

Later, you can refer back to this list when recruiting for interviews or planning site visits.
{% endstep %}
{% endstepper %}

## Results <a href="#results" id="results"></a>

A list of concrete user characteristics and profiles that will guide your discovery research and help ensure a range of perspectives are included.

## Tips

* Don’t try to cover everyone—start with 2–3 user types that matter most.
* Think about *differences that shape experience*, not just demographics.
* Be intentional about inclusion: who’s usually excluded from consultations?
* Keep this sheet visible during recruitment—it will help you check for balance and gaps.

***

### [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: 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/2-engage-who-are-we-designing-for/user-characteristics.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.