SuccessMessageNextStep [rule] v1.0.0

Every success or confirmation message must state what action completed AND offer a clear next step or navigation option — never just 'Done' or 'Success'.

Severity

warning

Applies When

writing feedback copy for completed actions, saved states, or successful submissions

Verify By

Check that the message (1) names the completed action, and (2) offers a logical next step or navigation path.

SuccessMessageNextStep [rule] v1.0.0

Every success or confirmation message must state what action completed AND offer a clear next step or navigation option — never just 'Done' or 'Success'.

Severity

warning

Applies When

writing feedback copy for completed actions, saved states, or successful submissions

Verify By

Check that the message (1) names the completed action, and (2) offers a logical next step or navigation path.

Examples

• Email verification: 'Email confirmed. You can now sign in →' — names the event + guides forward.
• Payment: 'Payment of $49 received. Your receipt is on its way.' — confirms what + sets expectation.
• Form save: 'Draft saved. Preview your listing →' — confirms + actionable next step.
• Bad: 'Success!' — no context, no direction.
• Bad: 'Done.' — vague; what is done? what should I do now?

Rationale

Bare confirmations leave users uncertain about system state and what to do next, stalling their flow. Users who don't know what happened next either repeat the action, explore randomly, or abandon.

Severity

warning

Applies When

writing feedback copy for completed actions, saved states, or successful submissions

Verify By

Check that the message (1) names the completed action, and (2) offers a logical next step or navigation path.