Seven Signs Onboarding Has Broken the Original Promise

Trace the promise from decision to first recoverable outcome

Capture the offer, checkout, confirmation, welcome sequence, first-use tasks, status messages, help, and common recovery paths for the same product version and audience. Write what a reasonable customer may expect, then record what the service actually requires and communicates. Diagnose the transition, not an isolated screen.

Classify each sign as observed, not observed, or unresolved. Repeated support reports can identify an area to inspect but do not by themselves prove design failure. Do not invent transactions or expose customer data. This framework is not a legal or accessibility conformance audit.

Evidence: GOV.UK Design System; UK Government Digital Service; UK Financial Conduct Authority

Sign 1: the customer cannot tell what completed

A receipt, status, reference, or success heading is absent or contradictory. The button changes but the customer does not know whether payment succeeded, an application was submitted, access is active, or another action is required. Duplicate attempts and repeated charges can follow ambiguous state.

Compare the displayed state with the transaction or workflow record. Check pending, duplicate, failure, and delayed cases, not only the happy path. Correct the confirmation language and provide an appropriate record and immediate next action.

Evidence: GOV.UK Design System; UK Government Digital Service

Sign 2: material prerequisites arrive only after commitment

Required equipment, identity documents, compatible software, language, schedule, recurring work, extra purchase, or skill appears in onboarding but was missing from the decision page. The issue is especially serious when the prerequisite changes fit, total cost, timing, or the ability to use the service.

Map each requirement to its first disclosure and operational owner. If it was material before purchase, repair the sales content and review affected customers; do not treat a better tooltip after payment as the complete fix. Distinguish a newly introduced requirement from one that was merely difficult to find.

Evidence: UK Government Digital Service; UK Financial Conduct Authority

Signs 3 and 4: progress is decorative and help is difficult to reach

Sign 3 appears when progress bars, “almost done” messages, or exact times are not tied to meaningful states, or when the next owner is unclear. Sign 4 appears when support location, channel, hours, response expectation, reference, or escalation changes unpredictably across pages. Customers repeat work or open multiple contacts because status and recovery are not usable.

Trace the underlying event for each message and compare help placement across the page set. W3C consistent-help guidance informs the accessibility perspective, while GOV.UK service materials inform support design. Neither proves that the observed service violates a standard.

• Status has no supporting event.
• Estimate ignores an uncontrolled dependency.
• Help moves or disappears across steps.
• Escalation is unknown for a blocked transaction.

Evidence: GOV.UK Design System; UK Government Digital Service; W3C Web Accessibility Initiative

Sign 5: the recovery path fails for the customer who needs it

Keyboard focus is trapped, error text lacks instruction, captions or language support disappear, uploaded work is lost, identity recovery requires inaccessible media, or the only alternative repeats the failed channel. A nominal support link is not recovery when the customer cannot use it.

Review representative accessibility and interruption modes with appropriate expertise. Preserve completed work where possible and give a non-digital or assisted route when required. Record the barrier, affected task, evidence, workaround, owner, and target date without claiming comprehensive conformance.

Evidence: UK Government Digital Service; W3C Web Accessibility Initiative

Sign 6: onboarding quietly rewrites the sales promise

The welcome path introduces a different product, narrower access, longer timing, greater effort, changed support, automatic renewal, or outcome limitation that conflicts with the offer. Friendly expectation-setting language may mask the contradiction. Compare exact versions and terms rather than relying on memory.

Stop treating the discrepancy as training. Resolve which statement is accurate, correct the source and downstream messages, preserve the reason, and address customers who made a decision under the old impression. Escalate legal or consumer-rights implications.

Evidence: GOV.UK Design System; UK Financial Conduct Authority

Sign 7: recurring expectation gaps never change the source

Support teams repeatedly explain the same prerequisite, status, billing, access, or timing issue, but the onboarding and sales owners receive no structured signal. Ticket closure becomes the metric while the cause persists. Another warning is feedback collection without a route, threshold, decision, or correction date.

Build an expectation-gap log with customer language, journey point, promise source, operational evidence, frequency, impact, owner, remediation, and recheck. Correct the earliest responsible artifact and retest dependent paths. Recheck by 2027-02-10 or after offer, workflow, support, accessibility, or terms changes.

Evidence: UK Government Digital Service; UK Financial Conduct Authority; W3C Web Accessibility Initiative