Case study

Why one dashboard wouldn’t work for
every pharma team

A healthcare data company needed to understand how pharmaceutical organizations would access and use its analytics products. I led the pharmaceutical research workstream, uncovering how differences in data maturity shaped customer needs—and why a single delivery model wouldn’t work for everyone.

Four pharma journeys informed
three delivery options.

Project at a glance

My role

Lead UX Researcher, pharmaceutical workstream

Industry & Client

Pharmaceutical data & analytics

Methods

Qualitative interviews, workflow analysis, personas, journey mapping, research synthesis, opportunity prioritization

Scope

Pharmaceutical research within a larger, 25-interview healthcare data initiative

Outcome

Four pharmaceutical personas and journey maps, three recommended delivery approaches, and prioritized product opportunities

Client details and research artifacts have been generalized to protect confidentiality.

The challenge

The same data could serve very different customers. But how should they receive it?

The client was exploring new data and insights products for pharmaceutical organizations. Before deciding how to deliver those products, the team needed to understand how customers actually worked with healthcare data—and what would make an offering valuable enough to adopt.

Why it was complex

Different business decisions

Marketing leaders measured campaign performance, sales leaders monitored territories, and forecasting teams evaluated market opportunities. Each needed different answers.

Uneven technical capabilities

Some organizations relied on spreadsheets and vendors to aggregate data. Others had sophisticated internal platforms, analytics teams, and established processes.

Barriers to adoption

Customers needed reliable data, flexible analysis, and meaningful insights. Another dashboard could create more work instead of solving their problems.

Doodle of a puzzled character with a question mark.

Would they even want
another dashboard?

Research & discovery

Following the data from collection to decision-making

I led the pharmaceutical research workstream, conducting stakeholder interviews, synthesizing findings, and developing personas and journey maps to identify both shared needs and meaningful differences.

Interviewing across functions

I spoke with pharmaceutical professionals in marketing, sales, forecasting, product management, and analytics to understand their decisions, tools, and frustrations.

Mapping complete workflows

I developed four persona journey maps tracing how users collected, combined, explored, interpreted, and communicated data to make business decisions.

Connecting findings to opportunities

I compared pain points across journeys and identified opportunities around data access, analysis, integrations, reporting, and actionable insights.

Key insight

“Data maturity matters more than job title alone.”

Job roles explained what people needed to accomplish, but their organizations’ data capabilities helped determine how they could use a solution. Teams without centralized systems needed accessible tools for exploring data. Organizations with established platforms wanted integrations, while technically advanced teams needed flexible API access rather than another dashboard.

Design response

Matching the delivery strategy to the customer’s existing workflow

The findings supported three distinct approaches to delivering data products.

Self-service data portal: For teams without centralized infrastructure, provide an accessible place to query, compare, and interpret data.

Integrations and connectors: For organizations invested in existing CRM and business intelligence tools, make insights available where they already work.

API access: For organizations with internal analytics capabilities, provide flexible access to data for their own customized solutions.

The journey maps and prioritization exercise also identified valuable capabilities across these approaches, including custom queries, transparent data sourcing, anomaly detection, and actionable insights.

Rather than treating the interface as the starting point, the research helped make the customer’s workflow the foundation for delivery decisions.

Outcome

Research that informed a more adaptable product strategy

The research provided a clearer picture of how pharmaceutical organizations worked with data and a practical framework for delivering products that fit their existing capabilities. Rather than recommending a single platform, the findings supported multiple ways to meet customers where they were.

The engagement concluded with research findings and strategic recommendations. Subsequent implementation and adoption outcomes were not confirmed.

A clearer approach to customer segmentation

The research demonstrated why job titles alone were insufficient for choosing a delivery model. Organizational data maturity and existing infrastructure became important considerations.

Prioritized product opportunities

The work informed three recommended delivery approaches and a prioritized set of capabilities, distinguishing immediate customer needs from longer-term opportunities.

What this shows about my work

Finding the patterns that shape product strategy

Research leadership

Led pharmaceutical interviews, synthesis, persona development, and journey mapping.

Challenging assumptions

Identified an important segmentation dimension beyond conventional job-role categories.

Strategic product thinking

Translated complex customer workflows into practical product delivery recommendations.

Making complexity clear

Organized research into visual journeys and prioritized opportunities that stakeholders could act on.