Jae Choi - Genospace

Patient information indicated in the image is de-identified to comply HIPAA.

DESIGN LEADERSHIP

Grow UX Maturity

The moment I joined Genospace, the UX team seemed functional and promising, yet I felt we needed to do more than deliver UIs based on preplanned solutions at the end of a product cycle, in order to show the true value of UX.

To advocate the design culture, I created UX roadmap, separate from a product roadmap, to push user centered design approach. Second, I gave a talk at an all-hands meeting to make sure everyone in the company has common understanding of the functionality of design, so we all could embrace design initiatives while seeing clear values for them and everyone. Then, I discussed UX roadmap with product owners before they define a product roadmap, so we would have enough time to tackle UX problems in a given timeline. I believe that the new design culture that we are building will bring positive impacts to our users and business.

View Full Deck ↗

DESIGN SYSTEM

Give Rules to UI Elements

Despite we had common UI elements, the way that they were used across the platform was not consistent. Contrary to the purpose of a design system, the elements added complexity to our product. The inconsistent usages confused users and prevented them from learning patterns. Also this problem caused designers to face unnecessary decision fatigues and slowed down the development process.

Starting with modal, since it had the large coverage, I defined clear rules about how it should behave based on careful understanding of how user interact with it. After collecting as many modals in our platform as possible, I carefully aligned and defined pixels to stay close to what have been implemented to avoid overwhelming users with big changes. While working on this, I kept the development process in my mind. Flexible modal sizes could be beneficial in a specific case, however, using fixed modal sizes in general provided more value by expediting the development process. Thus I provided four fixed sizes based on the current usage pattern.

View Full Deck ↗

DESIGN SYSTEM

Give Rules to UI Elements

Despite we had common UI elements, the way that they were used across the platform was not consistent. Contrary to the purpose of a design system, the elements added complexity to our product. The inconsistent usages confused users and prevented them from learning patterns. Also this problem caused designers to face unnecessary decision fatigues and slowed down the development process.

Starting with modal, since it had a large coverage, I defined clear rules about how it should behave based on careful understanding of how user interact with it. After collecting as many modals in our platform as possible, I carefully aligned and defined pixels to stay close to what have been implemented to avoid overwhelming users with big changes. While working on this, I kept the development process in my mind. Flexible modal sizes could be beneficial in a specific case, however, using fixed modal sizes in general provided more value by expediting the development process. Thus I provided four fixed sizes based on the current usage pattern.

View Full Deck ↗

DESIGN STRATEGIES

Manage Complexity: Consistency, Visual Hierarchy, and Information Visibility

While we as a team collectively do our best to envision and build our product functionalities based on the company’s vision and user requests, our designers’ overarching goal was to come up with strategies to best manage complexity of our product both in a macro and micro level, so we can serve our users to get their jobs done in the most efficient and pleasing way, and ultimately increase renewal/new contract rate of our business.

Despite the nature of complexity of our app designed for the highly trained users with specialized knowledge, we could still manage the complexity to produce the finest user experience by carefully addressing the three parts: consistency, visual hierarchy, and information visibility. While all these parts are equally imperative, I decided to first embark on defining a basic layout structure for consistency as it had the highest return on investment and was hindering novice users to adopt our platform.

View Full Deck ↗