Previous

Let's work together

I’m open to remote positions. Also, feel free to reach me if you need a hand on your side / open source project. I would love to connect with you.Let's build something awesome together, Say hi!

uderandi1221@gmail.com

© All Rights reserved by Erandi Attanayake

Childrens Services Platform A Digital Solution Supporting Professionals

Overview

Empowering safer, happier, and healthier childhoods.This project delivers a digital platform for Children’s Services, Fostering & Adoption, and Children’s Centres. It enables frontline professionals to manage incident reporting, tasks, and case collaboration more effectively. By streamlining workflows and automating routine tasks, it reduces administrative burden.Real-time visibility supports faster interventions and informed decision-making. The platform ultimately improves outcomes, helping children and families feel safer, healthier, and more hopeful.

The problem statement

Frontline professionals face:

  • Fragmented workflows and excessive paperwork.

  • Delays in critical interventions due to unclear processes.

  • Inconsistent safeguarding protocols and limited visibility across cases.

  • These inefficiencies compromise timely decision-making, accountability, and the quality of child welfare services.

The solution

A user-centered digital platform that:

  • Enables structured, multi-level incident reporting.

  • Automates task assignment and escalations.

  • Provides dashboards for admins and super admins to monitor workflow, compliance, and outcomes.

  • Supports real-time collaboration across teams while maintaining strict data security and GDPR compliance.

UX Process

Define the problem statement

  • Conducted shadowing and interviews with social workers, team leads, and managers.

  • Identified pain points: misreported incidents, manual task tracking, and fragmented communications.

Design Process

Double Diamond is the methodology that I used to find the best solution. In the first phase of Discovery, I needed to understand the problem context and the user needs before developing any solution. User flows were generated in the Definition phase. In the Develop phase, all the possible scenarios are explored to avoid some problems that might show up later. With a solid basis of UX findings, the visual part of the app was designed, including interactions completing the Delivery phase. 


Key insights 

User Persona

Since I didn’t have time to conduct in-depth research and gather validated representations of the company’s target audience, I relied on insights from desk research to create the following personas. These personas represent the primary users of the application, particularly parents who are seeking a safe and reliable platform.


The personas served as a starting point for evaluating the application and developing early design hypotheses. They also helped initiate and reinforce organizational awareness of the customer’s perspective, ensuring it remains a key consideration in strategic planning.


User persona

Admin persona

Super admin  persona

 Design Patterns

I also noticed from their social profiles and website that, by following the same design guidelines, they expect a consistent set of requirements.

Define MVP features

Once I got a somewhat clear idea of users, key requirements,  I started planning the features that should be available in the MVP.I would typically have a workshop with the team for a priority matrix exercise based on research, , and other raw data I collected from miro board when the user interview we collected data. Due to time constraints (and small accurate user data), I prioritized the key features based on the research insights and the  personas I created.

Identify Key Features

  • Incident reporting with category filters (safeguarding, health, wellbeing).

  • Task assignment and automated escalation triggers.

  • Role-based dashboards and workflow configurability.

User Flows

The main point of the user flow is to ensure that the functionality is always visible to the user, but not in an obstructive way. So I decided to create user flows for both user and admin users to identify the steps a user takes to complete that task. It helps me to make a clear way for the user to achieve their goals.

Sketches

For the visual design direction, I wanted to generate as many ideas as possible. After I got the idea about the application’s visual direction I drew these rough sketches as a guide to the visual designs.

Key Usability Findings

  • Users found the activity panel especially helpful for tracking.

  • Manual edit options were frequently used.

  • Users preferred bulk-assignment and resubmit features.

Identifying Assumptions and Constraints

Assumptions:

  • All incidents follow review & classification workflows.

  • Tasks are traceable to safeguarding categories.

  • Users may have varying technical proficiency.

Constraints:

  • Sensitive data handling (GDPR/ HIPAA compliant).

  • Integration with local authority systems.

  • Limited training time.

Key UI Screens

  • Incident Reporting Wizard: Step-by-step form with category filters and survey-style inputs.

  • Task Timeline Panel: Real-time status, updates, and completion history.

  • Admin Dashboard: Quick overview of pending incidents, overdue tasks, and alerts.

  • User Management Panel: Super admins can assign, edit, or deactivate users.

Success Metrics

  • 50% reduction in task completion time.

  • 80% improvement in incident reporting accuracy.

  • Higher user satisfaction (SUS score improvement).

  • The platform has been in successful use for over two years, with several enhancements implemented

 Usability Findings

  • A clear distinction is needed between incident types for admins.

  • Users preferred fewer fields per screen.

  • Super admins required editable workflow templates.

  • Real-time validation and task status visibility were critical across all roles.

Learnings & Outcomes

  • Empathy-led design is essential in emotionally intensive environments.

  • Real-time validation and simplified workflows reduce misreporting.

  • Balancing flexibility with compliance improves adoption.

  • Testing across all user roles uncovers blind spots early.

  • Phased MVP delivery enabled timely feedback without delaying critical service improvements.

