Playbook Update Proposal

Owned by Farina Owusu
Last updated: Dec 04, 2024 by Nico Lueck
3 min read

Aim: Make the playbook more accessible by creating different target group specific paths through the playbook

  • we divided the target audiences into two large groups

    • managerial staff (institutional decision-makers and political/ governance advisors)

    • digital teams involved in the digitization of government services

  • The 4 groups of people, as suggested by Ramkumar, could be included into these two groups

    • Policy

    • Processes

    • Provisioning

    • Practitioner

  • Before the two different paths for the target groups begin, a few short questions guide the reader toward the correct path based on their interests.

    • Possibly linking directly to corresponding chapters

    • this sort of questionnaire/ decision tree could also be included into the GovStack website as part of “GovLearn” to direct the audience to the right resources

 

Structure for managerial level (institutional decisionmakers and political/governance advisors)

The GovStack approach - a toolbox to build Digital Public Infrastructure

  • An intro to Digital Public Infrastructure and Digital Public Goods

  • GovStack’s Building Blocks - foundations for Digital Public Infrastructure

  • How GovStack's governance structures ensure sustainability

Creating the right framework for GovStack adoption

  • Defining priority areas and services

  • Integrating the GovStack approach in the country's digital strategy and roadmap

  • Assessing readiness and learning needs of key actors

Getting institutions ready for the GovStack journey

  • Developing a change management approach

  • The capacity building journey

  • Training for technical and non-technical skills

Digitizing public services in the GovStack framework

  • Setting up digital teams and assigning responsibilities

  • Co-designing a scaling strategy/digitization roadmap

Exchanging

  • Communities of practice (focus on CoPs for managerial staff)

 

 

 

Structure for "digital teams" involved in the digitization of government services

How can GovStack enable an efficient transition to digital public services?

Creating the right framework for GovStack adoption

  • Defining a reference architecture

  • Setting up a one-stop-shop for all services

Digitizing services in the GovStack framework

  • Co-designing a scaling strategy/digitization roadmap

  • All sub pages of "design & delivery"

Staying up to date

  • Local and global knowledge management

  • Technical communities of practice

 

Suggestion by Puja and Nico on 04.12.2024

image-20241204-113236.png
Following along the lines of such a process diagram of an implementation journey

Introduction

  • How to use playbook

  • Building Block Introduction

  • “Adopt govstack” content but change title

Planning

  • Maturity Assessment

  • Reference Architectre → PAERA Enterprise Architecture

  • Digital Team Composition

Design

  • eGov Portal (page “service catalog” and page “one-stop-shop”)

  • Services (all pages relating to service design)

  • System Architecture and Requirement Engineering → Brief introduction and link to GovSpecs

  • Solutioning/Market Research → Brief introduction and link to GovMarket

Prototyping (no enough content yet)

Procurement (no enough content yet)

Development (no enough content yet)

  • “Launch service”

Operations (no enough content yet)

Strategy & Management

  • Digital Strategy

  • Scaling Strategy

  • Learning and Exchange → Capacity Building Strategy

  • Change Mangement

Terminology

GovStack Resources

Contributor

Versions

 

Others

  • “Country use cases” integrate devlierables as examples in other chapters. Delete all content on PM

  • “Artefacts” to main level and call it “GovStack resources” and delete many dead links

  • “Terminilogy” delete all terms which can be googled within 10 seconds