Dispatches from the living amongst journalism's walking dead

Category: My Work Page 2 of 3

First try at using Xtranormal for news at TBD

In a wjchat a few weeks ago, we were brainstorming ways to use non-traditional new media tools for news. One of those tools was Xtranormal, an animation site that allows you to make cartoon videos with no offsite tools or experience. In that chat, I had suggested using it to re-enact conversations or press conferences.

Today, I put that idea into action at TBD, using Xtranormal’s tools to make a cartoon re-enactment of a phone transcript from the FBI investigation of an indicted public official in the D.C. area. I had enough free credits to build the most basic video (though it doesn’t cost much to buy more), so I built the one you see around the web where animals talk to one another.

Xtranormal’s tools made it very fast and easy. You pick a package, background and characters. You enter the dialogue as text in the order you want from the characters you want. To add pauses, sounds, camera angles and movements, just drag and drop them into the text at the right place. All told, it took me about 40 minutes – and that’s just my first try at a long transcript.

Jack Johnson, the former county executive for Prince George’s County, Maryland, is talking to his wife (also indicted) about hiding money and destroying evidence. The video is after the jump.

Using Foursquare and Crowdmap to track local elections

With the midterm elections coming tomorrow, lots of news outlets will likely be launching their fanciest new toys and social media ideas to best pull in that coveted election night audience on the web. TBD’s no exception, though our election day experiments are based in off-site crowdsourcing to better inform our on-site coverage.

As we did with the Washington D.C. primary elections, we’re launching a Crowdmap to track voting problems across the District, Northern Virginia and parts of Maryland. We’re asking readers to report long lines, broken machines, ballot refusals, electioneering and such at the polls using email, Twitter hashtags or on-site reports. It worked pretty well in September, though this time I’m a bit worried about Crowdmap’s servers holding up. Right now as I post this, they’re struggling to load any of our maps.

I’m particularly excited to try out Foursquare in Tuesday’s election coverage. In our attempt to take a local approach to the National Post’s Foursquare “exit poll” experiment, I set up three new venues to collect voter check-ins.: Virginia Congressional Elections 2010, Maryland Governor Election 2010 and D.C. Election 2010. Once readers check in to the correct venue, we’re asking them to submit a tip to that venue telling us who they voted for and why.

While these check-ins and tips won’t be any kind of real measurement, it will give an interesting look at how many people on Foursquare are voting in local races and how those votes are leaning – if people use it. If enough people check in, they could earn a Swarm badge, at least.

Here’s hoping something takes off.

Storify narrative: Death outside DC9

On October 15, I used Storify at TBD to make sense of an ever-changing series of events involving a death outside popular Washington D.C. nightclub DC9.

In the course of one day, the story took a lot of twists and turns, illustrated in the narrative by tweets (from both news orgs and those reacting), photos, video and documents. Reading down the story, you can get a feel for how the events developed and evolved in a way that’s not entirely dissimilar to more traditional narrative stories.

I talked a little bit more about the story behind this piece to the Nieman Storyboard, if you want to know more. Here’s the Storify:

[HTML1]

Social media’s role in covering the Discovery hostage situation

[HTML1]

TBD’s big moment and a view from behind the coverage

I hate these long gaps between posts as much as you do. I’ve been busy over at TBD, but I haven’t forgotten about the old ZJ.

I have a couple of other posts in the works, but a bit of a recap. Last Wednesday, Sept. 1, was a big day for TBD – and for me personally. When a gunman burst into the Discovery Channel headquarters in Silver Spring and took three hostages, we sprang into action and, in turn, were propelled into the spotlight for the first time since our launch.

It was my first real breaking news situation since starting at TBD – and the first I’ve ever experienced in a TV newsroom. Within minutes of hearing from a TV reporter’s wife (who works at the Discovery site) about the situation, we had a helicopter and live reporting on-scene. You don’t get helicopters at the Cincinnati Enquirer, so that was pretty mind-blowing.

Within minutes we were getting in photos and eyewitness reports from Twitter. We were streaming video online before anyone else – heck, it was even used on other news sites in our area. As things were confirmed, I was able to tweet them out ASAP. I had a lot of back-and-forth communication going on with our staff, some of our blogger partners on-scene and other eyewitnesses on Twitter (a few we even got to talk live on-air). In short, it was an amazing time to be behind the Tweetdeck.

