Design a Progressive Disclosure Pattern for Complex Settings

Receive a structured layout strategy for grouping advanced software settings into primary and hidden tiers to reduce user cognitive load and interface clutter.

Prompt

Prompt
Act as a Senior UX Designer. I need to design a progressive disclosure pattern for a complex settings dashboard. Please ask me these 3 questions first: 1. What is the primary user goal of the settings page? 2. What are the top 3 most frequently adjusted settings? 3. Are there any settings that are high-risk or destructive if changed? Once I answer, propose a layout that follows these rules: 1. Place the top 3 settings in the primary, always-visible view. 2. Group secondary settings into a collapsible 'Advanced' section. 3. Use an 'Advanced' toggle that clearly indicates what is hidden. 4. Ensure high-risk settings are only accessible behind a confirmation modal, not just a toggle. Output format: Section 1: Information Architecture list. Section 2: Layout Rationale. Section 3: Interaction Rules for the Advanced toggle. This is not professional UI/UX consulting; test these patterns with real users to validate usability.

Example output

Example for: A cloud storage file synchronization application. Section 1: Information Architecture 1. Primary View: Sync Destination Folder, Sync Frequency (Real-time/Scheduled), Bandwidth Throttling. 2. Advanced Section: LAN Sync, Ignore File Patterns, Proxy Server Configuration, SSL Certificate Verification, Temporary Cache Limit. Section 2: Layout Rationale The primary view addresses 90% of user needs immediately upon opening the settings. By prioritizing the sync destination and frequency, we minimize the time to productivity. The 'Advanced' section groups technical configurations that require specific domain knowledge, preventing novice users from breaking the sync connection. Section 3: Interaction Rules for the Advanced Toggle 1. The 'Advanced' section defaults to the closed state. 2. Clicking the 'Show Advanced Settings' button expands the container with a smooth vertical slide animation. 3. Any change to 'Proxy Server Configuration' inside the Advanced section triggers a modal window requiring the user to click 'Save and Reconnect' to prevent accidental loss of connectivity. 4. High-risk settings like 'Clear Local Cache' are placed at the bottom of the Advanced list with a red button style to signify destructive action. This design ensures the interface remains clean for general users while maintaining power for technical administrators.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Forces a clear hierarchy between essential and expert-only settings.
  • Ensures high-risk actions are protected by specific interaction rules.
  • Provides a logical layout structure that is easy to implement in code.

Use this to organize dense configuration screens in SaaS or enterprise tools. Works best in ChatGPT, Claude, or Gemini. Paste the prompt, answer the 3 questions, and the model will generate the architectural breakdown.

Common edits

  • Add a search bar rule if the settings list exceeds 15 items.
  • Specify if the Advanced section should persist its open state across sessions.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Design