A pattern library that people use

Every company I've worked at has had a design system. Most of them were graveyards: beautifully documented Figma libraries that engineers quietly worked around.

The adoption problem

A pattern library doesn't fail because the components are wrong. It fails because contributing back is harder than copying the code into your own folder. Friction is destiny.

What worked

• A two-line install. Anything longer and people fork.
• A 'pattern of the month' channel where someone demos a real use.
• Office hours, not tickets. The system team should be findable, not formal.
• Public contribution credits. Engineers ship patterns when they get named for it.

Treat adoption as the product

Components are the artifact. The product is the loop: someone hits a gap, files a pattern, gets it merged, ships their feature, and tells one other person. Build for that loop, not for the Storybook page.

"A design system is a community first and a library second."