Pattern 2A: Match the level of precision in UI communication with the system performance - Language

blue header bar

Problem

The user needs to form realistic expectations about how well the system can do what it can do.

Solution

Communicate that the system is probabilistic and may make mistakes through intentional use of uncertainty in language.

Use when

  • The stakes are low.
  • The user needs to understand the system might make mistakes.
  • The user is not interested in precise metrics of system performance.
  • Precise system performance metrics are not available.

How

For system outputs and/or behaviors that are best qualified with language, match the words’ precision to precision of system performance.

Collaborate with an AI/ML practitioner to get information about the level of precision the system can achieve and its confidence.

When deciding what level of precision to communicate, consider how to communicate the degree of certainty with words such as, for example, “will” or “is” versus “may,” “might,” or “probably.”

To communicate high system performance, use more certain language.

To communicate that the system may make mistakes, use less certain language.

User benefits

  • Speaks the user’s language and is easy for the user to interpret.
  • Enables the user to assess how much to trust the system’s output or behavior.

Common pitfalls

  • Overly certain language may lead the user to form over-inflated expectations about system performance.
  • Language that is too uncertain may lead the user to underestimate system performance.
  • The use of uncertain language may be subtle and difficult for the user to notice.
  • Uncertain language is so ambiguous that it becomes meaningless.
  • Language use treats all instances of system uncertainty as if they were the same.

Note: Over-inflated user expectations have been shown to cause frustration and even product abandonment.

References

Over-inflated user expectations have been shown to cause frustration and even product abandonment: