ux-research 2 linked patterns checked

GOV.UK task list iteration research

Documents research-driven task list changes including status tags no longer using uppercase text, whole-row clickable tasks, hint text, button-like status confusion, and drawing more attention to tasks needing action.

Read with a purpose

What this source can teach

Use this source to examine the study question, participants, observations, and limits before applying a finding.

  1. Start with the original. Open the source and find the guidance or example relevant to your task.
  2. Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
  3. Check the setting. Compare the source's platform, people, and constraints with your own decision.

Pattern Decisions This Source Supports

Pattern Supported decision Required contract Claim note
Complete multiple tasks Choose complete multiple tasks when users need a saved progress hub for several meaningful task sections in a transaction. Selecting a task row opens that task and returns users to the same hub with updated status after save, skip, or completion. GOV.UK research supports whole-row clickable tasks, hint text, status tags that do not look like buttons, and less visual weight for completed tasks.
Task list Choose task list when the interface needs row-level task names, links, hint text, and status labels for a known set of service tasks. A startable task row opens the represented task; the status label is not a separate primary command. GOV.UK research supports whole-row clickable tasks, hint text, non-uppercase status tags, avoiding button-like statuses, and lower emphasis for completed rows.

Comparisons supported by this source

Evidence Role

This source is treated as ux-research evidence. Its value comes from the specific claims and setting described above.

Publisher: Design in government. Last checked: .

Saved items