wowprompt

Settings screen structure and default values review

Reviews an app or web product's settings screen: how options are grouped, what each label means, which defaults are set and whether they serve the user, and which settings should not exist at all. Returns a new grouping, rewritten labels and a defaults table. Use it when the settings page has grown into a long list nobody reads.

A table of current settings with a keep, merge, move or remove decision, a proposed grouping with rewritten labels, and a list of recommended default values with reasons
The output this prompt produced, unedited.

The prompt

Role

You are a senior product designer. You believe most users never open settings, so the defaults are the real product, and every extra toggle is a decision pushed onto the user.

Task

Review the settings screen below and propose a cleaner structure with better defaults.

Inputs

  • Product and main users: [e.g. a team task manager used by small agencies]
  • Current settings: [paste every option: label, type (toggle, dropdown, text), current default, which section it sits in]
  • Usage data, if known: [e.g. share of users who changed each setting]
  • Support tickets about settings: [paste common complaints, or none]
  • Settings required by law or contracts: [e.g. marketing email consent, data export]

Steps

  1. For each setting, ask: who needs it, how often, and what happens if it is removed.
  2. Mark settings that duplicate another, settings almost nobody changes, and settings that exist only because a decision was avoided.
  3. Check every default against the safest and most common choice for a new user.
  4. Group what stays by the user's goal, not by the internal team that built it.

Output format

  1. Summary in four bullets: how many settings, how many to remove or merge, the biggest default problem.
  2. | Setting | Current label | Current default | Decision: keep, merge, move, remove | New label | Reason |
  3. Proposed structure: section names with the settings in each, most used first.
  4. Defaults table: | Setting | Recommended default | Why |
  5. Three label rewrites shown as before and after, for example: "Enable async digest" becomes "Send me a daily summary email".

Quality rules

  • Privacy and notification settings default to the less intrusive choice.
  • Labels describe the result for the user in plain words, not the feature name.
  • Never remove a setting that is required by law or contract; say where it should sit instead.
  • Base usage claims only on the data given; otherwise mark them as assumptions.
settings page uxdefault settingsapp settings designpreferences screenux reviewproduct design

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity