H3.13.3do not collapse partial success into failuredesignresearch

Partial success must not be labeled as total failure

Aliases: partial success · false total failure · mixed result title

What it is

Seventeen items are already in the system and a banner says “the operation failed.” That is a lie. Partial success is not failure: the title and summary must say both through and not, and a failure color must not swallow the successes. People act on the title—redo the batch, tell support “it’s all gone,” or send the already-sent mail again. This entry is about naming. It is not about how fine the list is, or whether a single item can be retried.

Why it happens

The title is the first bite of the result. Working memory loads it first; if details arrive late or behind a disclosure, the title has already set affect and the next step. “Failed” starts a redo script; “17 succeeded, 3 failed” starts a fill-the-holes script. Their side effects are nothing like each other. Failure styling may emphasize the three; the title must still admit the seventeen. Mapping a non-200 at the HTTP layer straight onto a page-level failure is the usual implementation source of this lie: one failure code on a collection paints a mixed result all red.

Studying it

Give the same mixed result three titles: all failed, all succeeded, both counts. Watch the next move.

Independent variables: how the title names a mixed result, whether failure color floods the page. Dependent variables: whether already-successful items are redone, whether people inspect the successful items, rate of a subjective “all lost.”

Do not ask whether they like the title. Watch which button they press and whether they open a successful item to check it still exists.

Where it stops holding

After a transactional rollback, total failure is true, but say it rolled back so people do not think part of it took. While some items are still unknown, the title is “part done, part still confirming,” not an early failure or success. A marketing “complete” with a tiny line “some did not succeed” is the same swallow in the other direction.

Applying it

  • Write the mixed-result headline as “N succeeded, M failed.” Color may emphasize M; the word failure must not be all that remains.
  • Do not use a collection endpoint’s non-200 as page copy; split per-item results, then name.
  • Notifications, mail, logs, and the page share the same counts, so one end does not say failed while another says succeeded.
  • Verify by showing only the title, no list, and asking how many already completed. Zero or all means the title swallowed one side with the other.

Related

  • Within the group: H3.13.1 Partial batch failure needs per-item status · H3.13.2 Failed items need their own retry, not a full redo · H3.13.4 Say whether the failed items already had side effects
  • Adjacent: H3.02 Three elements of error messages · H1.16 Post-submit result presentation · H7.13 Payment failure and unknown state
  • Search terms: partial success · mixed result · false failure

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/H3.13.3