top of page

Case Study

Integrating 200 separate drug brand sites into one consistent site - The Sanofi Campus Knowledge-base.

Integrating 200 separate drug brand sites into one consistent site - The Sanofi Campus Knowledge-base.

Context

The Sanofi Accelerator is an innovation centre within the global healthcare company aiming to transform the business with the use of digital experience, data and artificial intelligence. 
 
As one of six CX design leads embedded in Agile product teams, my role was hands on from product ideation and strategy through to UX and UI design, as well as contributing to the design system. 

Company:

Sanofi

Role:

Lead Product Designer

Expertise:

UX Strategy, Research, Product Design, UX/UI, Illustration

Market:

Healthcare, B2B, B2C

Challenge & Solutions

Challenge

  • It's complicated to achieve consistency when pulling content from 200 uniquely branded sites, with different content and navigation structures, managed by different stakeholders and agencies.

Solution

  • Devise a clear process and communication to explain the changes and reason for the project with stakeholders.

Challenge

  • The pace and fluidity of projects, when stakeholders have different ideas about schedule of innovation.

Solution

  • Use Agile methodology, with emphasis on epics, as well as sprints, so that we consider strategy.

Challenge

  • A new and incomplete Design System.

Solution

  • Work with design team to add new tokens, patterns  and elements, as needed. 

Process

Managing Stakeholders & Process

The idea of moving from more than 200 separate websites, to one unified knowledgebase was culturally complicated for Sanofi and the brands. A process was developed to explain the big picture and communicate the value of the Sanofi Campus Knowledgebase to stakeholders and explain the workflow process.
Defining the Process:
  • Identify which brand sites are included.
  • Develop timeline of integration for brands and sites.
  • Kickoff meeting - to introduce and explain what to expect for all participants.
  • Hold individual Brand kickoffs to explain workflow and timeline to stakeholders.
  • Redesign each product page to fit within the new design system.

Research

User & Business Research

To qualify and quantify our hypothesis that a single knowledgebase was necessary for the business and users, I performed research by interviewing three types of users: Medical Professionals, Scientists, and Patients.

Research Methods

User Diaries

Most medical professionals preferred making 2-3 minute audio or video diaries to observation. We asked them to explain out loud the research topic, why they chose it and level of success, as well as length.

User Interviews

I asked these questions to understand how Scientists and Medical Professionals performed their research:

  • Which resources/media do you use for your research on diseases?

  • How do you stay current about diseases and treatments?

  • How long do you spend on research?

  • How often do you perform research?

  • How easy is it to find the information you're looking for?

  • What would make your process faster?

  • When do you do your research?

  • What is your biggest painpoint?

Observation

I observed patients looking online for information about a disease, asking them to speak out loud their thoughts and process. I shared a prototype showing three different versions of the same webpage to understand which they preferred.

Insights

Untitled.png

Medical Professionals (HCPs)

Need to stay up to date with the latest research and development and treatments in their areas of expertise.

Pain Points
  • Are stretched for time and overwhelmed by information.

     

  • After a full day of seeing patients, they typically spend 30 minutes looking for relevant updates and knowledge to help their patients.

Information Sources
  • CDC, NICE, EMA and WHO.

Wants To
  • Receive relevant email newsletters.

     

  • Download and print articles for reference, and to share with patients and colleagues.

Untitled.png

Scientists

Need to keep up with the latest research & development of therapeutic treatments & new ways of thinking about diseases.

Pain Points
  • Are pressed for time.

     

  • Difficult to find out what drugs are in the pipeline.

Information Sources
  • CDC, NICE, EMA and WHO.

Wants To
  • Receive relevant email newsletters.

     

  • Download and print articles for reference, and to share with patients and colleagues.

Untitled.png

Patients

​Want to understand their diagnosis, what treatments are available, and learn about other patients' journeys.

Pain Points
  • Are often scared of their diagnoses and find it easy to fall 'down the rabbit hole' on Google.  
     

  • Many articles are difficult for a non-medically trained person to understand.  
     

  • There is too much information, often it is conflicting, outdated, or wrong.

Information Sources
  • Medical Professionals, Google, Other Patients, Patient Groups on Facebook, YouTube, AI.

Wants To
  • Understand what it is like to live with their disease and how other people cope.  
     

  • Would like customized information and articles, with quizzes and other interactive content to make it more useful and memorable.

All users preferred the approach of a unified Knowledge Website with clear paths between different diseases because it saved them time. 

Key Recomendations

See Across Diseases

Allow users to see treatments across different diseases, since patients may have comorbidities (asthma and atopic dermatitis for example), where both conditions utilise the same treatment.

Accessiblity First

Provide subtitles and downloadable transcript to support disabled & neuro-divergent users.


Content must meet the W3C Accessibility Standard (AA).

Tags & Suggestions

Content layout should follow a consistent template, be easy to scan, use tags, and suggest related articles to read next.

Design Migration Process

1.

  • Audit existing content

2.

  • Benchmark design against existing Design System.
    Identify gaps and missing elements and patterns.

  • Design solutions to address gaps.

3.

  • Internal design review to approve new design patterns for the Design System.

4.

  • Socialise design with Brand Manager and Product Owner
Design Phase
Scroll through the Figma prototype below to see how I morphed the content into our new design system.

Design Examples

bottom of page