Professional review status
No professional domain review recorded
This bundle covers privacy, safety subject matter. It uses cited sources to support research, but it is not professional advice and should not be the sole basis for consequential decisions.
Review before reliance: A qualified UX, accessibility, privacy, safety, or domain professional appropriate to the product, users, and jurisdiction.
Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.
Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Role guide
UX Designer Role Guide
Record request, intended decision, audience, organization, jurisdiction, date, role charter, delegation, evidence supplied, constraints, owner, approver, and reviewer.
Read the fileOverview
Overview
UX Designer is a role archetype whose mandate varies by organization, level, industry, jurisdiction, operating model, and local charter.
Read the fileQuality rubric
UX Designer Quality Check
- No fabrication: invents no user group, task, context, research consent, findings, product state, content, flow, interaction, accessibility evidence, analytics, constraints, risk, owner.
Read the fileBundle file
UX Designer Review Workflow
1. Record the request, intended decision, audience, scope, jurisdiction, date, evidence, and authority. 2.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting UX Designer work, plus teams reviewing its decisions and outputs
- Teams working in digital products, government services, financial services
When to use it
- An UX Designer task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- frame an UX problem
- synthesize usability evidence without inventing users
- prepare design rationale and handoff with clear ownership
What it helps produce
- UX problem and evidence brief
- information architecture and flow review
- usability and accessibility findings brief
- design rationale and handoff brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach UX Designer work by producing UX problem and evidence brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Details / 15 1255.00, then confirm that the reference is current and applicable. Inspect UX Designer Role Guide before drafting.
Context path: bundles/roles/ux-designer
What the bundle includes
Frameworks
- user-task-context evidence map
- flow and usability issue ledger
- design-decision handoff matrix
Evaluations
- UX Designer quality check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Role-support only; local mandate, evidence, ownership, access, decision rights, and professional conclusions require verification.
- Source frameworks do not establish organization-specific facts, compliance, outcomes, or authority.
- This bundle does not grant authority to contact participants, access recordings or analytics, publish research, change production designs, alter eligibility or policy, reprioritize roadmaps, certify accessibility, or deploy.
Safety notes
- Protect sensitive personal, customer, employee, commercial, security, research, financial, and unreleased information.
- For every material claim, record source, date, version, scope, status, owner, uncertainty, and missing evidence.
- Require explicit confirmation before you contact participants, access recordings or analytics, publish research, change production designs, alter eligibility or policy, reprioritize roadmaps, certify accessibility, or deploy.