End-to-End Product • 2019 - 2021
MEC SIMS App
Improving the shop floor.
Role(s) Performed
Project Lead • UX Designer • UX Researcher • UX Engineer • Scrum Master • Producer • Project Manager • Graphic Designer • Information Architect • Product Manager
Tools Used
Adobe XD • Miro • Jira • Adobe Creative Cloud • Microsoft Teams • Sharepoint • Visual Studio • Command Line • GitHub • Git • SQL • Analog Materials
Methodologies
Surveying & Screening • Qualitative Interviews • Mixed Method Data Compilation • Geurilla Recruitment • Moderated User Testing • Object-Oriented UX Design • Guerilla Product Research • Storymapping • Personas & User Design • Personas & User Design • Prototype User Testing • Brand Creation • Project Manager
Project start.
The situation involved a company that had relied on a piece of hardware for over 20 years with minimal software upgrades. While not surprising, it always left an impression due to the longevity of the system. Over the past five years, however, the hardware began to fail significantly, and more recently, the company discontinued the hardware altogether.
Team dynamics.
A team was formed to tackle the challenge, consisting of two primary members: one leading the front-end efforts and a back-end developer. Their objective was to recreate the software using a modern, reactive tech stack. Additionally, they needed to transition the software from a desktop-based solution to a primarily mobile platform.
To ensure the project’s success, several phases were outlined. These included organizing meetings with stakeholders, users, and the development team, updating user personas, conducting design sprints, holding Object-Oriented UX (OOUX) sessions, and developing a Minimum Lovable Product (MLP). Throughout the process, user involvement and evaluation were key to achieving the project goals.
Research and Discovery.
The project lead quickly recognized that user research needed to be prioritized before moving forward, as the users’ primary tool was about to be replaced and limited in functionality. The new Android scanner had a significantly smaller screen compared to the previous tool, which meant the information architecture would need a drastic overhaul.
Consideration of hardware.
When users were interviewed and surveyed, many expressed concerns about the smaller device. Despite the constant failures of the existing system, they were hesitant to agree that the same amount of information could be displayed effectively on the new hardware.
Throughout the design process, every step was reviewed by users first. The lead created numerous flip-book wireflows—so many that it could have been turned into a small "WireNovel."
Phase 1.
The project began with a phased rollout of the new technology, allowing the new system to run side-by-side with the old one. This approach ensured users had the option to revert to the previous system if issues arose and provided a smoother transition rather than forcing an abrupt switch.
The release was closely monitored, with the UX Engineer traveling more frequently to oversee the process. They encouraged users to directly share ideas and report bugs, which were logged and addressed without the need for intermediaries. A key part of the UX Engineer’s role was acting as a **customer support representative**, ensuring that employees, who had no choice but to use the software, felt heard and supported.
Next Steps.
Version 1.0 of the new system was officially released in 2021 across all necessary plants. Although the app continues to evolve and is being rolled out in phases, two plants are now fully reliant on the new inventory system. Users were anonymously surveyed for feedback, which was used to improve both the ongoing rollout and future updates. The UX Engineer emphasized the importance of letting users know that their voices were being heard.
While Version 1.0 included the entire Minimum Lovable Product (MLP), there are ongoing suggestions from users and stakeholders for app improvements. Bugs and minor issues are still being addressed, and each plant is being treated as a unique case, with continuous collaboration between the UX Engineer and users to implement enhancements that benefit everyone.