Month: June 2011

Johann Hari: it’s about trust

So Independent columnist Johann Hari has been caught out passing off quotes from other interviews as his own – and so far he’s defended the practice, claiming it’s “common” and suggesting he’s doing the readers a favour by choosing the clearest possible version of his subject’s ideas.

A lot of journalists and media folk, myself included, have chipped in on this one, but at the end of the day our views are not all that important. It’s Hari’s readers who have been deceived, they who will judge him, and they who will ultimately be the arbiters of whether his deception is acceptable or not.

It’s about trust. Has he lost it? Will his readers still trust him to report accurately, or will they be worried now that if he can deceive them about what was said to whom at what time, he can also deceive them about other things? Or does the end justify the means? Is it OK as long as he writes well and keeps doing important work?

I pulled together and Storified a few responses I had on Twitter to these sorts of questions earlier today. At the time, they didn’t bode well for Hari – but it’s a very small and unscientific sample. I’d be interested in more. Edit: the comments on this slightly tongue-in-cheek Independent blog post seem to back up my Twitter sample so far, but the response to his column in the paper tomorrow will be most telling.

Hari himself says: “My test for journalism is always – would the readers mind you did this, or prefer it?” That’s my question too. Would his readers really prefer pastiches to accurate quotes? Or would they rather he linked to his sources?

Twitter for Newsrooms: first impressions

Tonight Twitter released a set of guides for newsrooms. There’s going to be a lot said about them in the next few days I’m sure, and it’ll be a while before we see what impact (if any) they have on the news ecosystem. But here are a few first impressions, in no particular order.

  • Newsrooms, not (just) journalists. This isn’t just about newsgathering, it’s about process and presentation too.
  • This is basic stuff – tools, examples, glossary, links, support. That’s as it should be, I reckon. The newsroom denizens who understand Twitter well enough to build their own techniques are still vastly in the minority. This is about bridging a gap.
  • The examples of engagement are very well-chosen indeed, and it’s genuinely heartening to see a range of reporters from the internationally renowned to the metro beat, with follower count ranges to match. I hope they keep this list up to date.
  • There’s that word “branding” again, providing more fuel for the ongoing branding debates. This is good basic advice about making yourself recognisable and accessible on Twitter, but I suspect a fair few journalists will bristle at the problematic word.
  • The focus when it comes to reporting is on the @acarvin style of curation and publication, not on live reporting or on breaking your own news. There’s a small section on mobile reporting, but the bulk of the reporting guide is around tapping into pre-existing communities, building on top of citizen journalism work, and finding sources. That looks a little like a missed opportunity to tout the real power of Twitter as a direct conduit for breaking news.
  • I’m glad Twitter is making more of its advanced search tools. They’re immensely useful for journalists, but unless you already know about them they’re next to impossible to use. Including them here, prominently, is smart. And it’s wise to explain there’s a difference between Top and All tweets, even if it’s still not clear what “most relevant” means in this context.
  • Twitter is protecting/building its brand. Some of these guidelines are about making sure the platform gets credit for quotes and information shared there. Others offer ways to embed Twitter functionality on news sites. It reminds me of Facebook’s Open Graph plugins, in a nascent and very specific way – proliferating its own platform while performing useful functions. Aiming to become needed, where it isn’t already.

#hhldn: learning about rNews – Storified

#jcarn: Workflow hacking

For this month’s Carnival of Journalism, we’ve been challenged to write about life hacks, tips, tools and techniques that help us work smarter and more effectively.

It’s been an interesting one, because it’s forced me to quantify the things I do to try and work efficiently. The things I’m sharing here make me sound like some sort of uber robot journalist geek, which I’m not, really, but trying to follow these principles helps me pretend.

Your job is not your admin

  • Every job has a tedious admin phase you have to deal with every day. But that’s not your real job – it takes time away from doing what you need to do.
  • The most basic ways you can be more awesome involve cutting down on admin time and increasing the time you spend actually working.
  • I keep track of what I do to work out which tasks take up time without contributing anything meaningful. I’ve used Rescue Time, Remember The Milk, Epic Win and custom Google Docs to track this in the past.
  • Once I’ve worked out where there’s time to be saved, I start working out how to save it. This is useful admin time.
  • It’s always worth learning keyboard shortcuts for any program I use daily. It saves small chunks of time over and over again.
  • I use a To Do list for big stuff that needs it rather than day-to-day routine things – I’m using Remember The Milk at the moment, but I tend to rotate list apps every few months because otherwise the novelty wears off and I stop using them. I’ve used 2Do, Google Tasks, Outlook Tasks, Doomi, enormous spreadsheets and Epic Win in the past.

