A design system
for healthcare
2023
DAVINCI SALUTE
DESKTOP APP
PRODUCT DESIGN
DESIGN SYSTEM

ABOUT
DaVinci Salute is an Italian HealthTech company that specializes in telemedicine and the digitalization of local medicine. In 2022 Unipol Group, one of Italy 's largest publicly traded companies, acquired a 66% stake. This acquisition provided financial backing and the opportunity to build a Design System.
THE OUTCOME
Boosted Efficiency, Saved Costs
The goal of the project was to scale up the company’s main product: a management tool that facilitates the daily activities of doctors and healthcare professionals. Given the small team and limited time, we decided not to reinvent the wheel but to refine the existing UI and make general adjustments. This approach led to a significant reduction in bugs and errors, enhancing overall quality and saving operational costs.
Average time spent on bugs per sprint, in a team of 10 developers.
Number of errors per session per week, measured with Sentry.
MY ROLE
As
the
only
internal
designer
involved
in
the
project,
I
collaborated
with
to
establish
a
structure,
a
language,
and
a
process
for
the
design
system,
as
well
as
its
ongoing
maintenance.
This
collaboration
was
essential
given
the
complexity
of
the
task.
AUDIT
Time to Sit at the Table
Collect everything
To gain a better understanding of the product's state, we run a design audit. Our process started by examining all product flows and capturing hundreds of screenshots, which were organized in a Figma file, linking pages to mirror user navigation, forming a visual map.
Visual mapping
This visual map simplified our auditing process and guided our design decisions, ensuring thorough coverage and effective assessment of component reusability and flexibility.
FOUNDATION
Let’s Bring Some Order to the Chaos
Set the rules
To establish a solid foundation, we relied on data from our audit and team feedback. Collaborating with Belka and using the Tailwind framework as a starting point, we designed rules for typography, color palette, icons, layout, and tokens.
And apply to components
Starting from the existing library and applying the new foundation, we redesigned and tested the components alongside developers, enabling faster adjustments and iterative improvements. We also added some magic by using Figma’s new variables feature.
Neat and Tidy
We reorganized our Figma files by creating a structure in which the foundation serves as the single source of truth, with all other files connected to it. Each file is separated by scope and published only in its specific workspace, ensuring consistency and preventing cross-file interference.
The Perfect Formula
The documentation was made directly in Figma using the components themselves along with a couple of plugins. This method enabled us to scale the process easily and avoid recreating complex UIs each time.
Ask To The Team
We ran a Slack channel dedicated to the design system where the team could quickly discuss ideas, share progress updates, and get responses to any questions or needs. This space helped keep everyone on the same page, as we worked to improve and expand the project.
Neat and Tidy
We reorganized our Figma files by creating a structure in which the foundation serves as the single source of truth, with all other files connected to it. Each file is separated by scope and published only in its specific workspace, ensuring consistency and preventing cross-file interference.
The Perfect Formula
The documentation was made directly in Figma using the components themselves along with a couple of plugins. This method enabled us to scale the process easily and avoid recreating complex UIs each time.
Ask To The Team
We ran a Slack channel dedicated to the design system where the team could quickly discuss ideas, share progress updates, and get responses to any questions or needs. This space helped keep everyone on the same page, as we worked to improve and expand the project.
Spread the Word
As the project grew, I shared tutorial videos in a dedicated Google Drive folder, accessible to everyone in the company. These videos not only supported component development but also served as a future reference, ensuring that essential knowledge would endure over time.

This wasn’t a perfect project, and we faced many challenges. When working on a design system, it's easy to aspire to emulate giants like Google, but trying to mirror their steps on the first attempt often leads to failure. I learned that focusing on tangible value over unnecessary features is what truly drives progress. Starting small and knowing when something was 'good enough' helped us keep momentum, address real needs, and avoid overextending in the initial stages.

Next Project
WELBEE
Redesigning Unipol's Welfare Experience
Revamping Welbee’s HR platform to secure major clients like BPER and Coop.
© 2025 Gianluca Croci
A design system
for healthcare
2023
DAVINCI SALUTE
DESKTOP APP
PRODUCT DESIGN
DESIGN SYSTEM

