Project Overview

Summary

The full name of Siemens PMA is Siemens Pharmacy Management Application, a system to help pharmacists manage the order of the radiopharmacy and plan for the shipment. Working in the medical field means a lengthy testing process and acceptance of products that might influence users' health and well-being. As a result, we see our work on the market much later than in other industries. Currently, projects I've worked on are still in the pipeline or used by internal employees. I will share the high-level process and what I learned from this project. Don't hesitate to contact me if you want to go through the case study.

My Role

I supported the team with envisioning and crafting shipping management, pharmacy searching, and printing features through journey maps and interviews. I helped make these ideas tangible through prototypes and used Harris Evaluation to discuss the advantages and disadvantages of each prototype with the team.

Duration

6 weeks

Design process

01

Contextual inquiry

02

Research

03

Low-fi with harris- evaluation

04

Hi-fi with user study

Research

Step 1: Contextual Inquiry

When I knew I would work on this project, I set up 1:1 with the senior designer to learn about the project scope. During this process, I learned about the background of the project (Current user-flow, user needs, and design), the resources related to my project (Research documents, design documents, Components documents, stakeholder), and the glossary of the project ( Medical products usually contain many unfamiliar words).

Step 2: Scope of the project.

I checked and read past research work, including end-to-end pharmacist workflow on the current PMA software through the video and interview report to understand user needs. On the other hand, we planned to reuse info from an existing product while considering the habit of our users and engineering feasibility. In the end, we decided to focus on three features in phase one: shipping management, searching and printing feature.

Step 3: Competitor Analysis

Based on my research insights, I created several users flows to define these three features' critical interaction. The user flow helps us explain the use cases, pain points, and information users need. After we described the essential interaction and user need, I searched similar products/features on the market to see how other companies solve similar problems.

Low-Fi with Harris Evaluation

After research, I started to create low-fi prototypes to deliver my ideas. I shared the design with my teammates, and I also compared my lo-fi prototype via harris evaluation to let my colleague know the pros and cons of each of my ideas.

Hi-fi Prototype with User Study

Based on the feedback from the low-fi prototype, I picked three ideas and created a hi-fi prototype for them for the user study.

Shipping management

Searching

Printing

Key Takeaway

Because of the time restriction, I do not have a chance to participate in future product feature iterations. However, I learn a lot from communicating with our developer, senior designer, and product manager.

Designer & Manager

In this project, I worked closely with the senior design and manager tried to use the research method to present the advantage & disadvantages of each concept. I also participated in user interviews with my colleagues and discussed how to improve the efficiency of the user interview after the interview session.

Developer

From the communication with the developer, I understand how to cooperate and negotiate with developers from different perspectives and help developers get to know your design quickly and efficiency.
- Highlight the component which does not in the design system.
- Have a list of priorities of the importance of different feature.
- Negotiate with the developer from priority level, user feedback, commonality of the components.