Thursday, December 29, 2011

Stories vs. articles

I tweeted this last night, and a couple people (Kate Harmon and Chris Dunn) already responded, picking out favorite parts of an interview with Ben Montgomery of the St. Petersburg Times.

There's a lot of great stuff here and it'd be tough for me to pick a favorite line or whatever. But one thing that resonated with me was that early on in his career, he said, he "quickly came to understand that I wanted to do stories, not articles." And he set out to get to a place and a position in which he could do that, and did.

Almost all of us start out doing articles, or the equivalent of them in whatever job we have. If you really want to do stories instead of articles, it'll take a lot of hard work and a lot of feeling like you'll never have the time to do stories because you're doing articles, but don't stop trying. Stories are the thing.

Here's more on Ben.

Wednesday, December 7, 2011

Roy Peter Clark on writing complicated stories with clarity

Poynter's Roy Peter Clark guided us through a list of great tips on how to make a complicated story easy to read and understand during the last of NewsU's series of writing webinars this afternoon.

They're so good I'm going to list them all here (my notes from Clark's powerpoint). You can also see his webinar at (see me for access):

  • Use shorter words, phrases, sentences and paragraphs at the point of greatest complexity (from writing coach Donald Murray). You have to report well to do this effectively. But the point is: Guide people through the heavy stuff with your writing choices.
  • Slow the pace of information. Use periods to make the reader pause, at which point he/she can absorb information before moving on.
  • Translate jargon. Kind of self-explanatory. But basically, you don't need to use the same specialized language your source does in order to help your reader understand.
  • Lift numbers and technical info out of text and convey it in images (graphics, breakout boxes).
  • Engage readers in conversation. Blogs, social networks, etc. You'd like to get to the point where you know what language your readers are comfortable with.
  • Find a microcosm -- a small example that represents a larger reality. Clark gave the example of a New York Times reporter who told the story of 9/11 by focusing on one person, because the overall story was too big.
  • Introduce difficult concepts one at a time. I like this at the story level, but also at the sentence level. I think a lot of times we think we have to introduce several facts or concepts in one sentence, because they're related. But (see above) use the period and give readers a chance to absorb one piece of info, then the next, then the next.
  • Reward readers with high points. As Clark puts it, "gold coins" sprinkled throughout a story tell the reader, "Thanks for coming this far. Here's your reward. Keep going."
  • Keep boring parts short. Be selective. Use your best stuff. Self-edit and cut 10-20 percent of your text.
  • Assume responsibility for what readers learn. Can the reader ID the most important points of the story, pass that info on to another person, or pass a test on the main points?
  • Watch the separation of subjects and verbs. The further apart they are, the less understandable the sentence will be.
Terrific teaching, as usual, from Clark. Thoughts or elaboration on any of these points, anybody? 

Tuesday, December 6, 2011

To anyone who has never understood why some people won't comment ...

...even when the story in question is harmless, and maybe even fun, I give you this blog post from This American Life, in which the writer details his and his producer's effort to get a police officer to talk about a turkey attack. On him. Well, maybe he didn't think it was funny. Anyway ... the story is funny. Take 15 minutes for it after reading the blog post.