
a care experience in the making
From AI tools to care workflows—an early look at design-led transformation.
designed at.
Salesforce • Aetna-CVS
focus.
B2B
role.
Senior Experience Consultant
status.
Paused mid-project due to client-side contract reevaluation
This project aimed to enhance the Customer360 experience within the CVS-Aetna platform to better support internal teams working across multiple lines of business (Medicare, Medicaid, and Commercial). The initiative was a three-way collaboration between Salesforce, PWC, and CVS-Aetna, with Salesforce and PWC jointly leading the experience design. While PWC owned research and stakeholder relationships, Salesforce drove design execution. This created strong cross-functional input, and it also meant I worked with limited direct access to user research and with requirements that kept evolving. My role was to keep design moving by making assumptions explicit and designing modular components that could flex as direction changed. Despite the project being paused mid-way due to contractual reconsiderations, we delivered strong early-phase designs, UX strategies, and structural recommendations that could support future implementation.
objectives
Improve usability and consistency across Customer360
Revamp Claims and Assessments screens
Add and reorganize Quick Access features (e.g. Identity Verification, Contact Support)
Simplify the Left rail and Right Rail layout for more focused data display
Prepare a scalable, AI-enhanced platform experience
design constraints
Needed to support
MULTIPLE LOBS (Medicare, Medicaid, commercial) within a single layout
Ensure compatibility between SALESFORCE and AETNA'S AI TOOLS
Work around UNCERTAIN OR INCOMPLETE REQUIREMENTS from PWC
Needed to prioritize OUT-OF-THE-BOX (OOTB) COMPONENTS to reduce implementation complexity and stay within budget
the team
THE TEAM + WORKING MODEL
This was a multi-organization effort involving Salesforce, PwC, and CVS-Aetna. Salesforce and PwC partnered on experience design: PwC led research and stakeholder engagement, while Salesforce led design execution and UX strategy. Because research was shared with us as summaries, I had limited direct access to users and session recordings. Requirements also evolved as client feedback came in, so I worked in short cycles and kept our assumptions visible. I partnered closely with Kevin H., our Senior Experience Architect, to co-lead working sessions, alternating between presenting and capturing notes so nothing critical was missed.
MY ROLE, MY CONTRIBUTION
role.
Senior Experience Consultant
As the Senior Experience Consultant, I served as the lead designer for key components of the Customer360 platform. I was responsible for shaping the interaction strategy, producing user flows and wireframes, and translating the shared vision into tangible artifacts—despite shifting priorities and limited access to end users.
Working in tandem with my Senior Experience Architect (shoutout to Kevin H.), we divided our focus to move the work forward collaboratively:
-
Kevin focused on aligning with the business, facilitating co-creation sessions, and defining the future-state experience.
-
I translated those strategic insights into feature-level design outputs, co-creating deliverables that supported both vision alignment and execution.
my tasks and responsibilities.
Customer360 Screen Design
Led UX for the Customer360 layout, including Claims, Assessments, Quick Access, Alerts, and the Left/Right rail. Proposed a modular layout system adaptable across LOBs (Medicare, Medicaid, Commercial).
Experience Cloud Concepting
Designed concepts for dashboards, support portals, and admin tools within Salesforce Experience Cloud, aligning each with team roles and content accessibility needs.
Flow + Feature Design
Mapped capabilities across the platform, developed user flows, and validated feature requirements to ensure each element supported user needs and business priorities.
Experience Narrative + Key Wireframes
Delivered high-level wireframes and helped define the experience narrative to guide development teams through intended interactions and cross-functional dependencies.
Collaboration with Salesforce + PWC
Worked closely with Kevin H. to adapt our workflow to communication gaps between PWC and the client. We co-led design sessions, split note-taking and presentation duties, and continuously refined designs based on shifting direction.
Final Design Presentation
Presented the final set of mockups and UX recommendations to the broader stakeholder team, aligning on near-term solutions before the project was paused.
research + discovery
PwC led the initial research and stakeholder conversations and shared summaries with the Salesforce team. Since I didn’t have direct access to users or recordings, I made the assumptions behind my designs explicit and used working sessions to confirm them with stakeholders. As client priorities evolved, I adjusted the designs and documented what changed and why. To fill gaps in my understanding, I also referenced UI patterns from comparable healthcare organizations, like BCBS California, to guide structure and hierarchy.

process
The team used an agile-inspired, working-session-driven model with each phase focused on rethinking a specific section of the Customer360 UI—from page structure and alerts to AI integration and quick link filtering. Communication dynamics required adaptive workflows as Salesforce responded to evolving needs filtered through PWC.
stakeholder interviews
reference design audits
discover
define
wireflows
hierarchy mapping
design critiques
ideate
mid-fi mockups
whiteboarding
iterative visual exploration
prototype
hi-fi screen sconcepts
design critiques
usability testing
UAT testing
test
dev handoff
launch support
implement
feedback integration
Not reached - project was paused
FROM STRATEGY TO SCREENS
DESIGN ARTIFACTS: Flows, Features & Field Mapping
To translate business needs into actionable experiences, we started by identifying key capabilities and mapping them across the user journey. One of the early reference materials we received was a feature matrix shared by the team. To move things forward—especially where documentation was incomplete—I used ChatGPT to help group and name required fields, surfacing common patterns based on healthcare workflows. This approach helped structure our initial conversations and allowed us to accelerate the design of user flows, data inputs, and task paths across different LOBs.



