298 catalog entries 298 documented patterns 897 evidence sources

UX pattern selection checklist

Use this before design review, frontend implementation, or AI-generated UI. It helps teams choose a pattern from the person's task, the service state, and the consequence of a mistake.

Run the checklist Open pattern lab

Worked decision

A clinic check-in confirmation

A patient taps Check in at a kiosk. The kiosk receives the request while the appointment service records arrival a few seconds later. The design decision is the message the patient sees during that interval.

Strong reasoning

Map the pending and received states, use a status pattern during the handoff, then show a receipt-backed confirmation after the appointment service records arrival. Test whether patients understand the difference.

Weak reasoning

Place a generic Done message after the tap. The screen suggests completion while the service still has a pending handoff, so patients seek a second confirmation from staff.

Use the checklist to connect task, risk, alternatives, states, accessibility, and evidence. Study success confirmation →

The decision method

Start with the task and risk. Choose the pattern only after the context is clear.

Frame the task Name the user goal, risk level, reversibility, platform, and interruption cost.
Compare plausible patterns Use nearby alternatives to choose the pattern that best fits the task.
Define the state contract Plan empty, loading, error, disabled, success, keyboard, focus, and recovery behavior.
Reject known misuses Check anti-pattern conditions before the design reaches implementation.

Pattern readiness scorecard

Check each item that is already true. Aim for 8 before implementation starts.

User task is clear The review starts with the task, decision, or risk the user needs to handle. Write the task in one sentence before naming a component. Risk level is clear The team knows whether a mistake is minor, costly, destructive, private, or safety-related. Tag the flow as low, medium, or high consequence. Recovery path is clear The choice accounts for undo, cancel, edit, draft, recovery, and audit needs. State what happens if the user changes their mind. Alternatives were compared The chosen pattern beat plausible alternatives instead of winning by familiarity. Compare at least two patterns before implementation. Required states are listed Empty, loading, error, disabled, success, keyboard, focus, and recovery states are planned. Add missing states to the implementation brief. Accessibility contract is testable Labels, roles, focus order, contrast, keyboard support, and announcements can be verified. Turn accessibility needs into review checks. Known misuses are rejected The team has checked whether the design matches common anti-pattern conditions. List at least one misuse that would make this pattern wrong. Evidence is linked Guidance points to source-backed claims, platform conventions, or observed product behavior. Link the pattern choice to sources or catalog entries.

How to interpret the score

Use the score to locate the next design question. High-consequence flows need a complete state plan, accessibility checks, and evidence before implementation.

0-2

Define the task

Write the person's goal, consequence, and context before choosing an interface pattern.

3-5

Clarify the design

Compare alternatives and specify the states, access needs, and recovery route.

6-7

Complete the review

Resolve the remaining question and record its owner before implementation.

Ready to build

The choice has a clear task, state plan, rejection criteria, and source trail.

Copyable review prompt

Use this in design reviews, issue templates, PR descriptions, or AI prompts.

Use this UX pattern selection checklist before designing, implementing, or prompting AI to generate UI:

1. Name the user's task in one sentence.
2. State risk level, reversibility, platform, and interruption cost.
3. Compare at least two plausible patterns before choosing one.
4. List required empty, loading, error, disabled, success, keyboard, focus, and recovery states.
5. Reject the choice if known anti-pattern conditions match the flow.
6. Link the decision to source-backed guidance or a catalog entry.

Decision output:
- Selected pattern:
- Alternatives rejected:
- Required states:
- Accessibility checks:
- Evidence links:
- Review blockers:

Compare patterns

Cite this resource

Use the direct checklist URL when referencing it from articles, course notes, issue templates, or design-system docs.

Citation

UX Patterns Guide. "UX Pattern Selection Checklist." https://uxpatternsguide.com/resources/ux-pattern-selection-checklist/

Share summary

A practical UX pattern selection checklist for design reviews, frontend tickets, and AI-generated UI:
https://uxpatternsguide.com/resources/ux-pattern-selection-checklist/

It helps teams check task fit, risk, required states, accessibility, anti-patterns, and evidence before choosing a UI pattern.