Project Vision

F5XC (Distributed Cloud) is a SaaS-based security, networking, and application management console, on which we have multiple workspaces with different types of dashboards to support various protection and investigation. In each dashboard, users could utilize filters to narrow down the data and focus on a particular part that they care about most. In the original system, we did not have functionalities to support users reapplying a set of filters or sharing a filtered view, thus causing inconvenience in the communication between security engineers and technical account managers. We tried to solve this issue starting with the Bot Defense workspace, and figured out a new design pattern as phase one that could be easily adjusted and adopted to all the workspaces in the console.

Challenges

	Figure out a new design pattern that could meet the needs of Bot Defense users but also be applicable to other workspaces in the console.
	Address time expiration and data missing edge cases.
	Tackle dynamic filter values which would change based on configuration.
	Walk around the API constraints which are unable to present accurate missing information right on some pages, and unable to apply non-existing filter values.
	Make minimum but reasonable changes in phase one that could satisfy the functionality and get all stakeholder approvals to roll out.

Project Goals & Design Requirements

Clarify target users, their goals, workflow and pain points.

Through many discussions, I learned that we could serve multiple types of clinical people. The target usage scenarios include:

	Small clinics who need an exam storage and management system, or need a system to support ultrasound trainings for physicians.
	Teaching hospitals who need a system to support ultrasound trainings for residency medicine.

The use cases had many common needs and common parts in their user journeys, and the users could be roughly categorized into two types of roles – the exam operator, and the exam reviewer.

To keep it simple, we tried to integrate them into one representative general user journey:

	In the beginning, the ultrasound exam operators could use our software and device to scan and acquire desired data.
	Operators could upload exams to the online web portal, review and edit there, fill in reports, and submit for reviewers to review.

The use cases had many common needs and common parts in their user journeys, and the users could be roughly categorized into two types of roles – the exam operator, and the exam reviewer.

To keep it simple, we tried to integrate them into one representative general user journey:

	In the beginning, the ultrasound exam operators could use our software and device to scan and acquire desired data.
	Operators could upload exams to the online web portal, review and edit there, fill in reports, and submit for reviewers to review.

The use cases had many common needs and common parts in their user journeys, and the users could be roughly categorized into two types of roles – the exam operator, and the exam reviewer.

To keep it simple, we tried to integrate them into one representative general user journey:

	In the beginning, the ultrasound exam operators could use our software and device to scan and acquire desired data.
	Operators could upload exams to the online web portal, review and edit there, fill in reports, and submit for reviewers to review.

Design Challenges & Strategies

Tackle xxx challenges by.

The use cases had many common needs and common parts in their user journeys, and the users could be roughly categorized into two types of roles – the exam operator, and the exam reviewer.

To keep it simple, we tried to integrate them into one representative general user journey:

	In the beginning, the ultrasound exam operators could use our software and device to scan and acquire desired data.
	Operators could upload exams to the online web portal, review and edit there, fill in reports, and submit for reviewers to review.

Initially, KOSMOS UP only served students and faculties in medical schools. As the company expanded the service area to clinical usage, we wanted to build a new product which was similar to the existing product – Kosmos UP Education, but it could better support clinical use cases – “Kosmos UP Clinical.”

When I got looped in in an early stage, I found that the project scope was very ambiguous, so I worked together with the PM to clarify the scope that we should focus on for the MVP and for the future, based on the market needs.

	In the beginning, the ultrasound exam operators could use our software and device to scan and acquire desired data.
	Operators could upload exams to the online web portal, review and edit there, fill in reports, and submit for reviewers to review.

It happened that the company created a new branding guideline for marketing usage months before the project got kicked off, so my design partners and I followed the concept, typeface, and theme colors to develop a new design guideline for the new product.

I also found that there were many issues found in the previous free trials to our potential customers in the industry that were not covered in the scope, so I advocated to include usability improvement in the MVP as well, including the major issues in navigation, search, and input interaction.