> 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/gea/module-5-evidence-rollout-and-the-case/5.3-roll-it-out-across-sectors-and-why-the-second-is-cheaper.md). # 5.3 Roll it out across sectors — and why the second is cheaper The method is sector-agnostic — only the record at the centre changes — so roll it out as a wave roadmap: one sector first to build the shared platforms. {% embed url="" %} Scaling Enterprise Architecture across government sectors: the wave rollout (\~5 min) {% endembed %} **Watch first (\~5 min).** Then come back for the play. The video's recap slide carries an on-screen practice box — it is not narrated — and this page is where that box points. > **Single message.** The method is sector-agnostic — only the record at the centre changes — so roll it out as a wave roadmap: one sector first to build the shared platforms, then sectors one at a time, each cheaper than the last, governed into a single national architecture. ## The concept Suppose you want this beyond one sector. Two questions follow: does the method travel, and how do you roll it out without trying to do everything at once? The answers are linked — and the second sector is cheaper than the first. Most of the method does not change. The five phases, the four sign-offs, the six deliverables, the reuse-before-build default, the binding governance board — none of that is specific to one sector. What changes is only the record at the centre of the fragmentation. In education it is the learner. In health it is the patient. In agriculture the farmer; in social protection the beneficiary. Different domain, identical shape — registered several times, re-entered on paper, blocking a flagship the minister has promised. The problem rhymes across sectors because the cause is the same: no shared plan. Which means you are not buying a one-sector tool. You are building a national capability, of which the first sector is the foundation and the proof. So roll it out in waves. Wave one is one sector, done well. Pick the sector with a clear flagship the minister cares about — the single learner record, the single patient record — and run the full method there, end to end. But notice what wave one really builds: not just that sector's architecture, but the national foundations. The permanent team. The governance board. The first shared platforms, identity and data exchange. Wave one looks like one sector. It is actually the foundation the whole rollout stands on. From wave two, each new sector consumes what wave one built. The health sector uses the identity platform and the data-exchange backbone that already exist. Its run of the method is lighter, because the team, the framework and the governance are in place. It delivers faster and costs less, and every sector that joins makes the next one easier still. That is why the expensive part is building the muscle once. But it only compounds if you govern it. The same board that reviews projects inside a sector governs the national pipeline: which sector comes next, what each must reuse, where an exception is genuinely warranted. A rollout that is launched and left drifts back into fragmentation, one sector at a time. Then report the national picture upward, on one page, every quarter. How many sectors are live. The re-use rate across them. Which shared platforms are in place. This shows the minister a national capability actually growing — which is what sustains funding across a change of government — and it lets you see early if a sector is drifting from the shared foundation, while correction is still cheap. ## Do this on your own sector — Sequence your national rollout into waves {% hint style="success" %} **✍️ Drafting play · produces A31 National rollout wave plan** **Bring:** your sectors and their flagships. From **A26, A28, BB status register** (see [Your country workbook](/experience-digital-transformation/gea/your-country-workbook.md)). **Get:** a national wave sequence with per-wave reuse, plus the scorecard metrics. As text in the chat, not a file or a chart. **Time:** \~20 min · **Assistant:** any; the plays are tool-neutral. **With the kit:** no skill in this release, so the prompt runs bare in any assistant. **Watch for:** Directional sequencing, not a plan of record — a sector scheduled before its shared platform is authoritative will slip. {% endhint %} ✍️ **Drafting play.** You give a few facts; the play produces a first draft of a document you will edit. **What it does.** A Strategist with commitment in hand needs a national rollout sequenced as waves — which sector first to build the foundations, then which to bring on, each reusing the last — plus the scorecard to report it. {% 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](/experience-digital-transformation/gea/start-here/how-to-use-the-plays.md). ``` I am planning a national EA rollout for [country X] across these sectors [list them, with the flagship outcome each has if known]. Sequence it into waves. (1) Wave 1: recommend the foundation sector — the one with the clearest flagship — and note that Wave 1 also stands up the permanent team, the governance board, and the first shared platforms (identity, data exchange). (2) Waves 2 onward: order the remaining sectors, and for each name what it REUSES from earlier waves (which shared platforms) versus what is new. (3) The national scorecard: the few metrics to report quarterly (sectors live, re-use rate, shared platforms in place). Output: a wave sequence with reuse noted per wave, plus the scorecard metrics. ``` [Open in Claude](https://claude.ai/new?q=I%20am%20planning%20a%20national%20EA%20rollout%20for%20%5Bcountry%20X%5D%20across%20these%20sectors%20%5Blist%20them%2C%20with%20the%20flagship%20outcome%20each%20has%20if%20known%5D.%20Sequence%20it%20into%20waves.%20%281%29%20Wave%201%3A%20recommend%20the%20foundation%20sector%20%E2%80%94%20the%20one%20with%20the%20clearest%20flagship%20%E2%80%94%20and%20note%20that%20Wave%201%20also%20stands%20up%20the%20permanent%20team%2C%20the%20governance%20board%2C%20and%20the%20first%20shared%20platforms%20%28identity%2C%20data%20exchange%29.%20%282%29%20Waves%202%20onward%3A%20order%20the%20remaining%20sectors%2C%20and%20for%20each%20name%20what%20it%20REUSES%20from%20earlier%20waves%20%28which%20shared%20platforms%29%20versus%20what%20is%20new.%20%283%29%20The%20national%20scorecard%3A%20the%20few%20metrics%20to%20report%20quarterly%20%28sectors%20live%2C%20re-use%20rate%2C%20shared%20platforms%20in%20place%29.%20Output%3A%20a%20wave%20sequence%20with%20reuse%20noted%20per%20wave%2C%20plus%20the%20scorecard%20metrics.) *(experimental deep link: pre-fills the prompt in a new claude.ai chat; check the bracketed parts before sending)* *Input, output and the kit skill are in the box above.* {% endtab %} {% tab title="Example on Progressa — coming" %} {% hint style="warning" %} **Worked example pending.** The prompt above is final and runs today. The Progressa worked example, the annotated reading and the what-next notes are added when this module's examples are run (Module 1 shows the shape). {% endhint %} Run the play on [Progressa](/experience-digital-transformation/gea/start-here/progressa-the-demonstration-country.md) yourself in the meantime: paste the sections named in **Bring** above, and read the result against **Watch for**. {% endtab %} {% tab title="What next" %} File the output as **A31** in your country workbook once you have worked it the way **Watch for** asks. A fuller what-next is added with the worked example. **This artefact feeds:** 5.3b Map the method to a second sector, [5.6 Draft your closing one-page case for the minister](/experience-digital-transformation/gea/module-5-evidence-rollout-and-the-case/5.6-the-closing-case-proven-portable-and-necessary-now.md) See the full chain in [Your country workbook](/experience-digital-transformation/gea/your-country-workbook.md). {% endtab %} {% endtabs %} ## Sources * PAERA v1.0 §5.7 (Recommended Roadmap) — * PAERA v1.0 §5.4 (Organisational Assessment & Roadmap) — *** ## Also on this page — Map the method to a second sector {% hint style="info" %} **GitBook only — no video.** This play has no video of its own: it was folded into 5.3 when the module was tightened to six videos. The play is unchanged and still produces its artefact, so it lives here rather than being dropped. {% endhint %} {% hint style="success" %} **🔁 Translation play · produces A28 rev.2 Second-sector map** **Bring:** the first and second sectors and the second sector's bodies. From **A28, A31, BB status register** (see [Your country workbook](/experience-digital-transformation/gea/your-country-workbook.md)). **Get:** a one-page transfer map, including what is reused. As text in the chat, not a file or a chart. **Time:** \~20 min · **Assistant:** any; the plays are tool-neutral. **With the kit:** no skill in this release, so the prompt runs bare in any assistant. **Watch for:** This is a starting structure, not an assessment — confirm the gaps by running discovery on the real sector. {% endhint %} 🔁 **Translation play.** You give a question in one group's language; the play restates it for another. **What it does.** A Strategist weighing a multi-sector commitment wants a quick, concrete map of how the method would run on a second sector — what changes, and what it can reuse from the first. {% 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. ``` I have run, or plan to run, the EA method on [country X]'s [first sector]. I am considering [second sector]. Here are its main bodies [list them, one line each]. Produce a one-page map. (1) Classify each body (policy unit / regulatory agency / service-delivery authority / state registry / shared platform). (2) Name this sector's equivalent of the central duplicated record (the learner, the patient, the farmer, the beneficiary) and the flagship it is blocking. (3) Name the six deliverables for this sector. (4) List what this sector can REUSE from the first sector's work — the identity platform, the data-exchange backbone, the team, the framework, the governance — versus what is genuinely new. Output: a one-page map under those four headings. ``` [Open in Claude](https://claude.ai/new?q=I%20have%20run%2C%20or%20plan%20to%20run%2C%20the%20EA%20method%20on%20%5Bcountry%20X%5D%27s%20%5Bfirst%20sector%5D.%20I%20am%20considering%20%5Bsecond%20sector%5D.%20Here%20are%20its%20main%20bodies%20%5Blist%20them%2C%20one%20line%20each%5D.%20Produce%20a%20one-page%20map.%20%281%29%20Classify%20each%20body%20%28policy%20unit%20%2F%20regulatory%20agency%20%2F%20service-delivery%20authority%20%2F%20state%20registry%20%2F%20shared%20platform%29.%20%282%29%20Name%20this%20sector%27s%20equivalent%20of%20the%20central%20duplicated%20record%20%28the%20learner%2C%20the%20patient%2C%20the%20farmer%2C%20the%20beneficiary%29%20and%20the%20flagship%20it%20is%20blocking.%20%283%29%20Name%20the%20six%20deliverables%20for%20this%20sector.%20%284%29%20List%20what%20this%20sector%20can%20REUSE%20from%20the%20first%20sector%27s%20work%20%E2%80%94%20the%20identity%20platform%2C%20the%20data-exchange%20backbone%2C%20the%20team%2C%20the%20framework%2C%20the%20governance%20%E2%80%94%20versus%20what%20is%20genuinely%20new.%20Output%3A%20a%20one-page%20map%20under%20those%20four%20headings.) *(experimental deep link: pre-fills the prompt in a new claude.ai chat; check the bracketed parts before sending)* *Input, output and the kit skill are in the box above.* {% endtab %} {% tab title="Example on Progressa — coming" %} {% hint style="warning" %} **Worked example pending.** The prompt above is final and runs today. The Progressa worked example, the annotated reading and the what-next notes are added when this module's examples are run (Module 1 shows the shape). {% endhint %} Run the play on [Progressa](/experience-digital-transformation/gea/start-here/progressa-the-demonstration-country.md) yourself in the meantime: paste the sections named in **Bring** above, and read the result against **Watch for**. {% endtab %} {% tab title="What next" %} File the output as **A28 rev.2** in your country workbook once you have worked it the way **Watch for** asks. A fuller what-next is added with the worked example. **This artefact feeds:** nothing further in this course; this artefact is where the chain ends See the full chain in [Your country workbook](/experience-digital-transformation/gea/your-country-workbook.md). {% endtab %} {% endtabs %} --- # 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/gea/module-5-evidence-rollout-and-the-case/5.3-roll-it-out-across-sectors-and-why-the-second-is-cheaper.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.