Scott Liewehr presented on successfully integrating web2.0 tools in enterprises. He found that over 80% of wikis fail because organizations implement tools before understanding user needs and without planning. Liewehr recommends organizations first learn about their audiences' needs and how tools like communication and collaboration platforms can meet those needs. They should then start small by finding a specific use case where the tool enhances existing workflows. Planning is still required even for grassroots tools to avoid failures seen with poorly planned SharePoint rollouts and ensure web2.0 benefits the organization.

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. show of hands:
2

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

4. …are implementing web2.0
tools right now?
4

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

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

7. this is our greatest challenge
7

8. 1
>80% of wikis fail
(nevermind mashups, abandoned blogs, etc.)
Source: CIO Magazine, Feb 28, 2008
8

9. what works on the web
doesn’t necessarily work
inside our organizations
9

10. why?
10

11. …because we found a solution
before identifying our problem
11

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

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

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

15. “I yam what I yam”
-Popeye
15

16. the presence of technology
won’t change human nature
16

17. …it will only amplify it
17

18. great, so now what?
18

19. 3 options:
19

20. 1. plow ahead
20

21. 2. stop
21

22. 3. pause
22

23. the path forward:
23

24. 1. learn more about your
audience
24

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

26. communication | collaboration
estimation | metadata creation
aggregation | socialization
26

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

28. …where there is a clear
purpose and a common
interest…
28

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

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

31. resist the urge, and the peer
pressure
31

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

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

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

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

36. and if you can harvest it, good
luck managing it
36

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

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

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

40. scott liewehr, onesta
scott.liewehr@onestagroup.com
www.onestagroup.com
twitter: sliewehr