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. We created user personas based off of the different user types.
(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) 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.
After, enough upfront research we created journey maps to capture the overall areas of improvement. We then began wireframing and used agile methods to iterate quickly. We tested with the client and users to know if we were on the right path. We created an interactive prototype for this purpose.
(Above) Journey Maps
(Above) Example of a workflow (We did a lot of iterations on these)
(Above) 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. I also presented visual design languages to the client and explained the benefits of leveraging an existing guide to streamline development & design efforts. We went with a material inspired look and built off of that.
(Above) Material Design Example. 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 phases.