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
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
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.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Create an information architecture and menu tree
Organize cluttered navigation items into a logical, task-oriented app menu hierarchy. Ideal for product redesigns and software cleanup.
Plan a wireframe content hierarchy before sketching
Define section order, content goals, and component weighting for a single screen before drawing layouts. Use it to align stakeholders on layout intent first.
Build a content-first wireframe specification
Generate a structured wireframe copy specification with strict character counts and layout hierarchy before visual design begins.
Check UI microcopy for text expansion risks
Review interface copy to catch overflow, truncation, and layout breaks before sending strings to localization teams.
Triage conflicting design feedback by user impact
Turn contradictory stakeholder notes into an objective tradeoff matrix with clear decisions. Use it when design reviews stall over opposing priorities.
Write focused critique questions before a design review
Generate specific discussion prompts that keep reviewers focused on user flows and system usability rather than personal aesthetic taste.
- Audit and Rewrite UX Error Messages for User Recovery
- Create Accessible Keyboard Navigation Maps for Complex Web Layouts
- Structured Design Critique and Feedback Framework
- Audit desktop layouts for responsive mobile collapsing
- Run a SCAMPER brainstorm on a stuck feature
- Turn user interview quotes into an empathy map