The Scenario
A fintech app has 4 content designers who all write differently. One is formal ("Your transaction has been processed"), another is casual ("Done! Money sent 🎉"). The product feels inconsistent. The team needs a content design system.
The Brief
Build a voice and tone guide plus a UX writing pattern library. The system should ensure consistency without killing personality.
Deliverables
- A voice definition: 3-5 voice attributes with a spectrum (e.g., "Confident, not arrogant")
- A tone variation guide: how the voice adapts across contexts (success, error, neutral, celebration)
- A pattern library with templates for: CTAs, confirmation dialogs, empty states, error messages, and loading states
- A "this, not that" reference table with 10 before/after examples
Submission Guidance
Voice is consistent (who we are). Tone varies by context (how we sound right now). A fintech can be friendly on a success screen and serious on a payment error. Show this range.
Submit Your Work
Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.