Use Case USCT(Unconditional Social Cash Transfer) User Flow Draft

Introduction

For the Unconditional Social Cash Transfer Use case applied user flow draft was created based on the research, analysis and discussions conducted with experts. 

Sandbox Use Case Analysis - USCT 1 (Unconditional Social Cash Transfer)

Scenario

There were various possible scenarios can be created for this use case. These scenarios may change based on several aspects, such as the existing e-government system, availability of electronic payment, delivery systems (if they are integrated or not), approaches (on demand versus administrator-driven), accessibility of personal devices and internet connection for citizens and so on. Therefore for the sandbox, our scenario simulates most generic flows for different roles that might help possible sandbox users to understand and learn the role of BBs and the GovStack approach as easily as possible while reflecting it on UI and flow. For this scenario, the government decision is taken that the unconditional cash transfer program is approved. The budget of the program, possible benefit packages and eligibility conditions have already been decided. Mass surveys were conducted to understand the socioeconomic conditions of citizens. This simulation shows possible steps that civil servants and citizen takes during the eligibility, enrollment and payment phases. These steps are selected based on previous research, analysis and discussions with experts.

Preconditions for the scenario: 

  • Citizens have been registered in the Foundational ID system.

  • Citizens have min-condition to access integrated e-government system through personal devices.

  • Countries have deployed a GovStack which required bricks for social protection, notably a national registry, a central social registry, consent management, and a payment building block which will centralise G2P payments.

  • The future beneficiary will be assigned with Personal Social ID number for all social programs. 

  • The electronic payment system is available.

  • Possible benefit packages and eligibility conditions have already been decided.

  • Information regarding possible beneficiaries and their needs was collected. 

Why Eligibility / Enrollment / Payment steps:

  • The role of the building blocks is clearer for the payment, and enrollment phases compare to other steps. There is more documentation for these phases.

  • Based on the discussions, focusing on these three steps will help us to create a more realistic use case. 

  • Focusing and applying these three phases allow us to create linear scenarios for possible users.

  • Impact - Effort - Confidence map also showed the importance of these three steps even though the map was created before Use Case Service Blueprint and discussions with experts.

  • The eligibility step will not include beneficiary packet design or determining the benefit levels. Based on the discussion, this step will only show the list of possible beneficiaries, their information and predetermined eligibility aspects.

User Flow Draft

Related Figma file can be found through the link:

The flow is created for users to experience the generic steps of the USCT simulation while understanding and learning the GovStack approach. For the user flow; steps, possible UI based on the roles, content on that pages and inspiration for these pages are shown. It is important to note that page names or content can be changed, and they are decided based on previous research. For future design, these contents should show the affect of the GovStack approach and how BBs will help the government services while giving a somewhat realistic experience. It should not be highly detailed to not confuse the users or pull their attention to the UI simulation. These simple steps and on contents should help users to realize the role of the BBs, how they help the government services and learn about the GovStack approach as simple as possible.

Possible UI integration of USCT for Sandbox Scenerio1

Also, it can be considered that possibility of interacting with the page while those interactions may affect the other roles' interfaces.

Demo user flow for different roles and integration BB

 

Related content