# Prioritize Services

## Service prioritization & ranking

Defining which services should be digitized first varies from country to country. Prioritization criteria are usually based on selecting high-impact use cases for citizens and businesses and the feasibility of digitalizing them using current and future reusable software components/building blocks - the Country´s technology stack. 

The experience gained from deploying and integrating different software components/building blocks and designing the underlying systems needed to enable the priority use cases allows digital teams to gain the necessary experience to work with a building block approach. As more services are developed with reusable software components/BBs, the faster each design and delivery cycle becomes reaching scalability in a more sustainable and cost-efficient manner.

<figure><img src="https://content.gitbook.com/content/u5bWcujHi8xQ0fq3b0rz/blobs/Pky9tCbdrM5215KCjAnV/2.%20Scaling%20approach%20(4)%20(1).jpg" alt=""><figcaption><p>Service Prioritisation Roadmap</p></figcaption></figure>

More information on how to deploy and integrate building blocks to enable digital government services is available in the [GovStack Sandbox documentation](https://govstack.gitbook.io/sandbox/).

{% tabs %}
{% tab title="Activites / resources" %}

* Rank the catalog of services based on your country´s criteria for impact and feasibility.&#x20;
* Set one or two exemplar services from quadrant A to work with implementing the GovStack approach to [digital service co-design and delivery](https://specs.govstack.global/implementation-playbook/development/annex/service-design)

<figure><img src="https://content.gitbook.com/content/u5bWcujHi8xQ0fq3b0rz/blobs/fGTdbgqlwzvOd01Yn6hh/Scherm_afbeelding%202023-02-24%20om%2012.08.27%20(1).png" alt=""><figcaption></figcaption></figure>

* The below criteria are a reference. Each digital team can calibrate current criterion according to information availability, context & needs:

<table data-header-hidden><thead><tr><th width="120.27272727272725">Criteria</th><th width="119">Indicator</th><th>RFI input</th></tr></thead><tbody><tr><td>Strategic importance </td><td>Users demand </td><td><p></p><ul><li>Number of transactions per month </li><li>Number of service users    </li><li>Is a cross-border service  </li></ul></td></tr><tr><td>Impact </td><td>Complexity to access the service  </td><td><ul><li>Number of in person visits to a government office (customer visits required to get the service) </li><li>Number of prerequisites and documents</li><li>Time to response from Government to get the service (days/months)</li><li>Steps for follow-up &#x26; tracking</li><li>Number of Govt agencies involved </li></ul></td></tr><tr><td> </td><td>Government Impact </td><td><ul><li>Environmental footprint (Documents, commutes.) </li></ul></td></tr><tr><td> </td><td>Business impact </td><td><ul><li>Public Private Partnership </li><li>Attraction of Foreign Direct Investment  </li></ul></td></tr><tr><td> </td><td>Technical impact </td><td><ul><li>The service is a shared service, like Identity, payment, digital signature, among others that can be re-use and integrated with other government entities systems to enable digital services. </li></ul></td></tr><tr><td>Technical feasibility </td><td>Technical capacity  </td><td><ul><li>Digital skills required to enable the digital service </li></ul></td></tr><tr><td> </td><td>Financial resources </td><td><ul><li>Degree of existing Building Blocks that can be reuse to enable the service </li></ul></td></tr><tr><td> </td><td>Reliance on other technologies  </td><td><ul><li>Degree of existing infrastructure </li></ul><p> </p></td></tr><tr><td>Political feasibility  </td><td>Political acceptability  </td><td><ul><li>Alignment with national digital agenda - Services that a presidential or ministerial commitment.</li></ul><p> </p></td></tr><tr><td> </td><td>Regional harmonization  </td><td><ul><li>Data Taxonomy / Semantics </li><li>Regulatory synergies  </li></ul></td></tr><tr><td> </td><td>Stakeholder consensus  </td><td><ul><li>Number of Govt Agencies involved in the user journey that work well together </li></ul></td></tr></tbody></table>

* Continuously recalibrate the ranking based on:
  * Learnings of the different design and delivery cycles and as re-usability of BBs become common practice across digital teams.&#x20;
  * Simplification measures applied to the service catalog. For example, eliminating services associated with getting documents that another government entity requires by automatic consultations to different registries in government entities using [IM BB](https://govstack.gitbook.io/bb-information-mediation/v/information-mediation-1.0).&#x20;
  * Re-designing user journeys based on live events and proactively delivering them using event-driven architectures. Refer below examples from Estonia's vision documents on proactive services and event-driven architecture:

{% file src="<https://content.gitbook.com/content/u5bWcujHi8xQ0fq3b0rz/blobs/ZyilKooWIjfMcY8ohmFR/KrattVisionPaper.pdf>" %}

{% file src="<https://content.gitbook.com/content/u5bWcujHi8xQ0fq3b0rz/blobs/z2lDqRcYFgAOjZiMjDYl/Next%20Generation%20Digital%20Government%20Architecture%20(1).pdf>" %}
{% endtab %}

{% tab title="Responsibilities" %}
Who does what:

* Head of Service Design - Lead the integration of the service catalog.
* Service Design and Delivery Focal point - Complement and update the service catalog with services from their organizations. They follow up and coordinate the actions within their organization to digitize services according to the approved digitization roadmap
  {% endtab %}

{% tab title="Deliverables" %}

* Service prioritization criteria
* Ranked priority services
  {% endtab %}
  {% endtabs %}