Providence Genomics drew together a wide variety of programs, from research studies to patient-facing test orders. We had two core users: physicians assisting in internal programs or ordering tests for patients; and patients interested in tests. Some information was public and some was covered by HPAA. Therefore, we had to carefully design the site to be clearly navigable for users with a wide variety of goals.
Prototypes of the home page interactions were presented to stakeholders and developers, along with examples of movements from similar websites to get approval before proceeding to hi-fi designs.
One our goals was to emphasize the cutting-edge nature of the Providence Genomics program by differentiating the graphic design from the home Providence site. We did that with banner image choice, bespoke graphic elements, and creating dynamic and interesting section compositions.
Propel builds on top of previous successful genomics studies run by the Providence Genomics program- it is an end-to-end platform that creates clinical genomics trials for other systems. If your system is interested in genomics but needs help with implementation at scale, Propel is for you.
Creating a platform-as-a-service was not something that Providence had done before, so we wanted to differentiate the product with its own brand identity. I also wanted to set it apart from other genomics startups in the industry.
I created the logo and color scheme after a competitive analysis and built a visual language using a few selected design motifs (the helix ribbon and the underlined title style). I used this component library across the final website.
Designing for both physicians and patients required navigating two very different sets of expectations and mental models. Physicians came to the site with specialized vocabulary and a need for quick, precise access to ordering systems and research tools, while patients were often looking for approachable explanations, clarity, and reassurance. Balancing these priorities meant simplifying navigation and content structure so neither audience felt overwhelmed or excluded.
Wanting to show “cutting edge” meant pushing away visually from the main Providence style in certain areas, while still being recognizably part of the same institutional umbrella. It’s always a trade-off: stand out vs feel connected.
Building on my existing skills in both design and development, I was uniquely positioned to bridge the gap between visual design and CMS architecture. Because I understood how content was structured and how responsive layouts functioned, I could make quick, iterative changes that improved usability while streamlining implementation. This dual perspective strengthened my ability to design with both user needs and technical sustainability in mind.