Project 03

Child Welfare Services

Lessons learned from a $600M project

Let's start with

The kids were 17, 13, 12, 9, 7, and 3. They checked in late the night before, after their mother was taken into custody. Kay, the social worker, had just been assigned to the case and spent the morning reviewing the files, making calls, leaving messages, and sending emails. It became apparent that it's unlikely to find anyone in the family to care for them, nor any family friends. Kay's next hope was to find a long term place, ideally a foster family that can take all 6 of them, but this would be unlikely given the shortage of families and facilities. So she went to the emergency foster home to meet the kids for the first time. So, she had to ask them a question:

Notes of the interviews
Notes of the interviews

If you have to be split, which siblings do you want to be with? I shadowed Kay and interviewed the kids one by one. It turned out all the younger kids wanted to stay with the oldest sister except the 13 years old. Holding up his head and fighting back his tears, the boy said he's old enough, he could stay with the 9 years old and look after him.

What are we building the new system for?

The Child Welfare Digital Services (CWDS) is a collaboration of California State and local government agencies that support their shared stakeholders through technology to assure the safety, permanency, and well-being of children at risk of abuse, neglect or exploitation. They have 2 jobs:

  • maintaining and operating the existing Child Welfare Services / Case Management System (CWS/CMS)
  • developing the Child Welfare Services – California Automated Response and Engagement System (CWS-CARES), so it can replace CWS/CMS
Why it is so hard

To say it out loud, child welfare systems across the nation are broken. 424,000 children are in foster care on any given day nationwide. In 2019, over 672,000 children spent time in U.S. foster care. [Source]

While there are more children entering foster care every year, there are fewer families and facilities are available for them. The most significant challenges state child welfare agencies have been facing are [Source]:

  • Providing an adequate level of services for children and families,
  • Recruiting and retaining caseworkers, and
  • Finding appropriate homes for children

As a result, many foster children can't get placed in more appropriate homes in time or at all. Many of them have to go through different homes or placements, their lifes growing up in the child welfare systems can be anything but stability. One of the foster children we interviewed, a 15 year old from California Youth Connection (CYC), has been placed 53 times.

How many placements have you been to?

Map the child's experiences

The child's experience map
Child's experience map
Ideally, we'd start with defining the problem ...
In reality though

We skipped the discovery & framing phase which would have allowed us to look at the problem space from end to end. The entire project was divided into 7 modules based on the programs and domains, each module had its own team consisting of design, product, and engineering from multiple vendors, subject matter experts, product owners, and service managers from the state or counties. There were about 20 - 30 people in each module/service team. The plan was to onboard one team at a time, about 2-3 teams per year. The onboarded teams were expected to deliver "working codes" quickly, therefore the research was very modulized and solution driven early on.

sketch of the 7 modules
Sketch of the 7 modules

However, a year later the project started to feel the pain of solving problems within domain silos. For example, the state released a Resource Family Approval directive, but counties had their own ways to approve foster families for decades. They had developed systems and programs accordingly, which created obstacles such as sharing data across counties, or collaborating across services. During interviews, large counties with thousands of employees and small ones with a handful of employees were always asking something different, something tailored for their special needs. We had no choice but to demolish the silos and look at the services as a whole, rather than the sum of their parts.

Strategists, designers, researchers, and frontend engineers from different service modules joined to form a designOps. We pooled resources and shared our knowledge to develop a holistic and cohesive vision for the services end to end, with the help from the Subject Matter Experts and the frontline county workers.

One of the outcomes of the Discovery & Framing phase was a snapshot of the Emergency Placement, which is what Kay assigned to do with the sibling set of six case.

Take a slice of the Emergency Placement

Ongoing research & discovery

Solve the right problem

We occupied a conference room for a few weeks and turned it into a war room. All the plots, sketches, storyboards, designs, and banters were on the walls. When we were done, we cleaned the whiteboard but left the artifacts there and people liked that.

Prototype, validate, and iterate

During the largest Q meeting that we called "the Summit", I ran into Kay's supervisor and asked about the 6 siblings. It turned out no one ended up living with the 17 year old sister (the oldest), who went to the transitional program for young adults. The idea was to prepare her to live on her own and become self-sufficient as soon as possible, as she wanted to be able to adopt her younger siblings once she turned 18.

Leading UX Summit

Exploreing Emergency Placement at CWDS
Liz Leading UX summit at CWDS

More WORK

Portfolio | Project 03

Child Welfare

2017-2019

Portfolio | Project 04

Autozone

2015-2017

Oh my!

Old Portfolio

2007-2014

Portfolio | Project 05 🔒

Unemployment Insurance

2021-2022