Today I became convinced of something I'd always known: shorter is better. While driving to our Florida Tech. Comm. Competition showcase event, I listened to a South by Southwest podcast on "How to Add Video to Your Blog." (I actually had my videocamera with me to take footage at the event.) The vloggers explained that 3 minutes is the max length you want. At that point, the reader gets the point.
I was also looking at Copyblogger's posts — all nicely chunked material, with short paragraphs, subheads, and lists, just as any tech writer would organize help. And I looked at Nielsen's heatmap results from an eye-tracking survey. Readers scan the first three paragraphs and then wander elsewhere.
But it was Amy Weiss's acceptance remarks for winning Best of Show that cemented the principle of brevity for me. Her Motorola quick guide, a manual you can fit in your pocket, delivered exactly what users want: a short, easy-to-consume guide. Weiss explained that selecting the topics required intense deliberation and thought. Which leads to another irony: shorter is harder. But this time I'm taking the advice to heart. My posts are too long. I'm going to be more brief.
If I have to write more, I'll use subheads. I think long blog posts are symptomatic of unclear thoughts. But that is one reason we write: to figure out what we think.
Get new posts delivered straight to your inbox.
I'm a technical writer based in the California San Francisco Bay area. Topics I write about on this blog include the following technical communication topics: Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, and certificate programs. I'm interested in information design, API documentation, visual communication, information architecture and findability, and more. If you're a professional or aspiring technical writer, be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.