Requirement Matrix. A snapshot of the requirements matrix shared with the team—just a small sample of the 350+ items that guided functionality, layout, and user interactions across the Customer360 experience.

Desired Customer360 Fields. An early draft of the key data fields prioritized for the Customer360 view. These fields informed the tab structure and layout strategy, helping organize complex information by user need and business context.
ChatGPT Collaboration. With a 350+ item requirements matrix and incomplete documentation, I needed a faster route to a first draft. I used ChatGPT as a drafting aid to propose groupings and names for the Customer360 fields, giving it field labels only, with no member data.
I treated the output as a starting hypothesis: I edited the groupings against the feature matrix and typical healthcare workflows, then validated them with business stakeholders who represented the care operations team in working sessions. Their feedback led us to rename the sections to match the terminology their team already used, so the structure reflected how they actually talked about the work. The validated structure became the tab and layout strategy for the Customer360 view.


VISUALS
.png)
Envision Phase Demo. This screenshot from the Envision phase showcased a highly customized version of the Customer360 experience—used to help secure client buy-in. As the project moved into delivery, we needed to reset expectations around what could be achieved using out-of-the-box (OOTB) Salesforce components. Our approach included side-by-side comparisons of OOTB vs. custom options to highlight trade-offs and empower the CVS-Aetna team to make informed decisions based on value and effort.
OOTB
CUSTOM
LOW EFFORT
HIGH EFFORT



Exploring ID Card Display Options. Aetna expressed interest in displaying a member’s insurance ID card within the Customer360 view. We explored three potential solutions—ranging from OOTB flex cards to a fully custom module that would show a front-and-back image of the actual card. Our goal was to clarify the “why” behind the request: if the information was most important, a simpler nested flex card (Option 2) could meet the need without major impact to budget. If visual fidelity was critical, a custom module (Option 3) would be required. This conversation helped frame trade-offs and ensure the solution aligned with both purpose and feasibility.




Right-rail placement (left) and Center placement (right). Aetna-CVS AI Tools (Smart Care, Care Gaps, and Care Considerations) would be featured in a tab-component, with alert icon so care team members would interact. For the center placement, we also looked at featuring Aetna-CVS's tools in their own tables, stacked.
AI Integration Exploration. Both Salesforce and Aetna-CVS leveraged AI to support care teams in making informed, next-best-action decisions. As part of our work, we explored how these tools could co-exist within the platform. We looked at placement options: the center column for visibility versus the right rail for contextual support. These discussions helped guide decisions around prioritization, user focus, and scalability.

Annotated Member360 Mockup. A detailed mockup of the proposed Member360 experience, complete with annotations highlighting layout structure, key components, and feature behavior. This version was presented during what became our final team session with Aetna-CVS, used to align on priorities and gather feedback before the project was paused
PAIN POINTS + LESSONS LEARNED
limited access to user research
Research was led by a partner team and shared as summaries, so I had less direct visibility into user needs.
Made design assumptions explicit, validated them in working sessions with Kevin H. and client stakeholders, and used visual mockups to align everyone on what we were deciding
ui design for multiple LOBs
A single Customer360 layout had to flex to accommodate Medicare, Medicaid, and Commercial use cases.
Developed modular UI components with dynamic fields, adaptable CTAs, and consistent visual structure per LOB.
real estate + layout tensions
Competing priorities led to crowded left/right rails, making it hard to surface high-priority info.
Proposed collapsing card groups, new alert placements, and CTA groupings modeled after BCBS California’s design.
ai integration complexity
Combining Aetna’s AI tools with Salesforce AI posed performance and resourcing concerns.
Proposed shared architecture for data models, prioritized MVP use cases, and suggested an OmniScript-based rollout.
overwhelming quick links
Hundreds of potential links made the experience cluttered and hard to maintain.
Designed a tabbed, filterable utility bar with optional categorization by department, frequency, or LOB.
out-of-the-box vs. customization gap
The client was shown highly customized Envision-phase mockups, but the actual build was scoped for out-of-the-box (OOTB) components due to budget and timeline constraints.
We clarified what was feasible within standard Salesforce components and designed modular solutions that could be incrementally customized—highlighting trade-offs and setting realistic expectations for phase-based delivery.

POST PROJECT IMPACT
Although the project was ultimately paused due to a re-evaluation of the CVS-Aetna and Salesforce contract, the work delivered during early phases created a strong blueprint for future iterations. From modular screen concepts to AI tool integrations and scalable quick link design, this effort highlighted the value of collaborative problem-solving—even amid unclear priorities. The insights and artifacts from this phase remain valuable for any future Customer360 redesign focused on multi-LOB alignment, streamlined workflows, and patient-centered data visibility.



