Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Goal

Make State and eGov data-driven by providing easy, readable, and relevant data in 2021 🎯

Why

State and we at eGov need to be able to make data-driven decisions to improve our services and products respectively. Data is key in measuring success. For instance,

State

Data will help the State to build the right capacity, understand before/after of using DIGIT i.e. our impact and improvement areas, etc.

eGov

Data will help eGov

  • to reinforce citizens' trust in digital governance services/products

  • to make a strong value proposition for different state bodies and implementation Partners

  • to understand DIGIT performance for improvement

What

(A) Defining the right impact/adoption metrics for success

We will define key metrics for impact and adoption for the State and for ourselves. These metrics will have some overlap as both the entities should essentially focusing on serving the citizens (smile)

Below themes are to kickstart our process. Based on these, we will define specifics for each product/service

ULB arena

Theme

Parameters

Comments

Performance

  • Service Efficiency

  • State/ULB/Employee Efficiency

Revenue

  • Sources

  • Growth

ULB Engagement

  • Accessibility

  • Usability

The State might only be concerned about overall usability for its employees

Citizen Engagement

  • Reach

  • Sentiment

Citizen arena

Theme

Parameters

Comments

Acquisition

  • Channels

  • Reach

  • Messaging

Engagement

  • Intention (What purpose the citizen comes on the product?)

  • Accessibility

  • Usability/ Ease of use

    • Speed

    • Understandability

  • Transparency

  • Sentiment

Recurring

  • Frequency

(B) Making the data accessible and readable for the State and eGov teams

(B.1) Improve DSS

Our DSS services

(B.2) Prepare Analytical Data Mart for eGov team

OR use Kibana dashboards etc

How

(1) Defining the right impact/adoption metrics for success

Stakeholders: Leadership Team (also acts as Citizen Representative), State Representative

Participants: POC from Product Team, GTM Team, Implementation Team

15-Feb202122-Feb01-Mar08-Mar15-Mar22-Mar29-Mar05-Apr12-Apr19-Apr26-Apr03-May10-May17-May24-May31-May07-Jun14-Jun21-Jun28-Jun05-Jul12-Jul19-Jul26-Jul02-Aug09-Aug16-Aug23-Aug30-Aug06-Sep13-Sep20-Sep27-Sep04-Oct11-Oct18-Oct25-Oct01-Nov08-Nov15-Nov22-Nov29-Nov06-Dec13-Dec20-Dec27-Dec03-Jan202210-Jan17-JanMarker 1
Improve DSS
ADM

New Bar

New Bar

New Bar

When

  • No labels