Field Territory Insights Hub · Enterprise Analytics Anonymised

From territory datato focused HCPactions.

Helping pharmaceutical field teams move from territory-level performance data to focused HCP actions — one workflow for insight, evidence and next-best action.

Platform
Enterprise web app
Users
Field reps & territory managers
Client
Global pharmaceutical company
Product
Field Territory Insights Hub
Timeline
3 weeks
Role
Product / UX Designer
01Overview

One workflow for territory, HCP, insight and action.

Field representatives manage large territories containing hundreds of healthcare professionals. To prepare effectively, they need to understand both the overall territory and the individual HCPs influencing its performance.

The Field Territory Insights Hub brought together AI-generated territory insights, market and prescription trends, patient-switching behaviour, HCP performance rankings, search and HCP-level intelligence, weekly engagement recommendations and conversational data exploration.

The product connected territory analysis with individual HCP actions — moving users from “what is changing?” to “who should I engage, and why?”

02Design Problem

Data was abundant. Priorities were not.

Field teams had access to extensive market, prescription and customer data, but translating that information into clear priorities was hard. The experience needed to help users:

  • Understand performance across an entire territory
  • Identify the HCPs driving important changes
  • Compare multiple metrics without losing context
  • Verify AI-generated insights through supporting evidence
  • Move from analysis to a relevant engagement action
  • Manage recommendations without feeling locked into them
How might we

…help field teams quickly interpret territory performance, identify priority HCPs and convert insights into confident engagement actions?

03Role & Responsibilities

End-to-end product & UX ownership.

  • Translating business requirements into user stories
  • Defining the territory-to-HCP information architecture
  • Structuring the long-scroll dashboard
  • Mapping search, insight and recommendation flows
  • Designing charts, filters and leaderboard interactions
  • Creating AI insight and evidence patterns
  • Designing recommendation states and feedback controls
  • Building reusable components and interaction variants
  • Prototyping navigation, overlays and state transitions
  • Collaborating with business and development teams
04Process

A component-led enterprise UX process.

Requirements→User stories→IA→Dashboard structure→Component exploration→Hi-fi design→Prototype→Stakeholder iteration

Two core needs framed the product:

  • View consolidated insights for all HCPs within a territory.
  • Receive and manage weekly recommendations for individual HCPs.

The experience was then organised around a progressive journey — Territory overview → Key change → Supporting evidence → Priority HCP → Recommended action.

Open business questions on brand terminology, therapy-area comparisons, HCP naming conventions and future scalability were documented alongside the designs and considered during iteration.

05Research & Key Insights

Insights came from the field workflow.

The project file documented requirements and stakeholder questions rather than formal interview findings. The strongest UX insights came from analysing the field representative's daily workflow.

Territory first, HCP second

Reps manage many HCPs, so they need a territory-level view before investigating individual profiles.

Insights must lead to action

Charts alone show change; AI summaries were used to explain the change, name the contributing HCPs and point to the next investigation.

Explainability builds trust

Users needed to see why an insight or recommendation was generated — rationale, sources and dates sit alongside AI outputs.

Familiar patterns reduce adoption friction

Recommendation cards borrow the structure of the field team's existing CRM workflow, keeping familiarity while adding AI capability.

Recommendations require control

A suggestion may be wrong, mistimed or already done — users can explain, dismiss, snooze, complete, retrieve or ask for an alternative.

Dense data requires layered disclosure

Narrative insights, charts and a wide leaderboard could not compete at once — progressive disclosure and overlays kept the surface calm.

06User Flows & Wireframes

Structural exploration before pixels.

The working file explored structure and components rather than a separate low-fi set. The wireframes below reconstruct the intent — four flows and four skeleton layouts for the surfaces that ended up in the UI.

Territory exploration
My Territory→Timeframe / filters→Key insights→Evidence→Chart or HCP→HCP profile

Begin with a summary, then progressively access underlying detail.

HCP discovery
Search HCPs & Accounts→Select HCP→HCP insights→Follow-up question

Bypass the territory dashboard when the user already knows the HCP.

Recommendation management
Weekly recommendation→Review action→View explanation→Complete / dismiss / alternative

Dismissal includes reasons and snoozing; completed or dismissed items can be retrieved.

