Background

    As the HighBond product suite continues to evolve, the amount of in-product messaging is also growing.

    There are some notable inconsistencies amongst our existing messages, and a need to improve the quality and precision of our messages. We need a style guide to ensure that the content used in our in-product messaging is concise, used consistently, and assumes a pattern that is immediately recognizable to users - enabling a seamless UX experience as users travel between the different modules. Ensuring consistency between messages across the HighBond modules will also have a positive effect on translation quality and reduce translation cost.

    Audience and purpose

    This style guide is intended for UX and UI designers that need to integrate consistent messaging in HighBond.

    The purpose of this page is to gather a selection of the most commonly used messages in order to define:

    • different types of messages
    • when to use each type of message
    • what content goes in a message
    • writing strategies that will help in producing effective and maintainable message content
    • appropriate places for context-sensitive help links in messages

    Why well-written messages matter

    Poorly written messages can cause frustration for users and increase the number of support calls. Well-written messages provide the following information for users:

    • What happened and why OR what will happen as a result of certain actions
    • What they can do to prevent a problem for happening OR what they should do next
    • Where can they go for more information

    Ultimate aim

    The ultimate aim of this initiative is to package these commonly used messages and design patterns into a section in the UX style guide. This will make the information readily available to UX designers and developers that need to implement consistent messaging across the HighBond modules.