UxFlowTaskCompletion [rule] v1.0.0

Before shipping any user-facing feature, walk through each primary task as a first-time user and confirm there are no confusion points, dead ends, or missing affordances — a flow that passes functional tests but leaves users confused has failed its core purpose.

Severity

block

Applies When

reviewing any user-facing feature or flow before release

Verify By

Perform the following for each primary task: (1) Start as if you have never seen the product before. (2) Follow only visual cues — no documentation. (3) Note every moment of hesitation, confusion, or backtracking. (4) Confirm you reached the success state.

Checklist

• Can a first-time user identify the primary CTA without any guidance?
• Are all required inputs clearly marked and explained before submission?
• Does every error state provide a clear resolution path?
• Can the user recover from any mistake without losing progress?
• Is the success state unambiguous — does the user know they are done?
• Does the back button / navigation work as expected at every step?

UxFlowTaskCompletion [rule] v1.0.0

Before shipping any user-facing feature, walk through each primary task as a first-time user and confirm there are no confusion points, dead ends, or missing affordances — a flow that passes functional tests but leaves users confused has failed its core purpose.

Severity

block

Applies When

reviewing any user-facing feature or flow before release

Verify By

Perform the following for each primary task: (1) Start as if you have never seen the product before. (2) Follow only visual cues — no documentation. (3) Note every moment of hesitation, confusion, or backtracking. (4) Confirm you reached the success state.

Checklist

• Can a first-time user identify the primary CTA without any guidance?
• Are all required inputs clearly marked and explained before submission?
• Does every error state provide a clear resolution path?
• Can the user recover from any mistake without losing progress?
• Is the success state unambiguous — does the user know they are done?
• Does the back button / navigation work as expected at every step?

Rationale

Functional correctness is necessary but not sufficient. A feature can be bug-free and still leave users lost, frustrated, or unable to complete their goal. Pre-ship UX review is the last filter before user harm.

Severity

block

Applies When

reviewing any user-facing feature or flow before release

Verify By

Perform the following for each primary task: (1) Start as if you have never seen the product before. (2) Follow only visual cues — no documentation. (3) Note every moment of hesitation, confusion, or backtracking. (4) Confirm you reached the success state.

Checklist

• Can a first-time user identify the primary CTA without any guidance?
• Are all required inputs clearly marked and explained before submission?
• Does every error state provide a clear resolution path?
• Can the user recover from any mistake without losing progress?
• Is the success state unambiguous — does the user know they are done?
• Does the back button / navigation work as expected at every step?