Lessons learned from a $600M project
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:
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.
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:
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]:
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.
Having interviewed a few subject matter experts (SMEs) from different counties, I started a draft of the Child's Experience Map. More details were added and improved as we interviewed more SMEs and previous foster children. Later in the discovery phase, we validated the map through interviews and workshops.
During early research, the format of the VA journey map started to echo. How it outlined the ten life stages of any veteran and pinpointed "the moment that matters" on each stage resonated with the foster child's experience.
Check out our inspirationMy team was comfortable saying "I don't know". SMEs, social workers and foster children were keen to fill us in and guide us. With this mindset, we rendered the experience from a single line sketch to a map with just the right fidelity.
See how we iteratedWe researchers were asked why we should even care about the child’s experience. “They aren’t using the system”, we heard, “the state and county social workers are!” We had the foster youth to help us answer the question.
View it on MiroMany foster children can't get placed in appropriate homes and their foster life is anything but stable.
A video the CYC youth sharedResearch and testing helps to continue refining the problem, to inform the design and approach, and to ensure the improvement of the user experience.
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.
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.
Summary: Site visits / Group home visits / Community based Org / Stakeholder interviews / Frontline worker workshops
Artifacts: RFA User Journey Maps / service blueprint / data modeling
We took dozens of trips to county offices all over California, shadowing social workers on home studies, family interviews, complaint investigations and annual inspections. We also reached out to community based organizations and support groups. We interviewed and did usability tests with over a hundred people. County representatives helped the team to reach out, recruit and engage with people.
Debrief of one visitRFA was a new caregiver approval process that many counties had challenges to adapt to. We created two user journey maps, one for the caregivers and the other for the RFA workers. On the one for RFA workers, each layer of the opaque waves represented a specific worker's highs and lows during the process. By layering up multiple RFA workers' experience, we were able to find patterns among certain groups, such as, workers within one county, from small counties and from the early-adopter counties.
Task map shows all the crucial tasks involved in the RFA application, grouped into 5 categories, ordered in a cycle.
We called the quarterly event where county representatives met the project team Q meeting. Workshops, testings, role plays, presentations and training were lined up for one to three days, the crowd ranged from 20 to 120 people. They were intense, fun, open and engaging. Beside the Q meeting, there were weekly updates, online workshops open to the public, and live streamed demos - the first project at the time showcasing government transparency.
Summary: story mapping / Life cycle of RFH / War room sessions and more ...
Outcome: RFA application interactive prototypes
So what did we do with all the research findings and synthesis? We translated them into problem statements, broke them down to bite size issues on post-it-notes, we grouped, linked, sorted, and prioritized them until a product roadmap started to take shape. With story mapping, managing Jira/backlog became the easiest part of the project.
Check it out on MiroHigh level service blueprint of RFH live cycle. To become RFH, a caregiver needs to get RFA (Resource Family Approval).
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 --> Iterate from lo to hi fidelity
We started design explorations from low fidelity sketches. SMEs worked closely with the project team, especially when verifying the concepts. After a few runs of iterations, we brought them to the county social workers for feedback and test runs. (Video narrated by Alyssa, one of the designers).
This is one of the hi-fi prototypes we built during the war room session to test the RFA flow end to end.
Clickable wireframesThe interactive prototype helped the team to envision how placement workers like Kay could find the best matches for the sibling set of six.
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.