Repeated tasks can be automated

  • It’s worth a day of my effort to automate something that takes me more than about 20 minutes a day to do. If it’s an interruption or a flow-breaking task or something I will have to do every day for a year, it’s probably worth more.
  • I think of certain tasks – finding sources on Twitter, for instance, or researching a topic for a story – as building a re-usable resource, not a one-off event. It takes much less effort to build a Twitter list or filter and aggregate a few RSS feeds the first time around, so you can go straight back to your sources if you’re doing a follow-up.
  • I use a lot of dashboards. The new Google Analytics beta lets me customise and keep half a dozen ways of slicing web data at my fingertips, so I can answer common business questions in seconds not hours. iGoogle combined with custom alerts by RSS lets me filter the entire web for certain subjects. Hootsuite and Tweetdeck let me monitor social networks in similar ways.
  • I use macros to automate tasks in Excel and Word. I use Google Docs with various APIs to build a few regular reports, occasionally combined with ScraperWiki. I build a lot of very specific spreadsheets where I can plug in data in a certain format and get back insights very quickly. I try to build things that can be re-used or re-purposed.
  • If there’s a boring repetitive task, there’s almost certainly a plugin or a script somewhere on the internet that’ll help you make it faster or easier. Sometimes those are more work to rewrite/implement than it would be just to get on with it. Other times they’re lifesaving.
  • Greasemonkey can be astonishingly helpful in saving little annoyances (and big ones, sometimes). For instance, I love this script that automatically pushes the “access analytics” button in Google Analytics. It saves one click – but it saves it three or four times every single day.
  • After all that – I do very little coding. I mostly borrow other people’s code and put it to use in new situations.

All information can be filtered

  • Twitter lists, search operators and even individual users if they’re focussed on a specific topic of interest. The -RT search operator is fantastic. Topsy‘s advanced search is also amazing powerful. And it has an API, which I haven’t yet worked out how to use to best advantage.
  • RSS folders in Google Reader (or a similar reader service) and combinations and filters using Yahoo Pipes. Postrank is an awesome service that helps you filter popular and engaging content from feeds. Combining Postrank with Pipes gives you neat automatic filters.
  • Google alerts, especially using advanced search terms – you can use site:youtube.com with keywords to build a video alert service, for instance.
  • Google custom search – great for checking whether anyone’s covered a particular story, or for working out who on your beat is talking about a certain subject – just give it a list of links.

Interruptions can be limited

  • I use rules in Outlook to limit the number of times I see email alerts – I have several set up to filter out various levels of noise, including a white-list for emails most likely to need urgent responses. It was well worth the time spent setting these up – if every pop-up on-screen is only 5 seconds of attention, I’ve still saved more than 5 minutes a day.
  • I use rules in Gmail to sort incoming mail by priority, and use the email game to deal with it all in small bursts, quickly and efficiently, when it’s convenient rather than when a mail comes in.
  • I turn off email notifications for sites I visit every day anyway. I set up as much as possible to come via RSS (where I can filter it using Yahoo Pipes and categorise it in a sensible folder) or via Twitter (where its immediate impact is limited to 140 characters).
  • When I need to focus, I stay away from Tweetdeck completely. I have a 2-column view in Hootsuite with nothing but mentions and direct messages, so I can see anything requiring urgent responses at a glance. I turn my iPhone off.

Waiting kills productivity

  • If a task I do regularly is governed by a set of rules and involves waiting for something to happen, I do my best to automate it away. I win twice.
  • If I’ve got to do something that involves waiting, I plan for the wait: go take a break, stretch, do a simple time-limited task.
  • I have a  folder of RSS feeds from folks who write short, and I read a couple while Iwait. And I have Reeder on my iPhone, for long out-of-the-office waits (some people call them “commutes”).
  • I save up several stop-start tasks and use them as a “distraction loop” – taking each one in turn and switching when a wait starts.

What do you do to hack your workflow? What tools do you use to simplify the stuff that doesn’t matter and help you spend more time on the stuff that does?