Feature discovery

Feature discovery messages let people know about a new feature.

These messages highlight a new or recently updated experience. Let people know what's changed, and invite them to try something new. A feature discovery message should leave your reader feeling:

  1. Curious

  2. Excited

  3. Empowered

For more guidance on this messaging type, see the new or updated feature pattern.

Tips and tricks

  • When introducing the new feature, consider what the user is trying to accomplish, what they were just doing, and where they need to go.

  • Titles and messages should clearly indicate user benefits. For example, "Find your work faster" versus "New search".

  • This should be a positive experience for users, so it's ok to add a little "wink".

Voice and tone

Determine if you need to inform (a feature has moved) or educate (the experience or interaction has changed). Introduce the change, communicate its benefits, and provide a call to action if appropriate, such as, “learn more”.

Be bold and optimistic about a new feature, especially if there are benefits and improvements for the user. Be clear and practical, and you can add a little “wink” to entice the user to try something new.

Examples

The information flag below promotes the updated search feature, giving the option of learning more or trying out the new search.

Information flag to highlight a new search feature.

This example encourages and empowers the user to begin using Jira as intending by adding issues.

Information modal promoting how to add an issue to Jira.

This Bitbucket example encourages people to improve their Bitbucket experience by adding branch permissions. It clearly states the benefits and ideal state of using this feature.

An information modal for BitBucket highlighting how to add a branch permission.

Was this page helpful?

We use this feedback to improve our documentation.