REVEL
Health Engagement Software
THE PROBLEM
First up...Reporting Dashboard
Healthcare client has to report their engagement results every week/month/quarter/year to executives as well the government. The client created these confusing spreadsheets that were hard to navigate and took more way to long to sort through.
HIGH LEVEL TIMELINE
MAKE OF THE TEAM
Senior UX Designer
Data Product Owner
Data Scientist
Ongoing
KEY GOAL
Clean view into the data no matter the viewer.
Research & Interviews
Time for some interviews and research. I interviewed different stakeholders as well as users - finding pain-points and definition.
Data needs context. "Is that good?"
Robert: doing a lot of work trying to highlight what "good" is. Uses other plans that he knows are going well to signal what good is.
Matt F: Internal teams need data. A lot of problems come up because we don't have any high level view into how things are going in our programs. Additionally, people spend tons of time building these reports manually.
-How can we add some story telling to our generalized tools? -Are there ways we can highlight strengths and gaps in an automatic way? -Where should the tool stop and the account manager pick up?
Report Types pulled from research
After the research and interviews - I worked with the product owner to compile different report types - turns out there are a lot of different users of the reports - each user only needs certain information. In order to take away the constant sorting and search. We created different report types - specific to the different users.
First pass at design specs
Program Monitoring Report
Possible Metrics
Program Monitoring Report
Wireframes
Program Monitoring Report
I started wireframing out - how do we get these metrics into visual dashboard. So that they tell a story as well as give pertinent information in a clear way to the user.
Stress Testing Wireframes
Program Monitoring Report
TITLE OF THE CALLOUT BLOCK
LESSONS LEARNED
Is this the right solution?
For now - iterate - test and keep going for it...I would say that with software and technology there is a solution for now - but as users, technology and expectation change - we need to change as well.