> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.1-user-centred-design/3.1.1.2-involve-others-in-the-design-process.md).

# 3.1.1.2 Involve others in the design process

Find opportunities to collaborate closely with users, stakeholders, and other [team members with diverse multidisciplinary skills](https://govstack.gitbook.io/o/pxmRWOPoaU8fUAbbcrus/s/4D3oEcPGpYoKnwkQmCzJ/govstack-implementation-playbook/sample-digital-team-composition), throughout the design process.

Empower users to take an active role in co-creating and co-designing public services.

### Example activities

#### **Engaging Stakeholders:**

* Involve stakeholders early on to understand their expectations and objectives.
* Get feedback from stakeholders to review and comment on design decisions and findings.

#### **Collaborating with Team Members:**

* Conduct workshops or brainstorming sessions for diverse input.
* Have peer reviews to get the perspective of different roles in the design.
* Emphasise user needs and project goals within the team.

#### **Involving Users:**

* Carry out user research activities, like interviews and surveys, to understand user needs.
* Hold co-design sessions with users, for them to participate directly in the design process.
* Conduct [usability testing ](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.1-user-centred-design/3.1.2.1-test-with-users.md)with real users to identify issues and opportunities for improvement.
* [Collect user feedback](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.1-user-centred-design/3.1.3.2-monitor-performance.md) post-launch.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.1-user-centred-design/3.1.1.2-involve-others-in-the-design-process.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.