A new experience can include medium or large experiences that most people will encounter. This user journey is considered a medium or large first impression.

For small first impressions, like changes to an existing product experience, use the new or updated feature pattern 

This pattern is for people who already use the product. Avoid using this pattern for new users. We should only show new users a new product first impression, so we don't overwhelm them with content about experiences they haven't seen before.

Aim to make people feel supported, motivated, and empowered.

Help existing users understand the value of the new feature set, and how it benefits them and their team. Focus on the top two to three benefits for the user and show these in context.

Admins and end users may have different reasons to be excited about a new experience. Target the message to your audience:

  • For admins, focus on configuration and control.

  • For end users, focus on the feature set's benefits and how it empowers them.

  • Don't show change management messaging to new users.

Introducing a new experience consists of two basic parts:

  1. An appropriate entry point to notify the user of the new feature set.

  2. Educational components to communicate the top benefits of the feature set.

Entry points

Choose an appropriate place to notify people of the new experience, but don't take over their work. Entry points for new experiences should be dismissible.

Some entry points to consider include:

If you can't decide on the best entry point for your new experience, run an early signal test with existing users.

In this example, an admin gets a notification about a new feature set. They can either try out the experience or dismiss the notification.

User value modal trigger.

Use the spotlight component to highlight the top two to three benefits of the new experience in context.

Here, the admin chooses to try out the new feature set and is shown in context where it lives in the product. They are shown two to three dismissible spotlights that showcase the top benefits.

A spotlight component onboarding people to a new feature in Jira.
  • All first impressions should complement rather than compete with each other. Know what other first impressions or notifications people might encounter, so you can prioritize the right one at the right time and minimize distraction.

  • If your product supports in-app help, point out where people can find more information when they dismiss the tour.

  • Make sure people are prepared for the change with an opt-in to opt-out strategy before forcing everyone into the new experience.


Was this page helpful?

We use this feedback to improve our documentation.