StepOasis (3stepIT) serves as the primary case for this study. It is a Nordic B2B technology company focused on sustainable IT lifecycle services. I led the design efforts for their internal service ecosystem, building a shared component library that would support multiple applications and stakeholders.
In addition to StepOasis, this study includes insights from:
Elisa CUP, a telecommunications cloud automation portal that required a UI kit derived from a Elisa's central design system.
Veikkaus, Finland’s state-run gambling company, where design system governance and token-based scalability were central themes.
For StepOasis, I led the full design system build as part of the internal product development lifecycle. Responsibilities included:
Atomic design structuring
Component design and testing
Token setup
Component hierarchy planning
Designer–developer handoff workflow
Governance process mapping
The system was integrated into Figma, and I collaborated with internal developers to test its use in real production features. This also allowed me to validate how design decisions translated into frontend architecture.
For Elisa CUP, I built a tailored UI kit themed from an existing master system. I ensured it could support the cloud automation product’s unique workflow needs while maintaining visual cohesion and implementation speed.
At Veikkaus, I worked as a product designer in an environment where the design system was a core part of the development process. While I wasn’t responsible for building the system, I gained hands-on experience working within a mature enterprise-level design system, understanding its governance model, token structure, and how it integrates into large-scale development pipelines.
Estimated €120,000 saved through reusable components, reducing the need for custom-coded UI in new products.
Coding a single reusable component took ~2 weeks but eliminated 5–6 months of equivalent engineering time across multiple services.
Increased cross-team efficiency by creating shared components used by design, development, and product teams.
Accelerated the onboarding of new products into the platform by establishing scalable, documented design patterns.
Developer handoff time decreased by ~30% post system integration
Reduced visual QA feedback cycles significantly across all teams
Documented governance improved team clarity in design ownership
Component reuse across multiple teams and products increased dramatically, streamlining design delivery and reducing inconsistencies. Developer handoff time decreased by ~30% post system integration.
A system is only as good as its governance — poor structure leads to bottlenecks and visual drift.
Embedding design system thinking directly into real product work accelerates adoption.
Token-driven thinking unlocks scalable design, but only when responsibilities are clearly defined.
Don’t build a design system for its own sake. Build it within the product development context — let real-world usage drive structure and priorities.