Login
Content patterns blogpost cover
June 21, 2022

How to create a content pattern

Content patterns define a consistent way to communicate in user interfaces. But how do you start creating one? We’ll tell you how we create our content patterns.

What are content patterns?

Patterns are recurring solutions for common design problems. And you can use patterns when designing user interfaces.

We use patterns in our design community to create consistent experiences. But we started to evolve our patterns by looking more into content.

Content patterns create consistency in how we communicate. And they improve our existing patterns beyond look and feel.

Creating content patterns, in theory

You might already know the double diamond, popularised by the British Design Council. It’s a process that encourages exploration of a design problem to then take focused action. And like in any design discipline, this process applies to content design.

Double diamond framework

In short, the double diamond approach defines 4 design phases:

  • Discover, where you engage with areas and people affected by the problem to understand it
  • Define, where you analyse your insights to clarify the challenges
  • Develop, where you try to find possible solutions to the defined challenges
  • Deliver, where you test and refine your solutions to get an outcome

Creating content patterns, in practice

Discovering the pattern space

Background research is where we start, and is important when designing. You should look at how people approach the same solution, internally and externally.

When researching for a content pattern, aim to:

  • Benchmark other design systems
  • Collect inputs across the organisation, from different teams and stakeholders

Defining what the pattern should be

At this point we have lots of materials to look at, and we start organising them. You’ll start to notice recurring use cases that you can use as a foundation for documentation.

Try to discover as many use cases as possible. This helps you adjust the pattern to fit more contexts and streamline documentation.

We’ll also try the content patterns in context, so in our flows and UI components. This helps you to test if the UI components support the use cases coming from looking at the content.

When organising your content pattern inputs, aim to:

  • Group inputs into use cases
  • Identify the problem areas to look into
  • Test out how a pattern would work in different situations

Developing the pattern further

We develop the pattern further by testing it with users, and sparring with peers. This helps you spot use cases that you might’ve missed, or find conflicting principles.

When developing your content patterns, aim to:

  • Test them with users
  • Point out where you have conflicting ways to do things
  • Get input and feedback from your peers and stakeholders

Delivering the content pattern

We finalise and deliver the pattern by creating documentation for it. Documentation not only gives guidance about how to apply the pattern in flows. It also helps us keep track of the decisions we’ve made.

Aim to include these when creating documentation for your content pattern:

  • Structure of the pattern
  • In-context examples of the pattern
  • Overview of how we reached the outcome
  • Links to related documentation and resources
Example of a content pattern

Tips and learnings for creating your own content patterns

Creating a content pattern takes time

Take your time to collect examples for possible pattern use cases. This helps spot inconsistencies in communication and help round out the content pattern.

Look at the whole context

Look at elements other than text when creating content patterns. Icons, illustrations, colours or other visual elements are also important elements of messaging.

Include lots of examples

Strengthen your documentation by providing varied examples of a pattern in action.

More from the Blog