We sent 21 tweets on the situation that day. According to the Bivings Report, we were mentioned/re-tweeted 334 times. We got more than 400 new followers, a boost in web traffic – and a lot of wonderful praise from our audience and peers. My favorite tweet was from Justin Karp:

@TBD is having their CNN/Gulf War moment right now. They’re dominating coverage right now. Kudos.

All that praise and warm fuzzies aside – it proved once again that monitoring and using Twitter in breaking news is increasingly important for any news operation. Twitter “broke the story”, we all know that – and for better or worse it owned the coverage in a lot of ways. We in the news media can only engage the best and stream the rest when something like this happens in such rapid-fire succession. It was a day of lessons for us and every media outlet, I’m sure.

In the days afterward, I was working with others to determine who wrote that first tweet from the building and when it was sent, not only to give them credit, but also to see just how far behind we were. We had our first tweet out at 1:33 pm, about 20 minutes after the first tweet we found. We can do better – and next time we will.

TBD experiments in community engagement: Week 1

It’s the end of our first week on business at TBD and, admittedly, I’m completely exhausted. We all are.

It felt like a good first week for us – we got a lot of reviews, positive and negative, from other media sites and blogs. Despite the bugs and occasional complaints, we did have the opportunity to come out of the gates with a few engagement experiments you might find helpful at your own news orgs.

Open discussion on launch day

We had an open Cover it Live chat on the Community Blog from 9-4 on launch day. TBD Community hosts Lisa Rowan, Jeff Sonderman, Daniel Victor and Nathasha Lim took questions, complaints and bug reports from site visitors in an open and honest fashion. They didn’t just address the positive, they also did what they could to assuage the fears of those missing the former websites for WJLA and News Channel 8, now replaced by TBD.com.

Crowdsourcing for breaking news photos

On Thursday, the Washington, D.C. area woke up to severe thunderstorms, high winds, flooding streets – and a lot of damage. While our one full-time photographer was able to get a lot of art, we knew we couldn’t be everywhere. The call was sounded for photos on Twitter and on the site – and readers responded with submissions on-site and via Twitpic.

We ended up repeating this process later in the day with a reported electrical fire near the District’s business center. I first saw reports and Twitpics of the fire on a random Twitter search for “Fire near: Washington DC”. We quickly reached out on Twitter for permission to use the photos – and we were off to the races. It was great to get such good response out of the gate.

Working with bloggers on breaking news

Around 1:30 pm Tuesday, I looked over one of my series of Twitter searches and found a tweet reporting an alleged hit-and-run by a Metrobus in Arlington, Va. I contacted the guy, Matt, via reply and asked him if he’d talk to our Arlington reporter, Rebecca Cooper. He agreed.

At 2:12, network partner site Unsuck DC Metro, who the original tweet was directed toward, had a post up with the tip.

Another partner site, ARLNow, had a story with photos and quotes from the man involved in the accident at 3:07. TBD had a story with the tipster’s report and ARLNow’s report up before 4 p.m, approximately four hours before The Washington Post or WTOP (and a hat tip to the Post for promoting the great efforts of ARLNow).

Without the tip provided by Twitter and the hustle by the bloggers in our community network, there’s no way we could have had such a story so fast. Who says bloggers aren’t journalists? Not us.

Tapping into the crowd for political coverage

Questions submitted via Twitter hashtag

Questions submitted via Twitter hashtag

On Wednesday, TBD TV’s Newstalk program had the Democratic candidates for D.C. mayor on the program for a debate. In the hours before the 10 a.m. debate, we asked readers to submit their questions for the candidates via hashtag on Twitter. The response was more than we could fit on the program, which was great (see right).

When the debate went live on TV and online, fact-checking reporter Kevin Robillard had a live Cover it Live chat where readers could chime in with comments, ask questions and suggest facts to be checked as the candidates said them on the air.

The debate got a lot of traction on Twitter and on the chat. Kevin had some great material for The Facts Machine, which is a TBD blog dedicated to backing up or refuting questionable facts.

We hope to do a lot more projects like this in the future. Not bad for the third day out.

Weather coverage made easy

Weather is big business for those of us in news, especially when it gets to be extreme weather like just about every state has experienced in the last two weeks.

Lots of news outlets have developed amazing new ways to get out weather information and pull in interaction from readers, but sometimes what’s simple can work in a pinch.

Most of the time when we’ve had snowstorms in the past, we at Cincinnati.Com have had a basic story file set up that we re-top and add to throughout the day as the news changes. Without the occasional total re-write during the course of the news cycle, it can end up reading like a very long Frankenstein of an article, with the possibility of specific items getting buried in all of the text.

