Cognitive ux

Cognitive UX Router

Choose a specialist by the person’s primary job, not the industry label. A travel marketplace may need Marketplace + Travel; a patient portal may need Portal + Health. Start with the task that carries the greatest consequence if it fails.

Intake

Identify:

• Primary user, job story, context, device, accessibility needs, and consequence of failure.
• One primary outcome: understand/act, evaluate, buy, compare, reserve, learn, read, solve a problem, monitor/decide, complete work, set up, submit data, participate, manage an account, donate, manage care, manage money, travel, administer, access public service, or apply for a job.
• Secondary outcomes only if they independently alter the information architecture, risk, or validation plan.

Route

Read archetype map, select one primary skill, then state the selection and its rationale. Use one secondary skill only when it changes the task model. Never mix every checklist into one generic page.

Common contract

Every specialist skill must return:

1. User/job/context assumptions and a primary path plus recovery/edge paths.
2. Information architecture and attention hierarchy.
3. Accessible interaction and component behavior.
4. Evidence-to-decision ledger with source, label, limitation, and test metric.
5. Dark-pattern and high-stakes safety review.
6. Representative-user validation plan.

Use Standard / requirement only for a cited normative source, Evidence-informed default for relevant but contextual evidence, and Hypothesis to test for an unproven choice. Never invent an attention-span statistic, research claim, accessibility compliance result, or conversion guarantee.