Nanotech Software – Responsive & Material 2017-05-17T23:59:45+00:00

Project Description

Scientific Desktop Software

SOFTWARE FOR CHARACTERIZING NANOPARTICLES

Situation

Client is a leader in their scientific niche. However, they found that users had major issues with their software. It was outdated and incredibly difficult to use. Novice users were having a hard time with the intense learning curve and the client knew it was time for a change.

How does it work?

Scientists can use the data from the instrument to identify particles that are optimal for specific applications. A few use cases would be the perfect formula for making paint dry more quickly, or identify a preservative that would make food have a longer shelf life.

High Level Explanation “The Cool Stuff”

  • It involves lasers.

  • Scientists use the system to analyze materials.

  • System requires software & hardware to work together to run the device.

Tasks

Our team was tasked with doing a complete overhaul of their product ecosystem. We were to help set the precedent for the next generation of products. Starting with their flagship hardware and software. I was on the software team.

  • UX Research

  • User Experience

  • User Interface Design

Action

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.

High-Level Deliverables & Activities

  • Attended Site Visits

  • Conducted User Interviews

  • Created Journey Maps

  • Created User Personas

  • Created an Extensive Style Guide

  • Leveraged Material Design Guidelines to Expedite Development

  • Endless Wireframes

  • Iterated on Workflows & Micro Interactions

  • Designed Majority of Assets for User Interface

  • User Tested

  • Visual Design

Results

The new software UX and look was well received by the CEO and the rest of the company. The software went off to be developed by their team. The positive reaction spurred more projects and the client was excited to keep the ball rolling.

Click to view live