After Tyler acquired Socrata, multiple component libraries and product conventions were solving similar problems in different ways. Customers experienced inconsistency; teams repeated decisions and implementation work.
02 / DESIGN SYSTEM⌄
02 / DESIGN SYSTEM
TYLER FORGE
A shared design language and governance model for a growing family of civic technology products.

We audited the existing libraries and interfaces, compared Socrata and Tyler patterns, and used an offsite design sprint to expose where visual differences reflected real product needs—and where they were simply organizational history.
Unify the systems around shared principles and patterns, then make governance part of the product. The goal was not a perfect library; it was a dependable way for teams to make coherent decisions together.
I partnered with Tyler’s Corporate UX Director and designers across divisions to facilitate the audit, share the findings, generate the system direction, and establish cross-division ownership.
The work produced the foundation for an online system and a governance practice that could evolve across product lines. We will add adoption evidence when the corresponding artifacts are assembled.
A design system succeeds when teams can make better decisions with it—not simply when the library is complete.
The story is in place. These are the most useful original artifacts to bring in next.
AUDIT
A representative component-library comparison or interface inventory.
ONE PATTERN
The anatomy and rationale of a pattern that became part of Forge.
ADOPTION
A simple timeline showing how teams contributed to and began using the system.