Product Designer
Project Lead
Optum / UHG
Timeline
Nov 2024 - Feb 2025
Product Owners
Content Writer
Engineering Team
Healthcare
B2B
Internal Platform
Engineering Collaboration
CMS Integration
Wayfinding
Due to NDA restrictions, some details, visuals, and illustrations have been anonymized.
The Problem
Product Marketing pages were managed in a legacy admin system that was difficult to use, costly to maintain, and disconnected from the platform’s primary documentation and CMS.
What I did
Led the UX integration of Marketing Pages into the existing documentation platform and CMS, designing clear content structures and authoring workflows that aligned with established patterns and tight decommission timelines.
Impact
Successfully supported the decommissioning of a legacy CMS, reducing system fragmentation
Enabled product teams to manage marketing content in a single, centralized CMS
Improved content consistency and confidence in updating product information
Increased visibility of Marketing Pages by integrating them with a 14K+ MAU docs site
The Engineering Platform includes a documentation site and a centralized CMS used by product teams to manage content across the ecosystem. Product Marketing pages were previously managed in a separate, outdated admin system, making content difficult to update, inconsistent across surfaces, and costly to maintain.
I led the UX effort to integrate Marketing Pages into the existing documentation platform and CMS, creating a more unified, maintainable, and scalable content experience.
The legacy Admin CMS was difficult to use and discouraged content updates
Product Marketing pages were outdated, inconsistent, and hard to customize
Product information lived across multiple disconnected systems
Marketing Pages were not yet integrated into the platform’s primary CMS
This fragmentation increased maintenance cost and reduced content quality across the ecosystem.
Examples of the old Marketing Page layout and CMS
I led UX across the CMS, Marketing Page, and related navigation changes, including:
Auditing existing CMS and marketing workflows
Designing Marketing Page integration within the CMS dashboard
Defining content structure and page hierarchy within the documentation site
Creating low to high-fidelity prototypes
Partnering closely with PMs and engineers to meet decommission timelines
Supporting developers with detailed interaction and state designs
Reduced fragmentation by consolidating Marketing Pages into the documentation platform
Simplified page structure to support fast authoring and clear consumption
Early draft Marketing page wireframe ideas
Designed within existing CMS patterns to minimize dev effort and risk
Updated views for the new integration into the CMS
Validated direction through stakeholder and user feedback under tight constraints
Conducted multiple 1 on 1 user interviews and went over a high fidelity prototype and key navigational changes across the ecosystem with stakeholders and received very positive feedback
Enabled product owners to manage marketing content in a single, centralized location
Increased confidence and willingness among users to update product content
Increased visibility of Marketing Pages by integrating them with a 14K+ MAU docs site
A data mapping example showing CMS data tied to docs screens
The final solution:
Unified product marketing and documentation under one CMS
Reduced maintenance burden for product teams
Delivered a simpler, scalable Marketing Page template
Supported rapid development within strict timeline constraints
This work helped modernize how product information is managed and presented across a complex engineering ecosystem.
The final Docs Marketing page design
Global content impacts
Some CMS fields affected multiple surfaces across the ecosystem, creating risk for unintended changes:
I introduced warning and confirmation patterns to help users understand the downstream impact of their edits.
Dev tooling limitations
Engineering teams were not yet using Figma Dev Mode, leading to production inconsistencies post-release:
I provided explicit spacing, sizing, and state annotations to reduce ambiguity and rework.
Various edge cases I worked through with engineering
