Are pattern libraries too restricting?

In the last month or so, a few people have asked me this question. I always answer with a counterquestion: “Isn’t that one of the reasons we create them?”

Maybe you feel that a strict pattern library is killing your creativity. It forces you into using some patterns defined what seems likes ages ago. It ties you up and consumes space that could be used for doing things in a new way. All this can be true. But restrictions aren’t generally a bad thing.

Restrictions shouldn’t scare us. Sometimes the issue can be attributed to our own laziness. We ignore the rules because it’s so much easier to build something without being constrained by them. Try to fight this laziness and work with restrictions instead of resisting them. After all, it can improve the whole pattern library.

“True creativity comes from restriction and limitation.” (Paul Schrader)

Don’t call them restrictions

Start with that. Words have power. View these restrictions more as guidance. It can be this simple to alter your mindset. It may take time, but after a few weeks, you’ll see the difference. Not only in your own attitude, but those of your colleagues too.

When you need to solve a new problem and you have a pattern library, it’s a huge advantage. Adjust your thought process based around the pattern library. You don’t always need to look for a new tool. You don’t need to think again about basics as colors, typography or buttons. You just grab some existing components and use them. It will speed up your process immensely. Your wireframes won’t be gray and ugly anymore, but as beautiful as your final product.

Have a clear structure

The structure is key. You need to be able to utilise any component within a few seconds. If an element isn’t easily accessible, you won’t use it because it’s too complicated. Trust me, I’ve been there.

Create a solid design system for all the basics — colors, typography, layout and so on. Take your time in defining principles for various combinations of all these components. If you feel it’s necessary, add examples. It has to be 100% clear what you can and can’t combine.

Be careful with changes

I’ve seen libraries where components were like diamonds. Beautiful. Polished. And untouchable. After a period of time, many of these diamonds lost their value. And we didn’t do anything about it.

The living library doesn’t mean just fixing bugs or expanding it to include new components. Don’t be afraid to question old solutions. If you find a better solution to an old component, rewrite it to this better one. Your goal is to create the best solution possible. If you need to change the structure because your team has different needs than before, work on that and change it.

A word of warning however: be very careful with this. Even a small change should respect the rules. It should be compatible with existing components. This is the main reason why you should have a solid design system behind the pattern library. This is what is going to guide you.