Showing posts with label failure. Show all posts
Showing posts with label failure. Show all posts

Wednesday, October 1, 2008

If at first you don't succeed...

"If at first you don't succeed, call it version 1.0."

It's an old saying in the tech world. But it reflects the mindset that has enabled Silicon Valley to produce the likes of Apple, eBay, PayPal, and Google. This mindset says: "There's no such thing as failure. There's only version 1.0. And then version 2.0. And then 3.0."

Things aren't expected to work great -- or even work -- the first time around. But that's OK. Things not working right the first time around doesn't constitute failure. It constitutes a necessary step on the way to figuring out what does work.

It's a mindset news organizations simply need to adopt. They need to move away from "We don't release it to the world until it's fully baked" to "Let's throw it up against the wall and see what sticks."

So let's say it again: "If at first you don't succeed, call it version 1.0." (And then go back to the drawing board to start working on version 2.0.)

Photo courtesy of eyesplash Mikul. Creative Commons license.

Monday, September 22, 2008

Who would you fire?

Newspapers are experimenting with new tools left and right, as well they should. One they're trying to get a handle on is Twitter.

As you probably know, Twitter is a tool that lets you dispatch mini-updates -- up to 140 characters in length. Recipients can choose to get them in any number of places: On their cellphones, in their RSS readers, etc....

Newspapers are trying to figure out whether Twitter has any value to them. They're asking themselves what are the situations, if any, where sending 140-character bursts is useful to readers? And, of course, can Twitter be used to generate audience loyalty that can somehow contribute to the bottom line?

As happens whenever you experiment, not all your efforts pan out. There are two recent examples where newspaper Twitter reporting fell flat on its face.

-- As Hurricane Ike loomed, the Houston Chronicle created a special Twitter account that people could subscribe to get the latest storm info. But, as Cory Bergman over at Lost Remote points out, they totally bombed with their implementation. Instead of posting immediately useful information -- like "Bridge X now closed" or "Johnson HS in Town Y now accepting displaced residents" -- they have simply posted headlines to their stories, along with links to the articles online. Now let's think about this for a moment. If you're in the middle of a hurricane (or its aftermath) and are trying to make game-time decisions about what's best for your family or business, are links to stories online really the most useful information you could be receiving? Obviously not.

If you're getting the tweets on your cell phone, you might not have Web access to get to the articles. But even if you do, do you really want to stop what you're doing to read an inverted-pyramid story about this thing or that? No, of course not. You just want information you can act on immediately, like "Avoid this street" or "FEMA grant applications being accepted at the library from 10-12."


-- Meanwhile, the Rocky Mountain News has also been experimenting with Twittering, sending play-by-play updates from the Democratic National Convention, for example.

They got themselves into journalistic hot water, though, when a reporter sent to cover the funeral of a three-year-old victim of a widely covered traffic accident used Twitter to send minute-by-minute updates. The Poynter Institute's E-Media Tidbits blog challenged the news value of such tweets as "the father is sobbing over the casket" and "family members shovel earth into the grave." The Colorado Independent called the reporting "Utterly, and unforgivingly, inconceivable." Posters at a forum on SportsJournalists.org called for those involved to be fired.

Which leads us to the question of the day. Between these two incidents, if you were going to fire someone, who would you fire? The creator the benign yet useless Houston Chronicle tweets? Or the people behind the conceivably tasteless Rocky Mountain News tweets?

If it were me, I'd fire the Houston Chronicle staffer.

OK, "fire" is a little strong. I would have them reassigned.

As for the Rocky Mountain News folks, we'd definitely do a debrief and draft "lessons learned." But fire them? Not for a minute. Here's why.


The key to figuring out the future of news lies in experimentation. It is only through experimentation that we'll figure out what new forms of journalism both serve our readers and generate the revenue news organizations need to survive and thrive. In today's environment, we should never fire staffers who experiment and fail -- especially when they fail. Failure is a necessary part of learning and growing. (In fact, I remember a friend of mine once telling me soon after he started at the New York Times that the editors there had told the newcomers that if they weren't messing up every now and then, they weren't trying hard enough.)

