Design the experience

Define the needs and remove the unnecessary

Functional unit: Defining the need is a crucial step. Thinking in terms of functional units can help us focus on what is essential.

Follow the path of your users as much as possible.

Try to keep in mind to :

  • provide simplicity, frugality and efficiency,

  • focus on functional units that brings value to the users,

  • limit the number of clicks,

  • limit the time spent by the user on the application to find what he needs.

Design under constraints

Design in "Mobile first"

This can help simplify interfaces. As phone screens are smaller, this design mode allows to go to the essential and to propose only the functionalities and contents necessary to the user to realize his functional unit efficiently and simply.

Other constraints - less optimal network connection or older devices

To complete this "mobile first" approach, you can design for terminals with little power and a non-optimal network connection (3G rather than 4G for example). These technical constraints force us to focus on the essentials and produce a sober, low-impact digital service.

  • Mobile First

    It's easier to tackle wider screens afterwards

  • Older devices

    Design for older versions of devices & browsers first.

  • Non-optimal network

    Design with performances & slower networks first.

Base your design on standards

Design system

The Design System provides standard components, already coded, which meet the current regulations as well as the rules of development imposed or suggested within Michelin.

Questions to ask:

Questioning the needs:

  • Are the proposed functions well related to a use ?

  • Is it functionality that drives choices rather than the appeal of trendy technology?

  • Are the features being used by the user?

  • Are decisions justified and supported by reliable indicators of feature usage throughout the service life cycle?

Questioning the content:

  • Do you use proven development standards?

  • Which images are really meaningful and useful to understand the service (e.g. logo, link images, contractual images...)?

  • Which images can be dispensed with (not useful for understanding the service)?

  • Can text replace certain types of images (icons, pictograms, etc.)?

  • Which videos are really meaningful and useful to understand the service (e.g. logo, link images, contractual images...)?

  • Which videos can be dispensed with (not useful for understanding the service)?

Log in

Log in with Michelin ID

To connect to the Design System, I will need:

  • A Michelin ID (e.g. F012345)
  • Double authentification (with the NetIQ application or by SMS)
  • A password associated with your Michelin ID

I don’t have a Michelin ID and/or email

In order to connect to the Design System, I need:

  • A user ID or an email
  • A password

If you have never accessed the Design System, you can request access via this link.