Settings and preferences brief
Structure settings so ownership, scope, defaults, dependencies, and the consequences of change are clear.
Product features · 45 min · Advanced · 20 questions
Ownership and scope
Who may view each setting?
Who may change each setting?
Whose experience does each setting affect?
What does each setting apply to?
Which default applies to new entities?
Which default applies to existing entities?
What evidence supports those defaults?
Which inherited value takes precedence?
When may a local value override an inherited value?
How should a locked policy appear?
Change behavior and governance
When should a setting take effect?
Which setting needs a consequence preview?
Which setting needs explicit confirmation?
Which setting requires reauthentication?
Which change needs a reversible grace period?
Which setting enables another setting?
Which change invalidates another setting?
How will users find a setting they need to change?
Which prior setting changes should users see?
How will users know who changed a setting?
How to use this brief
Use this brief as a bank of questions for the conversation. Choose what is relevant, mark covered questions as you go, and skip anything that has already been answered.
Use this brief when...
Use when you need to structure settings so ownership, scope, defaults, dependencies, and the consequences of change are clear.
Best used as: Live call · Async intake
- Category
- Product features
- Discussion time
- 45 minutes
- Depth
- Advanced
- Last updated
- Jul 21, 2026
- Scope
- Design briefs
- Best used as
- Live callAsync intake
- Design roles
- Product designer
- Audience
- Product designersProduct managersUX and UI designersDesign leads
- Platforms
- WebMobileCross-platform
- Company type
- B2BB2CEnterprise
- Product stage
- GrowthMature product
- Tags
- product-featuressettings-and-preferencessystems-and-platformsaccount-configurationworkspace-administrationpersonal-preferences