> 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.2-phase-1-discover-map-what-the-sector-has-today.md). # 4.2 Phase 1, Discover — map what the sector has today Discovery produces one deliverable — an honest picture of what the sector has today, with no recommendations yet — signed off as accurate before any analysis begins. {% embed url="" %} EA lifecycle Phase 1: how to run Discovery on a government sector (\~4 min) {% endembed %} **Watch first (\~4 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.** Discovery produces one deliverable — an honest picture of what the sector has today, with no recommendations yet — signed off as accurate before any analysis begins. Watch it done on Progressa. ## The concept The first phase is Discover. One question: what exists today? Not what is wrong — that comes later. An accurate picture of where the sector is now. On Progressa, Discovery takes about three to four weeks and produces a single deliverable: the Discovery brief. Discovery collects five things on Progressa. The strategies in force — the national digital strategy, the education sector plan. The systems that exist — the school census system, the exam-management system, the social grant system. The registries and who owns them — the learner lists, the identity register. The stakeholders — the ministry, the authorities, the donors funding each piece. And the legal framework — the data-protection act, the mandates of each body. You gather, you do not judge. The hardest discipline in Discovery is to describe without recommending. When your architects find that the Examination Authority keeps its own learner list, the urge is to write 'this should be fixed'. Resist it. Discovery records that the list exists, who owns it, how many learners it holds. The judgement — is this a problem, how severe, what priority — belongs to the next phase. Mixing them biases the assessment before you have the full picture. Discover first. Judge second. Progressa's Discovery brief lays it out plainly. Five institutions, classified. The systems each runs. The registries — and here the brief simply records the fact that three separate learner lists exist, in the census, the Examination Authority, and the grant programme. The data flows — mostly paper and manual re-entry between systems. The legal constraints — what each body is mandated to hold. No recommendations. Just the picture, accurate enough to build on. Discovery ends with the first of the lifecycle's four sign-offs. The senior decision-maker — on Progressa, the digitalisation officer chairing the EA Board — confirms one thing: the picture is accurate enough to build on. Not complete, not perfect — accurate. This gate is cheap and fast, and skipping it is expensive: an assessment built on a wrong picture produces wrong priorities. Get the picture signed off as true, and the next phase stands on solid ground. ## Do this on your own sector — Draft your Discovery brief outline {% hint style="success" %} **✍️ Drafting play · produces A23 Discovery brief** **Bring:** your sector. From **A22, A0 §7 Legal and policy list** (see [Play 0](/experience-digital-transformation/gea/start-here/play-0-build-your-country-context.md)). **Get:** a Discovery brief outline with capture questions, a source column and the sign-off question. 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:** The brief is only as true as its sources. {% 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 starting Discovery on their own sector needs a brief outline that captures the right things and keeps recommendations out — so the picture is usable and the sign-off can challenge 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). ``` Draft a Discovery brief outline for [country X]'s [sector] sector. Structure it under the five collection areas: (1) strategies in force; (2) systems that exist; (3) registries and their owners; (4) stakeholders; (5) legal framework. For each area, list the specific questions to capture and the format to record the answer. Add a rule at the top: describe what is, do not recommend — recommendations belong to the Assess phase. Add a 'source' column so every entry records where it came from (document, interview, system). End with the sign-off question the decision-maker will be asked: is this picture accurate enough to build on? Output: a Discovery brief outline. ``` [Open in Claude](https://claude.ai/new?q=Draft%20a%20Discovery%20brief%20outline%20for%20%5Bcountry%20X%5D%27s%20%5Bsector%5D%20sector.%20Structure%20it%20under%20the%20five%20collection%20areas%3A%20%281%29%20strategies%20in%20force%3B%20%282%29%20systems%20that%20exist%3B%20%283%29%20registries%20and%20their%20owners%3B%20%284%29%20stakeholders%3B%20%285%29%20legal%20framework.%20For%20each%20area%2C%20list%20the%20specific%20questions%20to%20capture%20and%20the%20format%20to%20record%20the%20answer.%20Add%20a%20rule%20at%20the%20top%3A%20describe%20what%20is%2C%20do%20not%20recommend%20%E2%80%94%20recommendations%20belong%20to%20the%20Assess%20phase.%20Add%20a%20%27source%27%20column%20so%20every%20entry%20records%20where%20it%20came%20from%20%28document%2C%20interview%2C%20system%29.%20End%20with%20the%20sign-off%20question%20the%20decision-maker%20will%20be%20asked%3A%20is%20this%20picture%20accurate%20enough%20to%20build%20on%3F%20Output%3A%20a%20Discovery%20brief%20outline.) *(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 **A23** 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.3 Turn your Discovery brief into a ranked gap analysis](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.3-phase-2-assess-find-the-gaps-and-rank-them.md) See the full chain in [Your country workbook](/experience-digital-transformation/gea/your-country-workbook.md). {% endtab %} {% endtabs %} ## Sources * PAERA v1.0 §3.1.3 (Readiness Assessment) — * PAERA v1.0 §5.4 (Organisational Assessment & Roadmap) — --- # 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.2-phase-1-discover-map-what-the-sector-has-today.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.