> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it.md).

# Module 2 — Break the service down before you design it

The sector's catalogue and the blocks it shares; the register of what was asked; the records and their keepers; the goals; the shared registers; the architecture and its crossings

**Written for:** the team that commissions the service and makes the case to the minister (Strategist register). **Videos:** 6.

**What it teaches.** The sector's catalogue and the blocks it shares; the register of what was asked; the records and their keepers; the goals; the shared registers; the architecture and its crossings.

**What you can do afterwards.** Commission the documents that are written before any design: the catalogue, the register, the records, the goals, the shared registers, the architecture.

**What it uses of the worked example.** Filled extracts of the documents written before design, one for each subtopic.

## Subtopics

| #                                                                                                                                                                                    | Subtopic                                                          | Class | Demonstration | Single message                                                                                                        |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | ----- | ------------- | --------------------------------------------------------------------------------------------------------------------- |
| [2.1](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.1-one-catalogue-of-the-sectors-services-and-the-blocks-they-share.md) | One catalogue of the sector's services, and the blocks they share | Core  | —             | List every service the sector's bodies owe once, with what each rests on, before you specify any one of them.         |
| [2.2](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.2-write-down-what-was-asked-before-anyone-designs.md)                 | Write down what was asked before anyone designs                   | Core  | —             | One entry for each separate thing asked, in the customer's words, with where it was said.                             |
| [2.3](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.3-the-records-the-service-keeps-and-whose-each-one-is.md)             | The records the service keeps, and whose each one is              | Core  | —             | For every fact: we keep it, we take it from another body, or we must not hold it.                                     |
| [2.4](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.4-every-goal-named-and-each-tied-to-what-was-asked.md)                | Every goal named, and each tied to what was asked                 | Core  | —             | A service is broken into the goals people have in it; every goal serves an entry and every entry is served by a goal. |
| [2.5](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.5-what-every-goal-may-use-and-may-not-invent.md)                      | What every goal may use, and may not invent                       | Core  | —             | States, settings and code lists are written once and shared; a goal that needs something missing raises a question.   |
| [2.6](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.6-what-the-service-is-built-on-and-what-crosses-its-boundary.md)      | What the service is built on, and what crosses its boundary       | Core  | —             | One document names the platform, the shared blocks it uses and every flow that crosses to another body.               |

**Self-check.** [Four questions on what a manager decides](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/self-check-module-2.md), with the answer the module gives to each.

{% hint style="info" %}
The reference pages hold what every module uses: [the twelve documents](/experience-digital-transformation/building-block/the-twelve-documents.md), [the blank instruments](/experience-digital-transformation/building-block/the-blank-instruments.md), [the worked examples](/experience-digital-transformation/building-block/the-worked-examples.md), [the frameworks and standards](/experience-digital-transformation/building-block/frameworks-and-standards.md), [the public sources](/experience-digital-transformation/building-block/the-public-sources.md), [the standings of the method's standards](/experience-digital-transformation/building-block/the-standings-of-the-methods-standards.md), [the glossary](/experience-digital-transformation/building-block/glossary.md) and [the figures](/experience-digital-transformation/building-block/figures.md).
{% endhint %}


---

# 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://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it.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.