How I led the creation of a scalable Design System at Safendty (with no prior experience)

How I led the creation of a scalable Design System at Safendty (with no prior experience)

How I led the creation of a scalable Design System at Safendty (with no prior experience)

Q2, 2023 | Design system

This case study is based on a real-life project; due to confidentiality, logos and exact designs are omitted, but the content reflects the process closely.

As the lead UX designer, I took on the ambitious task of unifying our 3 main platforms under one cohesive system while guiding a team of three

As the lead UX designer, I took on the ambitious task of unifying our 3 main platforms under one cohesive system while guiding a team of three

My role

My role

As the lead UX designer, I set a clear vision for the project, fostering alignment on expectations and workflows across the team. This collaborative effort resulted in a robust component library now powering our company's main platforms.

Project duration

Project duration

1/5 year

Team

Team

4 designer (including me)

Why was this important?

Inconsistency was costing Safendty both user trust and operational efficiency. Without a unified design system, each platform functioned in isolation, requiring redundant work

Inconsistency was costing Safendty both user trust and operational efficiency. Without a unified design system, each platform functioned in isolation, requiring redundant work

Project goals

1

Streamline workflows between design and development teams

Streamline workflows between design and development teams

2

Standardize user experience across platforms

Standardize user experience across platforms

3

Scalable design system that could be used in multiple platforms

Scalable design system that could be used in multiple platforms

Our process

Stakeholder buy-in: building trust early

Stakeholder buy-in: building trust early

Securing stakeholder support was essential. I delivered a thorough UX audit report, focusing on the current system’s gaps and inefficiencies, while presenting a vision for a unified design system that would improve both user and developer experiences.

What we did:

  • Presented findings and impact, framing the system as a long-term solution

  • Addressed concerns and aligned everyone on a common goal

We conducted a UX audit to assess what was working and what needed improvement across our platforms, ensuring informed decisions before implementing any changes

We conducted a UX audit to assess what was working and what needed improvement across our platforms, ensuring informed decisions before implementing any changes

Findings in categories:

1. Inconsistencies
2. Lack of affordance
3. Accessibility
4. Lack of visual dynamism
5. Redundancies

Findings in categories:

1. Inconsistencies
2. Lack of affordance
3. Accessibility
4. Lack of visual dynamism
5. Redundancies

Agile design: iterating for impact

Agile design: iterating for impact

Adopting agile sprints allowed the team to stay flexible and responsive. We worked in 2-week cycles, refining designs, gathering feedback, and ensuring each sprint moved us closer to a cohesive, scalable system.

Execution: bringing the system to life

Execution: bringing the system to life

Execution: bringing the system to life

Design Iterations:
Once the framework was established, we began iterative design cycles, gathering feedback from internal teams and stakeholders to align with business and user needs. Each round refined components and improved overall consistency.

Comprehensive Documentation:
Detailed style guides and component documentation were created to ensure clarity and scalability for future teams, making adoption seamless across the organization.

Design-Development Collaboration:
Real-time collaboration with developers ensured accurate implementation of components. Continuous feedback loops allowed for on-the-spot adjustments, refining the system as it was built.

Impact and learnings

Impact and learnings

Achieved a 40% reduction in design time by refactoring components and creating a centralized repository, enabling faster workflows.

Achieved a 40% reduction in design time by refactoring components and creating a centralized repository, enabling faster workflows.

Learnings

Learnings

  • Starting without experience is okay: A structured plan, proactive communication, and a willingness to learn on the job will make it easier.

  • Alignment is everything: Establishing clear principles, roles, and workflows early on ensures everyone is on the same page.

  • Documentation is a superpower: Clear, detailed documentation can bridge gaps, especially when resources are limited.

  • Stakeholder trust matters: Addressing concerns and demonstrating tangible benefits early in the process can turn stakeholders into strong allies.

  • Starting without experience is okay: A structured plan, proactive communication, and a willingness to learn on the job will make it easier.

  • Alignment is everything: Establishing clear principles, roles, and workflows early on ensures everyone is on the same page.

  • Documentation is a superpower: Clear, detailed documentation can bridge gaps, especially when resources are limited.

  • Stakeholder trust matters: Addressing concerns and demonstrating tangible benefits early in the process can turn stakeholders into strong allies.

Other cases studies

Ola

Ola

Bringing people closer through real-life language experiences

Read the full story

Safendty

From clutter to clarity: a complete platform overhaul for seamless API integration.

Read the full story

Let's create something meaningful

Let's create something meaningful

Whether you’re looking to revamp an experience or craft something from scratch, I’m here to collaborate and bring your vision to life.

Send me an email

Book a 15 mins call