THE SOLUTION
A tablet-based software that includes device synchronization, visualization, and automation to make environmental monitoring seamless.
Along with the project manager, 2 domain experts, and 7 developers I designed the structure (information architecture and user flows) and user experience (design systems and screens) of the EM software to help pharmaceutical employees efficiently track data with the help of device synchronization and data visualization avoiding any breakdowns and errors.
Initially, I did not know much about Environmental Monitoring :(
Just like any other person outside the domain of pharmaceuticals - I also had endless questions like these.
I defined my design process, starting with answering these questions.

DOMAIN RESEARCH
Therefore, I first studied the domain of the problem
Reading literature and discussing the topic with the domain experts at Caliber helped me familiarize myself with the terminologies and the processes involved in the problem space.
Here is a very high level view of what Environmental Monitoring looks like:

Some key observations from the flow:

SUBJECT MATTER INTERVIEW
I started with understanding the user requirements
I conducted subject matter interviews to understand the “whys” behind the 3 major problems that were described to me initially. Additioally to undertand the users, painpoints and thier needs.

Key observations:


EXEMPLAR ANALYSIS
Existing products addressed some of the pain points, but no one product did it all.
Keeping the recognized user needs in mind, I analyzed the technologies used in the space of environmental monitoring based on the following factors:

DEFINING DESIGN GOALS
Our findings inspired design goals for the system:

USER FLOW & IDEATION
Design goals into action:
A few rounds of discussions with the product manager and team heads regarding the features, requirements, technical capabilities, and constraints happened, which inspired the user flow.
I did some quick paper prototyping to understand as well as communicate ideas of implementation to the team.

Wireframe sketches corresponding to each flow
A few rounds of discussions with the product manager and team heads regarding the features, requirements, technical capabilities, and constraints happened.
I did some quick paper prototyping to understand as well as communicate ideas of implementation to the team.
INFORMATION ARCHITECTURE
Structuring the ideas for designs and databases
As, the development team had to start working on the system, I created the Information architecture of the EM system which would not only get the findings validated but also become a reference for the tech team to work on the database for the EM module.
My engineering Background helped me to convey Information architecture in 2 ways - the design way and the engineering way.

CONTEXTUAL INQUIRY
Interacting with the EM employees in the context revealed some undiscovered insights
With this, I could map the painpoints over the user journey and realized the opportunities at every phase of the process during the contextual inquiry.

DESIGN CONSIDERATIONS
With opportunities in hand - there were a few considerations as I started designing the screens:
