Dispatches from the living amongst journalism's walking dead

Category: TBD

Posts I’ve written about TBD.

Quickly create a collaborative map with Crowdmap

Every election since I started my professional career has led the news organization I was working for at the time to say, “We really should have a map of election problems.” Then we’d build some UGC map held together by virtual duct tape. Sound familiar?

User-populated maps have come a long way in the past few years thanks to lots of free technology available on the web. Google Maps, for instance, was a early precursor that still has a lot of utility today. See my [very impressive] map for free donuts as a good (and yes, silly) example of a quick Google collaborative map.

In 2008, Ushahidi (which is Swahili for “testimony” – the more you know) made its debut in mapping post-eletion violence in Kenya . The mapping tool allowed for user to add reports to the map using SMS, email and on-site forms. They’ve since added support for reports via Twitter hashtag.

While they’ve had great success in mapping international crises (like the Haiti Rescue Efforts) and domestic trends (like the Atlanta Crime Map), the main problem with Ushahidi is that it isn’t altogether quick or easy to get a map set up. The software is free and open source, but you need to have a server and programming know-how to get it going.

Thankfully, Ushahidi recently launched a stripped-down, hosted version of it’s mapping tool called Crowdmap. In about 10 minutes, you can have a user-contributed map up and running with no programming know-how and no server.

WMATA Problem Map

WMATA Problem Map

Reports submitted on-site flow in to a back-end queue that’s easy to publish as verified or unverified reports. Messages sent via email or Twitter can be converted to full map reports by an admin in a matter of a couple of minutes. All reports have an option to add photos, videos or news links to more info. You can schedule reports to publish and certain times, plus designate specific submitters (like your staff) to have their reports be auto-approved.

Crowdmap does have a couple of downsides. For one, it isn’t embeddable on your site. It has to be used on Crowdmap, though you can use a Google analytics tracking code to track traffic. It also isn’t particularly customizable, so you can’t brand it or add significant new features as you can with Ushahidi. Still, though, it’s a heckuva lot better than some of the cobbled-together maps I’ve had to put together before.

I recently built a couple of these maps for TBD.com, one for mapping Washington-area transit issues and another for monitoring polling problems on the day of D.C.’s primary elections. Neither took much time to set up and both had/have decent participation, given that we promote it on our site. We got far more Twitter reports than anything else, which is likely because we put the most effort into promoting it there. At some point, I’d like to expand our reports to include SMS contributions.

I’ll have a post soon that will walk though setting up a Crowdmap, but for now, check out the site and tinker around. It’s super easy.

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.

TBD 1.0 launches, now let the real fun begin

If you’ve been reading here – or really on most any journalism blog of late – you know I’ve been part of a team of excellent journalists who’ve been toiling away the past few months to get TBD off the ground.

TBD Home Page circa 4 am, Launch Day

TBD Home Page circa 4 am, Launch Day

Today is finally the day. Today, TBD.com has launched and all of us who joined this venture with high hopes of shaking up the news business get our chance to sink or swim.

I hope you’ll take a few minutes and take a look at the site. Let me know what you think, either here in the comments, in our live chat today or wherever you tend to post your rants. If you see technical issues, please do us a favor and report them here.

What we put out there today is nowhere near a “finished” product. We’ve said from the beginning that TBD will always be developing and changing as we get new ideas and more information – so consider this TBD 1.0.

I really want to take this opportunity to say I’ve been so lucky as a journalist and as a person to have been able to build this site with these amazing people. I’ve never been so challenged, felt so excited or learned so much in such a short time as I have here. I have had the time of my life putting together this big crazy idea – and I expect it to only get better as we actually get down to the business we all came here to do.

We’ve been getting a lot of press in the lead-up to launch and I expect to see more reviews in the coming days. I’m collecting them here. Let me know if I’ve missed any links.

How we did it: Securing an occupied Twitter handle

It can be tough to be a new brand these days. Locking down namespace online is a huge part of a brand build – but much like potential mates, all the good ones seem to be taken.

We ran into that when we started building the brand for the soon-to-launch TBD. It’s a popular acronym, as everyone knows, so securing that namespace in social media was quite challenging. Though we’ve been tweeting for nearly two months as @TBDDC, this week we finally acquired @TBD. This is how it went down.

We wanted @TBD from the start, but it was occupied by a private, dormant account with zeroes across the board – no followers, no follows and no tweets.

Obviously, the first step in this scenario is to try to contact the handle owner. From my own account, I requested to follow this user to see if they were checking their notifications. Either they weren’t checking or I was rejected, because I never heard back.

I also sent the user a couple of @ replies to see if they were even checking those. No response.

It was time to turn to Twitter.

When you want to take this next step, it’s important to note Twitter’s policies in relation to your situation.

The policies are different depending on whether or not the account is active, whether the user is actively impersonating your brand and whether or not you have a registered trademark on your name.

If someone is actively using the handle you want in accordance with the rules, there’s little Twitter can do, even if you have a trademark on the name.

From Twitter:

Where there is a clear intent to mislead others through the unauthorized use of a trademark, Twitter will suspend the account and notify the account holder.

When an account appears to be confusing users, but is not purposefully passing itself off as the brand/company/product, the account holder will be notified and given an opportunity to clear up any potential confusion, per the guidelines listed below.

Contacting the user directly is really your only hope to getting the name in this instance.

If you want to acquire the handle of an inactive account, as we did, it really helps to have a registered trademark on the name. We did not have our trademark registration info right away, but I still submitted  a ticket request to have the name released.

Once we got our trademark registration information, I filed another ticket, this time under the trademark policy. This time I filled out the required trademark info. To do this, our Twitter account had to be linked to an email address from our domain (an important thing to note if you have a business or blog without a URL yet). This was the final thing that pushed it over the top and got us @TBD.

If you don’t have a trademark registration, you may still have a chance, though note this important point in Twitter’s inactive username policy:

We are currently working to release all inactive usernames in bulk, but we do not have a set time frame for when this will take place. If a username you would like has been claimed by an account that seems inactive, you should consider selecting an available variation for your use on Twitter.

Even so, it wouldn’t hurt to submit a ticket request from your account to report the inactive name.

When and if you get a username opened up, you can easily change your Twitter handle to the new one without affecting your followers, lists or settings. You can do this from the Account tab of your account Settings.  In our case, Twitter rolled @TBDDC over to @TBD for us.

When you change your Twitter handle, you have to be vocal about the change. If you can do it before the changeover, tell your followers what’s coming. After the change, they’ll receive your tweets at the new handle, but they may not realize the difference and may send replies and DMs to your old handle. Tweet about the change and encourage retweets. It might not hurt to briefly re-secure your old handle and put up a message there about the new account.

Note: If you get a second handle for this purpose, be  good citizen and don’t name-squat. After a couple of weeks or so, if you aren’t going to use this account for something else, delete it and re-open the name.

But even if you don’t get the handle you want, you shouldn’t let it stop you from jumping into social media.   It wasn’t a deterrent for TBD – we were able to build a lot of buzz on @TBDDC before we got the new name (and we were prepared to have that name be permanent).

If you can’t get the username of your brand, think of a way to make your own version. Shorten it, add an adjective or adverb, tack on a location or do something entirely out-of-the-box. It really isn’t all in a name. It all depends on how you use the medium and how well you can promote it elsewhere.

Mandy appears on News Talk to discuss Facebook

I had my first-ever TV appearance this morning on News Talk, a program produced by News Channel 8 (soon to be TBD‘s TV side). I was brought on to talk about the rise of Facebook in the wake of its 500 millionth user signing up this week.

I couldn’t get the video up on a server today, so we’ll have to make do with a link to News Channel 8’s video for now.

What measures success in journalism these days?

As part of our effort to be open about the ongoing development of TBD.com, the Community Engagement staff has been writing a series of posts as to why and how we ended up here. It’s always the first question I get asked when I meet someone here in DC (can you tell by the accent?), so it’s a good assignment for getting to know us.

The story of how I ended up here is relatively well known (thanks to this and this), so I wrote about why I made the move.

In putting it together, I was thinking back to when I first announced (in mid-April) that I was leaving the Enquirer to come to TBD. A young journalist I know asked me, “Why in the world are you doing this? You have a good job. You’ve made it.”

I guess, in some ways, she was right. I had a voice at the table at a decent sized newspaper (and  had made it through several layoffs). That used to be a major milestone in my planned career goal – but a few months ago, I had an epiphany: My goals are outdated – and they really weren’t mine to begin with.

From Day 1 of journalism school, we were taught that to work at a Known Media Source is the biggest of big deals. Our ultimate goal would be to work at the New York Times’, Washington Posts and CNNs of the world – because that’s what many generations of eager journalists before us wanted. We were led to believe if we, like them, were to do good work at several smaller newspapers, we’d someday get brought up to the Majors of journalism to do the important kind of news that matters.

It’s kind of laughable in hindsight.

The big newspaper as the end-all-be-all is a throwback to a state of journalism that doesn’t really exist anymore. The culture of today’s big newsrooms are more “Stepford Wives” than “His Girl Friday”, employing journalists from a certain kind of background from a certain group of universities to tell a certain kind of story in the same way they’ve always told stories. Some are willing to stretch out of that box, but most haven’t. As an individual, you have to be quiet and fit in or you leave.

You don’t have to be in the Majors of newspapering to do important news that matters to people anymore. You don’t even have to be at a mainstream media source or have gone to journalism school. You don’t even have to call yourself a journalist at all. Getting recognition from big newspapers or major awards, while still nice, isn’t really the bar we have to measure ourselves by anymore. Exposure, originality and branding is the key – and you can do that on your own blog.

And that’s where TBD came in for me. I wanted the chance to do something new – and it was becoming obvious that I’d have to leave that Stepford Journalist career path to do it. Who knows? It might have been too large a risk – time will tell – but I bet I learn more from my time at TBD than I would have at a newspaper.

Am I saying I might not go back sometime or that I wouldn’t still want to work at one of those bastions of journalism someday? Of course not. I’m just saying I don’t think the old measures of success apply anymore. My success, for now, is TBD (har har).

The new kid in the downpour of fresh ideas

When you’ve spent your entire professional career in a newspaper’s newsroom, it’s pretty easily to get your mind blown at a startup. I can attest to that firsthand in my first few days on the job at TBD.

Instead of shoehorning some new media approach into a centuries-old tradition, we’re building something so new, it’s still somewhat intangible – and that’s the fun part. It’s also sort of terrifying.

Because we haven’t launched yet, there are no deadlines, per se (which is a tough adjustment from my last few years working in breaking news). Our deadline for now is launch – and then infinite thereafter as we continue to add new features and tweak tools.

Right now, there are no rules, but I wouldn’t call it lawless, either. All of us currently involved with TBD have extensive experience in news and/or the social sphere. We know the framework of what we’re working toward, the rest is totally up for grabs.

In the past few days, I’ve been in several meetings with the rest of the community engagement staff where we have been brainstorming TBD’s processes for reader participation, community newsgathering and the all-important continuous breaking news. There are only five of us in a room, but it’s a hurricane of what-ifs and how-about-wes.

Not once has anyone said, “We can’t do that” or “That isn’t possible”. That’s a great feeling.

I know those times are coming. Some ideas will make it and others won’t. For now, though, I’m just trying to get a word in edgewise in a newsroom full of energy and rapid-fire ideas.

In addition to these sessions, we’re crowdsourcing our TBD plans, so if you have ideas you’d like to share, please do.

The community hosts are already miles ahead of me, working hard to recruit good bloggers for our network. I, on the other hand, am desperately trying to catch up.

I’ve found being the social media producer for a website that doesn’t exist in a city that doesn’t know you is a pretty tall order. All that community I built around myself in Cincinnati is now far, far away – so now the new task is cracking the Twitter code of this area.

In preparation to launch the TBD Twitter account(s) in the near future, I’m currently working on building up my own DC base on Twitter, figuring out who to follow for breaking news, community tips, laughs and tips about cheap beer. I’m working on finding the “nodes” (as my former editor was fond of calling them), that is, the Kevin Bacons on the metro DC social media sphere who are followed by and follow everyone important.

That’ll take some time, I know. I’m just not very patient. Have ideas/suggestions? You know the drill.

Because we haven’t launched yet, there are no deadlines, per se (which is a tough adjustment from my last few years working in breaking news). Our deadline for now is launch – and then infinite thereafter as we continue to add new features and tweak tools.

Online news is always TBD

So our new little metro site for Washington, D.C. is no longer nameless. It was announced today that the name of the site will be TBD – and I think it’s perfect.

As my future colleague Jeff Sonderman wrote,  it really fits with the mission of what we’re trying to do here.

News at the start of the reporting process is “to be determined” – though in the traditional model, many readers don’t get to see it or be a part of it at that point. You get it later, as a finished product in print, online or on-air. If you’re lucky, we’ll let you comment on it or write a letter to the editor when its done.

I truly believe needs to be alive to be relevant. Our goal is to get news out there fast, yes, but we also need to make that news evolve in time with the release of information, the ebb and flow of public opinion and the constant input of those affected by it.

There can and will be several avenues for the public to share in cultivating and developing the news at TBD – and I hope the people of metro DC will be as excited to be a part of it as I am. So far, the reaction seems positive. What do you think?

Page 2 of 2

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