# UX artifact references

These are starting points for structure. Keep the artifacts compact and adapt them to the actual domain.

## JTBD

```markdown
# Job to Be Done

When [situation], I want to [motivation], so I can [desired outcome].

Current solution:
Pain points:
Evidence:
Open questions:
```

Use the underlying goal, not a requested control or screen.

## Domain brief

```markdown
# Domain Brief

Users / roles:
Situation and trigger:
Primary goal:
Current practice:
Workarounds:
Success signal:
Risks / error costs:
Assumptions:
```

## Use-case inventory

```markdown
| ID | Goal | Trigger | Frequency | Importance | Error cost | Scope |
|---|---|---|---|---|---|---|
```

Use frequency and importance together. Keep unusual high-risk tasks visible even when rare.

## User journey map

A journey map may use these columns:

```markdown
| Stage | User does | User needs / thinks | Friction | Opportunity | Evidence |
|---|---|---|---|---|---|
```

Only create emotional or cognitive claims when they are supported by the interview or clearly labeled as hypotheses.

## Task analysis

```markdown
# Task Analysis

Goal:
Preconditions:
Trigger:

1. User intent:
   Information needed:
   Decision:
   System support:
   Alternatives:

Branches / exceptions:
Failure and recovery:
Completion signal:
Open questions:
```

A task is an activity in service of a goal. A form, button, or screen is not automatically the goal.

## User flow

```markdown
# User Flow

Entry points:
Primary path:
Decision points:
Alternative paths:
Exit points:
Important states:
Recovery / undo:
Questions to validate:
```

The flow should be understandable before visual styling.

## Prototype brief

```markdown
# Prototype Brief

Question to answer:
User and scenario:
In scope:
Out of scope:
Required path:
States:
Realistic data:
Test tasks:
What would validate or falsify the direction:
```

## Usability-test structure

Use task-based prompts rather than asking whether the participant likes the design:

1. brief introduction and context
2. ask about the participant's work and goal
3. present a realistic scenario
4. ask the participant to complete 2–3 tasks
5. observe actions, detours, hesitation, misunderstandings, help requests, and errors
6. ask focused follow-up questions
7. close by asking what was missed and who else should be consulted

A useful prompt is: “Imagine that [situation]. Show me how you would [goal].”

Do not treat simulated users or AI critique as a replacement for real user observation.

## External references

- Nielsen Norman Group, “Task Analysis: Support Users in Achieving Their Goals”: https://www.nngroup.com/articles/task-analysis/
- 18F UX Guide, “Usability Test Guide”: https://github.com/18F/ux-guide/blob/master/_pages/resources/usability-test-guide.md
- GitHub `awesome-copilot`, `SE: UX Designer`: https://github.com/github/awesome-copilot/blob/main/agents/se-ux-ui-designer.agent.md
- Google PAIR, People + AI Guidebook: https://pair.withgoogle.com/guidebook/

These links are references, not mandatory tool or vendor choices.