> 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-4-progressa-end-to-end-the-method-on-one-sector/4.1-meet-progressa-a-real-sector-with-a-real-fragmentation-problem.md). # 4.1 Meet Progressa — a real sector with a real fragmentation problem Progressa is a demonstration education sector with the fragmentation problem most countries share — the same learner registered in several places, identity proven on paper. {% embed url="" %} An Enterprise Architecture worked example: an education sector's fragmentation problem (\~3 min) {% endembed %} **Watch first (\~3 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.** Progressa is a demonstration education sector with the fragmentation problem most countries share — the same learner registered in several places, identity proven on paper. Meet its institutions and its problem, because the rest of this topic runs the full method on exactly this canvas. ## The concept To see the method work, you need a realistic place to run it. Progressa is a demonstration country with an education sector like many across the continent — real institutions, a real fragmentation problem, and a minister who wants results. Progressa's education sector has five bodies that matter. The Ministry of Education, Youth and Sport sets policy and funds schools. The National Examination Authority runs examinations and certifies results. The Learner Registry is meant to be the one list of who is a learner. The National Identity Authority owns the person identity every sector reuses. And the Digital Government Authority runs the shared data-exchange backbone and payments. Five bodies — a policy unit, a service authority, two registries, and a shared-platform provider. Here is the problem the minister feels. A learner is registered three times — once in the school census, once by the Examination Authority for exams, once by a social grant programme. None of the three lists agree. A parent proves the child's identity on paper at every counter, because no system trusts another's. The minister has promised a single learner record that follows the child from primary school to university — and it cannot be delivered, because the systems do not fit together. This is not a Progressa problem. It is the problem most education sectors share. Progressa is fictional on purpose: it shows every step without exposing any real country, and its shapes — duplicate registries, paper re-entry, a stalled flagship — are the ones you will recognise. At each step, ask what the equivalent would be in your own sector. Running the method on Progressa produces six things across the five phases: a picture of what exists today, a ranked gap analysis, a localised framework with build, buy or share calls, a target architecture, a sequenced costed roadmap, and a living, governed architecture — six deliverables, produced in that order. ## Do this on your own sector — Build your own demonstration canvas {% hint style="success" %} **✍️ Drafting play · produces A22 Demonstration canvas** **Bring:** your sector and its main bodies. From **A0 §6 Public bodies, systems and registries, A12, A13, the sector problem paragraph** (see [Play 0](/experience-digital-transformation/gea/start-here/play-0-build-your-country-context.md)). **Get:** a one-page canvas (bodies, symptoms, stalled flagship). As text in the chat, not a file or a chart. **Time:** \~10 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:** A canvas is a simplification, not an assessment. {% endhint %} ✍️ **Drafting play.** You give a few facts; the play produces a first draft of a document you will edit. **What it does.** An architect about to learn the method on Progressa learns faster with their own sector as a parallel canvas. This prompt produces a one-page canvas mirroring Progressa, to run the method against. {% 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). ``` Build a one-page demonstration canvas for [country X]'s [sector] sector, mirroring the Progressa education example. Produce: (1) the main public bodies and a one-line role for each, classified as policy unit / regulatory agency / service-delivery authority / state registry / shared platform; (2) the fragmentation symptoms likely present — duplicate registries (what is registered more than once), paper re-entry, point-to-point integration, a capability with no clear owner; (3) the 'stalled flagship' — the one cross-cutting outcome a minister has promised that the fragmentation is blocking. Output: a one-page canvas under those three headings, to run the five-phase method against. ``` [Open in Claude](https://claude.ai/new?q=Build%20a%20one-page%20demonstration%20canvas%20for%20%5Bcountry%20X%5D%27s%20%5Bsector%5D%20sector%2C%20mirroring%20the%20Progressa%20education%20example.%20Produce%3A%20%281%29%20the%20main%20public%20bodies%20and%20a%20one-line%20role%20for%20each%2C%20classified%20as%20policy%20unit%20%2F%20regulatory%20agency%20%2F%20service-delivery%20authority%20%2F%20state%20registry%20%2F%20shared%20platform%3B%20%282%29%20the%20fragmentation%20symptoms%20likely%20present%20%E2%80%94%20duplicate%20registries%20%28what%20is%20registered%20more%20than%20once%29%2C%20paper%20re-entry%2C%20point-to-point%20integration%2C%20a%20capability%20with%20no%20clear%20owner%3B%20%283%29%20the%20%27stalled%20flagship%27%20%E2%80%94%20the%20one%20cross-cutting%20outcome%20a%20minister%20has%20promised%20that%20the%20fragmentation%20is%20blocking.%20Output%3A%20a%20one-page%20canvas%20under%20those%20three%20headings%2C%20to%20run%20the%20five-phase%20method%20against.) *(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 **A22** 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:** [4.2 Draft your Discovery brief outline](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.2-phase-1-discover-map-what-the-sector-has-today.md) See the full chain in [Your country workbook](/experience-digital-transformation/gea/your-country-workbook.md). {% endtab %} {% endtabs %} ## Sources * PAERA v1.0 §2.1 (Problem statement) — * PAERA v1.0 §2.3 (Role of Enterprise Architecture) — --- # 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-4-progressa-end-to-end-the-method-on-one-sector/4.1-meet-progressa-a-real-sector-with-a-real-fragmentation-problem.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.