Design System ownership
- Role
- Sr. Product Designer / Design System Owner
- Core activities
- Design SystemGovernanceStorybook
- Period
- 2021-2024
- Product Tags
- ScomplerGovernanceDesign System
Context
Scompler is a complex B2B SaaS product used by enterprise marketing and content teams to plan, create, publish and analyze multi-channel content. The product had multiple modules and workflows, but no unified design foundation across planning, collaboration, editorial execution and reporting.
Product Landscape
Scompler / 2021-2024
Design System ownership connected product strategy, user workflows and implementation constraints. The work needed to support the immediate feature scope while leaving the product easier to extend.
Design system governance and SSOT for a complex B2B SaaS platform.
- Design System scope
- Governance scope
- Storybook scope
- SaaS scope
Challenges
The work started with a set of product, workflow and system constraints that had to be resolved without slowing delivery.
- Fragmented UI patterns across product modules created inconsistency and rework.
- Design and frontend delivery were slowed by repeated interpretation and unclear handoff.
- The product needed a shared language across Figma, Storybook and Confluence.
- Legacy UI had to be migrated gradually without blocking feature delivery.
Approach
Design process
I translated the product problem into reusable UX structures, validated the direction with stakeholders and prepared implementation-ready design specifications.
- Built the system from tokens upward: typography, color, spacing, iconography, shadows and semantic states.
- Created core components such as buttons, inputs, switches, chips, accordions, dropdowns, avatars and pickers.
- Defined product patterns for navigation, forms, search, modals, tables, filters and empty states.
- Aligned Figma, Storybook and Confluence as a single source of truth for design and engineering.
Outcome
The result was a clearer product experience, stronger delivery alignment and a more scalable foundation for future work.
- Reduced design and frontend delivery time by roughly 35-40%.
- Established a reusable library of 200+ UI components and patterns.
- Reduced design-development friction through clearer specifications and governance.
- Made the design system the default path for all new feature work.
200+
UI components and patterns
35-40%
Faster design and frontend delivery
3
Linked sources of truth
Reflection
General experience
Good system work is less about perfect component inventory and more about creating repeatable agreement between product, design, and engineering.
The most useful artifacts were the ones teams could apply immediately in delivery: decision rules, naming conventions, reusable states, and practical examples.
Featured Projects
My product design cases from the last few years.
