THE CHALLENGE
Inconsistent experiences and duplication across multiple applications
The Source to Pay suite comprised multiple enterprise procurement applications that had been built independently over time. Each application had its own design patterns, interaction models and visual language — creating a fragmented experience for users who worked across all of them.
The result was high training overhead, frequent user errors at workflow boundaries, and a codebase with significant duplication.
THE APPROACH
Standards accelerate delivery
The decision to adopt IBM Carbon as the foundational design system provided a common vocabulary, but the real work was in mapping existing patterns to Carbon components and establishing how teams would adopt and contribute to the system.
Key Insight: A design system without an adoption strategy is just a Figma library. The governance model that wraps it is what determines whether it actually gets used.
What I Built
Adoption roadmap mapping existing components to IBM Carbon equivalents
Reusable enterprise UX patterns specific to procurement workflows
Contribution model enabling teams to extend Carbon within guardrails
Design review cadence reducing duplicated decision making across teams
Cross-team governance forum establishing shared standards
Consistent UX across products
Reusable Patterns: Consistent components and patterns across the entire suite
Faster Delivery: Reduced development cycles by removing repeated design work
User Satisfaction: Improved user satisfaction across the procurement workflow
Built strong partnerships with Product Owners, enabling design recommendations to influence architectural and engineering decisions throughout delivery.
Established shared UX standards that improved consistency, simplified implementation, and created a common design language across the platform.
