Case Study 01 • Platform Migration & Governance

Enterprise Sitecore Migration & Structured Content System

Leading UX architecture, component governance, and cross-functional delivery across tens of thousands of pages—enabling engineers, vendors, and content teams to scale without duplicating work or sacrificing accessibility.

Organization
Johns Hopkins Medicine
Leadership Scope
UX, IA, Governance & Production Delivery
Teams Directed
Engineers, Digital Tech Specialists, Vendors & 45+ Editors
Key Outcomes
50+ Standards • Zero Duplicate Entry • Org-Wide Adoption

01 / Business Context & The Enterprise Challenge

Migrating an enterprise health system website spanning tens of thousands of pages is never just a technical lift—it is an operational transformation. Over years of decentralized publishing, generic CMS styles had accumulated. Editors were applying visual formatting like quote blocks for general layout, creating underlying HTML markup errors and accessibility risks.

At the same time, content teams were manually recreating the same clinical and editorial information across multiple pages—once for a landing-page callout, again for a category directory, and a third time for a detail page. Leadership needed a scalable Sitecore architecture that protected brand consistency, met strict accessibility standards, and worked for hundreds of non-technical contributors.

02 / Negotiating Constraints & Cross-Functional Alignment

My role extended far beyond wireframing templates. I operated as the bridge between user/editorial needs, vendor implementation, and internal engineering realities:

ENGINEERING ALIGNMENT

Working Through Technical Roadblocks

When software engineers initially pushed back on dynamic display rules as too complex for the CMS build, I walked through the field-level logic with them step by step—separating baseline required fields from optional add-ons so we met user needs within platform constraints.

PRODUCTION ORCHESTRATION

Defining Procedures Across Roles

I translated architectural decisions into concrete execution procedures—defining build specs for developers, configuration workflows for digital technology specialists, and structured publishing steps for content editors.

ACCESSIBILITY BY DEFAULT

Eliminating Markup Abuse

Instead of relying on editors to remember HTML rules, I replaced ambiguous styles with roughly a dozen purpose-built, device-agnostic modules that enforce semantic markup automatically upon input.

03 / System Architecture: Enter Once, Render Everywhere

Select a display context below to see how my structured content model takes a single CMS form entry and adapts it automatically across three levels of the site.

Interactive Architecture Model • Single Source of Truth

Editor Input (Done Once): Title, Short Summary, Specialty Tag, Clinical Image, and Full Body Copy.

[Rendered Thumbnail]
Auto-cropped 16:9
Featured Program

Comprehensive Heart Failure Center

Auto-pulled Summary Field: Multidisciplinary diagnosis and personalized treatment plans for complex cardiac conditions.

System Rule: Full body copy suppressed; Title + Summary + Image active.
A–Z CLINICAL SERVICES DIRECTORY

Comprehensive Heart Failure Center →

Multidisciplinary diagnosis and personalized treatment plans for complex cardiac conditions.

System Rule: Image suppressed for scannability; Title auto-links to Detail URL.
Heart & Vascular Institute / Programs

Comprehensive Heart Failure Center

Lead: Multidisciplinary diagnosis and personalized treatment plans for complex cardiac conditions.

Full Body & Optional Extensions: Renders complete clinical overview, care team modules, and optional condition-specific callouts without affecting upstream cards.

System Rule: All baseline + optional extension fields active.

04 / Governance, Enablement & Lasting Impact

A design system fails if the people maintaining it don't understand how to use it. To ensure quality survived long after initial launch, I led organization-wide enablement:

  • 50+ Component & Governance Standards: Authored comprehensive documentation detailing component use cases, build procedures, and UX rules adopted across the enterprise.
  • Live Training at Scale: Created hands-on CMS training guides and delivered live online enablement sessions to groups of up to 45 editors at a time.
  • Eliminated Duplicate Maintenance: Replaced manual copy-paste workflows across landing pages, directories, and detail pages with a single structured input model.
  • Sustainable Accessibility: Embedded WCAG-compliant markup directly into reusable modules so accessibility persisted across thousands of contributor edits.