Levno for Faults
Helping Levno Administrators to Manage Faults
Part of creating new and innovative hardware is occasionally things will go wrong. This interface was designed to make it easy for Levno administrators to deal with faults from the hardware and make choices about what to do to fix the fault.
After doing some analysis on the original faults interface by watching what administrators do and asking them questions I helped identify some key problem areas with it.
Every option opened in a new tab meaning administrators would get flooded with tabs
The buttons to make a decision around what to do with the fault were on the main page before you could see information about the fault type. Administrators would have to go back to the main page and find the fault to action in a large list which could get confusing at times.
There were many false positive faults or ones that had been resolved on their own types so admins were often clearing faults from the list.
If they accidentally refreshed the page it was hard to know what faults they had looked at already and what status they were in.
Administrators had trouble knowing what was actioned on a fault as there wasn’t a clear activity log or history documented with a fault.
After one of my teammates created a wireframe I was asked to give feedback. The wireframes showed the detail view of every product. When we were looking at only a couple of faults this would have been okay, however Levno as a business is growing and this design wasn’t going to scale.
After consulting the administrators, I came up with a list view which gives the admin a quick overview for where they’re at with a simple tick or cross. I also created a few iterations of how the interface could look creating various light and dark themes.
After showing variants of the UI design to the administrators - they requested the dark theme as they would often be looking at this interface for a while (a few hours) and they’d set their other applications to have a dark theme. Dark themes are often the lowest priority but the most requested feature and when you’re working with these people everyday - it’s a good idea to keep them happy.
Quite often the role swaps around the company for who is doing faults - especially around break periods. What we’ve done with this interface to deal with this scenario is to highlight the most commonly used option for that fault type to indicate to the administrator what they probably should do. That way if someone new is doing faults - the interface guides them into making the correct option most of the time.
The response to the design was overwhelmingly positive and administrators were impressed by how good it looked. It was such a rewarding experience to create something that my own team members could finally love.
