Innovation in Software

One of the problems with modern journalism is that some of the barriers taken for granted have broken down, and that can mean new ethical dilemmas being created every day.

Take the story of David Rohde’s kidnapping. Who he? You might very well ask. A reporter for the New York Times, he was kidnapped around seven months ago by the Taliban. You didn’t read about it in the papers? Well, no. Despite it being picked up by an Afghan news agency and being reported in some UGC news websites, the New York Times conducted a cover-up operation over the last seven months.

The only people who didn’t play ball the NYTimes were worried about were a couple (perhaps only one) of the Wikipedia editors who spent a reasonable amount of effort trying to insert one single reference to the kidnapping in Rohde’s Wikipedia article.

The Wikipedia team conspired to remove the edit and temporarily block the page from time to time. The New York Time have decided to point out how tricky dealing with this was by way of a free puff piece for Wikipedia and Jimmy Wales.

It’s an interesting case in how truth takes a back seat for a while, and raises some interesting questions for me about how exactly news organisations are meant to behave in a new era of constant information flow.

First, their reasoning for suppressing this information:

Times executives believed that publicity would raise Mr. Rohde’s value to his captors as a bargaining chip and reduce his chance of survival. Persuading another publication or a broadcaster not to report the kidnapping usually meant just a phone call from one editor to another, said Bill Keller, executive editor of The Times.

Well, that doesn’t seem very sound logic. Yes, if it had been splashed across CNN for a couple of news cycles because there wasn’t much going on that weekend, you’d have a problem. However, that wouldn’t happen. Even the original news stories that were published intimated journalists being kidnapped were not big news, and part of daily life in that part of the World.

In fact, the story not getting sympathetic coverage could well have caused more damage – why feed and keep a man who is worthless to you and his fellow journalists? If no ransom is possible,  wouldn’t it be simpler to just kill him?

Then there is their attempt to change history that irks a little:

Two days after the kidnapping, a Wikipedia user altered the entry on Mr. Rohde to emphasize his work that could be seen as sympathetic to Muslims, like his reporting on Guantánamo, and his coverage of the Srebrenica massacre of Bosnian Muslims. Mr. Rohde won a Pulitzer Prize for his Bosnia coverage in 1996, when he worked for The Christian Science Monitor.The Wikipedia editor in that case was Michael Moss, an investigative reporter at The Times and friend of Mr. Rohde who has written extensively about groups like Al Qaeda and the Taliban. Like many Wikipedia editors, he adopted a user name that hid his true identity.

“I knew from my jihad reporting that the captors would be very quick to get online and assess who he was and what he’d done, what his value to them might be,” he said. “I’d never edited a Wikipedia page before.”

With his editors’ blessing, Mr. Moss had already made similar changes to Mr. Rohde’s “topic page” on The Times’s Web site, and in both cases he omitted the name of Mr. Rohde’s former employer, because it contained the word Christian.

Woah, there! That’s some pretty hefty editing going on there. First, Michael Moss edits the page to make Rohde look more sympathetic to Muslims, under a pseudonym. Then he edits up the NYTimes.com topic pages, all the while trying to get rid of the mention of his previous employer.

I have to ask, why? The most prominent article on Rohde found through Google before the story of his escape and this cover-up broke over the weekend, points out quite clearly who his previous employer was. This was, in essence, a futile exercise that did not take or remove any information away from the Internet that was already out there, and simply made the NY Times look like they were practising their Stalinist air-brushing techniques.

I’m disappointed in all involved. I don’t think Rohde would have been killed if things had been left as they were. I don’t think a short mention on the evening news would even have happened. A couple of small pieces in competing papers pointing out his work in highlighting issues Muslims around the World faced might actually have helped him gain an earlier release. Either way, if he was still alive after seven months, there was little chance he would be killed at any point by his captors.

Wikipedia might be the biggest boy in town when it comes to UGC news content, but it won’t be for long. You won’t be able to suppress stories in future that are based in fact, and the final line of the NYTimes pieces:

…the idea of a pure openness, a pure democracy, is a naïve one.”

Harks of naïveness in itself: journalists are no longer gate-keepers to truth. Yes, lives are involved and everybody is glad that Rohde managed to escape over the last couple of days. However the guys sat in news rooms – foreign correspondents whose lives are on the line, even more so – are going to have to accept this behaviour just isn’t going to be possible a few years from now. The real question then is should it be?

Here we go again. A round-up of links for a Sunday spent in front of the PC, or if you’re a corporate slave, a way to pass Monday morning bunking off doing real work.

What is the Secret Behind Contagious Behaviour – This video from Stanford’s Always On summit has some fascinating discussion about contagious behaviour, implementing innovation and working out how to give up control of marketing and products to your customers. My favourite phrase from it probably has to be “fragile fires”. Mitchell Baker of Mozilla, Perry Klebhan – inventor of the modern snow shoe, and Gil Penchina of Wikia discuss how to get users doing the work for you. Moderated by Bob Sutton of Stanford and Diego Rodriguez of IDEO.

Collaboration doesn’t Work – if you’re afraid of the Kool Aid, this article from inc.com suggests teamwork and collaboration doesn’t work. I think the conclusions drawn here are all wrong (obviously) but for a simple reason: the author thinks that collaboration can be done by anybody, without training. It’s a skill that needs time to develop, much like the skill of being able to write software, write a PR release or do a cashflow forecast. Asking people to just walk in a room and start brain-storming without any prior training is asking them to behave in a business context using skills that to this point they had only learnt in social contexts, i.e. contexts where being polite is more important than being right.

Wikipedia Forks – It’s quite common within open source projects for groups within the project to reach disagreement and one set walks off with a copy of the project (which is legally OK for them to do), set up camp somewhere else and create a new project with the old code as a base. This is known as ‘forking’ and it happens a lot more than the media would have you believe. Now a group from Wikipedia believe it’s time to create a new project that has the good bits of Wikipedia but with the oversight of experts, and so off they march. Initially we as readers won’t see much difference, but the proof of the pudding will be in the long-term eating. I wish them well.

iPod users prefer CDs to iTunes – and who can blame them? The issue here of course is ‘DRM’ or ‘Digital Rights Management’. If you buy music through iTunes, Apple get to tell you which devices you can play that music on and how. If you buy a CD and rip it into iTunes you get a physical back-up, you can play the music where you want, and the ripped files can be copied to any device including ones not made by Apple. I genuinely think that within the next 3 years there will be a massive consumer revolt at DRM and the only way to deal with it will be to completely restructure the way music labels (and in the future, Hollywood studios) make their money.

8 Steps to better IT meetings – In fact, not just IT meetings, but any meeting. A nice round-up of how to keep meetings on track. Personally, I think meetings should be avoided completely – individual conversations work much better and if kept to the point can be a great deal quicker and more productive. Having everybody in the room really is as productive as having nobody in the room. However, if you insist on meetings, this is a great way to make them less brain-dead.

The 25 Worst web-sites in the World, ever – I remember most of these when they launched. Truly horrendous, and in my opinion the number one spot holder deserves it – utterly awful website (I won’t spoil the surprise for you though). That said, none of these were as bad as Microsoft Bob in the ‘I… don’t… believe… they… did this…’ stakes.

50 favourite design resources – for those of you who, like me, find design something that has to be worked on as a skill rather than something that comes naturally, here’s a crib sheet.