Archives for category: Data + Graphics

My former colleagues at the L.A. Times noted a milestone in community reporting today: The Homicide Report has been active for a year.

Reporter Jill Leovy, who has been primarily responsible for the blog, wrote a feature about her efforts to record the facts of every homicide in Los Angeles, a city of an estimated 3.8 million.

“None of the more ambitious stories I’d previously done for the paper seemed quite as effective as simply listing victims, one by one by one,” Leovy wrote.

The project has become a magnet for the community and is often cited as an exemplar of online journalism, one that is both uncomplicated (a blog and an interactive map) and powerful.

Online, The Homicide Report caught the attention of other sites, including

But perhaps more significantly, readers responded to the Times’ efforts in a visible way. By offering a dispassionate view of murder in the city through the map, and a place for the public to comment and mourn in the blog, LAT did a service for its community, one that was rewarded with frequent site visits and comments.

I’m told visits to the blog alone numbered in the hundreds of thousands, making a case for news organizations to put time and resources into similar local projects that meld traditional, skillful, locally focused reporting with imaginative online execution.

What are some of your favorites? Do you have a project you’d like to share? Feel free to post a link and your story in the comments.

Earlier this week I attended a workshop conducted by Edward Tufte, the Yale professor emeritus and information design lecturer.

During the day-long course, he emphasized the need for high-resolution, information-dense graphics and gave several examples of his concept.

Among them was a discussion about the iPhone interface.

He argued the iPhone hardware presented the perfect platform to deliver lots of detail in a small space and the widgets, particularly the stock and weather widgets, were cartoonish and a wasted opportunity.

Something about this assessment felt wrong.

When putting together a news story for the Web, people often bring up the architecture maxim: Form follows function. If the story is best told through images, should they be still or moving? If the story will be enhanced by sound, should you use a narrator or let the subject speak for themselves throughout? Should text be on an article page, a blog post or in a Flash presentation?

And most importantly, what will best serve the reader?

In the case of the iPhone, most users are glancers and scanners who need the basic information upfront while moving and a way to dive into things when they’re at rest. Goofy as the widgets may look, they do serve these purposes.

Christopher Fahey of graphpaper.com makes a more elegant rebuttal, saying Tufte misses this critical point:

“You are neglecting the fact that iPhones are *mobile phones*, designed to be used primarily by people on the go, or by people who are otherwise occupied. …Typical iPhone usage lends itself well to the information-thin designs you criticize precisely because it does not attempt to do more than deliver the most important information in a heartbeat.

Many others agreed with Fahey, even while defending Tufte. What’s your take?