Pattern 2B: Match the level of precision in UI communication with the system performance - Numbers

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 precision in numeric measurements.

Use when

  • The user needs to understand the system might make mistakes.
  • System behaviors and/or outputs can be qualified numerically.
  • The system output is numerical.
  • It is useful to qualify numerically individual system behaviors.

How

For system outputs and/or behaviors that are qualified numerically, match precision of numbers used in the UI to the precision of system performance.

Understand the level of numerical precision common to the domain.

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

Communicate only the numeric measurements directly relevant to the user’s task or goal.

When deciding what level of numerical precision to communicate, consider how many decimal place values to show, how granular measurements should be (e.g., seconds, minutes).

To communicate high system performance, use more precise and granular measurements.

To communicate that the system may make mistakes, use less precise and granular measurements such as range or rounded numbers, or use expressions such as “a few minutes,” “about,” “approximately” (see pattern G2-A: Match the level of precision in UI communication with system performance – Language).

User benefits

  • Enables the user to identify when the system is performing within or outside specifications.
  • Enables the user to assess how much to trust the system’s output or behavior.
  • Enables the user to monitor system performance.

Common pitfalls

  • Overly precise numbers may lead the user to form over-inflated expectations about system performance.
  • Insufficiently precise numbers may lead the user to underestimate system performance.

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

References

Model calibration:

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