Neon Digital Playbook

Appearance

UX Principles ​

Neon software must respect the user’s time, attention, and mental model. These principles guide decisions at every level—from layout to workflow.

Start With the User’s Job ​

  • Design around the tasks users actually perform
  • Avoid forcing users to understand internal system structures

Reduce Cognitive Load ​

  • Fewer decisions, clearer paths
  • Defaults that make sense
  • No hidden surprises

Preserve Momentum ​

  • Users should not lose context or data when errors occur
  • Flows should continue forward, not reset or dead-end

Feedback Is Mandatory ​

  • Every action must show a result: success, failure, or progress
  • Errors explain what went wrong and what to do next

Predictability Over Cleverness ​

  • Controls behave like similar controls elsewhere
  • Patterns reused unless there's a compelling reason not to

Minimal Friction ​

  • Fewer clicks when possible
  • Avoid unnecessary forms, modals, confirmations

Safety First ​

  • Users should not fear breaking things
  • Non-destructive actions should be undoable or reversible

Consistent Components ​

  • Use shared UI components and design tokens
  • No bespoke elements unless patternised

The Neon UX Test ​

A feature passes when:

A user can complete their task on the first attempt without thinking.

If they hesitate, the UX has failed.