Case Study

Blue Cross NC

Understanding Experiences Through Ecosystems

A nine-year engagement that expanded from product design into research, strategy, and ecosystem understanding across member, sales, enrollment, employer, and agent experiences.

Blue Cross NC’s digital portfolio had grown across products, channels, and teams. Individual improvements solved immediate needs, but the broader experience became harder to understand, maintain, and evolve as a connected whole.

The work increasingly required shared models that could help teams see how customer decisions, operational relationships, and organizational systems shaped the experience.

Blue Cross NC engagement hero image

A representative view of the Blue Cross NC experience ecosystem — spanning member products, sales pathways, enrollment flows, agent tools, research frameworks, and organizational service models.

Case Snapshot
What Changed
Experience work shifted from improving isolated digital products to creating shared models, frameworks, and strategies that made customer decisions, operational dependencies, and service ecosystems visible across teams.
Role
Visual Designer → Product Designer → Senior Product Strategist
Partners / Collaborators
Researchers, content strategists, UX practitioners, product teams, agile delivery teams, sales technology leadership, and stakeholders across member, sales, enrollment, employer, and agent experience areas.
Focus Areas
Product Design, User Research, Information Architecture, Product Strategy, Behavioral Modeling, Experience Strategy, Ecosystem Mapping
Engagement
2015–2024
Primary Contribution
Helped shape product experiences, research frameworks, strategy artifacts, ecosystem maps, future-state concepts, and governance models that made complex customer and operational systems easier for teams to understand and act on.
Progression Overview
Product Design → Portfolio Thinking → Research-to-Strategy → Ecosystem Thinking → Ecosystem Stewardship
01

Creating Intentional Product Experiences

Core Question

How do we intentionally evolve products instead of accumulating features?

Early product work focused on member tools like Billing & Payments, Blue Rewards, and Find a Doctor / Drug & Pharmacy. Each solved a different problem — payment state clarity, wellness progress, and guided healthcare search — while revealing the need for stronger shared patterns across the portfolio.

Across BlueConnect Legacy and related member experiences, I contributed to initiatives that made specific member tasks easier to understand and complete.

Billing & Payments translated payment states, account conditions, AutoPay, billing preferences, recovery scenarios, and policy reinstatement workflows into a clearer member journey. Blue Rewards organized available activities, reward status, progress tracking, filtering, and educational content into a centralized Activity Center. Find a Doctor / Drug & Pharmacy introduced guided pathways and supporting education for members trying to find the right healthcare resource without first understanding insurance complexity.

Together, these initiatives showed where fragmentation was accumulating: account states, progress cues, guided decision points, navigation patterns, educational content, and repeated reinvention of common interactions.

Member Product Foundation: Billing, Rewards, and Provider Search
What became visible

The same needs kept appearing across different products: clearer account states, progress visibility, guided pathways, educational support, and more consistent ways to help members understand what to do next.

What became possible
  • Clearer billing, payment, recovery, and reinstatement pathways
  • Progress and status patterns for wellness engagement
  • Guided search patterns for provider, drug, and pharmacy discovery
  • A stronger foundation for shared portfolio patterns
Reflection

Consistency was not simply visual polish. It was a mechanism for creating clarity, reducing friction, and helping products evolve together rather than independently.

Once the team improved individual tasks, the next challenge was understanding why similar problems kept appearing across multiple products and programs.

02

Building a Shared Experience Foundation

Core Question

How do we create one intentional portfolio instead of many disconnected products?

As more capabilities were introduced, the work shifted from individual screen improvements to shared systems for navigation, information hierarchy, dashboard patterns, and interaction consistency. The goal was no longer visual sameness; it was coherence across experiences.

Shared navigation systems, dashboard patterns, information hierarchy, and component models became a way to create continuity across the growing BlueConnect ecosystem.

The design system established for BlueConnect 2.0 became more than a member platform toolkit. It became a modernization foundation that other product areas began adopting, giving teams a shared language for interface patterns, states, navigation, and product evolution.

This was a mental shift for the organization. The goal was not for every product to look identical. The goal was for experiences to feel connected, easier to modernize, and less likely to diverge as new product areas evolved. Consistency was not the goal. Coherence was.

BlueConnect 2.0 Design System & Modernization Foundation
What became visible

Coherence was not just a visual standard. It was an organizational capability: a way for teams to modernize products without creating new divergence across the portfolio.

What became possible
  • Shared component, navigation, and state patterns across products
  • A modernization foundation adopted beyond BlueConnect 2.0
  • Reduced divergence across member-facing product areas
  • A stronger design system influence across the portfolio
Reflection

Better interfaces made products easier to use. But they could not explain why members struggled, what information they needed, or how they made decisions.

That unanswered question became central to BlueConnect 2.0.

03

Turning Human Understanding Into Experience Strategy

Core Question

How do we turn customer understanding into shared direction?

BlueConnect 2.0 shifted the work from designing around products to understanding how members make healthcare decisions — then translating that understanding into future-state experience direction, architecture, and alignment.

Improved interfaces solved some problems, but they did not explain why members struggled to understand options, evaluate costs, navigate healthcare terminology, or make confident decisions.

