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