Paths for new and expert users

Expert & First-Time User Paths

A great product neither abandons first-time users in front of a blank screen nor forces experienced daily users to click through slow, patronizing onboarding wizards on every task.

Workflow

1. Make first-time and empty states actionable, not decorative:
   • When a workspace, project, or list is empty, show:
     • What this view is for in one clear sentence.
     • One direct primary action to create the first item or start from a realistic template/example.
   • Avoid multi-step modal product tours that force users to click "Next -> Next -> Got it" before they have even seen the workspace; use contextual inline guidance at the moment of action instead.
2. Build fast lanes (accelerators) for experienced users (Nielsen):
   • Ensure daily workflows stay fast after the 100th use:
     • Keyboard access & shortcuts: Preserve native control behavior and consistent focus/escape paths. Add shortcuts or a command palette only when actual repeated tasks justify them; avoid conflicts with text entry and platform shortcuts.
     • Remembered preferences & recent picks: Default to the last-used project, filter view, or model selection where appropriate.
     • Direct & bulk actions: Use direct actions to remove demonstrated repetition. Add multi-select operations only for a real batch workflow, with clear affected-item scope, permission checks, and partial-failure feedback.
3. Prevent novice-help from cluttering expert views:
   • Keep permanent helper copy concise (1 line or a subtle info popover) so repeat users can scan dense tables, boards, and logs without scrolling past paragraphs of instructions.
   • Coordinate keyboard navigation and focus management with the accessibility specialist (A11y).

Handoff & Acceptance

• Deliver first-time and repeat-use paths for the same representative task, with entry state, primary action, visible completion evidence, and recovery from an error or cancellation. Identify the repeated friction each accelerator removes.
• Walk both paths, including keyboard-only use: a newcomer can start from an empty state and recognize completion; a returning user reaches the task directly without repeating onboarding. Check remembered choices are still valid and permitted. Report observed obstacles and remaining assumptions rather than claiming usability from a diagram alone.