Firmware OTA Console
Overview
Note: This project did not launch to production. Only a few key images have been included, and names and labels have been scrubbed.
I took on the task of designing a self-service firmware OTA (over the air) experience. I had absolutely zero experience with OTA services, so the first thing I did was research the problem space. I met with and interviewed several developers to gain a better idea of what an ideal OTA service looked like, what features would be needed for MLP and how OTAs work in general. The team had an existing OTA flow but was all done through CLI. My job was to translate the existing CLI features into a user-friendly web interface.
CompanyRedacted RoleLead UX Designer, VXD, IXD, IA, User Researcher Year Redacted
The design that never was... This was a highly technical and complex project. It required dozens of iterations, user interviews, and had constantly shifting requirements. Regardless, I completed and delivered designs and redlines to dev on time. The tragic side of this story is… the interface never saw the light of day. At first, the project was put on hold due to resource limitations, however over time it was deprioritized since the CLI method could be used as a viable solution. Once on hold, it never returned. R.I.P.