> 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-1-why-a-paera-anchored-ea.md). # Module 1 β€” Why a PAERA-anchored EA Seven short videos that make the case for a national Enterprise Architecture anchored on PAERA. **Persona:** Strategist (CDO, Director-General, sector minister or ministerial-equivalent sponsor). **You leave with:** A1, A2, A3, A4, A5, A6, A7, filed in your country workbook. Runtime \~31 minutes across seven videos. Seven short videos that make the case for a national Enterprise Architecture anchored on PAERA β€” what it is, why projects cannot do it themselves, what the lifecycle looks like, and what to ask your minister for. Each video hands you one play to run on your own country. ## Subtopics | # | Subtopic | Single message | Your play | Kit skill | | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------- | ----------------------- | | [1.1](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.1-why-your-country-needs-a-national-ea.md) | Why your country needs a national EA | Without a shared plan for your government's digital systems, every new programme rebuilds what others have already built. The country pays. The citizen pays. Your minister cannot deliver what they promised. | πŸ” A1 | β€” | | [1.2](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.2-what-an-ea-actually-is-in-one-breath.md) | What an EA actually is, in one breath | An EA is the picture everyone agrees describes your government β€” minister, ministry CIO, donor, vendor. With it, you can lead the conversation. Without it, others lead it for you. | ✍️ A2 | β€” | | [1.3](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.3-why-projects-cant-do-this-themselves.md) | Why projects can't do this themselves | Procurement rules can require interoperability. They cannot deliver it. Only planning at the level of the whole government, supported by reference architectures, can. | ✍️ A3 | β€” | | [1.4](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.4-why-an-ea-matters-more-now-and-what-it-lets-your-minister-actually-do.md) | Why an EA matters more now β€” and what it lets your minister actually do | For thirty years, digital work meant putting paper online. That era is ending. The work now is to redesign how your ministry serves citizens β€” and that work needs business and IT in the same room, using the same words. | πŸ” A4 | β€” | | [1.5](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.5-why-paera-anchored-the-head-start-you-do-not-pay-for-twice.md) | Why PAERA-anchored β€” the head start you do not pay for twice | PAERA gives your team five years of head start. Adopt it, and the architecture work begins on day one. Do not adopt it, and your first year is spent inventing what others have already published. | πŸ” A5 | `paera-reference-check` | | [1.6](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.6-the-lifecycle-on-one-page.md) | The lifecycle on one page | Six months from start to a roadmap your minister can take to cabinet. Then ongoing governance. Five phases. Four sign-offs. One continuous practice. | ✍️ A6 | `ea-governance-drafter` | | [1.7](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.7-what-you-will-need-from-your-minister-and-how-to-ask-for-it.md) | What you will need from your minister β€” and how to ask for it | Four asks. A small permanent EA team. An EA Board with real authority. About two per cent of digital budget, sustained for five years. And one promise β€” that the team will not be pulled onto the urgent project of the week. | ✍️ A7 | `ea-governance-drafter` | ## How the plays chain in this module ```mermaid flowchart TD A0["A0 Country context pack\n(Play 0)"] A1["A1 Fragmentation diagnostic\n(1.1)"] A2["A2 Ministerial explainer slide\n(1.2)"] A3["A3 Re-use business case (directional)\n(1.3)"] A4["A4 Joint business–IT agenda\n(1.4)"] A5["A5 PAERA foundation coverage map\n(1.5)"] A6["A6 Phase RACI and role-gap list\n(1.6)"] A7["A7 EA Governance Board Terms of Reference\n(1.7)"] A0 --> A1 A1 --> A3 A1 --> A5 A0 --> A2 A2 --> A4 A0 --> A3 A3 --> A7 A0 --> A4 A4 --> A6 A0 --> A5 A5 --> A6 A0 --> A6 A6 --> A7 A0 --> A7 ``` The full chain, including where these artefacts come from and go next, is on [Your country workbook](/experience-digital-transformation/gea/your-country-workbook.md). {% hint style="info" %} **Before you start.** Every play asks you to paste country context. Build it once with [Play 0](/experience-digital-transformation/gea/start-here/play-0-build-your-country-context.md) β€” that is **A0**, and it feeds the whole chain. No country to hand? Run them on [Progressa](/experience-digital-transformation/gea/start-here/progressa-the-demonstration-country.md), the fictional demonstration country. {% endhint %} {% hint style="info" %} New to the plays? Read [How to use the plays](/experience-digital-transformation/gea/start-here/how-to-use-the-plays.md) and [Working with AI](/experience-digital-transformation/gea/start-here/working-with-ai-the-ground-rules.md) first β€” part of the about fifteen minutes of Start here, and they apply to every module of every Knowledge Product. {% 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/gea/module-1-why-a-paera-anchored-ea.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.