Sometimes a design system is only as strong as it’s weakest implementation.
My company had a problem versioning for our design library - it was initially built in a language that many of our developers couldn’t consume or implement. Someone else stepped up to the plate of making a comparable version in a language the developers could consume, but lost many of the important details (and intentions of use) of the original elements in the process.
I ran into this problem when I worked with a team that implemented our design system in a wonky, incorrect way, and to combat that I decided to audit the comparable system and note the differences in excruciating detail.
Watch me narrate a video explaining the correct usage cases for a design system element below.