Content design brief
Design product language around the user's situation, decision, and path to recovery.
Product features · 45 min · Standard · 17 questions
User context
What situation is the user in?
What does the user already know?
What emotion could affect comprehension?
How urgent is the user's task?
What should the content help the user do?
Language and hierarchy
Which term will users recognize?
Which internal term conflicts with user language?
What must the user understand first?
Which consequence of the user's choice must the content state explicitly?
How should the tone change in a stressful moment?
What meaning must remain clear without visual styling?
Recovery and governance
What should an error message help the user do next?
Which phrase may fail when translated?
Which local format must the content support?
Which statement requires legal approval?
Who owns the content after release?
What event should trigger a content review?
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 design product language around the user's situation, decision, and path to recovery.
Best used as: Live call · Async intake
- Category
- Product features
- Discussion time
- 45 minutes
- Depth
- Standard
- Last updated
- Jul 21, 2026
- Scope
- Design briefs
- Best used as
- Live callAsync intake
- Design roles
- Content designer
- Audience
- Product designersUX and UI designersDesign leadsFreelancers and consultants
- Platforms
- Cross-platform
- Company type
- StartupB2BB2CEnterprise
- Product stage
- Early-stageGrowthMature product
- Tags
- product-featurescontent-designproduct-and-experiencecontent-designproduct-languagecontent-governance