ABOUT
DaVinci Salute is an Italian HealthTech company that specializes in telemedicine and the digitalization of local medicine. In 2022 Unipol Group, one of Italy 's largest publicly traded companies, acquired a 66% stake. This acquisition provided financial backing and the opportunity to build a Design System.
THE OUTCOME
Boosted Efficiency, Saved Costs
The goal of the project was to scale up the company’s main product: a management tool that facilitates the daily activities of doctors and healthcare professionals. Given the small team and limited time, we decided not to reinvent the wheel but to refine the existing UI and make general adjustments. This approach led to a significant reduction in bugs and errors, enhancing overall quality and saving operational costs.
Average time spent on bugs per sprint, in a team of 10 developers.
Number of errors per session per week, measured with Sentry.
MY ROLE
As
the
only
internal
designer
involved
in
the
project,
I
collaborated
with
to
establish
a
structure,
a
language,
and
a
process
for
the
design
system,
as
well
as
its
ongoing
maintenance.
This
collaboration
was
essential
given
the
complexity
of
the
task.
AUDIT
Time to Sit at the Table
Collect everything
To gain a better understanding of the product's state, we run a design audit. Our process started by examining all product flows and capturing hundreds of screenshots, which were organized in a Figma file, linking pages to mirror user navigation, forming a visual map.
Visual mapping
This visual map simplified our auditing process and guided our design decisions, ensuring thorough coverage and effective assessment of component reusability and flexibility.
FOUNDATION
Let’s Bring Some Order to the Chaos
Set the rules
To establish a solid foundation, we relied on data from our audit and team feedback. Collaborating with Belka and using the Tailwind framework as a starting point, we designed rules for typography, color palette, icons, layout, and tokens.
And apply to components
Starting from the existing library and applying the new foundation, we redesigned and tested the components alongside developers, enabling faster adjustments and iterative improvements. We also added some magic by using Figma’s new variables feature.
Neat and Tidy
We reorganized our Figma files by creating a structure in which the foundation serves as the single source of truth, with all other files connected to it. Each file is separated by scope and published only in its specific workspace, ensuring consistency and preventing cross-file interference.
The Perfect Formula
The documentation was made directly in Figma using the components themselves along with a couple of plugins. This method enabled us to scale the process easily and avoid recreating complex UIs each time.
Ask To The Team
We ran a Slack channel dedicated to the design system where the team could quickly discuss ideas, share progress updates, and get responses to any questions or needs. This space helped keep everyone on the same page, as we worked to improve and expand the project.
Neat and Tidy
We reorganized our Figma files by creating a structure in which the foundation serves as the single source of truth, with all other files connected to it. Each file is separated by scope and published only in its specific workspace, ensuring consistency and preventing cross-file interference.
The Perfect Formula
The documentation was made directly in Figma using the components themselves along with a couple of plugins. This method enabled us to scale the process easily and avoid recreating complex UIs each time.
Ask To The Team
We ran a Slack channel dedicated to the design system where the team could quickly discuss ideas, share progress updates, and get responses to any questions or needs. This space helped keep everyone on the same page, as we worked to improve and expand the project.
Spread the Word
As the project grew, I shared tutorial videos in a dedicated Google Drive folder, accessible to everyone in the company. These videos not only supported component development but also served as a future reference, ensuring that essential knowledge would endure over time.

This wasn’t a perfect project, and we faced many challenges. When working on a design system, it's easy to aspire to emulate giants like Google, but trying to mirror their steps on the first attempt often leads to failure. I learned that focusing on tangible value over unnecessary features is what truly drives progress. Starting small and knowing when something was 'good enough' helped us keep momentum, address real needs, and avoid overextending in the initial stages.

Next Project
WELBEE
Redesigning Unipol's Welfare Experience
Revamping Welbee’s HR platform to secure major clients like BPER and Coop.
© 2025 Gianluca Croci
A design system
for healthcare
2023
DAVINCI SALUTE
DESKTOP APP
PRODUCT DESIGN
DESIGN SYSTEM