Conversational exploration
Open assistant→Suggested prompt or custom Q→Generated response→Continue

Complements the structured dashboard rather than replacing it.

Territory dashboard
Low-fi
Wireframe A · Long-scroll analytical viewTerritory header → AI insight cards → market / switching charts → high-density HCP leaderboard with anchored name column.
HCP insights & assistant
Low-fi
Wireframe B · Conversational HCP viewHCP profile with prescribing summary, distribution and switching charts. Suggested prompts and a persistent assistant input at the bottom.
NBA recommendation
Low-fi
Wireframe C · Recommendation lifecycleRecommendation card with feedback controls, Explain-the-Suggestions and Alternate-Recommendation actions revealing an evidence body underneath.
CRM suggestions list
Low-fi
Wireframe D · Familiar CRM patternLeft rail counters for scheduled calls and emails; stacked HCP suggestion cards with Dismiss / Mark as Complete affordances borrowed from the existing CRM.
07UI Design & Design Decisions

Four surfaces, one connected workflow.

Four hi-fi surfaces cover the territory dashboard, its scrolled analytical view, the integrated conversational assistant, and the weekly Suggestions list. All copy, HCPs and territory names are fictional; only the drug-class terminology is retained for realism.

Anonymised for a global pharmaceutical client — a fictional brand identity ("Compellium Pharmaceuticals") and territory ("Sarasota") replace the original references.
01 · Territory Level Insights — AI-generated insight cards
02 · Territory Level Insights — market correlation, engagement radar & switching matrix
03 · HCP Leaderboard with conversational assistant open
04 · Suggestions — weekly recommendation cards with lifecycle actions

AI insights before raw data

The dashboard opens with concise territory insights covering class movement and share changes — an interpretation is offered before the detailed chart.

Evidence without losing context

Selecting View Evidence opens a contextual overlay with the supporting chart and source dates instead of navigating to a separate report.

Territory-to-HCP navigation

HCP references in insights, tooltips and leaderboard rows are interactive — a click opens the individual profile from anywhere in the flow.

Layered data visualisation

Market correlation, patient-switching, share-vs-volume and HCP ranking each get their own module; tooltips reveal deeper metrics only on demand.

A usable high-density leaderboard

Rank and HCP name stay anchored while metric columns scroll horizontally — filters narrow the visible group, comparison never collapses columns.

Recommendation lifecycle

Every card is stateful — explain, feedback, complete, dismiss with reason, snooze, retrieve, previous suggestion, generate an alternative.

Integrated conversational assistant

A prompt entry point lives inside the territory experience with suggested starters and a usage disclaimer on generated answers.

Reusable component system

Insight cards, KPI tiles, filters, tables, tooltips, overlays, recommendation states and feedback controls were built as one library to scale across brands and therapy areas.

08 · Design Impact

Product outcomes, not quantified metrics.

The working file did not contain verified production metrics — the impact below is presented as product outcomes rather than business results.

Connected territory performance with individual HCP action
Reduced the need to interpret multiple disconnected reports
Converted complex data into prioritised narrative insights
Made AI outputs more transparent through rationale and evidence
Improved control over recommendation status and relevance
Supported both broad territory review and direct HCP search
Created reusable patterns for future insight modules
Preserved familiarity with existing field-team workflows
09Learnings & Reflections

Enterprise dashboards need hierarchy — not more data.

Enterprise dashboards need hierarchy, not more data

Narrative insights established direction; charts and tables provided progressive levels of evidence.

AI outputs need visible reasoning

An insight becomes credible when users can inspect its rationale, sources and underlying chart — not just a conclusion.

Reversibility strengthens user confidence

Dismiss, snooze, retrieve and previous-suggestion states gave users room to decide without fearing permanent consequences.

Component states are part of the UX

Expanded, completed, dismissed and alternate states aren't visual variations — each is a stage in the user's decision.

Long-scroll needs intentional navigation

Vertical dashboard scrolling combined with a horizontally scrollable leaderboard preserved readability without hiding data.

Familiarity and innovation coexist

Aligning recommendations with a known CRM pattern reduced the learning curve; AI explanations and alternatives added the new value.

Scalability begins with terminology

Questions about brand labels, therapy comparisons and HCP naming exposed the importance of components that support future products, not just the first use case.