Why would you want your teams to put work into and work with a design patterns library?
Design systems are such a trend right now. So hot right now. Design systems are not new though.
I am taking a little time out tonight to remind myself why we do design patterns.
First: What are design patterns?
Let’s break that down a little: What is a pattern? The Oxford English Dictionary states:
A regular and intelligible form or sequence discernible in the way in which something happens or is done.
Patterns are everywhere. Just look around you. Life is a collection of patterns on every level.
Designing is bringing structure to something. We design to bring structure to how a person interacts, with your product or service. Design is about that person’s experience. And a user’s experience is the result of a team’s work, not one person’s work.
In a web-based product or service, design should be the outcome of accumulative efforts of these functions/roles:
- Interaction design.
- Content design.
- The production means (on the web that is code and the tech required).
- Product management.
A design pattern is a record of a design. It’s a guide to elements of your design work. What might we record?
You are on a website and need to provide your name, address, and telephone number for something to be delivered to your home. How you provide your name is a pattern.
How have you filled in your name recently? Is it several boxes, one for
First nameand another for
Last name? Is it several boxes, one for
First nameand another for
Surname? Is it one box for
Your name? Was it something else? Did the form ask you to provide your gender? How? Was that actually important? What happened if you left a box empty? Did the page tell you? How did the page tell you? Did the box go a different colour? Was there a message telling you what you need to? How did it say it? Where was that message? Did the page reload before it told you this?
The pattern here is A person providing their name. Our design solution to that is what we record as a pattern.
So, a design pattern is not just a record of “how it looks”. Patterns note the interaction, the experience. They are not a thing just for “websites”.
More intriguingly, the dictionary continues with the following about “patterns”:
An example for others to follow.
Simply, that is the aim of design patterns. To be an example.
Patterns start small. We design something. We record what we have designed. And as we learn more, as improvement happens the design work evolves – and so does the pattern. The pattern recorded evolves.
By recording a design pattern we create a reference for the future to adopt, to adapt – for those continuing the work and others how may need to reference it.
So, what makes a good pattern? I think it is important to know what good looks like. For design patterns and their library to be useful they need some conditions, some acceptance criteria. I believe in the following being recorded:
- A name.
- An explanation of what the pattern: What does it do?
- An example – or better examples. Show the thing, either as screen grabs (static, animated GIFs, or video) and wherever possible link to the pattern in another library (say, a production library or a Github repo) and/or showing it “in the wild”.
- Context: How did the pattern come to be? What problem is it solving? Who is it designed to work for?
- Guidance for use: Say where it should be used, and where it could be used, and why. Are there any technical factors? (The most common is the differences between device screen sizer and the user’s input methods). Environmental factors, be they emotions, motivations, behaviours, should also be noted.
- Who has contributed: Often overlooked, but indicate contacts, either as teams or even the people who have worked on it.
- Status: Every pattern committed must come with a state of play: Whether a first pass used under duress or used in many places, having been tested and iterated over time to reach this current point. Preferably patterns will have been tested and revised at least once before entering the library. Also look ahead: What opportunities for learning are there with this pattern? How would you like it be tested further?
As design pattern represents the collective efforts of people’s thinking and making, that cross-discipline representation means design pattern libraries have the capability to be a cross-discipline resource, not just for “designers”.
Many design patterns collected together are kept in a design patterns library.
If we have recorded our patterns to an acceptable level of quality our library will have patterns that are replicable with relative ease.
Such a library of provides a baseline system that allows us to start a few steps on already, to start further along, and spend time and effort looking at the harder problems we can solve. Design as patterns as a commodity as a platform as an opportunity for innovation through further design work. (And innovation as a natural outcome, not a role.)
What this means is new products and services do not come into being just by copying and pasting bits together. That gives you a start. You will need to learn and test and improve in context.
Underlining all that I recommend the following principles:
- Honesty. Say it as it is in your patterns’ commentary. This isn’t marketing. Patterns help make things better. Patterns are also a thing that need to be better.
- Little, often. Record regularly as you go along.
- Start early. And start as you mean to go on. Putting this off will create a bigger problem later.
- Don’t wait for permission.
- Patterns are an outcome of your communities, from communities of practice to the team that are focused on the product. Disparate, separate teams will share, discuss, understand, agree – and disagree – their work.
- Find what works. And find what doesn’t work. Acknowledge both. A pattern always needs to be tested. There is always the potential for improvement from new learning. When new research brings further supportive evidence, that’s just as valuable as corrective measures.
- Use patterns to avoid being all over the fucking place: Go for consistency of experience.
- Building patterns takes times.
- Consistency takes time.
- This is all about continual gradual improvement.
- Make sure everyone understands why we have patterns – and support you.
- Use simple English to explain. Avoid jargon.
- Communicate, clearly, to all involved.
- Involve everyone.
A library should give us a idea of what is good. Design patterns are not just a record of what we have learnt to this point, but a thing we can use to plan the future, for foresight.
I often get asked “Don’t our brand guidelines cover this?“ A design pattern library isn’t brand guidelines. Brand guidelines are usually a reference about the tone of an organisation. Design patterns should reflect the organisation in what they do and how they do. Hopefully a design patterns library will reflect the brand.
Are design patterns a style guide? In a way, yes. A design patterns library will carry the elements of a style guide: Fonts, sizing, layout, and so on.
A design pattern library isn’t a front-end code library – although the best design patterns library include and link off to examples in any front-end code library.
Are design pattern libraries for everyone?
Does a “small product” need something so in-depth? Maybe not.
But anything of weight – a large product, a number of products, particularly over a spread organisation – yes. Want consistency in your approach to making your organisation’s products and services? That’s why you should do patterns. They make all your things better by making your making better.
Feel you need patterns and not doing them already? Start small. Look at problem you have solved already and unpack your works. Take an hour out as a team to huddle to record it. And you’re off.
Doing patterns already? Remind yourself of them. Check they are fit for purpose.
Have and use patterns because they are useful, not because others are, not because you feel they are a commitment you need to meet. Understand their usefulness, and value that usefulness.