Auditing a Settings Screen Against Nielsen's Heuristics
You're handed a settings screen for review before launch. It has: a "Delete Account" button that immediately deletes the account with no confirmation; a "Sync Now" button that shows no feedback while syncing (it just silently completes seconds later); labels using internal engineering terms like "Purge Cache" instead of "Clear Downloaded Data"; and a flat list of 30 settings with no grouping.
- Identify which specific Nielsen heuristic each of the four issues violates.
- For each, propose a concrete fix.
- Which one would you flag as highest priority to fix before launch, and why?
1 & 2. Heuristic violated and fix, per issue
- "Delete Account" with no confirmation violates error prevention (heuristic #5) — an irreversible, destructive action has no safeguard against an accidental tap. Fix: require an explicit confirmation step (a dialog that names the consequence, e.g., "This permanently deletes your account and cannot be undone"), and ideally require typing the account name or a similar deliberate action to proceed, matching the severity of the consequence.
- "Sync Now" with no feedback violates visibility of system status (heuristic #1) — the user has no way to know sync is happening or when it finishes. Fix: show a spinner or progress indicator immediately on tap, and a brief confirmation ("Synced just now") on completion.
- "Purge Cache" jargon violates match between system and the real world (heuristic #2) — "purge" and "cache" are engineering terms, not concepts a typical user has a mental model for. Fix: rename to user-facing language describing the actual effect, e.g., "Clear Downloaded Data (frees up storage)."
- Flat list of 30 settings violates aesthetic and minimalist design (heuristic #8) and works against recognition rather than recall (heuristic #6), since users must scan the whole list to find anything rather than recognizing a labeled group. Fix: group related settings under labeled sections (Account, Notifications, Privacy, Data & Storage), with progressive disclosure for advanced or rarely used options.
3. Highest priority
The "Delete Account" issue is highest priority, because it's the only one of the four with an irreversible, high-severity consequence — a user who accidentally deletes their account cannot undo it, versus the other three issues, which are annoying or confusing but recoverable (a jargon label can be misread and corrected, a missing sync indicator causes uncertainty but not data loss, a flat list causes friction but not harm). When issues compete for limited pre-launch time, severity of consequence — not just heuristic violated — should drive prioritization, and destructive actions without confirmation are the category most likely to cause real, unrecoverable user harm.
Share this question