But people should be fired for being stuck in the past. And that's why I'd fire -- OK, reassign -- the Houston Chronicle staffer who authored those benign but useless Hurricane Ike tweets.

To explain:

-- The Houston Chronicle people fundamentally don't understand the technologies they're working with. They are stuck in the old world model: "We write articles. Our goal is to get our readers to read our articles." People who start out with that mindset will never be able to find the future. As tough as it is, news organizations need to get people like that out of the way so that the people who do get where things are headed can do their work and find the future.

-- The Rocky Mountain News folks do get what the new technologies are all about. It seems like they messed up in this one case, but that's OK. Try it and learn from it. You'll never find what is valuable and useful unless you're willing to push the bounds.

Here's an analogy. There are some people I know who will only go to a show (theater, music, etc...) if it's received a stamp of approval and they're guaranteed that it's going to be great. I take a different approach: I'm willing to try anything that sounds like it could be interesting. Invariably, some of the shows bomb, and I end up walking out at intermission. But because I was willing to take risks, I've also found a lot of good shows that my safety-minded friends never saw. It's only by taking risks that we make discoveries.

When it comes to weekend entertainment, the stakes are pretty low. So I have some friends who never get to discover cool shows because they aren't willing to take risks. So what. No harm done.

In the news business, however, the stakes are higher. The stakes are, in fact, our very survival. As such, we must
be willing to take risks. Playing it safe may ensure that we never accidentally transgress. But it will also ensure that we don't have a future.

Friday, July 25, 2008

It's OK not to know

According to the Pew Research Center's Project for Excellence in Journalism, 95 percent of newspaper editors and publishers feel like they can't predict what newsrooms are going to look like in five years.

And apparently, they think that's a problem.

"I feel I'm being catapulted into another world, a world I don't really understand," Virginian-Pilot editor Denis Finley told Pew.*

But you know what, that's OK. That's what innovation is all about.

When I first landed in Silicon Valley in the late '90s, nobody knew what the future of the Internet was going to be. They had no idea whether a certain kind of website would have a future. Whether a certain business model would pan out. Whether they would be able to find customers or an audience for a specific use of the web.

Not only was that not a problem, however, it was part of the fun. I can remember interviewing for a job at a specific Internet company, a new one that was doing something that had never been done, and thinking to myself, "By working here and coming up with new ways of doing stuff, I'm going to be creating the paradigms that websites are going to be using for years to come."

Of course, the difference was that there wasn't an "old way" of doing things that we were breaking away from. We weren't at risk of breaking any paradigms. No paradgims existed.

And this is what I think is the crux of the problem for traditional jouralists. Their paradigms, which served them extremely well in the print era, are the ball and chain preventing them from diving into the digital world, moving forward confidently, and actually discovering how to use the web to deliver great journalism.

There are two paradigms in particular: A canon, and a bias against failure.

The canon, of course, is everything that we think of as constituting "good journalism." Being "objective." Keeping attitude out of copy. Inverted pyramids. Publishing only once you have all your ducks in a row. I've talked about that before and will talk about it again, so I'll put this aside for now.

The bias against failure is equally problemantic. This is the longstanding view that any error was cause for monumental shame. What reporter hasn't dreaded filing a correction, knowing that too many of them would constitute a firing offense? What editor hasn't raged upon being scooped? What journalist hasn't died in their chair when a source called up to tell them they got the story all wrong?

And yet, in this new world we're entering, there's going to be nothing but failure. Maybe that overstates the case a bit. But by definition, when you're trying something new, you're experimenting. And when you're experimenting, many of your experiments will fail. That's how you find what doesn't work--and, eventually, what does. As Thomas Edison once said, "I haven't failed. I've just found 1,000 ways that don't work."

So here's my advice to all the editors out there biting their nails over the fact that they don't know what the future is: Relax. Relax, experiment, learn, try again. And you will get there, eventually, even if you don't know where it is you're going.

* Via Maui Time Weekly, Via
AltWeeklies.com

Photo courtesy of Dementia_X. Creative Commons license.