Childrens Services Platform A Digital Solution Supporting Professionals

Overview

Empowering safer, happier, and healthier childhoods.This project delivers a digital platform for Children’s Services, Fostering & Adoption, and Children’s Centres. It enables frontline professionals to manage incident reporting, tasks, and case collaboration more effectively. By streamlining workflows and automating routine tasks, it reduces administrative burden.Real-time visibility supports faster interventions and informed decision-making. The platform ultimately improves outcomes, helping children and families feel safer, healthier, and more hopeful.

The problem statement

Frontline professionals face:

  • Fragmented workflows and excessive paperwork.

  • Delays in critical interventions due to unclear processes.

  • Inconsistent safeguarding protocols and limited visibility across cases.

  • These inefficiencies compromise timely decision-making, accountability, and the quality of child welfare services.

The solution

A user-centered digital platform that:

  • Enables structured, multi-level incident reporting.

  • Automates task assignment and escalations.

  • Provides dashboards for admins and super admins to monitor workflow, compliance, and outcomes.

  • Supports real-time collaboration across teams while maintaining strict data security and GDPR compliance.

UX Process

Define the problem

statement

  • Conducted shadowing and interviews with social workers, team leads, and managers.

  • Identified pain points: misreported incidents, manual task tracking, and fragmented communications.

Design Process

Double Diamond is the methodology that I used to find the best solution. In the first phase of Discovery, I needed to understand the problem context and the user needs before developing any solution. User flows were generated in the Definition phase. In the Develop phase, all the possible scenarios are explored to avoid some problems that might show up later. With a solid basis of UX findings, the visual part of the app was designed, including interactions completing the Delivery phase. 


Key insights 

User Persona

Since I didn’t have time to conduct in-depth research and gather validated representations of the company’s target audience, I relied on insights from desk research to create the following personas. These personas represent the primary users of the application, particularly parents who are seeking a safe and reliable platform.


The personas served as a starting point for evaluating the application and developing early design hypotheses. They also helped initiate and reinforce organizational awareness of the customer’s perspective, ensuring it remains a key consideration in strategic planning.


User persona

Admin persona

Super admin  persona

 Design Patterns

I also noticed from their social profiles and website that, by following the same design guidelines, they expect a consistent set of requirements.

Define MVP features

Once I got a somewhat clear idea of users, key requirements,  I started planning the features that should be available in the MVP.I would typically have a workshop with the team for a priority matrix exercise based on research, , and other raw data I collected from miro board when the user interview we collected data. Due to time constraints (and small accurate user data), I prioritized the key features based on the research insights and the  personas I created.

Identify Key Features

  • Incident reporting with category filters (safeguarding, health, wellbeing).

  • Task assignment and automated escalation triggers.

  • Role-based dashboards and workflow configurability.

User Flows

The main point of the user flow is to ensure that the functionality is always visible to the user, but not in an obstructive way. So I decided to create user flows for both user and admin users to identify the steps a user takes to complete that task. It helps me to make a clear way for the user to achieve their goals.

Sketches

For the visual design direction, I wanted to generate as many ideas as possible. After I got the idea about the application’s visual direction I drew these rough sketches as a guide to the visual designs.

Key Usability Findings

  • Users found the activity panel especially helpful for tracking.

  • Manual edit options were frequently used.

  • Users preferred bulk-assignment and resubmit features.

Identifying Assumptions and Constraints

Assumptions:

  • All incidents follow review & classification workflows.

  • Tasks are traceable to safeguarding categories.

  • Users may have varying technical proficiency.

Constraints:

  • Sensitive data handling (GDPR/ HIPAA compliant).

  • Integration with local authority systems.

  • Limited training time.

Key UI Screens

  • Incident Reporting Wizard: Step-by-step form with category filters and survey-style inputs.

  • Task Timeline Panel: Real-time status, updates, and completion history.

  • Admin Dashboard: Quick overview of pending incidents, overdue tasks, and alerts.

  • User Management Panel: Super admins can assign, edit, or deactivate users.

Success Metrics

  • 50% reduction in task completion time.

  • 80% improvement in incident reporting accuracy.

  • Higher user satisfaction (SUS score improvement).

  • The platform has been in successful use for over two years, with several enhancements implemented

 Usability Findings

  • A clear distinction is needed between incident types for admins.

  • Users preferred fewer fields per screen.

  • Super admins required editable workflow templates.

  • Real-time validation and task status visibility were critical across all roles.

Learnings & Outcomes

  • Empathy-led design is essential in emotionally intensive environments.

  • Real-time validation and simplified workflows reduce misreporting.

  • Balancing flexibility with compliance improves adoption.

  • Testing across all user roles uncovers blind spots early.

  • Phased MVP delivery enabled timely feedback without delaying critical service improvements.

Previous

Let's work together

I’m open to remote positions. Also, feel free to reach me if you need a hand on your side / open source project. I would love to connect with you.Let's build something awesome together, Say hi!

uderandi1221@gmail.com

© All Rights reserved by Erandi Attanayake