the path from solutions
      back to needs
integrating web2.0 in the enterprise successfully
           [a ‘twitterized’ ...
show of hands:




      2
how many of you have
implemented web2.0 tools on
    your site(s) already?




             3
…are implementing web2.0
     tools right now?




           4
…are planning to implement
web2.0 tools in the not-too-
      distant future?



             5
…feel >90% confident the new
      tools are going be
  embraced by your users?



             6
this is our greatest challenge




              7
1
                  >80% of wikis fail
    (nevermind mashups, abandoned blogs, etc.)




Source: CIO Magazine, Feb 28, 20...
what works on the web
doesn’t necessarily work
inside our organizations



           9
why?




 10
…because we found a solution
before identifying our problem




              11
…because we focused on how
  and when instead of on
     whether and why



            12
…because we don’t know (or
  listen to) our audience




            13
…because we don’t
understand the tools and the
     needs they satisfy



             14
“I yam what I yam”
             -Popeye




        15
the presence of technology
won’t change human nature




            16
…it will only amplify it




           17
great, so now what?




         18
3 options:




    19
1. plow ahead




      20
2. stop




   21
3. pause




   22
the path forward:




        23
1. learn more about your
         audience




           24
2. learn more about the tools
and the “-ations” they serve




              25
communication | collaboration
estimation | metadata creation
  aggregation | socialization



              26
3. find a specific
problem, project, product, gro
       up, scenario…



              27
…where there is a clear
purpose and a common
      interest…



           28
…and where the tool can be
integrated as a part of the
  users’ normal activities



             29
the key is to start small, but
keep the larger picture in mind




               30
resist the urge, and the peer
           pressure




              31
just because these are “grass-
 roots” applications does not
   mean that planning isn’t
          required



           ...
avoid the SharePoint pitfall
(hang on microsoft platinum sponsor guy in the
              back, I’ll explain)




        ...
great tool, but often
implemented with minimal
         planning



           34
good luck harvesting
information out of 10 gazillion
    SharePoint teamsites
       after-the-fact…



               35
and if you can harvest it, good
        luck managing it




               36
web 2.0 is great, but let’s not
 throw caution to the wind




               37
find a balance:
avoid analysis paralysis, but
  proceed with caution…



              38
and be armed with a clear
   purpose, a grounded
understanding, and a sound
           plan



            39
scott liewehr, onesta
scott.liewehr@onestagroup.com
     www.onestagroup.com
         twitter: sliewehr
Upcoming SlideShare
Loading in …5
×

Web 2.0 & CMS - The Path From Solutions Back To Needs

1,017 views

Published on

Presentation from 6/3/09 @ Gilbane San Francisco

Let's get away from putting the cart before the horse and focus on the tried and true practices to ensure adoption of web 2.0 tools for organizations (inside or out).

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,017
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Web 2.0 & CMS - The Path From Solutions Back To Needs

  1. 1. the path from solutions back to needs integrating web2.0 in the enterprise successfully [a ‘twitterized’ presentation] Scott Liewehr Gilbane Conference San Francisco | June 3, 2009
  2. 2. show of hands: 2
  3. 3. how many of you have implemented web2.0 tools on your site(s) already? 3
  4. 4. …are implementing web2.0 tools right now? 4
  5. 5. …are planning to implement web2.0 tools in the not-too- distant future? 5
  6. 6. …feel >90% confident the new tools are going be embraced by your users? 6
  7. 7. this is our greatest challenge 7
  8. 8. 1 >80% of wikis fail (nevermind mashups, abandoned blogs, etc.) Source: CIO Magazine, Feb 28, 2008 8
  9. 9. what works on the web doesn’t necessarily work inside our organizations 9
  10. 10. why? 10
  11. 11. …because we found a solution before identifying our problem 11
  12. 12. …because we focused on how and when instead of on whether and why 12
  13. 13. …because we don’t know (or listen to) our audience 13
  14. 14. …because we don’t understand the tools and the needs they satisfy 14
  15. 15. “I yam what I yam” -Popeye 15
  16. 16. the presence of technology won’t change human nature 16
  17. 17. …it will only amplify it 17
  18. 18. great, so now what? 18
  19. 19. 3 options: 19
  20. 20. 1. plow ahead 20
  21. 21. 2. stop 21
  22. 22. 3. pause 22
  23. 23. the path forward: 23
  24. 24. 1. learn more about your audience 24
  25. 25. 2. learn more about the tools and the “-ations” they serve 25
  26. 26. communication | collaboration estimation | metadata creation aggregation | socialization 26
  27. 27. 3. find a specific problem, project, product, gro up, scenario… 27
  28. 28. …where there is a clear purpose and a common interest… 28
  29. 29. …and where the tool can be integrated as a part of the users’ normal activities 29
  30. 30. the key is to start small, but keep the larger picture in mind 30
  31. 31. resist the urge, and the peer pressure 31
  32. 32. just because these are “grass- roots” applications does not mean that planning isn’t required 32
  33. 33. avoid the SharePoint pitfall (hang on microsoft platinum sponsor guy in the back, I’ll explain) 33
  34. 34. great tool, but often implemented with minimal planning 34
  35. 35. good luck harvesting information out of 10 gazillion SharePoint teamsites after-the-fact… 35
  36. 36. and if you can harvest it, good luck managing it 36
  37. 37. web 2.0 is great, but let’s not throw caution to the wind 37
  38. 38. find a balance: avoid analysis paralysis, but proceed with caution… 38
  39. 39. and be armed with a clear purpose, a grounded understanding, and a sound plan 39
  40. 40. scott liewehr, onesta scott.liewehr@onestagroup.com www.onestagroup.com twitter: sliewehr

×