ABOUT
DaVinci Salute is an Italian HealthTech company that specializes in telemedicine and the digitalization of local medicine. In 2022 Unipol Group, one of Italy 's largest publicly traded companies, acquired a 66% stake. This acquisition provided financial backing and the opportunity to build a Design System.
THE OUTCOME
Boosted Efficiency, Saved Costs
The goal of the project was to scale up the company’s main product: a management tool that facilitates the daily activities of doctors and healthcare professionals. Given the small team and limited time, we decided not to reinvent the wheel but to refine the existing UI and make general adjustments. This approach led to a significant reduction in bugs and errors, enhancing overall quality and saving operational costs.
Average time spent on bugs per sprint, in a team of 10 developers.
Number of errors per session per week, measured with Sentry.
MY ROLE
As
the
only
internal
designer
involved
in
the
project,
I
collaborated
with
to
establish
a
structure,
a
language,
and
a
process
for
the
design
system,
as
well
as
its
ongoing
maintenance.
This
collaboration
was
essential
given
the
complexity
of
the
task.
AUDIT
Time to Sit at the Table
Collect everything
To gain a better understanding of the product's state, we run a design audit. Our process started by examining all product flows and capturing hundreds of screenshots, which were organized in a Figma file, linking pages to mirror user navigation, forming a visual map.
Visual mapping
This visual map simplified our auditing process and guided our design decisions, ensuring thorough coverage and effective assessment of component reusability and flexibility.
FOUNDATION
Let’s Bring Some Order to the Chaos
Set the rules
To establish a solid foundation, we relied on data from our audit and team feedback. Collaborating with Belka and using the Tailwind framework as a starting point, we designed rules for typography, color palette, icons, layout, and tokens.
And apply to components
Starting from the existing library and applying the new foundation, we redesigned and tested the components alongside developers, enabling faster adjustments and iterative improvements. We also added some magic by using Figma’s new variables feature.
Neat and Tidy
We reorganized our Figma files by creating a structure in which the foundation serves as the single source of truth, with all other files connected to it. Each file is separated by scope and published only in its specific workspace, ensuring consistency and preventing cross-file interference.
The Perfect Formula
The documentation was made directly in Figma using the components themselves along with a couple of plugins. This method enabled us to scale the process easily and avoid recreating complex UIs each time.
Ask To The Team
We ran a Slack channel dedicated to the design system where the team could quickly discuss ideas, share progress updates, and get responses to any questions or needs. This space helped keep everyone on the same page, as we worked to improve and expand the project.
Neat and Tidy
We reorganized our Figma files by creating a structure in which the foundation serves as the single source of truth, with all other files connected to it. Each file is separated by scope and published only in its specific workspace, ensuring consistency and preventing cross-file interference.
The Perfect Formula
The documentation was made directly in Figma using the components themselves along with a couple of plugins. This method enabled us to scale the process easily and avoid recreating complex UIs each time.
Ask To The Team
We ran a Slack channel dedicated to the design system where the team could quickly discuss ideas, share progress updates, and get responses to any questions or needs. This space helped keep everyone on the same page, as we worked to improve and expand the project.
Spread the Word
As the project grew, I shared tutorial videos in a dedicated Google Drive folder, accessible to everyone in the company. These videos not only supported component development but also served as a future reference, ensuring that essential knowledge would endure over time.

This wasn’t a perfect project, and we faced many challenges. When working on a design system, it's easy to aspire to emulate giants like Google, but trying to mirror their steps on the first attempt often leads to failure. I learned that focusing on tangible value over unnecessary features is what truly drives progress. Starting small and knowing when something was 'good enough' helped us keep momentum, address real needs, and avoid overextending in the initial stages.

Next Project
WELBEE
Redesigning Unipol's Welfare Experience
Revamping Welbee’s HR platform to secure major clients like BPER and Coop.
© 2025 Gianluca Croci
A design system
for healthcare
2023
DAVINCI SALUTE
DESKTOP APP
PRODUCT DESIGN
DESIGN SYSTEM

