The Axiom H2 machine produces molecular hydrogen. It’s odorless and tasteless. You can inhale the hydrogen through your nose, apply the hydrogen to your eyes, or through your ear canal, for brain health. You can also use the machine, with an attachment, to create your own hydrogen enriched water.
My stakeholder, the owner of the company, is selling the machine as a therapeutic device to a variety of users.
I wanted to concentrate my efforts to solve problems for the majority of actual users.I was able to create a persona that would prove useful.
Once I could take a step back and study my research, I formulated a new problem statement so I could have a narrower focus going forward.
After discussing with the CEO, he agreed this was a strong course of action to follow.
Once I could look at the problem from a wider perspective, the perspective of over-all health, I could also look for examples from indirect competitors.
The cancer.net app proved a very useful study, showing a way that I could structure the Axiom app around a health dashboard of sorts.
I gathered a list of common symptoms for autoimmune disease sufferers, things like anxiety, fatigue, constipation, etc...These symptoms are really just a starting point, though. There is also a space for the user to name, and therefore, track a symptom of their choosing. Once the user selects a symptom, and date (with a current time default) they can quickly rate the severity.
This data will be logged and can be referred to on the dashboard.
No matter what kind of user you are. Hydrogen intake is what makes this app unique.
Users can easily select their intake type and time from convenient, predetermined intervals. Once they log their event, the data is stored and can be referred to on the dashboard.
This dashboard is where all the logged data can be seen in a visual representation. Of course you can apply different to the graph, based on H2 delivery methods, timeframes, etc…This data can be downloaded and shared, allowing users the ability to connect with each other over individual successes and failures.
Logging data and tracking graphs is all well and good, however, the living beating heart of the app is the dashboard--where all the data comes together, to help thew user.
At the very top of the dashboard we have trends and reminders.
Trends are just factoids of data movement direction. For example – they could report on symptoms that are improving or hydrogen use that is declining or point out the correlations between medications and symptoms.
Reminders, on the other hand, kind of goad the user into taking actions – like reminding the user to change the filter of the machine (every two weeks), or reminding the user to continue to log their symptoms after a delay. Reminders could be extrapolated into OS notifications, as well.
Since I still had access to users from the initial interviews, I reached out to see if anyone would test the prototype--and a few did. They indicated that they could see this app being useful.
This was a short, explorative project. Axiom may go forward with the app or they may not. I, however, learned a lot in the design process. I really had to push past the initial problem (of tracking hydrogen usage) until I got a broader view of things. Once I was able to see a user, with their needs and frustrations, I could begin looking for comparable solutions. Then, I still needed to implement a fresh system to bring everything together, which would be the dashboard.
In retrospect a dashboard is obvious, but it was only going through the entire process that I understood the dashboard's true meaning and usage. Because I used a methodical design process, once I got to the dashboard element, I could feel the usefulness of the solution, relative to the project constraints. And that was a good feeling.
If Axiom chooses to move forward, they would really have to focus their engineering on creating the logic for the dashboard's reminders and trends. Again, these are the key and what give the app some actual "legs."