All case studies

IBM Partner Portal ยท Carbon for Salesforce

Scaling IBM's design system into Salesforce.

As partner workflows moved into the Partner Portal on Salesforce, the same governed Carbon experience had to exist there too. Carbon for Salesforce (C4S) is the reusable library of Lightning Web Components that made it possible.

Role
Product manager and design leader
Platform
Salesforce, Lightning Web Components
Worked with
Engineering, 23 product squads, executive stakeholders
Line illustration of interface components, from carousels and toggles to a calendar, surrounding a browser window

Results

117Components delivered
23Squads building with C4S
40Releases
1.4KWeekly Figma component inserts at peak

Squads were shipping with C4S within two months of the team forming.

The challenge

Product teams couldn't reliably reuse Carbon components in Salesforce, so they rebuilt UI patterns with local variations. Prototypes and production drifted apart, and common patterns like forms, tables, modals, and empty states were solved, reviewed, and reworked again and again.

Without a shared system, governance broke down and consistency between IBM brand-approved domains and the partner experience couldn't scale across a growing Salesforce footprint.

What we learned

The team audited existing Partner Portal UI patterns, worked through LWC, Shadow DOM, and security constraints with engineering, and checked which components teams needed first to ship.

  • The system had to standardize markup, styles, and behavior, not just visuals.
  • Carbon's React-based components couldn't be dropped into Salesforce as-is.
  • Partner workflows needed components beyond baseline Carbon.

The approach

We translated Carbon into Lightning Web Components with shared component contracts, so prototype and production behaved the same. Usage guidance lived in Storybook and updated straight from Figma, and squad requests were tracked openly in Jira and a shared Airtable dashboard.

  1. Carbon to LWC translation
  2. Token-driven theming instead of one-off overrides
  3. Partner extensions built as first-class components
  4. Documentation and contribution paths so teams could move incrementally

My role

  • Set the roadmap and prioritized which components to port first based on partner workflow demand
  • Partnered with engineering to make Carbon patterns work within Shadow DOM and Salesforce security limits
  • Set the bar for when Carbon should be extended for partner needs instead of worked around
Next case studyTurning navigation into a guided path