Experience Principles

Identify a set of guiding principles to inspire the design of a specific service experience.

also called

Design Principles, Experience Pillars

what is it

Experience principles are inspiring values that help create a shared experience vision within an organization, by applying then consistently across several projects and initiatives. They are based on research, and incorporate insights about what users expect from the relationship with a specific organization or service.

use it to

Guide multiple teams or work-streams to pursue the same goals in terms of user experience.

remember to

Create strong statements to explain the principles, and add visuals that help memorizing them.

references

Kumar, V. (2012). 101 design methods: A structured approach for driving innovation in your organization. John Wiley & Sons.

case studies

1

feature image of 'Experience Principles to keep each other honest at Deliveroo' case study

Example by Deliveroo Design

Experience Principles to keep each other honest at Deliveroo

description

Deliveroo, the food delivery app, wanted design thinking to permeate into the company culture. To align themselves and educate those around, they created Experience Principles to at least tell people some of the things that they believed, if not explain everything they did. Their goals for these principles were two-fold:

  • Have better discussions about the quality of our output, and easily bring new joiners to the same shared conversations.
  • Introduce conversations about user needs, scalable design and things we care about to the product teams and wider organisation.

They came up with four principles, an easy number to remember. They were about- designing for the future; keeping user needs at the centre; going out and empathising; focusing energy. Below these were team and discipline specific principles, focused more on single user groups and execution. Teams could add and use those as they wished, but these four were enough for the business as a whole to get on board with what they’re up to and how they think.

what was interesting

What was interesting was that what they ended up with, they were confident they were already doing in some capacity — but in articulating them they could double down on them.  These things aren’t always obvious to everyone. The people in a product team may read them and see them as no-brainers, but by being first principles-based and general, they could educate others too.

Read more about this case study

View more

contribute

Grow with us!
Share your case studies

The collection is always evolving, following the development of our practice. If you have any interesting tools or example of application to share, please get in touch.

contribute