CGM & PUMP
Creating data visualization across multiple devices using first of its kind data integration between insulin pumps, continues glucose monitors, blood glucose devices food and exercise data.
I was the Lead Designer on this project and responsible for wires, user testing, prototyping, and all design. I worked along side one Product Manager to make sure all goals were reached.
We started by going over Medtronic, Dexcom, Insulet, Tandem, CapturAGP and many other software platforms graph by graph, chart by chart. We leveraged our Medical Advisory Board (a group of widely accredited diabetes doctors we consult with) to get feedback on what they liked, what they didn’t like and how the software they use now can be better. After a week of interviews we had a directions for the web platform that focused on 3 key features.
With the patient app we already had a good starting point for what we thought patients wanted to see. CGMs and Insulin Pumps would be specific to one set of users, those with Type 1 diabetes. Based on past user testing we outlined two new sections we thought would satisfy most T1 patients.
I identified several key personas that I would target in our initial launch. For doctors I focused on those still working with PDF reports or that use some sort of graphing software. For patients I decided to focus on first adopters, that means the data nerds and the highly motivated parents with a T1 children. This platform was our first crack at the CGM and Insulin Pump market I wanted to make sure the early adopters would become advocates.
SKETCHES AND QUICK MOCK
I started sketches solutions while we were still discussing with doctors about which direction we should go and doing our research. Between the Medical Advisory Board, the PM and myself we had enough information for me to put a full color mock together in a day or two. It wasn’t too pretty but it was something we could start getting feedback on instead of a concept we had to describe.
WEEKLY USER TESTING AND DEVELOPMENT
Each week we met with patients and doctors and each week our mock got better and better. While working on finalizing the mocks we were getting our developers rolling on proving out the concepts we had in mind. So when it came time to bring our concepts to life the devs were already building it and just needed the finishing touches. We had some time to work with since the backend engineers were still hard at work on the data integration piece.
GET OUT OF THE BUILDING
The Product Manager and I traveled to Boston and Kansas City to sit down with patients and doctors to get first hand feedback. Because of the number of patients and doctors (30) and short amount of time (4 days) the interview process needed to be very efficient.
Joslin Diabetes Center
Joslin Diabetes Center is the world’s largest diabetes research center, diabetes clinic, and provider of diabetes education. It is located in Boston, Massachusetts, USA.
Children's Mercy Hospital is a comprehensive pediatric medical center in Kansas City, Missouri that integrates clinical care, research and medical education for patients ages birth to 21.
- Lifestyle and behavior
Learning about a person’s current habits is one of the most important steps to understanding a products success or failure in a person's life.
- Pain point ranking
We singled out 6 common pain-points to people with diabetes and asked which was most important. This would help guide feature prioritization.
- Upload personal data
Having our MVP run with personal data made patients more engaged with our testing. There was a personal stake in making sure we got things right with their data.
- Tell us what you see
We let users explore the system and describe what they see without interfering to explain. It was very beneficial to let the user dive deeper into the product for answers.
Asking users to complete tasks using the system to gauge ease of use. (ex. How much did you bolus last night? Can you tell us the last time you went high? etc)
- General feedback
An opportunity for users to voice things they liked, didn’t like and things we might be missing.
- If we could make one thing for you what would it be?
Boiling down all of their feedback into one big ask. This consistent question helped us group patients by interest for future product testing.
People saw patterns in their diabetes data but wanted to know what to do next.
Every doctor had a different preference for displaying patient data and one view we didn't include was highly requested.
The ability to easily see the food they ate or miles they ran is crucial for making sense of glucose events.
Adults need help figuring our bolus amounts for food while kids struggle finding the correct basal rates.
Try often to improve often
Creating a quick first version leads to quicker critique and faster improvement. Subsequent iterations should follow the same rapid feedback cycle to ensure the product is on the right path.
Show and tell
Visualizations of data aren’t enough, both patients and healthcare professionals are looking for easier identification of problem areas and recommendations for treatment.