D4.07.4Visible adjudicationdesignresearch

Adjudication should let users perceive that a conflict occurred

Aliases: transparency · conflict notice · adjudication feedback

What it is

Users should be able to tell that a conflict occurred and how the system resolved it. If the system resolves a contradiction internally and shows only one outcome, users cannot know that an input was ignored, nor recover when the result does not match intent.

Why it happens

Opaque adjudication removes causal control: a user issues two inconsistent commands, the system takes one, and only the result is visible, so the user may conclude their other input was never recognized or may repeat attempts to raise the odds. Surfacing the conflict also lets users check whether their input was understood—especially important in multimodal input, where recognition reliability differs across channels. Transparency costs attention, so the presentation should stay light, such as a brief status line rather than a modal dialog.

Studying it

Compare transparent and opaque adjudication: under conflict, record whether users can correctly state which input the system used, whether they repeat inputs, and whether they can correct the ignored one. Variables include presentation style, conflict frequency, and task criticality. Outcomes include accuracy in judging causality and success at correction, the latter directly reflecting recoverability.

Where it stops holding

When conflicts are very rare or low-stakes, extra notices draw needless attention. When conflicts affect critical operations or an input is silently ignored, transparency is required, because users need to know the system disagrees with their understanding. If the notice is too prominent, users are interrupted repeatedly, so visibility and interference must be balanced.

Applying it

  • After adjudication, show a light status note naming which input was used.
  • Offer a quick way to reselect or resend the ignored input so users can recover.
  • For frequent conflicts, fix recognition or the interaction rather than relying on notices long-term.
  • Verification: under conflict, test whether users can correctly state the adjudication and correct it; a high failure rate means transparency is insufficient.

Related

  • Within the group: D4.07.1 Systems usually trust vision first when channels conflict · D4.07.3 Forcing one dominant sense discards useful information from the others
  • Adjacent: D5.08.3 Fallback should tell the user which interpretation was used · O4.02 System consistency and the building of trust
  • Search terms: transparency · conflict notice · recovery affordance

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/D4.07.4