Planning New Media Projects: What Every Manager Should Know


Published on

Douglas Arellanes' talk from the "New Media Essentials for NGOs" training organized by Transitions Online in Prague, 25-29 January 2010.

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Planning New Media Projects: What Every Manager Should Know

    1. 1. Planning New Media Projects What every manager needs to know Douglas Arellanes, Media Development Loan Fund
    2. 3. The Big Picture Flickr: Ethan Hein
    3. 4. The Big Picture Flickr: Ethan Hein Technology is Cheaper More widespread More adopted More complicated?
    4. 5. Setting clear goals for your tech <ul><li>Common mistakes </li></ul><ul><li>How to communicate with techies </li></ul><ul><li>Practical advice </li></ul>Flickr: Itsgreg
    5. 6. Tug of War <ul><ul><li>Coordination and transparency </li></ul></ul><ul><ul><li>Secrecy and privacy </li></ul></ul>Flickr: Quasarsglow
    6. 7. Tug of War <ul><ul><li>Mass audience </li></ul></ul><ul><ul><li>Targeted audience </li></ul></ul>Flickr: Quasarsglow
    7. 8. Tug of War <ul><ul><li>Price </li></ul></ul><ul><ul><li>Performance </li></ul></ul>Flickr: Quasarsglow
    8. 9. Tug of War <ul><ul><li>Getting it perfect </li></ul></ul><ul><ul><li>Getting it out on time </li></ul></ul>Flickr: Quasarsglow
    9. 10. How to communicate with your geeks Flickr: Grant Mitchell
    10. 11. <ul><li>Learn about what the techies are doing for you </li></ul>Douglas Arellanes
    11. 12. <ul><li>Focus on what you want, not how you get it </li></ul>Flickr: Chris Owensl
    12. 13. <ul><li>Be consistent with your requirements </li></ul>Flickr: Jon Watson
    13. 14. <ul><li>Changing the requirements changes the price </li></ul>Flickr: Alastair Thompson
    14. 15. <ul><li>Make a specification and stick to it </li></ul>Flickr: Define23
    15. 16. <ul><li>Identify “interpreters” you can communicate with (and through) </li></ul>Flickr: Petteri Sulonen
    16. 17. How to communicate with your geeks <ul><li>Agree on clear deliverables </li></ul><ul><li>Agree on a timeline and tie delivery to full payment </li></ul><ul><li>Understand their motivations </li></ul><ul><ul><li>Are your techies “mercenaries” or “true believers?” </li></ul></ul><ul><li>Get a second opinion </li></ul><ul><ul><li>And maybe a third </li></ul></ul><ul><li>Don't be intimidated </li></ul><ul><ul><li>It's your project </li></ul></ul>
    17. 18. What makes technology projects fail? Flickr: Rebecca Lader
    18. 19. What makes technology projects fail? <ul><li>No commitment </li></ul><ul><li>Too ambitious </li></ul>Flickr: Rebecca Lader
    19. 20. What makes technology projects fail? <ul><li>Outsourcing everything </li></ul><ul><li>“ Not invented here” syndrome </li></ul>Flickr: Rebecca Lader
    20. 21. What makes technology projects fail? <ul><li>“ Mission creep” </li></ul><ul><li>“ Abandonware” </li></ul>Flickr: Rebecca Lader
    21. 22. What makes technology projects fail? <ul><li>No planning past the launch </li></ul><ul><li>No planning for contingencies </li></ul>Flickr: Rebecca Lader
    22. 23. What makes technology projects fail? <ul><li>Putting everything in one staffer’s hands </li></ul>Flickr: Rebecca Lader
    23. 24. Reinventing the wheel!
    24. 25. Accidents will happen. Plan for them. Flickr: Gravestone
    25. 26. Contingency planning <ul><li>Build contingencies into the plan </li></ul><ul><ul><li>Budget </li></ul></ul><ul><ul><ul><li>Set aside a certain percentage for contingency </li></ul></ul></ul><ul><ul><li>Identify potential workarounds </li></ul></ul><ul><ul><li>Set clear priorities </li></ul></ul><ul><ul><ul><li>What is “must have” and what is “nice to have”? </li></ul></ul></ul>
    26. 27. <ul><ul><li>Time </li></ul></ul><ul><ul><ul><li>Identify which tasks can take longer </li></ul></ul></ul><ul><ul><ul><li>Build in “pre-launch holds” </li></ul></ul></ul>
    27. 28. Managing a team in multiple locations <ul><li>Communications tools </li></ul><ul><li>Working processes and rules </li></ul><ul><li>Regular face-to-face meetings </li></ul>
    28. 30. Communications tools <ul><li>Skype </li></ul><ul><ul><li>Encrypted </li></ul></ul><ul><ul><li>Chat </li></ul></ul><ul><ul><li>File sharing </li></ul></ul><ul><li>Mailing lists </li></ul><ul><li>Google Documents </li></ul><ul><ul><li>Good coordination tools </li></ul></ul><ul><li>Wiki </li></ul>
    29. 31. Working processes and rules <ul><li>Deadlines </li></ul><ul><ul><li>Be strict, but be realistic </li></ul></ul><ul><li>Payment </li></ul><ul><ul><li>Based on delivery, not salary </li></ul></ul><ul><li>Documentation </li></ul><ul><ul><li>Write down work processes </li></ul></ul><ul><ul><li>Share them online </li></ul></ul><ul><ul><li>Stick to them </li></ul></ul>
    30. 32. Cross-cultural misunderstandings <ul><li>Prepare time to mediate between different cultures </li></ul><ul><li>Assume people mean well </li></ul>
    31. 33. Flickr: Stefano Corsa (pensiero) ‏
    32. 34. Flickr: Wetwater
    33. 35. Cory Doctorow
    34. 36. “ Your work needs to be easily copied , to anywhere whence it might find its way into the right hands.
    35. 37. That means that the nimble text-file, HTML file, and PDF (the preferred triumvirate of formats) should be distributed without formality Flickr: Haribote
    36. 38. no logins, no e-mail address collections and with a license that allows your fans to reproduce the work on their own in order to share it with more potential fans. Flickr: SLDownard
    37. 39. Remember, copying is a cost-center insisting that all copies must be downloaded from your site and only your site is insisting that you — and only you — will bear the cost of making those copies. Flickr: Jared_Cherup
    38. 40. Sure, having a single, central repository for your works makes it easier to count copies and figure out where they're going, but remember: dandelions don't keep track of their seeds. Flickr: Fotos by Dee
    39. 41. Once you get past the vanity of knowing exactly how many copies have been made, and find the zen of knowing that the copying will take care of itself, you'll attain dandelionesque contentment. Flickr:Óli Jón
    40. 42. Once your work gets into the right hands, there needs to be an easy way to consummate the relationship. Flickr:wetwater
    41. 43. Flickr:wetwater A friend who runs a small press recently wrote to me to ask if I thought he should release his next book as a Creative Commons free download in advance of the publication, in order to drum up some publicity before the book went on sale.
    42. 44. I explained that I thought this would be a really bad idea. Internet users have short attention spans. Flickr:Bob Au Buchon
    43. 45. The moment of consummation — the moment when a reader discovers your book online, starts to read it, and thinks, huh, I should buy a copy of this book — is very brief. Flickr: Private Custard
    44. 46. That's because “ I should buy a copy of this book” is inevitably followed by Flickr:wetwater
    45. 47. “ Woah, a youtube of a man putting a lemon in his nose!”
    46. 48. and the moment, as they say, is gone.
    47. 50. cc: Aid85@Flickr
    48. 51. cc: Bern@t@Flickr
    49. 52. Thank You! Douglas (dot) Arellanes (at) Skype/Twitter: dougiegyro Facebook: douglasa