> 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.md).

# 3 Service design good practice guidelines

This section serves as a checklist for assessing quality of a service by following the points in this guide

## 3.1 User-centred design

Continuously improve services to meet the needs of users.

* [ ] [Understand user needs](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.1-user-centred-design.md)
* [ ] [Test with real users](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.1-user-centred-design.md)
* [ ] [Iterate based on feedback](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.1-user-centred-design.md)

## 3.2 Accessibility and inclusion

Build services that are usable and equitable for all.

* [ ] [Test for accessibility](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion.md)
* [ ] [Test your service with diverse users](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion.md)
* [ ] [Involve users in the design](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion.md)

## 3.3 Consistency

Create user-friendly services that build trust.

* [ ] [Use simple language](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.3-consistency.md)
* [ ] [Reuse existing styles and patterns](#id-3.3-consistency)
* [ ] [Provide a joined-up experience](#id-3.3-consistency)
* [ ] [Share design decisions](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.3-consistency.md)

## 3.4 Technology choices

Making decisions based on needs.

* [ ] [Balance security and usability](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.4-technology-choices.md)
* [ ] [Optimise performance and connectivity](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.4-technology-choices.md)
* [ ] [Design cross-platform](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.4-technology-choices.md)


---

# 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.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.
