top of page

Srot | Strengthening
Child Protection Systems

Data collection and visualization tools to drive digital transformation

Tough one...

What was your objective?

Srot aimed to address the critical issue of child vulnerability in India, where approximately 100,000 children go missing annually. Srot, a nonprofit is dedicated to building and fortifying child protection systems to ensure the safety, support, education, and protection of the most vulnerable children. Srot's overarching goal is to provide these children with childhoods free from trafficking, child marriage, hazardous work, violence, and exploitation.

Project Tags : UX Research and System Thinking 

Problem statement

Srot confronts the challenge of scaling its impact tenfold to address the alarming number of missing children in India. Leveraging the widespread use of mobile phones, the design goal is to craft two digital solutions for scalability and efficiency, ensuring Srot effectively safeguards the most vulnerable children.

Screenshot 2023-12-06 at 6.42.52 PM.png


Scale of Impact:

Srot aspires to extend its impact tenfold, reaching a significantly larger number of children.

Digital Transformation Opportunity:

The widespread use of mobile phones across India presents an opportune moment for Aangan to digitize its programs for increased accessibility and efficiency.

Design Process

  1. Problem Identification

  2. Stakeholder Mapping 

  3. Service Blueprint

  4. Product Ideation

  5. Prototype Development

6. Iterative Design Thinking

7. Accessibility Considerations

8. Real-time Dashboard Development

9. Critical Indicator Implementation

10. Continuous Improvement

Let's look at the approach we took:

In 2019, Srot provided training to 5,153 women and engaged 854 officials, positively impacting 1,30,284 children. By 2019-2020, their multi-layered programs enhanced the safety of 4,15,172 hard-to-reach vulnerable children. These outcomes were achieved through empowering community members and implementing reporting systems. However, manual data collection on handwritten forms introduced challenges of accuracy and reliability, coupled with a time-consuming survey sorting process. A need-finding workshop with Srot's team highlighted challenges faced by the core team, training and impact associates, and community data collectors, paving the way for targeted design solutions.
Problem Identification:

  • Identified challenges in manual data collection, including accuracy issues and time-consuming processes.

  • Conducted a need-finding workshop to understand the specific pain points of key stakeholders.

Integrated Solution:

  • Mapped the needs of core team members, training & impact associates, and community data collectors.

  • Recognized the difficulties faced in manual data compilation and

      on-ground data collection.


Product Design

Few Intuitive User Experiences:

Srot envisions bringing technology to regions with limited engagement. The examples below demonstrate how facilitators interact with their Android app, showcasing how the application operates.


Homepage :

Choosing the right form and access to hamburger with account customization option

The homepage has been designed based on using the list layout the homepage is structured using a list layout, presenting information in a linear and vertically aligned format. This layout is commonly employed for its simplicity and efficient presentation of content in a sequential order, making it particularly suitable for scenarios requiring a clear and structured display of information.

Reminders as Schedule flow :

Facilitators responsible for data collection find scheduling events to be a critical task.

Facilitators can utilize the calendar feature in the app to set reminders for various events during their data collection activities. Schedule flow is the most logical layout option for this action.


Hamburger menu:

Access account settings, personal preferences, and other form-related details through the hamburger menu.

we incorporated the hamburger menu, also known as the navigation or side menu, for infrequently accessed options. This menu provides quick access to features like account settings, user profiles, personal information, and notification settings.


List view vs card picking  to choice of form:

Because the number of forms was more than 25 we thought of using a list view for easy scrolling

Initially, facilitators utilized a card-picking method for selecting forms. However, with the growing number of forms and time consumption observed during testing, we recognized that a list-based solution would be more efficient.


Form management:

This flow was used for the user's actions and choices within the form, including selecting, modifying, or deleting specific elements.

In the list view flow, managing a form with a range of 40 to 100 questions posed challenges in tracking errors during surveys. Recognizing the importance of easy access to functions like deleting, clearing, and iterating through each question, form management tools were introduced in this section.

Summary of User Interaction Flows  

Login/Authentication Flow:

User authentication process.

Homepage Navigation:

Navigation to different sections or forms.

Form Selection Flow:

Choosing a specific survey or form type.

Form Input Flow:

Entering details and responses into the selected form.

Question Management Flow: 

Handling individual questions, including deletion and clearing.

Submission Flow::

Submitting the completed form.

Error Handling Flow:

Managing and resolving errors 

Permissions Flow:

Managing app permissions required for survey tasks.

Notification Flow:

Handling notifications related to survey updates or completion.

Profile/Account Settings Flow:

Managing user profiles, preferences, and account settings.

Feedback/Support Flow:

Providing feedback or

accessing support features.

Offline Mode Flow:

Handling survey tasks when

the device is offline.

Data Sync Flow:

Synchronizing survey data with a server.

Settings Configuration Flow:

Configuring app settings such

as language, theme, etc.

Survey Analytics Flow:

Viewing analytics or insights

related to survey responses.

Form Editing Flow:

Editing or updating

existing survey forms.

Survey Export Flow:

Managing and

resolving errors 

Exporting survey data or reports.

Visual representation of progress within a survey.

Tutorial/Onboarding Flow:

Guiding users through app features

during the first use.

Logout Flow:

Logging out or

ending a user session.

Real-time Dashboard Development:
  • Developed a real-time dashboard to track survey results.

  • Designed the dashboard to present information in multiple formats and generate granular insights.

Accessibility Considerations:
  • Designed for low literacy by incorporating voice recording of content, simplifying language, and providing translations.

  • Ensured confidentiality by not collecting personal information, maintaining user anonymity.

Service blueprint:
  • A service blueprint to helped us map the gaps of the shortfall of language understanding level during the interactions in the data collection process.

  • Collaborated with Srots(an organisation working on the same subject) core team to understand the workflow and challenges thoroughly.

Find client facing solution at
Thank You
bottom of page