I recently set up a basic WordPress blog specifically to handle weather events news to avoid this problem. It has links to all the basic weather info we have available on the site, a way to search all of the posted entries and tags/categories that make posts easy to browse by topic or location. The blog uses the TDO mini Forms plugin that can allow our reporters – and our readers – to submit updates from where they are.

Even though we haven’t yet gotten a lot of reader submissions, the blog has been immensely helpful from a news management standpoint. Reporters can file to the blog from their homes, phones or satellite offices, all we have to do it click “publish” in our dashboard. No re-writes are necessary because as the story develops, we can just add news posts. The format also provides an easy way to “sticky” important posts at the top and generates an easy link for the day’s event cancellations.

This easy method of publishing updates weather news has been a great supplement to our info releases and content on Twitter, on our mobile site, text alerts and all of the usual photos and videos we bring out fr every story. The blog’s been doing great traffic on storm days and, from my view, has been a huge burden lifted from the backs of already busy online editors (such as myself).

Because this info has such a short shelf life, I’ve just been deleting all of the old content as soon as the storm coverage ends. We don’t want readers coming back for new weather updates only to find outdated info from last week’s storm. I know that isn’t the greatest option for the sake of SEO and outside linking, but it has made it very easy to essentially launch whole new blogs for each circumstance. I’m curious to hear others’ thoughts on what they would do to prevent link breaks and confusion.

Anyway, that’s been our publishing plan these past two weeks – and if it’s something you think you could use, go for it. WordPress is free, quick to set up and has lot of plugins to enhance user experience.

What has anyone been doing to cover these storms online? What have you been reading?

Blog Archive: Seen and Heard

Probably my favorite project, Seen and Heard was a popular blog on local people-watching on JSOnline from 2005 to 2007. In addition to my usual work duties, I wrote this first person narrative blog as a labor of love. Even though the JS site did not yet have blog technology that could support commenting, I got a tremendous amount of email every day in response to my posts.

It is no longer featured on the JS site following their redesign last year, but I have an archive link here that will need to do until I can archive it elsewhere for myself.

Seen and Heard Screenshot

Radio Feature: ‘Green Bean Casserole’

Although I was a regular producer for WKSU, my own voice very rarely actually appeared on the radio. Lucky for me, during the holidays I had more opportunity to get a piece of my own on the air. When the Inventor’s Hall of Fame in Akron, OH (in our coverage area) announced it would be inducting the inventor of the recipe for green bean casserole in November of 2003, I jumped at the chance to record a holiday feature.

I conducted the interviews, recorded the on-scene and studio audio and produced the entire piece in Cool Edit Pro.

This final product aired on Thanksgiving Day, 2003:

Green Bean Casserole

Daily news podcasts

I spear-headed the start of the Journal Sentinel‘s daily news podcast in 2006. It started with me or another member of the online staff writing, voicing and producing the podcast in Sound Edit Pro each night, but eventually I trained several copy editors to join in a daily rotation for podcasting.

Here are a couple of podcasts I voiced and produced myself during that time. Once I get the stupid Flash player to actually work on this site, I’ll have a pretty audio player to play them here.

Here’s one from February 6, 2007 and one from March 1, 2007.

Radio production: WKSU special projects

I was incredibly lucky to have spent a few years working at WKSU-FM, an excellent Northeast Ohio NPR station, for my graduate school fellowship. Each year WKU did a large-scale news series based around a topic in the news. During that time period, I got the chance to work with some of the best reporters I’ve ever met to help produce these story packages.

The following two projects were products of teamwork, I claim no individual glory. My duties on these pieces ranged from audio editing (we used Cool Edit Pro), in-studio recording, piece selection and transcriptions. I may not be the reporter in the pieces, but I’m very proud of the work I did there.

I encourage you to listen to the pieces or at least check out the transcripts – there’s some amazing stuff here:

A place for me? Adoption and foster care in Ohio

Class in America: The Unspoken Divide

Video: Man-on-the-street interviews

The following video was created in conjunction with Anna Roberts in February of 2007 as part of a local newsroom package on global warming. We shot the man-on-the-street video interviews on a consumer-grade digital handheld camera and edited the video in Final Cut Pro.

And, by the way, this was one of the worst assignments ever. I don’t think I’ve ever been cursed at more than I was that day.

Page 2 of 3

Powered by WordPress & Theme by Anders Norén & Hosted by Pressable