{"id":532,"date":"2025-06-11T01:18:27","date_gmt":"2025-06-11T01:18:27","guid":{"rendered":"https:\/\/oriaadvisory.com\/blog\/?p=532"},"modified":"2025-06-12T02:27:39","modified_gmt":"2025-06-12T02:27:39","slug":"clarifying-high-stakes-warnings-in-the-universal-credit-site-flow","status":"publish","type":"post","link":"https:\/\/oriaadvisory.com\/blog\/2025\/06\/11\/clarifying-high-stakes-warnings-in-the-universal-credit-site-flow\/","title":{"rendered":"Clarifying High-Stakes Warnings in the Universal Credit Site Flow"},"content":{"rendered":"\n
\n

A Redesign Audit of the \u201cIf you’re getting other benefits\u201d Screen<\/p>\n\n\n\n

\n

In this short UX audit, I examine a key decision screen<\/strong> in the Universal Credit<\/a> (UC) online service: the page that appears after a user confirms they are making a claim for themselves (step 3 in the process flow). It warns applicants that their existing benefits will stop<\/strong> if they apply for UC, even if their application is unsuccessful<\/strong>.<\/p>\n\n\n\n

\n

Because this is a legally sensitive screen, poor phrasing or layout can directly lead to misunderstanding and emotional stress<\/strong> \u2014 especially for users with low literacy or confidence<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n

Research with these user groups \u2014 conducted during my doctoral work shows that abstract phrasing<\/strong>, dense layouts, and checkbox-based confirmations<\/strong> (as seen in the current Beta screen) can reduce comprehension \u2014 or worse, lead to abandonment or unintentional consent<\/strong>, especially when irreversible outcomes<\/strong> are involved.<\/p>\n\n\n\n

\n

As of 2021, 20-50%<\/a> of UK adults had limited digital skills, and around 18%<\/a> in England had low literacy levels. These users are not edge cases, they are part of the mainstream public<\/strong><\/p>\n<\/blockquote>\n\n\n\n

Importantly, the issue isn\u2019t user failure \u2014 it\u2019s design that doesn\u2019t align<\/strong> with how all users think, read, or move through tasks. <\/p>\n\n\n\n

This mini audit highlights a section screen that could unintentionally block access for many users offers small, actionable testable ideas to support a more inclusive user experience. <\/strong><\/p>\n\n\n\n

\n\n\n\n
<\/div>\n\n\n\n

Method<\/strong><\/p>\n\n\n\n

    \n
  1. Simulated<\/strong> the experience<\/strong> of a first-time applicant with low literacy and digital confidence<\/strong>, based on fieldwork with functionally excluded users<\/strong> navigating mobile services<\/li>\n\n\n\n
  2. Applied cognitive walkthroughs<\/strong> and heuristic analysis, using GDS principles and inclusive design guidelines for users with low literacy and limited digital skills.<\/li>\n\n\n\n
  3. Annotated comparison between the original screen and a redesigned<\/strong> mockup<\/strong> based on inclusive design patterns<\/strong><\/li>\n<\/ol>\n\n\n\n
    \n\n\n\n
    <\/div>\n\n\n\n

    <\/span>Key Issues<\/strong><\/p>\n\n\n\n

    The screen below shows the current Universal Credit “claim conditions” screen (step 3 in the process flow). Each detail may seem minor in isolation but together, they create a disorienting and exclusionary experience<\/strong>.<\/p>\n\n\n\n

    \n

    Critically, many users may treat the checkbox confirmation like social media terms and tick without truly understanding. <\/p>\n\n\n\n

    The original design assumes a literate, contract-style interaction, presenting irreversible outcomes as legal statements, followed by a passive checkbox<\/strong><\/p>\n<\/blockquote>\n\n\n\n

    \n

    Fig 1: Annoted Friction Points on the Original Universal Credit Screen (Beta Version)<\/strong><\/p>\n\n\n\n

    The annotations below highlight common friction points for users with low literacy or digital skills that could result in misunderstanding or premature consent.<\/p>\n<\/div>\n\n\n

    \n
    \"\"<\/figure>\n<\/div>\n\n\n
    \n

    The flow also reverses how users typically process<\/strong> high-stakes information \u2014 showing consequences before rules, and burying the list of affected benefits after the confirmation<\/p>\n<\/blockquote>\n\n\n\n

    \n\n\n\n
    <\/div>\n\n\n\n

    Design Suggestions<\/strong><\/p>\n\n\n\n

    The revised version supports reflection, not reflex. <\/strong>It mirrors how users naturally reason through high-stakes decisions<\/strong>:<\/p>\n\n\n\n

    What\u2019s happening? \u2192 What does it mean for me? \u2192 What can I do?<\/em><\/p>\n\n\n\n

    Aongside adjustments to language, tone, help, and confirmation, this ensures:<\/p>\n\n\n\n

    Consent becomes an intentional step \u2014 not a reflex<\/strong>.<\/p>\n\n\n\n

    These are small, low-risk design changes<\/strong>, annotated below. They are in line with GDS principles and based on patterns that, in previous fieldwork, significantly improved task completion and reduced error rates.<\/strong> They can be tested through A\/B trials<\/strong> or inclusive usability studies.<\/p>\n\n\n\n

    \n

    Fig 2: Redesigned Mockup (proposed improvements)<\/strong><\/p>\n\n\n\n

    The annotated redesign illustrates how each change targets a known friction point for users with low literacy\/digital skills.<\/p>\n<\/div>\n\n\n

    \n
    \"\"<\/figure>\n<\/div>\n\n\n

    These designs were developed while considering GDS principles and are starting points for other service teams<\/strong> that could be adapted further to tackle similar inclusion goals.<\/p>\n\n\n\n

    \n\n\n\n
    <\/div>\n\n\n\n

    Why This Matters<\/strong><\/p>\n\n\n\n

    In high-stakes moments, clear design<\/strong> isn\u2019t just helpful \u2014 it\u2019s what makes informed consent <\/strong>possible. <\/p>\n\n\n\n

    \n

    Even small shifts in flow or language can build confidence, reduce abandonment, and support users who might otherwise be left behind.<\/strong><\/p>\n<\/blockquote>\n\n\n\n

    \n\n\n\n
    <\/div>\n<\/div><\/div>\n\n\n\n
    <\/div>\n<\/div><\/div>\n\n\n\n

    <\/p>\n","protected":false},"excerpt":{"rendered":"

    A Redesign Audit of the \u201cIf you’re getting other benefits\u201d Screen In this short UX audit, I examine a key decision screen in the Universal Credit (UC) online service: the page that appears after a user confirms they are making a claim for themselves (step 3 in the process flow). It warns applicants that their…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,7],"tags":[17,35,15,55,8,26,59],"class_list":["post-532","post","type-post","status-publish","format-standard","hentry","category-skills","category-user-experience","tag-digital-literacy","tag-functional-illiteracy","tag-inclusive-design","tag-low-literacy-users","tag-mental-models","tag-research-reflections","tag-universal-credit-feedback"],"_links":{"self":[{"href":"https:\/\/oriaadvisory.com\/blog\/wp-json\/wp\/v2\/posts\/532","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/oriaadvisory.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/oriaadvisory.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/oriaadvisory.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/oriaadvisory.com\/blog\/wp-json\/wp\/v2\/comments?post=532"}],"version-history":[{"count":37,"href":"https:\/\/oriaadvisory.com\/blog\/wp-json\/wp\/v2\/posts\/532\/revisions"}],"predecessor-version":[{"id":592,"href":"https:\/\/oriaadvisory.com\/blog\/wp-json\/wp\/v2\/posts\/532\/revisions\/592"}],"wp:attachment":[{"href":"https:\/\/oriaadvisory.com\/blog\/wp-json\/wp\/v2\/media?parent=532"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/oriaadvisory.com\/blog\/wp-json\/wp\/v2\/categories?post=532"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/oriaadvisory.com\/blog\/wp-json\/wp\/v2\/tags?post=532"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}