> 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/roadmap/the-worked-examples.md).

# The worked examples

These nine files show what each step of the method for assessing a country's digital public infrastructure and writing its roadmap produces, using Progressa, the fictional country used across these knowledge products. They form one story: Progressa's desk assessment and questionnaires lead to one maturity table, its gaps are registered and ranked, the roadmap addresses those gaps, the investment case costs the roadmap, and the validation round answers comments on both.

| File                                                                                                                                                                                                  | Step                                    | What it shows                                                                                              |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| [E1\_five-domain-frame.md](/experience-digital-transformation/roadmap/the-worked-examples/e1-the-five-domain-frame-set-for-progressas-education-sector.md)                                            | 1. Frame the assessment                 | The five domains read from PAERA, and Progressa's one-page scope                                           |
| [E2\_automatic-desk-assessment.md](/experience-digital-transformation/roadmap/the-worked-examples/e2-the-automatic-desk-assessment-the-question-bank-and-a-run-for-progressa.md)                      | 2. Run the automatic desk assessment    | The question bank and workflow, and a desk run on Progressa's public record                                |
| [E3\_domain-questionnaire.md](/experience-digital-transformation/roadmap/the-worked-examples/e3-the-digital-data-questionnaire-the-blank-instrument-and-a-completed-extract-for-progressa.md)         | 3. Put one questionnaire to each domain | The blank Digital Data questionnaire with its guides, and a completed extract                              |
| [E4\_verification-templates.md](/experience-digital-transformation/roadmap/the-worked-examples/e4-verification-the-blank-templates-and-how-progressas-team-used-them.md)                              | 4. Verify the answers                   | Blank verification templates, and three points Progressa's team verified                                   |
| [E5\_domain-report-and-maturity-table.md](/experience-digital-transformation/roadmap/the-worked-examples/e5-the-digital-data-domain-report-and-progressas-maturity-table.md)                          | 5. Score and report                     | The scoring rule, the Digital Data domain report, and the maturity table and findings for all five domains |
| [E6\_gap-register.md](/experience-digital-transformation/roadmap/the-worked-examples/e6-the-gap-register-and-its-priorities-for-progressa.md)                                                         | 6. Consolidate and rank the gaps        | The gap report outline, the priority rule, and Progressa's gap register                                    |
| [E7\_roadmap.md](/experience-digital-transformation/roadmap/the-worked-examples/e7-progressas-education-dpi-roadmap-the-shape-of-the-document-with-the-first-horizon-in-full.md)                      | 7. Write the roadmap                    | The roadmap's structure, with the first horizon in full and the component register                         |
| [E8\_investment-case.md](/experience-digital-transformation/roadmap/the-worked-examples/e8-the-investment-case-for-progressas-roadmap-in-four-sheets.md)                                              | 8. Lay out the investment case          | The four sheets: cost by component, cost by domain, funding sources, returns                               |
| [E9\_validation-response-matrix.md](/experience-digital-transformation/roadmap/the-worked-examples/e9-validation-and-revision-progressas-response-matrix-and-the-ai-prompts-that-run-the-revision.md) | 9. Validate and revise                  | The four-phase revision with its AI prompts, and Progressa's response matrix                               |

**How the files link.** Findings carry identifiers `F-…` (E5), gaps `G-…` (E6), roadmap components `C-…` (E7), investment lines `INV-…` (E8) and comments `CM-…` (E9). Each gap names its findings, each component names its gaps, each investment line names its component, and each comment names what it refers to, so a reader can follow any budget line back to the evidence behind it.

**The scale.** Maturity is scored on the five stages of the UNDP Digital Development Compass — Basic, Opportunistic, Systematic, Differentiating, Transformational — on its range of 0 to 5. The five domains are PAERA's. How the scale is applied to the domains is the team's own rule, stated in E5.

**The figures.** Every figure about Progressa is invented and every table of figures is illustrative. Figures from public sources are quoted with their source and year.


---

# 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/roadmap/the-worked-examples.md?ask=<question>&goal=<user_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.
