Impact
Creating a UI for mapping group structures allowed two new ben-admin clients to manage their enrollments with Noyo.
Problem
Smaller ben-admin platforms tend to rely on a complex spreadsheet to manually map their members into insurance carrier codes for billing. This process is not compatible with Noyo's API, it's time-consuming, and it's costly for the ben-admins.
Solution
I designed a rules-based UI within the Noyo dashboard. Clients are able to easily manage their data mappings in a way that is compatible with Noyo's main offering, the API.
Overview
Role
Design lead
Methods
Research, usability testing, interaction design, prototyping
Type
Web app
Insights:
Providing context at the right time and place gives even new users direction and confidence.
Adding information about the insurance billing codes (like member types, locations, and other data) enabled the users to make rules that would put the right people in the right billing codes. It mattered much less how experienced they were with mapping; they could glean from that data who the rule needed to be made for.
Rule-building is a good way to let users "code" dynamic information without actually coding.
One of the observations I made during our workshop sessions was that our users had to essentially make code to categorize data, but through a spreadsheet. However, our target user was not an engineer. We needed a way for them to be able to code without knowing any code - which is where building out rules steps in.
If you rely on assumptions, without testing those assumptions, they may be wrong.
One of the assumptions at the beginning of the project was that users would not need a UI to populate their dropdowns for the left-hand side, since they would be able to use the API to do that. So I did not test that part. However, after launch we realized that they were unable to do so, and we had to quickly figure out a workaround for them. Had I insisted on testing that flow, I would have caught that and made onboarding easier.
Process
Discovery
I held several workshops with key stakeholders to understand the mapping process, and to see in their own words (and drawings) what an ideal mapping tool might include. I learned that the process involved custom variables and conditionals, required a lot of copy and pasting in a manual spreadsheet, and that other data sources often had to be referenced for more context.
Prototypes & Validation
After learning about the needs of the tool, I built a clickable prototype and held usability sessions to test it out with internal and external stakeholders. 100% of the users I tested were able to complete the mapping accurately with minimal assistance, even those who were new to the concept of mapping.
Solution
The solution was a rules-based UI that allowed users to map their data through Noyo.
