12m Read Time
Context
In-House Startup
5 Months
5 Core Team Members
Lead UX
Deliverables
User Story Maps
User Flows
Wireframes and Prototypes
Hi-Fi designs
User Research, Reports and Presentations
Service Maps
Storyboards and Illustrations
Personas
Design Sprint
1 Web App,
1 Mobile App
Circulo Health was founded in 2021, with a mission to create the future of health using innovative solutions that put people first. In November of 2021, Circulo Health acquired a company that hires caretakers, which became Circulo Homes.
These caretakers are Direct Support Professionals (DSPs) who provide home and community-based services to people with Intellectual and/or Developmental Disabilities (IDD) in Southeast Ohio. Historically, this role sees a very high turnover rate, and Ohio is facing a shortage of DSPs.
At Circulo, we intended to shift this go-to-market from a focus on health and sickness to a focus on empowering individuals with IDD to live their best lives and attract passionate caretakers from outside of the field.
I was the lead UXer and strategist for this go-to-market in which Circulo planned to expand across Ohio.
My two Product Managers, Bill and Sam, and I had big goals in mind:
hire nearly 1,000 new caretakers to help us expand across Ohio.
improve overall job satisfaction for caretakers, and thusly, individuals
I led a user story mapping session with each PM and goal, where we prioritized features for the flow of an application from start to finish and potential areas of improvement for caretakers . We also identified problematic areas and questions for development.
At the time, Circulo Homes hired caretakers manually, using paper applications. As a group, we decided that this was a bottleneck in the process.
We decided our first quick win would be to create a paperless hiring process - from finding the job, to applying, to onboarding. This made sense to me because:
We needed it in order to scale quickly
I could spend more time doing a deep dive into our user needs to inform any solutions for improving caretaker job satisfaction instead of guessing
But first, to ensure all of our teams were building towards the same goal, I created a service map that showed what touchpoints we would need at the internal, direct support professional, and client levels for hiring and improving overall job satisfaction.
I invited directors of engineering, technical product management, and product managers across the organization to question, communicate, and fill in gaps across our service levels.
This served two purposes:
As the backbone for future conversations about user experience across Circulo.
To visually align the team on what was coming next and what developers would be working on
We needed to understand what problems Direct Support Professionals (DSPs) face in their day-to-day roles and find ways to solve those problems to improve overall job satisfaction and decrease employee turnover.
Research Goals
Learn about direct support professionals (DSPs) and who they are as people
Determine what information is needed for interested people to understand and then apply to become a direct support professional
Understand what happens in the day to day work life of a DSP
Discover the touchpoints between a DSP and managers, individuals, county workers, medical professionals, and so on
Uncover how DSPs learn about their client and track information about their client
Applications for these learnings
Pain point and opportunity identification
Feature creation and prioritization
Figure out what we don't know and what we need to know more about
Learn how to increase interest in the field from folks in other fields or fresh graduates
Decrease churn
To get at these questions, I planned out the research with our UX Researcher, Jake, and we split the tasks.
We learned quickly from SME interviews conducted by the core team that DSPs read from and write in a large binder, kept at the client's house. This binder contains paper sheets that DSPs use to keep track of client information, such as weight, bowel movements, and food intake. It also contains the client's Individualized Service Plan (ISP), a large document that averages around 50-70 pages containing information about the client's background, health, family members, goals, risks, behaviors, and so on.
I created and conducted a 2 week diary study with 13 DSPs. At the end, I interviewed 5 of them to ask follow-up questions.
I invited the team, developers, and stakeholders to attend the follow-up interviews, as quiet participants. I asked them to submit a survey using Airtable, a collaborative spreadsheet database, for each observation they made so that I could later filter through these and easily export them into Miro, our digital whiteboarding tool.
In Miro, I led an affinity diagram exercise with our core team to surface themes hiding in our data. Jake and I then created a written report, and I made an illustrative, easy to absorb presentation for findings to share out with the company.
It was becoming clearer that one answer to improving overall job satisfaction could be in creating a native mobile app for caretakers to access ISP information and track other data about their client on the job.
Other caretaker and company pain points, such as difficulty clocking in and out, also started to emerge - things that could be rolled into this idea of a caretaker app.
Okay, so we know we have to create an application in order to hire employees to be caretakers, but why is churn so high in this field? Our secondary research helped to shed some light on the DSP workforce.
In my follow-up interviews, I also asked questions to learn more about:
how people entered the field
what concerns they had coming into the role,
why they stayed
I used this information to determine how best to design a landing page for the hiring application.
Now that I had a better understanding of DSPs and their needs, I stared drafting wireframes for a landing page that would lead into the application. I elected to do this alongside the data synthesis in order to maintain momentum and enable Circulo Homes to scale quickly.
The interviews and literature review indicated that my design should:
Be mobile-first because DSPs only have access to smartphones
Explain what a DSP is and use clear language
Show how we're different from other places
Be transparent about pay and hiring process
My PM, Bill, took care of the applicant tracking system, where we used active campaign to keep track of applicants moving through the hiring process, Gusto for onboarding, and asked me for help and feedback as needed. Meanwhile, I worked with our designer, Tim, as he created the Hi-Fis from my Lo-Fis.
I drafted several lo-fis and then worked closely with our visual designer, Tim, on the final landing page designs.
Next, I started working on wireframes and prototyping the DSP application. I pushed back on the business to remove unnecessary steps from their manual process that would help us decrease time to complete:
Why do we need employer information? How is it used at this step in the hiring process?
Why do we need home address
Can an applicant have no employment history?
Do we need month, day, and year for employment history?
I leveraged our existing design patterns to create a mobile-first application that could be completed in 10 minutes or less, anywhere, anytime.
Before moving into dev, I used UserZoomGo (formerly Validately) to usability test the new application for improvements. From there, I iterated, wrote specs, and worked closely with our front-end dev, Shelby, to launch.
A UI design I'm proud of - I used the metaphor of day and night to create clarity for applicants when selecting their preferred working hours.
Synthesis continued while readying launch of the DSP job application.
In addition to creating personas, which I worked on with our user researcher, Jake, I also created illustrative storyboards that summarized our day-in-the-life DSP research.
I presented these storyboards to our larger maker group, with other stakeholders and adjacent teams, to ensure that everyone can see, visually, what DSPs do, how our solutions can change their lives, and why it matters.
I continued to reference and share these artifacts as the team moved forward in the design of our projects, namely the caretaker app.
A top-down decision to focus on Circulo Homes as the #1 go-to-market for Circulo meant that I needed to:
Get the company up to speed on our team's research
Set the course for product vision
Using findings from the research, I presented a fictional story that followed Doug's journey to Circulo Homes and Sheryl's journey to becoming his DSP, showing how our business and new tools would simplify these paths. These new illustrations helped foster shared understanding across the company about the way forward.
-Sean Lane, CEO, after presenting illustrations to the full company
Now that we had enabled growth through our DSP application, synthesized research insights, and onboarded new departments, it was time to flesh out the caretaker app, specifically the Individualized Service Plan (ISP), the book of supports, activities, and so on required for meet a client's life goals.
To generate design ideas using our research, I planned and facilitated a design sprint for our PMs, researcher, and front-end developer.
The design sprint revolved around the question: How might we make digital ISPs easy and useful for DSPs?
The Design Sprint included:
Lightening Interviews with SMEs / Research refresh
Grouping themes from the interviews
Creating How Might We's
Creating sprint questions
Drawing the map and selecting a focus
Concept sketching within the focus
Based on the diary study, we knew that DSPs most often checked the ISP for information about their client's risks and behaviors, like for example, a swallowing risk. So we zoomed in on how best to surface this information.
The team agreed that the best path forward for putting information about a DSP's client in their hand was through a native app. We settled on three concepts to move forward with, including a button chat bot, which I considered to be our dark horse concept - AKA, a concept that we knew had low odds of performing well but that I knew we could learn from.
Using Axure, I created 3 different prototypes based on the concepts the team generated during our design sprint.
🥇An app that chunked out ISP information
A button chat bot
and a PDf view of the ISP*
I probably could have saved more time here by following my instincts and moving forward with the concept I thought was most useful, which ended up being the chunking app.
However, by taking the time and risk to create our dark horse, the button chat bot, we learned that DSPs feel that they need to confirm information by reviewing other sections and have a need to feel sure that what they're reading is correct - a learning we planned to apply to the winning prototype.
*The PMs wanted V1 to be a simple PDF, but I didn't think that this route would be any different in value from skimming paper in a binder. I tested the PDF version to show what value it could bring.
Working with Sam, the PM for the caretaker app, we reviewed an old user story map that we'd been updating as we learned more through our research and design sprint about what DSPs need in their day to day work.
I took our updates and created a product roadmap to align stakeholders and developers on future feature iterations.
We decided to focus our attention on creating an easier, more efficient system for clocking in/out and logging trips, followed closely by the ISP work, because:
this would help recapture $400,000 lost in clock in/clock out user errors through the old system
As a result, it would be another quick win
and give us more time to flesh out the ISP portion of the app, of which the design sprint only focused on one portion
All still moving the needle on improving pain points in the day-to-day of a DSP's life.
While I worked on the prototypes and roadmaps you see above, I asked the PMs to work on breadboards, also known as simple page flows, to help unblock our UI designer, Tyler, for the caretaker app.
Our UX researcher, Jake, spent time usability testing Tyler's clocking in/out designs.
Meanwhile, we also started working with the scrum team on a Sprint 0 and beyond, to start standing up the architecture needed and communicate with the state of Ohio on clocking in/out requirements.
And, due to the pivot, other go-to-markets at Circulo besides Circulo Homes, were now shifting focus to our IDD work. I led our team and the UX designers from our previous go-to-markets in creating a concept map, so we could see plainly how all of our systems will need to interact.
🤝 As a strategist, my job depends on trusting others. It's okay to lean on people for support, like asking for breadboards from the PMs
🕔 It's okay to follow your gut while waiting for research. And also it doesn't always matter because...
🏇🏽 ...Failure can be success! Testing a dark horse concept, even if it fails, leads to applicable insights (okay, this one I already knew!)
📈 Working at a start-up means knowing when to sacrifice process for speed and also when to pump the brakes