The biggest challenge of this project was understanding the ideal workflow for scientific uses. We spent a lot of time on user research and coordinating with a key industry expert to ensure success. This involved live sessions and Q&A alongside our research. We also interviewed students and industry scientists to help us identify the key issues and use cases.
(Above) Survey Monkey Example. We sent out a survey to customers to help us better identify our users as well as identify common use cases.
(Above) Map of Existing Menu Architecture
(Above) What a site visit typically looks like. Photo by Roy Kaltschmidt, LBNL.
(Above) Old Scientific Software.
Most scientific software is not designed using modern technologies. I was surprised to know that scientists use such outdated software every day in the workplace.
(Above) Journey Maps
After, enough upfront research we created journey maps to capture the overall areas of improvement and user story.
(Above) User Persona
We divided user personas into three main user categories based off of our interviews. Our archetypes were the novice student, the lab manager, and the working scientist, who were our power users.
(Above) Onboarding workflow
We used these workflows to discuss user paths with expert users to help define our course of action before creating wireframes.
(Above) Example Wireframe for Collecting Data
We then created an interactive prototype to hand over to their product manager to perform testing with their clients. They also used our prototype to review with senior leadership and to show developers the expected interactions.
(Above) Material Design Example.
I presented visual design languages to the client and explained the benefits of leveraging an existing system to streamline development & design efforts to meet our aggressive timeline. We went with a material inspired look and built off of that. I lived in this documentation for a while, I was the main knowledge holder and would commonly leverage and check standards to streamline the design & development.
(Below) Style Guide Snap Shot.
I designed the visuals for multiple screen sizes to ensure proper responsive definition and created an in-depth style guide for the software team hand off.