ABOUT
DaVinci Salute is an Italian HealthTech company that specializes in telemedicine and the digitalization of local medicine. In 2022 Unipol Group, one of Italy 's largest publicly traded companies, acquired a 66% stake. This acquisition provided financial backing and the opportunity to build a Design System.
THE OUTCOME
Boosted Efficiency, Saved Costs
The goal of the project was to scale up the company’s main product: a management tool that facilitates the daily activities of doctors and healthcare professionals. Given the small team and limited time, we decided not to reinvent the wheel but to refine the existing UI and make general adjustments. This approach led to a significant reduction in bugs and errors, enhancing overall quality and saving operational costs.
Average time spent on bugs per sprint, in a team of 10 developers.
Number of errors per session per week, measured with Sentry.
MY ROLE
As
the
only
internal
designer
involved
in
the
project,
I
collaborated
with
to
establish
a
structure,
a
language,
and
a
process
for
the
design
system,
as
well
as
its
ongoing
maintenance.
This
collaboration
was
essential
given
the
complexity
of
the
task.
AUDIT
Time to Sit at the Table
Collect everything
To gain a better understanding of the product's state, we run a design audit. Our process started by examining all product flows and capturing hundreds of screenshots, which were organized in a Figma file, linking pages to mirror user navigation, forming a visual map.
Visual mapping
This visual map simplified our auditing process and guided our design decisions, ensuring thorough coverage and effective assessment of component reusability and flexibility.
FOUNDATION
Let’s Bring Some Order to the Chaos
Set the rules
To establish a solid foundation, we relied on data from our audit and team feedback. Collaborating with Belka and using the Tailwind framework as a starting point, we designed rules for typography, color palette, icons, layout, and tokens.
And apply to components
Starting from the existing library and applying the new foundation, we redesigned and tested the components alongside developers, enabling faster adjustments and iterative improvements. We also added some magic by using Figma’s new variables feature.
Neat and Tidy
We reorganized our Figma files by creating a structure in which the foundation serves as the single source of truth, with all other files connected to it. Each file is separated by scope and published only in its specific workspace, ensuring consistency and preventing cross-file interference.
The Perfect Formula
The documentation was made directly in Figma using the components themselves along with a couple of plugins. This method enabled us to scale the process easily and avoid recreating complex UIs each time.
Ask To The Team
We ran a Slack channel dedicated to the design system where the team could quickly discuss ideas, share progress updates, and get responses to any questions or needs. This space helped keep everyone on the same page, as we worked to improve and expand the project.
Neat and Tidy
We reorganized our Figma files by creating a structure in which the foundation serves as the single source of truth, with all other files connected to it. Each file is separated by scope and published only in its specific workspace, ensuring consistency and preventing cross-file interference.
The Perfect Formula
The documentation was made directly in Figma using the components themselves along with a couple of plugins. This method enabled us to scale the process easily and avoid recreating complex UIs each time.
Ask To The Team
We ran a Slack channel dedicated to the design system where the team could quickly discuss ideas, share progress updates, and get responses to any questions or needs. This space helped keep everyone on the same page, as we worked to improve and expand the project.
Spread the Word
As the project grew, I shared tutorial videos in a dedicated Google Drive folder, accessible to everyone in the company. These videos not only supported component development but also served as a future reference, ensuring that essential knowledge would endure over time.

This wasn’t a perfect project, and we faced many challenges. When working on a design system, it's easy to aspire to emulate giants like Google, but trying to mirror their steps on the first attempt often leads to failure. I learned that focusing on tangible value over unnecessary features is what truly drives progress. Starting small and knowing when something was 'good enough' helped us keep momentum, address real needs, and avoid overextending in the initial stages.

Next Project
WELBEE
Redesigning Unipol's Welfare Experience
Revamping Welbee’s HR platform to secure major clients like BPER and Coop.
© 2025 Gianluca Croci