links for 2008-12-18

links for 2008-12-17

  • "Beat blogging really is a give and take. It’s not about marketing the same old content in new ways or pushing old content onto new platforms. Beat blogging is about expanding ones network of sources." I actually like how Patrick put it on Twitter: "Journalists have to be social on social media for it to work." I'll elaborate on that in a long overdue post shortly.

links for 2008-12-16

  • Keith and the Girl is a great little podcast that I listen to occasionally, and if traditional media want to make the transition from mass media to social media, they should read these tips. I'll be writing about my recent US election road trip, and I used many of the same techniques to build community around the project. Live events and rewarding your most passionate supporters are a good place to start. If you reward positive behaviour instead of just punishing negative behaviour, you'll grow a strong, happy community.
  • Is consolidation the answer that will save newspapers? If it was, Gannett would be doing better.
  • Heather Hughes is asking question that a lot of journalists are asking right now. What next? The photojournalist left newspapers after climbing the ranks only to find her opportunities drying up. The fact of the matter is that the market for journalists is shrinking, and many of us who had planned to spend the rest of our lives doing journalism have to consider something else to do. She started her own wedding photography business, but I wonder what text journalists will do. The one thing she asks fellow photojournalists is not to undercut each other and agree to cutrate fees. During desperate times, she advises not to give into desperation.

20 signs you don’t want that internal social media project

I just nearly burst my appendix laughing at Chris Applegate’s 20 signs you don’t want that social media project. I am thus inspired to write my own list of tips that, perhaps, one doesn’t really want that internal social media project after all.

  1. Client wants to code their own blog/wiki software because “we want total control”.
  2. Client insists that only the management be allowed to have internal blogs.
  3. The PR department wants to write the CEO’s internal blog posts.
  4. IT won’t allow anyone to install an RSS reader until it’s been through a code review. Which could take upwards of a year. And that’s not including reviewing updates…
  5. Client insists on using Lotus Notes as their blogging platform.
  6. When you ask how much experience staff have of social media, IT replies, “Oh, we block all those sites.”
  7. The client wants Facebook.
  8. “Why don’t we just throw some mud at the walls and see what sticks?”
  9. IT disables all RSS feeds because of “a potential exploit we read about on Slashdot”.
  10. Client insists on using Sharepoint as their wiki.
  11. User surveys show some staff have more than 50,000 unread messages in their inbox, yet management insist, “We really don’t have a problem with email here.”
  12. Management refuse to learn new terminology, resulting in statements like “I just posted a new blog to our wiki.”
  13. Apparently, IM is “just for kids.”
  14. Client decides that only “management-approved labels” can be used as tags in the social bookmarking app.
  15. Client’s wiki is called CompanyPedia, is already out of date and is never used for actual collaboration.
  16. IT eschew open source software because “Who would provide support?”
  17. There are regular discussions as to which is the best Web 2.0 application: Lotus Notes or Sharepoint?
  18. “Why don’t we just install some forums?”
  19. Client thinks that “adoption” means everyone is going to end up looking after a small orphaned child.
  20. The CIO still has his secretary print out all his emails.

UPDATE: The above list has now been translated into French by the lovely Frédéric de Villamil!

links for 2008-12-11

links for 2008-12-09