Diagnocat UI
Working for a conventional online service is easy. Lodging reservations, car rental, crypto exchange, e-commerce — each of them has their industry standards, best practices and big no-no's.
Finding inspiration on a market saturated with competitors is a handy thing when you're starting out new product. Blue Ocean Strategy is what scares designers — where do you for a references, what visual direction to take?
But what happens when you combine both? Enter Diagnocat, a web-based AI-driven dentist's virtual assistant.
Force of habit
Problem: How do you introduce a modern-looking online services to dental professionals who have trouble finding "share my screen icon" during user testing interviews? How do you compete with a 20-years old native dental imaging software they got used to?
You take a path, trodden by Forex. For many years, Forex software was native-only, meaning you have to install it as a stand-alone program/application on your computer. Normally this software wasn't having anything resembling an interface, just raw data, tables and ugly charts. It wasn't until mid-2000 when first publicly available web services for foreign exchange markets started to pop-up.
Back to the dentist's chair. With the help of deep-interviewing prosthodontists, endodontists, orthodontists and facial surgeons from Israel, USA, Europe and Japan I've managed to see exactly how they use their software, what they like and dislike, what annoys them and what are their needs. This usability research was applied to Diagnocat.
Onboarding
Problem: When introducing new feature or list of features to users there's a need to onboard them with a new functionality. To do that you add some form of a product tour, walkthrough or just a series of tooltips. But what happens in real life is that the timing of those are never right. User just wants to do a certain thing, but a pop-up, tooltip or panel blocks him from doing that exact thing. Irritated, she closes the onboarding never to see it again. But when moment comes and the same user stumbles upon a new feature thinking "wait, what's that again?"
To resolve that unobvious issue I've added 'skip tour button" and a folding animation where the tooltip flows into the question icon on the bottom right. Upon clicking that question icon user can either get support or relaunch the onboarding again when he needs it.
Reverse engineering
Problem: Agile development implies that there're few bottlenecks and every member of research, planning, design, development and testing process can be on the same page. But what if the dev team just can't keep up? What if new functionality introduced by designer is going to take at least 4 sprints of development?
A new feature called "Dental photo" was introduced with a a full-scale file storage, naming and renaming, metadata parsing, folder management, searching, filtering etc. It was a bite more than one can chew.
I've decomposed this feature to 7 different iterations. From plain and simple things to complex operations. First came a single-level folderless file grid with. Last were the multi-directory moving, bulk operations and sharing options.
Metric/Imperial
Problem: aside from different date format, computed tomography scans and studies from different countries might also carry different dental notation. It means that CT scan created in the USA can have teeth associated with other numbers in quadrant of human jaws than the one made in Europe.
In order to address this issue I've suggested an additional round or learning to Diagnocat's ML that would establish individual tooth number. Combined with a global setting for two main variants of dental notation it did wonders.
Diagnocat UI
Working for a conventional online service is easy. Lodging reservations, car rental, crypto exchange, e-commerce — each of them has their industry standards, best practices and big no-no's.
Finding inspiration on a market saturated with competitors is a handy thing when you're starting out new product. Blue Ocean Strategy is what scares designers — where do you for a references, what visual direction to take?
But what happens when you combine both? Enter Diagnocat, a web-based AI-driven dentist's virtual assistant.
Force of habit
Problem: How do you introduce a modern-looking online services to dental professionals who have trouble finding "share my screen icon" during user testing interviews? How do you compete with a 20-years old native dental imaging software they got used to?
You take a path, trodden by Forex. For many years, Forex software was native-only, meaning you have to install it as a stand-alone program/application on your computer. Normally this software wasn't having anything resembling an interface, just raw data, tables and ugly charts. It wasn't until mid-2000 when first publicly available web services for foreign exchange markets started to pop-up.
Back to the dentist's chair. With the help of deep-interviewing prosthodontists, endodontists, orthodontists and facial surgeons from Israel, USA, Europe and Japan I've managed to see exactly how they use their software, what they like and dislike, what annoys them and what are their needs. This usability research was applied to Diagnocat.
Onboarding
Problem: When introducing new feature or list of features to users there's a need to onboard them with a new functionality. To do that you add some form of a product tour, walkthrough or just a series of tooltips. But what happens in real life is that the timing of those are never right. User just wants to do a certain thing, but a pop-up, tooltip or panel blocks him from doing that exact thing. Irritated, she closes the onboarding never to see it again. But when moment comes and the same user stumbles upon a new feature thinking "wait, what's that again?"
To resolve that unobvious issue I've added 'skip tour button" and a folding animation where the tooltip flows into the question icon on the bottom right. Upon clicking that question icon user can either get support or relaunch the onboarding again when he needs it.
Reverse engineering
Problem: Agile development implies that there're few bottlenecks and every member of research, planning, design, development and testing process can be on the same page. But what if the dev team just can't keep up? What if new functionality introduced by designer is going to take at least 4 sprints of development?
A new feature called "Dental photo" was introduced with a a full-scale file storage, naming and renaming, metadata parsing, folder management, searching, filtering etc. It was a bite more than one can chew.
I've decomposed this feature to 7 different iterations. From plain and simple things to complex operations. First came a single-level folderless file grid with. Last were the multi-directory moving, bulk operations and sharing options.
Metric/Imperial
Problem: aside from different date format, computed tomography scans and studies from different countries might also carry different dental notation. It means that CT scan created in the USA can have teeth associated with other numbers in quadrant of human jaws than the one made in Europe.
In order to address this issue I've suggested an additional round or learning to Diagnocat's ML that would establish individual tooth number. Combined with a global setting for two main variants of dental notation it did wonders.