{
 "schemaVersion": 1,
 "pathSlug": "design-psychology",
 "items": [
  {
   "questionId": "ux_design.design_principles__100434",
   "topic": "ux_design",
   "subSkill": "design_principles",
   "difficulty": 1,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Which definition best matches what designers mean by 'mapping' as a foundational principle?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "The grouping of related visual elements on a screen so they appear to belong to one cognitive unit."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "The translation of brand guidelines into reusable components inside a shared product design system."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "The arrangement of menu items in a hierarchy that mirrors the structure of an underlying database schema."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "The relationship between the layout of controls and the layout of the things they actually affect."
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_principles__71608",
   "topic": "ux_design",
   "subSkill": "design_principles",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What UX failure does 'feature bloat' or 'feature creep' cause?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Reduced development costs through shared component code"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Faster application performance due to code optimization"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Better SEO rankings from having more content pages"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Complexity that buries core tasks and slows learning"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_principles__71647",
   "topic": "ux_design",
   "subSkill": "design_principles",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is 'Norman's action cycle' and what are its two main phases?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "A delivery loop of design, build, and release repeated once per calendar quarter by the team"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "An iterative loop of research, prototype, and test repeated until a study passes"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "A loop of execution, where an intention is formed and carried out, and evaluation of results"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "A commercial loop of plan, execute, and measure run by the leadership each year"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_principles__71742",
   "topic": "ux_design",
   "subSkill": "design_principles",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is 'design debt' and how does it accumulate in products?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Piled-up inconsistencies, stale patterns, and quick fixes that compound over the years"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Hours burned in critique meetings that push the build schedule out further each week"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Shortcuts that live purely in the stylesheet layer, such as overrides stacked on overrides"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "The payroll cost of keeping practitioners on staff for the whole length of a project"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_principles__71512",
   "topic": "ux_design",
   "subSkill": "design_principles",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "The 'aesthetic-usability effect' describes what cognitive bias?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Users perceive aesthetically pleasing designs as easier to use, even when they are not objectively so"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Aesthetic designs need fewer rounds of usability testing because the visual polish already proves the flow works"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Users rank minimalist layouts above every other visual style when asked to choose one"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Attractive interfaces measure better on performance metrics than plain ones running the same code"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_principles__400883",
   "topic": "ux_design",
   "subSkill": "design_principles",
   "difficulty": 4,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A fintech app has an 'Approve transfer' confirmation screen. Users report 'I read the screen and still didn't realise I was sending it to the wrong account.' Logs show users spent under 2 seconds on the screen before approving. Which design response is most aligned with the underlying principle?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Reduce the cognitive cost of approval: make the confirmation control even more prominent so users feel the action is completing faster"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Increase the visual polish of the approval page: apply more brand styling so the page is more pleasant to read carefully"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Reduce the recipient label's font size so it does not visually dominate the layout of the approval confirmation screen"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Raise the cognitive cost of approval: highlight the recipient and require an active confirmation, not a habitual tap"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_principles__200444",
   "topic": "ux_design",
   "subSkill": "design_principles",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Mobile analytics show the 'Delete account' button at the bottom edge of a settings screen is mis-tapped 4× more often than 'Log out' which sits in the screen centre. Both buttons are the same size. Which design law is most relevant?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Fitts's Law: edge-anchored targets are easier to hit, with the screen edge stopping the cursor for free"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Tesler's Law: there is irreducible complexity in destructive actions that must be absorbed by either user or system"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Postel's Law: the form should be liberal in what it accepts from the user and conservative in what it sends back"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Hick's Law: the settings screen presents too many destructive choices for the user to evaluate in a short time window"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_principles__10286",
   "topic": "ux_design",
   "subSkill": "design_principles",
   "difficulty": 4,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "In a dense enterprise interface that experts use all day, which property most reduces avoidable confusion?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Bespoke layouts per screen tuned to that screen's specific data"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Distinct terminology per feature area to mirror each team's domain"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Maximal information density so every datum is visible at once"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Consistent visual hierarchy and predictable interaction patterns"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_principles__500671",
   "topic": "ux_design",
   "subSkill": "design_principles",
   "difficulty": 5,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A senior team debates how to classify the 'forcing function' on a destructive flow (typing 'DELETE') within Norman's principle vocabulary. Which framing best resolves where forcing functions sit in that taxonomy?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Forcing functions belong to feedback because they reveal system state and they do not stop the destructive completion in any way"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Forcing functions are a sub-class of physical/logical constraint that compels a deliberate intermediate act before the destructive completion"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Forcing functions are signifier-only patterns that communicate consequence; they do not actually block the user's destructive intended action"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Forcing functions and Norman's principle set are unrelated; forcing functions belong to Nielsen heuristics while principles live elsewhere"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_principles__71534",
   "topic": "ux_design",
   "subSkill": "design_principles",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What does Tesler's Law (the Law of Conservation of Complexity) state about interface design?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Complexity is conserved, moving between user and system"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Complexity increases linearly with the number of features"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Users prefer complex interfaces because they signal capability"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Simpler interfaces always outperform complex ones in user testing"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.usability_testing__10266",
   "topic": "ux_design",
   "subSkill": "usability_testing",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Which set of measures gives the most useful signal in a task-based usability session?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Net Promoter Score collected from the company's existing mailing list"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Participant age, location, and other recruited demographic attributes"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Total page views and average session length across the whole product"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Task success, completion time, and the errors users make along the way"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.usability_testing__71651",
   "topic": "ux_design",
   "subSkill": "usability_testing",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "During usability testing, 4 out of 5 participants fail to find the search feature. What is the most likely UX issue?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "The search algorithm returns irrelevant results"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Poor discoverability: the search input lacks visible affordance or is positioned outside expected locations"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Users need more training before they can use the product"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "The search feature should be removed since users cannot find it"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.usability_testing__1380519",
   "topic": "ux_design",
   "subSkill": "usability_testing",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "For a B2B SaaS product with two distinct personas, current NN/g guidance changes how you allocate the 5-user heuristic. What is the adjusted recommendation?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Run roughly five users for whichever persona has the riskier task path"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Run roughly five users total split evenly across the two personas"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Run roughly five users for the primary persona then add two for the rest"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Run roughly five users per persona, not five for the study as a whole"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.usability_testing__71624",
   "topic": "ux_design",
   "subSkill": "usability_testing",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is a 'heuristic evaluation' and who typically performs it?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "A performance test that measures page load times"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "A user survey that measures satisfaction on a Likert scale"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "An automated tool that scans code for accessibility violations"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "An expert review where UX specialists evaluate an interface against established usability principles"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.usability_testing__307418",
   "topic": "ux_design",
   "subSkill": "usability_testing",
   "difficulty": 5,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A research lead is asked to validate an enterprise dashboard with statistical confidence on completion times. They propose 5-user qualitative testing. Engineering pushes back wanting 50 users for power. Anchored in research design, what is the principled response that resolves both concerns?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Use a small qualitative round to find and fix usability problems, then a separate larger benchmark study once the design has stabilised to measure completion time"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Use a sequence of two 5-user rounds two weeks apart so the longitudinal completion-time trend can substitute for the larger-sample benchmark engineering requested"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Use a single combined study with 50 participants so the qualitative themes and the quantitative completion-time estimate are produced from one matched cohort"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Use a within-subjects design with 20 participants exposed to both the old and new dashboards so the paired comparison reaches the power engineering is asking for"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.usability_testing__71756",
   "topic": "ux_design",
   "subSkill": "usability_testing",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A/B testing and usability testing serve different purposes. When is A/B testing more appropriate than usability testing?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "When you have no existing traffic or user base to test with"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "When you want to understand why users struggle with a specific flow"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "When you need statistical proof of which design performs better on a specific metric with real traffic at scale"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "When the design change is fundamental rather than incremental"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.usability_testing__71636",
   "topic": "ux_design",
   "subSkill": "usability_testing",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is the 'Hawthorne effect' and why does it matter in usability testing?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Test results improve when using brighter room lighting"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Users perform better on familiar devices during testing"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Longer test sessions produce more reliable data"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Participants may alter their behavior because they know they are being observed, skewing results"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.usability_testing__71831",
   "topic": "ux_design",
   "subSkill": "usability_testing",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is 'cohort analysis' in UX analytics?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Studying the audience's demographics in order to build out the marketing segments used"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Comparing behaviour across groups that joined at different times to read retention"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Measuring how somebody works through one capability inside a single visit"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Splitting the audience into random groups so a variant can be compared"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.usability_testing__428193",
   "topic": "ux_design",
   "subSkill": "usability_testing",
   "difficulty": 1,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A junior researcher hands participants a printed list of features and asks 'Can you find each of these in the app?'. Watching the recording later, the lead notices participants are scanning labels instead of trying to accomplish anything. What core mistake did the session make?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Recorded the screen instead of the face, which is what removes the ability to observe genuine hesitation and confusion"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Prompts named features instead of goals, turning the session into a label-matching exercise rather than realistic task performance"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Used a within-subjects design when a between-subjects comparison would have been the appropriate evaluation approach here"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Ran the session moderated when an unmoderated tool would have produced a more representative behavioural sample"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.usability_testing__612847",
   "topic": "ux_design",
   "subSkill": "usability_testing",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Session recording from a Maze unmoderated test shows the participant completing the task in 14 seconds with zero errors and a 9/10 satisfaction rating. Engineering ships the design. Two weeks later, support tickets on that exact step triple. Which test-design gap is most likely the cause?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Unmoderated tasks had no screener so participants skewed too technical here"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Unmoderated tasks were too leading and primed the participant down the path"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Unmoderated tasks were too short so participant fatigue masked real friction"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Unmoderated tasks lacked a severity rubric so misclicks were not weighted"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_critique__950507",
   "topic": "ux_design",
   "subSkill": "design_critique",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A senior designer who built a settings screen over four months reads it as clear, while people meeting it for the first time stall on it in every session. Which account fits both observations?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "The screen is dense for everybody, and four months of use taught the senior designer shortcuts around the dense parts"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "The screen is clear and the sessions are measuring an onboarding gap a first-run explanation would close"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "The screen is clear in isolation and the sessions reach it through a task flow that arrives with the wrong expectations"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "The screen is fluent for the one person who holds the model behind it, and that ease is taken for clarity"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_systems__10339",
   "topic": "ux_design",
   "subSkill": "design_systems",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A team must decide whether a newly built pattern belongs in the shared core library or in their own product. Which signal most justifies promoting it to core?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "It was the hardest component to build, so centralizing it saves the next team the same effort"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "It already uses shared tokens and atoms, which on its own qualifies it for the core library"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "It is used across multiple products and its shape has proven stable over several iterations"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "It is the most visually polished component the product team has shipped this quarter so far"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_systems__100892",
   "topic": "ux_design",
   "subSkill": "design_systems",
   "difficulty": 1,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What are Apple's Human Interface Guidelines as Apple publishes them?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Platform guidance on patterns, controls, and principles for designing apps on Apple systems."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "A licensed icon set developers ship inside their apps to comply with App Store submission rules."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "A code-signing toolchain teams run on macOS to validate accessibility tags before release builds."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "An automated linter for SwiftUI that rewrites view hierarchies to match the latest visual style."
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_systems__732894",
   "topic": "ux_design",
   "subSkill": "design_systems",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Shopify's Polaris was reorganized so that consumers of the system pick up new visual decisions without rewriting components. What is the recommended way to consume Polaris design decisions today?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Override component props with literal hex codes per screen so the tokens stay locked"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Fork the components and rebuild the tree with bespoke CSS modules whenever a new release ships"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Bring in the token package and let the Polaris parts read those values at runtime"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Hand-copy the token package values from the Polaris repository into each stylesheet"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_systems__71940",
   "topic": "ux_design",
   "subSkill": "design_systems",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A design-ops lead wants to standardize accessibility annotations and automate icon insertion inside Figma without leaving the canvas. Which capability addresses both?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Figma variables: reusable values for color and spacing that switch modes for themes and breakpoints in practice"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Figma branches: parallel copies of a file that let teams stage edits before merging back to main"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Figma libraries: published components and styles shared across files to keep usage consistent"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Figma plugins: third-party extensions that add tooling like a11y checks, asset insertion, and linting"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_systems__200529",
   "topic": "ux_design",
   "subSkill": "design_systems",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What purpose does governance serve in a mature design system?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Approve every individual pull request a product team raises against any consumer feature branch."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Decide which marketing campaigns are allowed to reuse the brand colour palette in paid placements."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Audit unrelated backend services for compliance with the same naming style as UI components."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Define how changes, contributions, and deprecations are reviewed so the system stays coherent."
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_systems__71861",
   "topic": "ux_design",
   "subSkill": "design_systems",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is 'visual regression testing' and how does it support design system quality?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Testing whether the visual design follows current trends"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Regression testing of JavaScript logic in visual components"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Manual review of screenshots by a design team member"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Automated screenshot diffs that catch unintended changes"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_systems__10340",
   "topic": "ux_design",
   "subSkill": "design_systems",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A product team repeatedly bypasses the system's components to hand-build one-off UI for the same screens. Beyond the immediate work, what is the compounding cost?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Visual drift and rising maintenance, since each bypass becomes code no shared fix can reach"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Loss of brand ownership, since any custom UI legally transfers design rights to the product team"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Slower initial delivery, since hand-building is always more time-consuming than reusing a component"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Reduced test coverage, since components built outside the system cannot be unit-tested at all"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_systems__20053",
   "topic": "ux_design",
   "subSkill": "design_systems",
   "difficulty": 4,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is the primary governance challenge as a design system scales from 2 to 20 consuming teams, and what practice typically resolves it?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Version management: systems with 20 consuming teams must pin every component to a specific commit hash for stability"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "The primary challenge is runtime performance: large design systems have too many bundled components for smaller teams"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Color token governance: 20 consuming teams will inevitably each request their own different brand colors and palettes"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Contribution model: who proposes, reviews, and promotes components - addressed via RFC process or federated maintainers"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_systems__200345",
   "topic": "ux_design",
   "subSkill": "design_systems",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "An accessibility audit logs WCAG 1.4.3 contrast failures on six surfaces, all using the system's text-secondary token over surface-2. The token values are correct in isolation but fail on that specific background. What is the cleanest systemic fix?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Have each surface override text-secondary with a darker custom hex for that page"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Introduce on-surface-2 paired tokens with contrast guaranteed against surface-2"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Lower the surface-2 lightness instead, so existing text tokens regain contrast"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Document the failing pair in storybook and rely on designers to avoid it manually"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.design_systems__300948",
   "topic": "ux_design",
   "subSkill": "design_systems",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What role does Storybook play in a component-library workflow?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "A static site generator that publishes marketing landing pages from MDX content authored by writers."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "An end-to-end browser harness that drives the production app and asserts against API responses."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "A backend service that stores feature flags and exposes them to product clients over WebSocket."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "An isolated environment for developing, documenting, and reviewing components in defined states."
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.user_research__231854",
   "topic": "ux_design",
   "subSkill": "user_research",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A researcher demos a clickable prototype, then asks 'What did you think of the new design?' All eight participants respond positively. Shipped feature underperforms. Where did the method fail?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "The researcher likely framed the prototype as 'new', anchoring participants on novelty over critical evaluation."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Eight participants is below the threshold for qualitative confidence, which inflated the apparent positivity."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "The prototype fidelity was too low, so participants could not form an accurate first impression of the design."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Asking opinions on a designed artifact triggers social-desirability bias; tasks-and-observations expose actual usability problems."
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.user_research__20015",
   "topic": "ux_design",
   "subSkill": "user_research",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What distinguishes qualitative from quantitative user research?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Qualitative research only uses A/B testing methodology to compare design variant performance"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Quantitative research is always more accurate than qualitative regardless of the question asked"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Qualitative explores why and how via observation and interviews; quantitative measures frequency and magnitude via metrics"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Qualitative research uses larger sample sizes than quantitative research in all study types"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.user_research__71724",
   "topic": "ux_design",
   "subSkill": "user_research",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is 'wizard of Oz testing' for AI features?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "A person quietly plays the model's part while somebody uses the interface"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Having a model run the participant interviews without a human being present"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Running scripted automation that mimics how a person would behave"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Trying the capability out inside a themed and decorated study room"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.user_research__503893",
   "topic": "ux_design",
   "subSkill": "user_research",
   "difficulty": 5,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Which statement best describes the continuous-discovery interviewing cadence advocated by Teresa Torres?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Product trios talk to a steady stream of users every week and connect those conversations to ongoing opportunity mapping"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Product trios outsource all participant conversations to an external agency that delivers a quarterly insight report"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Product trios run a single deep cohort study at the start of each annual planning cycle and freeze inputs afterwards"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Product trios delay any user conversations until after engineering has shipped a minimum-viable feature to production"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.user_research__71715",
   "topic": "ux_design",
   "subSkill": "user_research",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "How should UX researchers study the usability of AI-powered features differently from traditional features?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "AI features should only be tested by machine learning engineers"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "By evaluating trust calibration, error recovery, and whether users appropriately rely on or override AI suggestions"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "AI features do not need usability testing because they are self-optimizing"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Standard SUS questionnaires capture all relevant AI usability metrics"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.user_research__402644",
   "topic": "ux_design",
   "subSkill": "user_research",
   "difficulty": 4,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Which statement best describes ethnographic research in a UX context?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Sustained in-the-field observation of people in their everyday environment to understand culture, routines, and meaning"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Lab-based eye-tracking sessions that quantify gaze patterns across a fixed grid of static page screenshots"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Co-design workshops where invited customers and product teams jointly sketch future-state journey artefacts"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Short remote intercept surveys triggered immediately after a participant finishes a critical task in production"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.user_research__200517",
   "topic": "ux_design",
   "subSkill": "user_research",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Which statement best describes affinity diagramming during research synthesis?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Ranking proposed design solutions by estimated implementation cost against an internal effort baseline"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Grouping raw observation snippets into emerging clusters bottom-up to surface themes across many sessions"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Plotting survey responses on a two-axis matrix to position respondents against precomputed persona archetypes"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Mapping user journeys onto a service blueprint to align frontstage moments with backstage support steps"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.user_research__503894",
   "topic": "ux_design",
   "subSkill": "user_research",
   "difficulty": 5,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Which statement best describes the Mom Test heuristic for early customer conversations?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Present a polished pitch deck and capture the participant's enthusiasm score on a five-point Likert reaction scale"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Open with the proposed feature concept and probe how much the participant would be willing to prepay for access"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Stay strictly inside a scripted moderator guide so every session is comparable across the full recruited cohort"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Ask about specifics of past behaviour and avoid pitching the idea so even a biased listener cannot lie about it"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.user_research__10241",
   "topic": "ux_design",
   "subSkill": "user_research",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A team recruits interview participants only through an in-product invite banner. Which recruiting decision most threatens the validity of the findings?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Mixing two adjacent target segments and tagging each transcript by which segment it came from"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Over-recruiting from a paid panel and capping each session at a strict sixty-minute limit"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Scheduling sessions across several time zones rather than concentrating them in one work week"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Sourcing solely from active in-product users, which silently excludes lapsed and churned people"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.user_research__71531",
   "topic": "ux_design",
   "subSkill": "user_research",
   "difficulty": 1,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is a 'jobs to be done' (JTBD) framework in user research?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "A recruiting frame for assembling a research group inside a large organisation"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "A frame that centres on the underlying goal somebody is trying to reach here"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "A scheduling tool for handing out the practitioner work across a team"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "A method for putting effort estimates on units of engineering work"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.interaction_patterns__201169",
   "topic": "ux_design",
   "subSkill": "interaction_patterns",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is a tooltip in a UI?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "A modal step in an onboarding tour that walks the new user through the primary actions on a screen"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "A persistent panel rendered next to a control to host the full reference documentation for the feature"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "An inline validation message that appears below an input once the field-level form rule has been broken"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "A small hover- or focus-revealed label that supplies a brief hint about the control it is attached to"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.interaction_patterns__71543",
   "topic": "ux_design",
   "subSkill": "interaction_patterns",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is an 'optimistic UI' pattern?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Showing only positive feedback and hiding all error states in practice"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Using bright, cheerful colors throughout the interface to lift the mood of the user"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Designing interfaces that assume users will never make mistakes in practice"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Immediately reflecting a user action in the UI before the server confirms success"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.interaction_patterns__71881",
   "topic": "ux_design",
   "subSkill": "interaction_patterns",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is a 'design handoff checklist' and why does it prevent rework?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "A list of the guiding principles to keep in mind while sketching rough frames"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "A fixed list of the drawing tools to install before work begins on a new project"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "A sign-off record used to capture formal stakeholder approval before a release"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "A fixed list of deliverables and specs to complete before the build can start"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.interaction_patterns__300453",
   "topic": "ux_design",
   "subSkill": "interaction_patterns",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Comparing a non-modal side drawer with a route change to a dedicated edit page, the drawer is preferable when:"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "The edit form is so long it must scroll past the viewport height multiple times to complete"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "The edit task needs its own URL so it can be deep-linked and rehydrated for return visits"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "The originating list view is so dense that any side surface would obscure the workspace fully"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "The user benefits from seeing the originating record while editing details on the side"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.interaction_patterns__71686",
   "topic": "ux_design",
   "subSkill": "interaction_patterns",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Users report losing work when they navigate away from a form without saving. What interaction pattern prevents this?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Switching each navigation link off for as long as the form remains open on screen"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Taking the browser's own back control out of service on those pages"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Submitting the form automatically each time a single field is altered"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "A guard on unsaved edits that warns before navigation and can keep a draft copy"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.interaction_patterns__20042",
   "topic": "ux_design",
   "subSkill": "interaction_patterns",
   "difficulty": 5,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What are the second-order effects of implementing optimistic UI updates (showing success state before server confirmation) in a collaborative editing application?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Optimistic UI is always safe in collaborative apps because conflicts are automatically resolved by the server layer in practice"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Conflict handling grows complex when one user's optimistic write fails and rollback must reconcile committed state"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "The only observable effect is a brief visual flicker when the server response differs from the optimistic update state"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Optimistic UI eliminates the need for conflict resolution entirely because all updates appear instantaneous to users in practice"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.interaction_patterns__10231",
   "topic": "ux_design",
   "subSkill": "interaction_patterns",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A team standardizes its button, menu, and dialog behaviors into a shared pattern library. What is the strongest UX argument for doing so?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Shared patterns are mainly a hand-off aid for the engineers and do not change how a user behaves"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Users carry learned behavior from one screen to the next, so new flows cost less attention"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Shared patterns make every interaction feel novel, which is what keeps users engaged over time"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Shared patterns let the team skip usability testing on flows that reuse an existing component"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.interaction_patterns__71603",
   "topic": "ux_design",
   "subSkill": "interaction_patterns",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "The 'privacy zuckering' dark pattern refers to what manipulative design practice?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Offering a sign-in through a public network in order to shorten the registration"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Placing a link to the privacy statement in the footer of each page"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Confusing somebody into sharing more personal detail than they meant to share"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Encrypting the stored records with a proprietary in-house algorithm"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.interaction_patterns__71520",
   "topic": "ux_design",
   "subSkill": "interaction_patterns",
   "difficulty": 1,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What interaction pattern does a 'breadcrumb' navigation serve?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Displays a list of bookmarked pages for quick access"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Shows a loading progress bar during page transitions"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Tracks which pages a user visited in chronological order"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Shows location in a hierarchy and links to parents"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.interaction_patterns__71846",
   "topic": "ux_design",
   "subSkill": "interaction_patterns",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is 'contextual help' versus 'global help' in product UX?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Contextual help sits next to the thing it explains; global help is a separate library"
       }
      ],
      "shape": "code"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Global help beats contextual help in each case, so the inline variety is wasted effort"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Contextual help works offline; global help needs a live connection to the server"
       }
      ],
      "shape": "code"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Contextual help removes the need for a second source of guidance anywhere else"
       }
      ],
      "shape": "short"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.information_architecture__200386",
   "topic": "ux_design",
   "subSkill": "information_architecture",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is a polyhierarchy in an IA?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "A single item legitimately belongs under more than one parent category in the structure."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "A category groups several teams that share an owner across multiple product lines for a quarter."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "A category page is split into pagination chunks once item count exceeds a configurable site setting."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "A category name varies per locale while the underlying URL path stays identical for analytics joins."
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.information_architecture__20029",
   "topic": "ux_design",
   "subSkill": "information_architecture",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is card sorting used for in information architecture?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "To understand how users categorize and label content, informing navigation and taxonomy"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "To test whether users can successfully find specific content in an existing navigation structure"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "To measure task completion speed across different navigation menu depths and information layers"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "To rank product features by perceived importance before roadmap prioritization planning sessions"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.information_architecture__200345",
   "topic": "ux_design",
   "subSkill": "information_architecture",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Choosing between a broad-and-shallow hierarchy and a narrow-and-deep one for a navigation menu, which observation captures the established trade-off?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Broad-shallow is always faster regardless of menu width; narrow-deep is only useful in very small apps in practice"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Broad-shallow only works on touch devices; narrow-deep only works for keyboard-first power users"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Broad-shallow ignores breadcrumbs entirely; narrow-deep forbids the use of any global search bar"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Broad-shallow reduces clicks but raises label-scanning cost; narrow-deep adds depth but reduces per-level choice"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.information_architecture__71590",
   "topic": "ux_design",
   "subSkill": "information_architecture",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is a 'site map' in information architecture?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "A machine-readable file listing each page address so a search crawler is able to index them"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "A geographic plot showing where the hosting regions and edge locations physically sit today"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "A shaded overlay showing which parts of a screen get pressed most frequently by visitors"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "A tiered diagram showing how the pages and sections of a product relate to one another"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.information_architecture__3091846",
   "topic": "ux_design",
   "subSkill": "information_architecture",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A docs site adds breadcrumbs above the H1 of every article. Six weeks later analytics show the breadcrumb's parent link gets 11% of clicks per page-view, while back-button rate drops from 34% to 22%. What does this pattern suggest about the breadcrumb's IA role?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Breadcrumbs are serving as a lateral exploration aid, users use them to climb back to a category and pivot, not as decoration"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Breadcrumbs are absorbing the clicks that would otherwise hit the global nav, so the global nav should now be removed as redundant overhead"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "The 11% click rate proves breadcrumbs are mostly ignored, and the back-button drop is fully attributable to unrelated reading-time changes"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Breadcrumbs are confusing users about page hierarchy, which is why back-button usage fell as people give up navigating entirely"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.information_architecture__71778",
   "topic": "ux_design",
   "subSkill": "information_architecture",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What is the difference between 'top-down' and 'bottom-up' IA approaches?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "They arrive at identical navigation structures in each case that is run"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Top-down runs tree tests while bottom-up runs card sorting and nothing further"
       }
      ],
      "shape": "short"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Top-down starts from business goals; bottom-up starts from the content itself"
       }
      ],
      "shape": "code"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Top-down works handheld to desktop; bottom-up works desktop to handheld"
       }
      ],
      "shape": "code"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.information_architecture__200384",
   "topic": "ux_design",
   "subSkill": "information_architecture",
   "difficulty": 2,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What role does a sitemap play during IA design?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "It records the user's click trails over a week so analysts can review the structure after launch"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "It surfaces accessibility violations across the routes and is consumed mainly by automated audit tooling."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "It shows the planned page tree and links so a designer can review the shape before any build"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "It lists every URL the crawler should index, ranked by traffic and reviewed solely by the SEO team"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.information_architecture__11293847",
   "topic": "ux_design",
   "subSkill": "information_architecture",
   "difficulty": 4,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "A large enterprise app merges two products into one shell. Post-launch, NPS drops 14 points and support logs 'I can't find X anymore' as the top theme. Tree testing shows 28% first-click accuracy for the merged top nav. What IA strategy addresses this?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Add an extensive onboarding tour that walks users through the new navigation structure, since the drop reflects awareness gaps rather than any IA mismatch issue"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Run open card sorts on each legacy product separately, then federate the two resulting taxonomies under a single root using the larger product's categories as can"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Restore the two original top-level entry points inside the merged surface, since users built models around the legacy product vocabularies as truth"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Run a hybrid card sort to build one taxonomy on the merged surface, using both legacy vocabularies as raw input rather than fixed truth"
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.information_architecture__100272",
   "topic": "ux_design",
   "subSkill": "information_architecture",
   "difficulty": 1,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "What does tree testing evaluate as an IA method?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Users rate the visual hierarchy of a homepage mockup across five seconds of exposure time."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Users complete tasks on a clickable prototype while a facilitator probes their reasoning live."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Users locate items in a text-only hierarchy stripped of visuals to isolate findability."
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Users describe out loud how they would group products before any prototype is shown to them."
       }
      ],
      "shape": "long"
     }
    ]
   }
  },
  {
   "questionId": "ux_design.information_architecture__300455",
   "topic": "ux_design",
   "subSkill": "information_architecture",
   "difficulty": 3,
   "stem": [
    {
     "type": "p",
     "runs": [
      {
       "t": "text",
       "v": "Comparing audience-based navigation (e.g., 'For Developers' / 'For Designers') with task-based navigation (e.g., 'Integrate' / 'Customise'), which observation is best supported?"
      }
     ]
    }
   ],
   "widget": {
    "kind": "mcq",
    "options": [
     {
      "id": "o1",
      "label": [
       {
        "t": "text",
        "v": "Audience nav requires per-role authentication checks; task nav requires no role-based access control logic"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o2",
      "label": [
       {
        "t": "text",
        "v": "Audience nav always lifts conversion on marketing sites; task nav always reduces it for B2B SaaS products too"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o3",
      "label": [
       {
        "t": "text",
        "v": "Audience nav is forbidden by WCAG accessibility guidance; task nav is the only WCAG-conformant pattern allowed in practice"
       }
      ],
      "shape": "long"
     },
     {
      "id": "o4",
      "label": [
       {
        "t": "text",
        "v": "Audience nav helps users self-identify but can hide tasks; task nav surfaces actions but can miss self-image"
       }
      ],
      "shape": "long"
     }
    ]
   }
  }
 ]
}