Prose
Long-form typography for articles and case studies: Funnel Sans at 18 to 19px on a 68-character measure, Instrument Serif headings, pull quotes, lists with moss markers, figures, code, tables and a rule.
People open settings when something has gone wrong. The bill was higher than they expected, a teammate can see what they shouldn't, or the emails won't stop.
That makes settings the most emotional screen in most products, and the one we design last. Here's what changed when we wrote every setting as a promise about what will happen, not as a label for a switch.
Write the sentence, then the switch
Before drawing anything, I write every setting as one plain sentence: "Send me an email when an invoice fails." If I can't write the sentence, the setting isn't ready.
- Say what will happen, in the words a customer would use.
- Say who it affects: only you, or the whole team.
- Say when it takes effect, and whether it can be undone.
The best settings page is the one people leave sure of what they changed.
Group by the job, not the database
Saltmarsh had eleven pages named after tables in their schema. We moved to four pages named after jobs: your account, your team, billing and notifications. Search for a setting with / anywhere.
Next: the same idea applied to error messages.