Date: 2022, 2023
These are all conceptual reimaginings of the Noyo ben-admin dashboard experience.
None of these are published, but were done in order to generate discussion or brainstorming, explain concepts visually, and explore what could be.
This was made to imagine what could be if we had pivoted to a specific type of connection-based model. Each row is a group <> carrier connection, and the at-a-glance list version here would highlight the connection status and connection health of each one.
The navigation was changed to include a universal, app-wide search for that ben-admin company.
An example of a single connection page, with summaries/highlights/calls-to-action as one of the first things the user would see. This would then help the user to know what the most important things to do/know about this connection are, and guide them to that action right away.
If we selected the “employees” tab, we’d see a list of all employees, and the ones with an enrollment discrepancy would be highlighted.
This is a similar concept, but if we continued with a “groups” model, or at the groups level. This list would also highlight the group connection status and group connection health of each group.
Again, the detail page of each group would highlight the important calls-to-action on the front page.
This is an individual employee’s page - showing the most recent values we have and the most recent values at the carrier for each possible API field. Discrepancies are highlighted, and would of course in theory allow discrepancy resolution right here on this page.
This is kind of a similar concept as the others above, but with some changes, more attention to detail on interactions, and different element styles.
The move away from the side-nav was to allow for more horizontal screen-space for page elements and for a secondary navigation (that would not take away from horizontal screen-space) The secondary navigation changes based on the topmost-navigation selection.
Home consists of a home page with quick access widgets (not shown), an issues page (which would show all the random data or enrollment problems that need to be addressed), a metrics page (which would contain important metrics that a ben-admin company would want to track), and an Open Enrollment Center, which would be sort of a one-stop shop for anything related to open enrollments.
Of course, the specific content of each page would have needed much more research, testing, and validation - these were mainly just to start discussions.
The connections page would give users 4 different ways to see their managed connections at Noyo - connections (for group <> carrier connections), groups, members, and carriers.
At the time of building this concept, we were also trying to envision how we might display a new product visually - member snapshots.
This concept imagines that we basically combine the idea of the member profile with the idea of a member snapshot. My hypothesis was that our users have their own member profiles on their own dashboards, and given that Noyo owns the connection management, the most useful thing we could show for members would be their most recent snapshots and the status of each change coming in from that snapshot. The profiles had already contained pretty much all those same fields anyway as the snapshot, and this was a way to ensure that users could know exactly what data had been updated or was still processing for each user.
I did not get to explore this hypothesis, but that would have been my next step.