Newsletters Worth Opening Every Week
We unsubscribed from almost everything last spring. These are the newsletters that earned their way back in.
Every studio accumulates habits it never chose. Once a year we list them and ask whether each one still earns its place.
The first version of anything is a question, not an answer. Treating it that way makes feedback easier to give and much easier to hear.
The finished piece rarely looks like the plan. That is fine; the plan was only there to get us started.
The part nobody mentions
We keep a running document of things that went wrong on past projects. It is not a list of failures so much as a list of warnings, and we read it before every kickoff.
- Start with the problem, not the tool
- Test with real content, never lorem ipsum
- Show work early and often
- Keep the version that failed
Typography exists to honor content.
Robert Bringhurst, The Elements of Typographic Style
Small improvements compound. A page that loads a little faster, a heading that reads a little clearer, and a form with one fewer field all add up.
Most of the improvement in a draft comes from cutting. We aim to remove a fifth of every piece on the second pass, and the reader never misses it.
We keep a running document of things that went wrong on past projects. It is not a list of failures so much as a list of warnings, and we read it before every kickoff.
Constraints are underrated. A fixed word count, a single typeface, or a two-colour palette forces decisions that an open brief lets you postpone forever.
Related posts
How to Edit Your Own Work Without Hating It
A practical checklist for the second, third, and fourth pass.
The Case for Writing Badly First
Why the fastest route to a good draft runs straight through a terrible one.
Ten Books That Changed How We Edit
A reading list for anyone who has ever stared too long at a paragraph.
Comments · 12
I disagree slightly on the second point, but the rest is spot on. Constraints really do help.
Good question. We will cover that in a follow-up soon.
Agreed, that part surprised us too.
Good question. We will cover that in a follow-up soon.
Yes! Same experience here.
The quote at the end made my day. Sharing this with the whole team.
Small typo in the third paragraph, but otherwise a perfect read with my morning coffee.
Thanks so much! Let us know how it goes.
Do you have a recommendation for someone just starting out? Everything I find assumes years of experience.
Bookmarked. I keep coming back to your posts whenever I get stuck.
Thank you for including the code. I adapted it for our docs site in about ten minutes.
Such a clear explanation. I finally understand why our pages felt sluggish on mobile.