Particle Health
YEAR
2021-2022
ROLE
Building the Product Design Team
Senior Product Designer
Particle branding by Order︎︎︎
2021-2022
ROLE
Building the Product Design Team
Senior Product Designer
Particle branding by Order︎︎︎
Initial Audit and User Research
This paragraph should explain what was the status quo and how there was disjointed research and mainly how there was a lack of source of truth and shared understanding of what our product is and what our portal does/offers.
This paragraph should explain what was the status quo and how there was disjointed research and mainly how there was a lack of source of truth and shared understanding of what our product is and what our portal does/offers.
︎︎︎
Customer Journey template we created to fill in the gaps and create a unified single source of truth for cross-functional reference within the company.
Customer Journey template we created to fill in the gaps and create a unified single source of truth for cross-functional reference within the company.
We carried out interviews with users accross multiple stages of the journey, and critically complemented these with primary and secondary research accross all relevant stakeholders within the company. The resulting artifact quickly highlighted the complexity of the processes happening around the Sales and Implementation cycles.
Focusing on the Portal
Our research highlighted how the journey splits from our controlled environment (website and portal) during the Sales and Implementation cycles, thus creating a non-continuous experience that drives focus away from what is mean to be a state-of-the-art portal. Users and different teams within the company had different expectations as to what this portal should do, but rather disappointingly, non of these seemed to be fully considered while curating the experience within. We therefore started thinking about a future ideal state of this portal that could drive the different phases of the journey within itself and also accommodate any future tools or product we may want to add to further enhance this experience.
Our research highlighted how the journey splits from our controlled environment (website and portal) during the Sales and Implementation cycles, thus creating a non-continuous experience that drives focus away from what is mean to be a state-of-the-art portal. Users and different teams within the company had different expectations as to what this portal should do, but rather disappointingly, non of these seemed to be fully considered while curating the experience within. We therefore started thinking about a future ideal state of this portal that could drive the different phases of the journey within itself and also accommodate any future tools or product we may want to add to further enhance this experience.
Designing a new vertical
We were presented with a new challenge that, although clear in its overall objective, lacked from any concrete definitions around the kind of product it should be. After making an in-depth study of our pre-existent Admin Portal’s IA we realized it would be possible to create a new platform capable of unifying both the existing Admin Portal and the new product. We also planned this new Admin Console in such a way that it could be easily retroactively incorporated into our existing Portal, therefore building towards a unified experience.
We were presented with a new challenge that, although clear in its overall objective, lacked from any concrete definitions around the kind of product it should be. After making an in-depth study of our pre-existent Admin Portal’s IA we realized it would be possible to create a new platform capable of unifying both the existing Admin Portal and the new product. We also planned this new Admin Console in such a way that it could be easily retroactively incorporated into our existing Portal, therefore building towards a unified experience.
︎︎︎
Snapshots of intermediate versions of our new IA.
︎︎︎
Snapshots of intermediate versions of our new IA.
︎︎︎
Displaying two screens of the new platform accross five different iterations. The main focus of these improvements was on environment selector and main navigation. Visual aspects of the UI components, typography, and color use were iteratively improved as well, but not prioritized over our usability efforts.
Displaying two screens of the new platform accross five different iterations. The main focus of these improvements was on environment selector and main navigation. Visual aspects of the UI components, typography, and color use were iteratively improved as well, but not prioritized over our usability efforts.
New product roadmap
Circumstances were such that we worked on our first procuct launch without a clear vision of what would the next steps be. While this was to be expected from the stage the company was at, we decided it was necessary to nevertheless plan for a version of our product that would be robust yet flexible enough to accommodate any future developments or tools within it with ease. This ideal future state would be intended to end the disjointment of experiences currently happening across multiple environments.
Circumstances were such that we worked on our first procuct launch without a clear vision of what would the next steps be. While this was to be expected from the stage the company was at, we decided it was necessary to nevertheless plan for a version of our product that would be robust yet flexible enough to accommodate any future developments or tools within it with ease. This ideal future state would be intended to end the disjointment of experiences currently happening across multiple environments.
Design System
Allocating our resources as efficiently as possible, we decided to build our design system alongside our first product, the Admin Console. This allows us to focus on the components and other elements/values that are directly necessary for this product’s design, while at the same time think about these with a long term approach: how reusable will they be? Planning ahead for more dynamic and demanding times, our main goal is to have at our disposal a system that allows us to rapidly build and iterate new products, enable a larger design cross-team collaboration, and make the dev hand-off as seamless as possible.
Allocating our resources as efficiently as possible, we decided to build our design system alongside our first product, the Admin Console. This allows us to focus on the components and other elements/values that are directly necessary for this product’s design, while at the same time think about these with a long term approach: how reusable will they be? Planning ahead for more dynamic and demanding times, our main goal is to have at our disposal a system that allows us to rapidly build and iterate new products, enable a larger design cross-team collaboration, and make the dev hand-off as seamless as possible.
A New Design Process
We are now implementing a more structured design process to guide our new product workstreams from conception. Applying the Double Diamond framework allows to methodically research, synthesize, define, ideate, and implement from any given challenge.
We are now implementing a more structured design process to guide our new product workstreams from conception. Applying the Double Diamond framework allows to methodically research, synthesize, define, ideate, and implement from any given challenge.
Let’s chat ︎
Instagram︎︎︎ LinkedIn︎︎︎ CV︎︎︎ email︎︎︎