This project involved multiple departments in integrating the newly recreated hardware pages to the new architecture established in the previous Product page launch. The main point of focus was to integrate responsive design into the page template, create new responsive UI web components and convert existing components to be responsive.
In addition to developing the UI for the Responsive Hardware Web Application project, I was tasked to help lead, build up and establish our front-end process.
The page is live on production now and is viewable here.
I was given the opportunity to be a team lead to improve the process for our code contribution, and build a stronger bridge between design and development.
Developers and Designers were in silos
I recognized we needed accountability and visibility to ensure that developers weren't going straight to development without consultation with the UI/UX Designers. By establishing a method of visibility for our Design Team we could ensure that designers and developers were aligned.
As a result, we were able to decrease development time. Key UX decisions that surfaced could be addressed quickly now that links were made between developers and designers.
Our Organizational structure meant our Design team was in a different department from our Development team. Both resources were coming together in a project-based team structure. This meant that our design feedback loop was new and unfamiliar to our team members. We found that as we moved from Proof of Concept phase to Development, we were losing feedback from our Creative Director. This meant lost time and effort as the development team needed to sift through Jira comments and our Creative Director needed to rewrite her feedback.
We were losing this feedback because the feedback and UI/UX concerns brought up needed further exploration or went beyond the scope of that particular "story". With the original agreement that the UX issue would be handled moving forwards, the Creative Specialist would move the story forward. However we found that there were cases where the developer/designer would not come back and take action.