> 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-6-run-the-method-in-your-administration/6.6-carry-the-method-to-another-sector.md). # 6.6 Carry the method to another sector The method holds no sector's content; another sector brings its own catalogue and its own records. {% embed url="" %} Carry the method to another sector (\~5 min) {% endembed %} **Watch first (\~5 min).** Then read on: the page carries what the video says, and the AI usage tip. > **Single message.** The method holds no sector's content; another sector brings its own catalogue and its own records. ## The concept Another ministry, health or agriculture, sees the education team's results and asks to use the same method. Nothing in the method itself is about schools. What changes is the sector's own content, and the sector must bring it. Most of the method stays exactly as it is. The twelve documents stay, in the same order. The people who accept them stay, by role: the owner of the service, the head of the ICT unit, and the official who will live with the result. The checks stay, and so do the rules that always hold, such as no hand edits and an open question with a name on it. So do the blank instruments. The twelve documents give the business side and the builders one shared language, so a decision means the same thing in both rooms. The new sector brings its own content. It writes its own catalogue of services, owed by its own bodies. It writes the register of what was asked from its own law, not from education's. It names its own records, and who keeps each one. And it brings a reference pack: its usual procedures, reusable pieces of design, a checklist of what is realistic in that sector, and one finished example to compare against. A program checks that the pack is complete, and that the method's own tools hold nothing of any one sector. The pack is the sector's own, kept by the sector. Carry the method, not the results. Nothing found in education is a fact about health or agriculture. Health has its own registers, its own law and its own officials. A sector's examples are rebuilt on its own records and its own law. An assistant can help adapt the examples, but every place where the sector's own law must be read is marked, and the sector's officials correct the drafts. Its officials know its law; the method only shows where to look. This course works through one sector only, education, because that is its demonstration. Another sector is described here as a list of what it brings, not as a worked case. Before the new sector writes its first document, it names the people the method relies on. Who owns the service in that ministry, as the Director of Higher Education owns it in the ministry of education? Who writes the sector's catalogue of services, once, for all the bodies of the sector? And which officials will read the adapted examples against their own law and correct them? With those names written down, the twelve documents can begin, in the same order, accepted by the same kinds of person as before. {% hint style="success" %} **The worked example of this subtopic** is [E6-6](/experience-digital-transformation/building-block/the-worked-examples/e6.6-what-another-sector-brings-and-what-stays-the-same-the-teams-blank-instrument.md), built for Progressa. {% endhint %} ## Your turn — Adapt the method's examples to a service of another sector {% hint style="success" %} **💡 AI usage tip** · Adapt the method's examples to a service of another sector **Bring:** The examples of the twelve documents and the description of a service in the new sector. **Get:** The twelve examples adapted to the new service, with every place to be read in the sector's law marked, followed by the list of those places. **Time:** \~10–15 min · **Assistant:** any; the tips are tool-neutral. **Watch for:** The adapted examples are drafts for that sector's officials to correct. {% endhint %} **The problem it solves.** A team in another sector wants to use the method, but every example it has seen is about education. This prompt adapts the examples of the twelve documents to one service of the new sector, and marks every place where that sector's own law must be read. {% tabs %} {% tab title="Prompt" %} Copy the prompt, replace the bracketed parts with your own context, and run it in the AI assistant of your choice. Never paste personal data or unpublished documents — see [How to use the plays](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/how-to-use-the-plays). ``` Below are the examples of the twelve documents of the specification-driven method, written for an education service: [paste the examples]. Below is a short description of a service in [the new sector], with the bodies that owe it: [paste the description]. Rewrite each example for the new service, keeping its form and replacing every name, record and value. Mark every place where the content depends on the new sector's law, policy or practice as [to be read in the sector's law: what must be read], and do not fill it in from education or from general knowledge. Do not carry any finding, figure or rule from education across. Output: the twelve examples adapted to the new service, with every place to be read in the sector's law marked, followed by the list of those places. ``` [Open in Claude](https://claude.ai/new?q=Below%20are%20the%20examples%20of%20the%20twelve%20documents%20of%20the%20specification-driven%20method%2C%20written%20for%20an%20education%20service%3A%20%5Bpaste%20the%20examples%5D.%20Below%20is%20a%20short%20description%20of%20a%20service%20in%20%5Bthe%20new%20sector%5D%2C%20with%20the%20bodies%20that%20owe%20it%3A%20%5Bpaste%20the%20description%5D.%20Rewrite%20each%20example%20for%20the%20new%20service%2C%20keeping%20its%20form%20and%20replacing%20every%20name%2C%20record%20and%20value.%20Mark%20every%20place%20where%20the%20content%20depends%20on%20the%20new%20sector%27s%20law%2C%20policy%20or%20practice%20as%20%5Bto%20be%20read%20in%20the%20sector%27s%20law%3A%20what%20must%20be%20read%5D%2C%20and%20do%20not%20fill%20it%20in%20from%20education%20or%20from%20general%20knowledge.%20Do%20not%20carry%20any%20finding%2C%20figure%20or%20rule%20from%20education%20across.%20Output%3A%20the%20twelve%20examples%20adapted%20to%20the%20new%20service%2C%20with%20every%20place%20to%20be%20read%20in%20the%20sector%27s%20law%20marked%2C%20followed%20by%20the%20list%20of%20those%20places.) *(pre-fills the prompt in a new chat; check the bracketed parts before sending)* *What to bring and what you get are in the box above.* {% endtab %} {% tab title="Example input" %} {% hint style="warning" %} **Draft worked example, 2026-10-05.** Progressa is the fictional country used across these courses. The input below and the output in the next tab were written for this page to show a typical run of the prompt; they are simplified, and they have not been checked as the worked examples of the method have. {% endhint %} The bracketed parts of the prompt were replaced with the following: **\[the new sector]:** health. **\[paste the examples]:** short excerpts of the education examples, one for each of the twelve documents. Among them: * Register of what was asked: "R-03 The minister decides the licence (article 11 of the Higher Education Regulations)." * Records: "The register of institutions, kept by PHEQA, one entry for each institution under an identifier like INS-00217." * Shared groundwork: "Kinds of institution: university, university college, technical institute. Kinds of licence: provisional, full. States of a licence: granted, suspended, cancelled. Application fee: 1,200." * Goal in full: "An applicant applies for a provisional licence through PHEQA's self-service." **\[paste the description]:** In Progressa, a private clinic must be licensed before it opens. The service is owed by the ministry of health, whose facilities unit receives applications and inspects. Applicants sign in through PNIA. (Invented for this example.) {% endtab %} {% tab title="Example output" %} {% hint style="warning" %} **Draft: model output, shortened and unverified.** Read it with the notes in the next tab, not on its own. {% endhint %} | # | Document | Adapted example | | -- | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | Own documents | The health act and its regulations on private facilities; \[to be read in the sector's law: the act and article that require a licence] | | 2 | Register of what was asked | R-03 The minister of health decides the licence (\[to be read in the sector's law: the article]) | | 3 | Records | The register of health facilities, kept by the facilities unit, one entry for each clinic under an identifier like FAC-00041 | | 6 | Shared groundwork | Kinds of facility: hospital, clinic, pharmacy. Kinds of licence: provisional, full. States of a licence: granted, suspended, cancelled. Application fee: \[to be read in the sector's law: the schedule of fees] | | 7 | Goal in full | An applicant applies for a provisional licence through the ministry's self-service, signing in through PNIA | | 12 | Working application | Generated from the accepted model; accepted once an officer of the facilities unit finishes a real task | *(Rows 4, 5, 8, 9, 10 and 11 follow the same pattern and are left out here.)* **Places to be read in the sector's law** 1. The act and article that require a clinic to be licensed. 2. The article under which the minister decides. 3. The schedule of fees. {% endtab %} {% tab title="Reading the output" %} This is the teaching part of the tip. Work through the output the way a chief architect would: what is earned, what is invented, what is missing.
1. The form is kept and the obvious names are replaced Every education name has gone: the facilities unit instead of PHEQA, a register of facilities instead of institutions, the education fee of 1,200 replaced by a marked place. The three places it lists are real questions for health officials.
2. Education's licence was carried across unmarked "Provisional, full" and "granted, suspended, cancelled" are education's, set by the Higher Education Regulations. Nothing in the description says a clinic's licence has two kinds or three states, and row 7 builds on it. These should have been marked. The safeguard is what catches them: the sector's officials correct the drafts, and nothing here is health law until one of them confirms it.
3. The kinds of facility came from general knowledge "Hospital, clinic, pharmacy" sounds right, and so it slips through. The description names clinics only, and a pharmacy may well be licensed by another body. The list belongs among the places to be read, with the question of who keeps it.
{% hint style="danger" %} **Safeguard.** The adapted examples are drafts for that sector's officials to correct. Nothing in them is taken as that sector's law until an official of the sector has confirmed it. {% endhint %} {% endtab %} {% tab title="What next" %} Hand the drafts to the officials who will correct them, named before the first document is written, and fill in the blank in [E6-6](/experience-digital-transformation/building-block/the-worked-examples/e6.6-what-another-sector-brings-and-what-stays-the-same-the-teams-blank-instrument.md). The new sector starts with its own catalogue, on [the blank catalogue](/experience-digital-transformation/building-block/the-blank-instruments/the-catalogue-of-the-sectors-services.md). {% endtab %} {% endtabs %} ## Sources This subtopic cites no public source. Its content is the specification-driven method itself, described at the level of the manager. --- # 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-6-run-the-method-in-your-administration/6.6-carry-the-method-to-another-sector.md?ask=&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.