Sanofi
Improving Dashboard Discoverability and Data Transparency for Clinical Teams
Role
Product Designer Intern
Team
1 Design Lead
1 Designer (me)
2 Product Owners
1 Developer
Project Status
Launched in Q1 2025
Project Timeline
Sept 2024 - April 2025
Overview
As a Product Design Intern on the Digital Consumer Experiences team, I led the design of the end-user experience and supporting admin workflows, with guidance from my design lead. I collaborated with product owners and developers throughout the project, from early exploration through launch.
Problem
Clinical teams needed a reliable way to find relevant dashboards and assess whether their data was up to date.
With 100k+ Power BI dashboards across Sanofi, finding relevant reports and determining whether their data was current could be difficult, slowing decision-making and undermining confidence in the insights they used.
Research
I synthesized user interview findings and helped identify recurring challenges.
I shadowed my design lead during interviews with 12 clinical users, taking notes and synthesizing their feedback into three key findings that helped me understand users’ challenges and inform my workflow analysis.
No clear starting point
Users relied on bookmarks, saved links, and colleagues to find the dashboards they needed.
Uncertainty about data freshness
Users were not always confident that dashboard data was up to date.
Limited visibility into ownership
Users did not always know who managed a dashboard or whom to contact with concerns.
Opportunity
How might we help clinical teams find relevant dashboards and assess the reliability of the information they contain?
Approach
I established the portal’s foundation with my design lead, then tested and refined the wireframes with 4 users.
-> Lo-fi Desktop
-> Lo-fi Mobile
Design Decision 1/4
Making dashboard freshness and ownership visible helps users assess reliability and find the right contact.
-> Final Design for Assessing Reliability
The Challenge. Users needed to assess whether dashboard data was current and know whom to contact about concerns, and freshness could vary between pages within the same dashboard.
My Decision. I made dashboard ownership and contact information easy to find, added an owner filter, and surfaced freshness at the page level where it was most relevant.
Design Decision 2/4
Keeping page exploration separate from access requests lets users evaluate dashboards before requesting access.
-> Before and After
The Challenge. An earlier iteration replaced the Pages button with a Request button, preventing users from inspecting dashboard contents before deciding whether to request access.
My Decision. I kept the Pages button available and moved the Request action beneath the owner’s name, allowing users to explore dashboard pages before deciding whether to request access.
Design Decision 3/4
Hierarchical search helps users find relevant dashboards and pages without losing context.
-> Final Design for Search experience
The Challenge. Search needed to surface relevant dashboards and individual pages while preserving the relationship between each page and its parent dashboard.
My Decision. I designed a two-level search hierarchy, showing dashboards as parent results and their pages as indented child results, with relevant tags and medical KPIs to help users identify matching content.
Design Decision 4/4
Using a dedicated page for dashboard pages avoids disruptive shifts in mobile navigation.
-> Final Design for Mobile Page Viewing Experience
The Challenge. I initially explored an accordion to mirror the desktop experience, but expanding it pushed content down and required extra scrolling to collapse, disrupting navigation.
My Decision. I designed a dedicated subpage to display all dashboard pages, keeping the layout stable and making it easier for users to move between search results and dashboard pages.
Solution
Sanofi InsightsHub: Improving Dashboard Discoverability and Data Transparency for Clinical Teams.
-> The Sanofi InsightsHub end-user facing portal
How it works. InsightsHub displays applications, dashboards, and reports based on each user’s organizational role. Users can search, favourite, and request access to relevant dashboards, check when data was last updated, and identify dashboard owners to follow up on data concerns.
Impact
14 days after launch, InsightsHub's user base grew 8x, and 75% of users engaged with the platform daily.
To support adoption, I designed internal communications materials and conducted post-launch interviews with users to identify navigation friction and design inconsistencies. I collaborated with developers to implement hotfixes based on their feedback, helping address usability issues as they emerged.
8× growth in user base
InsightsHub grew from 80 users at the end of Day 1 to 869 by Day 14.
75% of users active on Day 14
By Day 14, 75% of users had accessed the platform in at least one session that day.
15-point increase in SUS score
Post-launch SUS scores increased from 72 to 87 following user feedback and usability improvements.
Retrospective
Designing around constraints rather than trying to solve everything at the source.
Initially, I questioned why we couldn't address data reliability directly within Power BI. Through discussions with the product owner, I learned how governance policies and distributed dashboard ownership limited our ability to make changes to the underlying dashboards. Instead, we designed an experience that gave users more transparency into data freshness and a way to contact dashboard owners.
I also learned that seemingly small behaviors, such as bookmarking dashboards or asking colleagues for links, can reveal deeper usability problems. These workarounds helped us understand where the existing experience fell short and informed a more centralized approach to dashboard discovery.