The initiative introduced new ways of understanding behavior through personas, behavioral segmentation, lifecycle journeys, Jobs To Be Done, information architecture research, concept testing, and customer feedback. Rather than asking, “What should we build?” the organization began asking, “What outcomes are people trying to achieve?”

That understanding created a new challenge. Research alone could not guide investments, priorities, or product direction. Teams needed shared structures for translating insight into future-state planning, experience architecture, ecosystem models, and quality standards. BlueConnect 2.0 became less a redesign effort and more a vehicle for aligning teams around a shared direction for the member experience.

BlueConnect 2.0 Research-to-Strategy Framework
What became visible

Members were not simply using products. They were making decisions under conditions of uncertainty, cost, trust, terminology, timing, and personal consequence — and teams needed shared structures to turn that understanding into direction.

What became possible
  • Shared understanding of member behaviors, motivations, and decision styles
  • Outcome-driven opportunity framing
  • More informed information architecture, dashboard, and concept decisions
  • Shared future-state experience direction
  • Stronger alignment across teams and stakeholders
Reflection

Observation became understanding. Understanding became direction.

As teams planned future experiences, operational and organizational constraints became increasingly visible.

04

Understanding the Sales Ecosystem

Core Question

Where does the experience actually begin and end?

Sales, enrollment, employer, and agent initiatives revealed that customer experiences were shaped by more than products or journeys. Operational decisions, ownership structures, channels, and supporting actors influenced outcomes long before someone interacted with a screen.

Working with Sales Technology leadership gave me visibility into the teams, ownership structures, technologies, channels, and operational processes responsible for delivering those experiences.

Customers moved between products. Agents supported customer journeys. Enrollment processes influenced outcomes. Operational decisions shaped the experience long before someone interacted with a screen.

For the first time, the organization itself became visible. The sales ecosystem also introduced a new divergence risk: a vendor-created sales flow brought its own design patterns, while guided selling, enrollment, and agent-facing work increasingly needed to feel like parts of one larger experience.

Sales Ecosystem & Organizational Relationship Mapping
What became visible

Customer experience was not shaped by a single product, team, or audience. It emerged from an interconnected network of customers, agents, employers, support teams, channels, technologies, and operational decisions.

What became possible
  • Greater visibility into organizational relationships and ownership structures
  • Stronger awareness of cross-product and cross-channel dependencies
  • Better understanding of how sales, enrollment, and agent experiences influenced customer outcomes
  • A foundation for ecosystem-level planning and decision-making
Reflection

Products became journeys. Journeys became ecosystems. The organization itself became part of the experience.

That realization set up Agent 2025, where the visible portal became an entry point into a much larger internal ecosystem.

05

Agent 2025: Designing an Internal Service Ecosystem

Core Question

How do we help an organization understand and improve the systems supporting its agents?

Agent 2025 brought the earlier lessons together by revealing that the visible portal was only one part of a larger service ecosystem. Research, ecosystem mapping, future-state concepts, and governance work reframed design as stewardship of the systems and structures that sustain experience quality.

Years of work across member, enrollment, employer, and agent experiences revealed the same pattern repeatedly. Agents were not struggling because of a single product. They relied on a complex ecosystem of tools, reporting systems, quoting experiences, enrollment platforms, training resources, support channels, permissions, workflows, and operational processes to serve customers effectively.

While individual products solved specific problems, the broader ecosystem required agents to navigate disconnected experiences, duplicate effort, fragmented information, and unclear relationships between systems. The lessons from BlueConnect 2.0, sales ecosystem mapping, and agent-facing initiatives converged into a new question: how do we intentionally improve the ecosystem supporting agents?

Agent 2025 Research & Ecosystem Discovery
What became visible

The portal was not the experience. It was the visible surface of a larger internal service ecosystem shaped by tools, permissions, workflows, information, support models, ownership, governance, and organizational structure.

What became possible
  • Shared understanding of agent behaviors, motivations, and workflows
  • Greater visibility into ecosystem complexity and operational dependencies
  • Future-state strategy grounded in research and cross-functional alignment
  • Clearer ownership structures and more sustainable content operations
  • A stronger model for long-term stewardship of agent experiences
Reflection

The portal was visible. The ecosystem behind it was not.

The engagement ended with a different understanding of the problem than the one the organization started with.

Closing

The Portal Was Never the Real Problem

Agent 2025 made the larger lesson clear: improving individual products helped, but many of the most important challenges lived in the relationships between products, services, information, support models, operational processes, and organizational structures.

By the end of my time at Blue Cross NC, the challenge was no longer improving individual experiences alone. It was understanding the conditions that create them — and designing the structures needed to sustain them.

Products became ecosystems. Research created understanding. Understanding shaped strategy. Design became stewardship.

The engagement where I learned that experience challenges are often ecosystem challenges.

Next Case Study → CDC DEX

Helping organizations understand, steward, and evolve complex service ecosystems.

CONSULTANCY
AboutResume
Case Studies
Blue Cross NCCDC DEXCMS Hybrid Cloud
© 2025 CuriousWill. Service design with intention.