Optum: Cloud Product Contextual Inquiry Study
Problem
Poorly designed Optum internal cloud platform product
Loss of Software Engineer productivity and increased time to deployment
Lack of expected functionality
Declined engagement
Business Goals
Decrease time on task per session with the cloud product
Increase engagement with the cloud product
Confirm and add product features to the product road map
Study Duration
5 weeks
Study Presented
01/06/2023
Company
Optum
Cross Functional Team Members
Product Owner
Lead Software Engineer
Software Engineer
Methodologies
User Interviewing
Contextual Inquiry
Heuristics
Sample roadmap- does not reflect product in this case study
Impact
Using a combination of interviewing, contextual inquiry, and heuristics methodologies, my goal was to understand from users how to improve the functionality of an internal cloud platform product.
I submitted 9 recommendations to the Product Owner and software engineering team.
As a result of the implementation of my recommendations:
A time savings of 20 minutes per session was realized
Across all Software Engineer users, an average of 500 sessions a day were conducted before improvements, and increased to an average of 1500 sessions a day after implementation of my recommendations
Based on my recommendations 4 features to improve were either confirmed or added on the product road map
Research
Users Expected Conventional Functionality
The product was comparable to a commonly used product by the general population. With this in mind, I wanted to understand the mental model users had for the internal Optum feature, and how the feature could be improved to satisfy that mental model.
Interview Study with Contextual Inquiry Rationalization
I wanted to ask participants about their pain points and to show me how they used the feature by demonstrating past behavior.
Product Owner Identified 3 User Segments
I collaborated with the PO to understand user segments they prefered so that I could write appropriate research questions.
High Volume Users: 90+ uses
Intermediate Users: 6-89 uses
Low Volume Users: 1-5 uses
I Wrote a Moderator Guide
I asked interview questions related to job title and responsibilities as they related to use of the product:
Current product use behavior
How the product successfully meets their needs
How the product could be improved to better meet their needs
I Followed with Contextual Inquiry
I had participants share their screen and demonstrate how they used the feature by showing me examples of past product use.
I asked follow up questions when appropriate based on their behavior as I observed them using the feature.
Unprompted, Participants Reported Pain Points
Participants compared the Optum product with the well-known product used by the general population. This was a clear indication how the Optum product could be improved.
Reflections
This was my first study at Optum, and I really enjoyed working with the PO who was responsible for the Product in the Optum cloud platform that I ran the study for.
Transition From Confluence to Word
In my previous UXR role, I had been trained to use Confluence to construct my study plan. At Optum, I was given a study plan template in a Word document.
What I learned
I preferred writing my study plan in a Word document
Sharing it was easier as team members didn’t need to create an Atlassian account to access a Confluence link
Readability was improved compared to the non-linear layout of the Confluence study plan I had been taught to build