Design Systems at Mitti (SafetyCulture)

Strategy / Architecture / Governance / Enablement / Advocacy

I’ve spent the last few years transforming SafetyCulture’s (now Mitti) design system from a set of borrowed brand styles and barebones code library to a fundamental, cross-platform piece of infrastructure. My north star for any design system is for teams to be able to make the right calls without me in the room.

Recently, I’ve broken down some systems and started again. Not because it failed, but because it wasn’t what we needed anymore. Today we have more consumers than ever — designers and engineers, but also product managers, go-to-market teams, and even people leaders. The strategy shifted from maturing the system to making it easy to produce the right thing, the first time. I’m currently looking at how we make systems deterministic enough so that AI generated output is compliant by default, rather than building up as design debt.

Dive in to some of the areas I’ve covered during my time:

Shipping systems as a one person team with a dream ➝

Designing for machines ➝

Killing a system on purpose ➝

Rebranding the whole platform through tokens ➝