MN Department of Human Services

SaaS System Redesign

“If I had asked people what they wanted, they would have said faster horses.” - Henry Ford

My Role

  • UX Researcher

    • Secondary Research

    • Cognitive Walkthrough

    • Contextual Inquiry

    • Information Architecture

  • UX/UI Designer

    • Sketches

    • Digital Wireframes

    • Interactive Prototyping

Tools

  • Figma

  • Figjam

  • Google Docs

  • Google Sheets

  • Slack

  • Zoom

Client

The Minnesota Department of Human Services (MNDHS) is a state funded organization who’s mission is to protect, maintain, and improve the health of all Minnesotans. When it comes to child welfare, one important aspect of some service plans is an Out-of-Home Placement Plan (OHPP) document. An OHPP addresses federal and state case plan requirements that support a child’s safety, permanency and well-being. The setup and documentation of an OHPP within the Social Services Information System (SSIS) was the core focus of the project. Within that scope, my team was enlisted to research and recommend design system changes for the setup phase of an OHPP. I served as the lead moderator for our contextual inquiry session and made individual recommendations based on collaborative synthesis.

Goals


Who does this system impact?


Minnesotan case workers and case aids that connect children in need of living assistance due to a number of circumstances are the primary user group. Case workers are passionate about what they do and aim to successfully and effectively find safe and sustainable living situations for all children in their caseload. An OHPP must be created within 30 days of a child being placed in foster care.


Where to start?

Determining case workers pain points and goals allowed me to focus on the features that would make the most positive impact.


Contextual Inquiry

I was the sole, lead moderator for my UX team of 8, and crafted a script to focus on intricacies, pain points, and standards of the system. The user, a caseworker, guided the walkthrough based off scenarios, questions, and statements I communicated, while I warmly asked the user why they performed specific actions, what changes they would like to see, what affordances certain functions or tasks had, and what work arounds they use. Continually asking the user why gave my team and I insight into what the users pain points are, the opportunity areas, and the users primary goals.


Caseworkers ultimate goal is to be in the field spending more time with families to help them live in dignity and achieve their highest potential.


What did I find?

An entangled web of folders with little to no clarity of navigation, visibility, or functionality, is not consistent with modern design systems and was proven to be extremely inefficient.


What was communicated

  • Visibility of confirmation and verification that correct information was typed would reduce errors.

  • Caseworkers were confused about whether information was regulated or subjective.

  • 1 worker stated it took them 2 years to fully comprehend the SSIS system.

  • Unfamiliar or new users receive little to no training on the SSIS system which leads to frustration and an extreme loss of efficiency.

What was observed

  • Creating an Out-of-Home Placement Plan (OHPP) is a time sucking, energy taking, and frustrating process for case workers.

  • Organizational issues such as folder inconsistencies, page clarity, and hierarchy of fonts, colors, and icons.

  • Inconsistent and non-responsive feedback allowed for mistakes to go undetected.

  • We observed that users needed to recall information from previous pages on a consistent basis which led to frustration and inefficiency.


Synthesizing research led me to focus on…

Streamlining and simplifying organization to increase productivity and reduce recall and frustration.

Incorporating reliable feedback to increase confidence and reduce confusion.

Create an intuitive navigation to increase efficiency and decrease stress.

After synthesis of all research led to a few main themes, I quickly sketched out a screen flow of what my vision was. This afforded me the ability to highlight where the changes I wanted to make fit into the system and what screens may be most important in a short period of time. Then I created low-fidelity, hand sketched wireframes of what was originally thought to be three main flow screens to align with the main themes that were synthesized.

Low-Fidelity Vision

Simple wireframes and a screen flow allowed me to quickly scope out the rest of my process and made the location of impact clear.

Hand sketches of three different flow screens.



Screen flow created to establish where changes will be made. “ICWA” changed to “Eligibility”



The Impact

An interactive prototype that guides caseworkers to their ultimate goal of being in the field effectively and efficiently.


Efficiency

Autofill Functionality

Streamlined Documentation

Feedback

Error Prevention & Confirmations

Organization

Folders, Navigation,
& Branding

To view the interactive prototype, you may click this button —>



Reflection


Understanding a users ultimate goal guiding them on an effective journey to achieve it is continuing to embody my work. For caseworkers in the state of Minnesota, that means to spend more time in the field with families and children they have an unconditional connection with. Designing a system that provides more efficient productivity accompanied with less strain and energy output allows these caseworkers to succeed and thrive in the expert areas they were hired for in the first place. Continuing research of the SSIS software would be necessary to provide more insight into pain points of the existing system, elicit opportunity areas for change and growth, and create an even deeper connection and empathic understanding of the users.


Key Deliverables