Think average reading time to reduce story length
I am, sadly, monolingual, so I am not able to read 20 minutes, a free commuter newspaper published in Geneva and Lausanne, Switzerland.
But that doesn’t mean I couldn’t appreciate it.
20 minutes lets readers know in its title how much time they’re likely to read the piece. In other words, it reports average reading time, or A.R.T.
If your piece is short enough, reporting A.R.T. may increase readership. Readers who had planned to put your piece in the pile of things “to read later” — aka the rest stop on the way to the trash can — may say, “Geesh, surely I can spend two minutes on this now.”
Here’s how to establish, measure, manage and report A.R.T. on your own pieces.
1. Establish A.R.T.
Writers measure the length of their messages in words, inches or pages. Readers use a different measure: time. So instead of using writer-centric measures, think like your reader.
Rather than asking, “How many words should this be?” ask, “What’s a reasonable amount of time to expect someone to spend reading this piece?”
Roy Peter Clark, Poynter Institute senior scholar, estimates that most people can read about 200 words a minute. So to fulfill the promise it sets up in its flag, 20 minutes needs to be no more than about 4,000 words long.
So before you hit the keyboard, determine how much time you’d expect readers to spend reading each piece you write or assign and multiply that time, in minutes, by 200.
So if you are aiming for a one-minute release, you’ll want to limit it to 200 words.
And if your audience members aren’t likely to spend more than 15 seconds on your check-stuffer, you’re looking at a 50-word piece.
Beware: We tend to overestimate how much readers are willing to read.
How much time are they willing to spend? For instance, employees participating in a London study, for instance, spent only about two minutes reading their own CEO’s message. The longest message — Lloyd’s of London’s, at 872 words — actually got less reading time than the shorter two, from GE and Heinz, at about half that length.
As a recent PRSA Strategist article on employee communications was called:
They’re Just Not That Into You
How much time can you afford to have them spend? Also consider how much time you’d want readers to invest in learning this information.
After all, if you’re producing employee communications, your readers have to take time off from working to read your piece. How much staff time are you willing to dedicate to getting the word out?
Let’s say it takes each employee two minutes to read your 400-word story. Now run the math:
Is that a reasonable investment? Or would a 200-word, one-minute story make more sense?
2. Measure A.R.T.
During the editing process, divide your total word count by 200 to find out how many minutes it will take the average reader to get through your piece.
So if your piece is 400 words long, it will take two minutes to read.
Is that too long? If so, you’ll need to …
3. Reduce ART.
You might find that it makes sense to cut your piece to save your readers time.
4. Report A.R.T.
If your piece is short enough, reporting A.R.T. may increase readership. So tell ’em how long it’ll take to tell ’em.
This approach is trending:
- 20 minutes reports ART in its name.
- So does “Take Five,” the twice-monthly email newsletter for Bank of America employees.
- “Humor Power Tips,” an e-zine by speaker John Kinde, reports at the top of the issue: “Word count: 350 words; Reading time: two minutes.”
Saint Luke’s Health magazine promises readers that they’ll learn about a health topic in two minutes with one of the health system’s experts.
And when two minutes is just too long, Fast Company’s “60 Seconds” introduces readers to a tastemaker in just a minute.
How can you report A.R.T.?
Let your readers know at the beginning of each piece — and maybe even in your title or headline — how long it should take them to read it.
A.R.T. for this piece:
- Word count: 800
- Average reading time: 4 minutes
Source: Sandra Oliver, “Message from the CEO: a three-minute rule?” Corporate Communications: An International Journal, vol. 5, no. 3, 2000, pp. 148-167