Book - Collaboration in The Cloud - OK
Book - Collaboration in The Cloud - OK
Book - Collaboration in The Cloud - OK
Then
in Chapter 3 we introduce the new nature of the frm, where not just com-
petition but especially collaboration is of the essence for survival. We intro-
duce the value chain 2.0.
Chapter 9 will hand you a list of questions to use to keep your feet on
the ground. It will serve to measure the reality of any proposal and guide
you when examining cloud and collaboration further, in combination with
Chapter 10.
In Chapter 10 we debunk some of the common myths around
collaboration.
J
T
U
I
F
F
O
E
U
P
F
O
E
F
Y
Q
F
S
J
F
O
D
F
E
F
M
J
W
F
S
F
E
8IPNBOBHFTUIFBQQMJDBUJPO
TPGUXBSFFYQFSJFODF4-"
Customer-
managed
Provider-
managed
Co-managed
Hosted
outsourced
IT
Traaditional
software
Software
as a Service
Building Block
Services
Co-location
Services
Hosted
Infra & Applications
Todays
In-House IT
Outsourced IT,
On-site Contractors, Asset Transfer, etc.
Finished
Services
Attached
Services
Figure 7.5: Delivery Model shows some dimensions of services versus control. An
example of a building block service is Amazon EC2, an attached service could be
Microsoft Exchange hosted services, and a fnished service could be Microsoft Offce
Live Online
Obviously, there are implications for IT visibility and for the concomitant
governance models based on the choice of where in the spectrum the organ-
ization decides to source a service. Clearly, on-premises application infra-
structure enables the most robust governance models whereas cloud-based
services pose challenges with respect to data privacy, data harmonization,
and control and archiving.
Heterogeneous User Profles and Populations
Organizations are realizing that they have a wide and diverse set of users,
ranging from (usually) centrally located knowledge workers through produc-
tion/task workers, contract employees, freelancers, then partners, suppliers,
and more and more customers with whom they have to support and interact
the organization providing the appropriate access and security for each
individual.
173
7 Mixing Software + Services
For example, many new real estate companies often have only relatively few
centrally located employees and the vast majority of the people whom they
must support may be independent, self-employed real estate agents, some of
whom may even be freelancers working to their own constraints and sched-
ules. On the other hand, an organization such as Microsoft has a large
number of full-time and often centrally located employees and comparatively
fewer freelancers, vendors and contractors. In either case, IT is responsible
for the productivity of all of the individuals in the organization and the busi-
ness as a whole.
More and more organizations with signifcant manufacturing units ask why
they need to provision on-premises email capabilities for their shop-foor
employees. While email may be the vehicle to share organization-wide infor-
mation and updates, it is quite likely that many of these employees will not
access their email, and that a manager may print out the information and
put it up on a bulletin board. They usually start by asking, Why not use a
so-called consumer provider for these user populations? And while some
may beneft and derive value from these services, many are more likely to
look to and leverage commercial grade cloud-based services for these user
populations.
This brings us to the realization that there is not only a spectrum of services
(from internally provided to cloud-provided), but there is also a spectrum of
roles, ranging from centralized (corporate) users to customers or even the
general public. Each of these roles will have a different expectation for the
services they consume: for a corporate user robustness might be essential,
while for someone in the general public the level to which the service can be
integrated (for example, into Facebook) might be more important.
Multi-Headed User Experiences
The customer experience for the future appears to be multi-headed. There
will be a diversity of software and services for the various channels and
devices and the user experience will be tuned to the channel and the inter-
action whether it be a mobile device, a TV, a PC or the rich web. And prob-
ably the best example of this is the email experience Microsoft delivers to its
customers today around Exchange. A user could fnd the richest experience
through Outlook; for a more casual experience, a user with a browser could
also use Outlook Web Access, and a user could use Outlook on a variety of
174
Collaboration in the Cloud
mobile and other devices. A user plowing through a lot of email is more likely
to use Outlook. If the user is on an airplane trying to catch up, that user will
most likely only use Outlook. But if the user is doing some casual email, or
is at an internet kiosk, that user is more likely to use Outlook Web Access.
And a user on the go can use the most convenient available device to access
the same email.
Business Implications
IT organizations of all sizes and from all industry sectors are looking for a
model of IT usage to support their wide spectrum of user profles and user
populations, and a spectrum of available application services is promising
the ability to meet this need. Organizations are seeing the potential of being
able to provide the right levels of service to their entire range of IT users in
a dynamic and agile fashion; that is the ability to provide a new level of Dif-
ferentiated IT. Businesses are thinking in terms of their IT portfolio a
portfolio of capabilities that they want to intentionally partition across both
on-premises and cloud-based software.
7.5
Conclusion
The IT industry has historically been defned by a sequence of infection
points in the way consumers and businesses beneft from computing, and we
are in the midst of another momentous shift a services transformation.
Software as a Service (SaaS) is fundamentally about service delivery
changing how we think about both deployment and delivery of new software
applications. Many of the core assumptions and constraints in the conven-
tional approaches to software deployment and delivery are being challenged
and overthrown with this infection point in service delivery.
Service-Oriented Architecture (SOA) is about the harmonization of multiple
systems and services and fundamentally about service federation and serv-
ice composition. Many of the basic assumptions about applications have been
challenged with the emergence of SOA. The notion of an application as a
static entity has been replaced by the notion of an application as a dynamic
composition of services, often directed by the end user.
175
7 Mixing Software + Services
Web 2.0 is about the social and collaborative experiences made possible
through services on the cloud, and about their monetization. Many of the
core assumptions about the user experience and monetization have been
overthrown by the emergence of the Web 2.0 model.
Together, SaaS, SOA and Web 2.0 are converging to create a new software
architecture model a model of Software + Services. This model is based on
the premise that the harmonization of on-premises software and cloud-based
services will be superior to either of those approaches in isolation. As we
move to software interaction through a broader mix of digital devices and
form factors, the multi-headed experience will become the default user
scenario for both consumers and business users. Being able to optimize the
mix of software and services gives IT the visibility and control to understand
whats happening both inside and outside the corporate network, as well as
the necessary fexibility in intentionally partitioning which capabilities are
best delivered on-premises versus in the cloud. Software + Services will
ultimately enable business to have the optimal portfolio of capabilities to
meet the unique needs of each and every individual user.
The social and inherently cross-boundary nature of collaboration drives the
need for such a user-focused architecture that can quickly deliver highly
useable and fexible support for collaboration. Self provisioning and quick
response to new collaboration partners are essential. When information and
activities need to cross borders, the technology needs to support it smoothly,
driving towards this architecture where all sorts of services can be combined
into one portfolio that the user can pick and choose from. Also, when organ-
izations are looking to more extensively collaborate and combine their serv-
ices to a new offering to the market, the integration of IT needs a pragmatic
approach with the ability to make strategic decisions about who does what;
the essence of SaaS and Software + Services.
177
Case ITAGroup
Case: ITAGroup Leaps Into the World of Collaboration
Need to Share Intellectual Property Spurs Move
If there were ever a company ideally suited to beneft from collaboration technology,
it would be ITAGroup. Until now, the expert in people performance management has
relied on the rudimentary internal collaboration capabilities built into the Microsoft
Ofce suite not well suited for such a dynamic, team-oriented organization.
Given the nature of ITAGroups $200+ million-a-year business, the lack of a collabo-
rative environment has been a glaring hole in its quest for greater productivity. In its
role helping clients establish and administer sales, employee and channel perform-
ance improvement programs, ITAGroup assembles teams of people plucked from six
diferent functional areas to support programs that will run at least a year. Each team
must coordinate skills ranging from program development and marketing communi-
cations to technology support and client interaction. Plus, an internal survey found
that, on average, ITAGroup employees work on 6 teams at a time, and up to 20 dur-
ing the course of a year.
Without an efective collaboration platform, managing so many variables has been
a challenge. Communication has been handled via email, resulting in attachments
at varying stages of development being scattered among multiple inboxes, and chok-
ing storage resources. Additionally, the lack of a standardized methodology for stor-
ing critical data has made fnding information nearly impossible. The biggest chal-
lenge we faced was efectively bringing new team members into a project, says John
Rose, vice president of information technology. We needed to be able to share
information, ideas and documents more easily.
Good Technology + Employee Buy-In = Faster Path to Success
ITAGroup believes it has found the answer in the form of Microsoft SharePoint Server
2007. SharePoint features an interface thats familiar to anyone accustomed to work-
ing in Windows. Its easy to set up a collaborative site, it has powerful search capa-
bilities embedded in it, and it can take all that scattered information from email
inboxes and desktop fle systems and make it easily discoverable to anyone with
permission to access it.
ITAGroup is in the midst of a company-wide rollout of the technology, with the frst
collaborative elements introduced to all employees in January 2009. The companys
intranet is running on SharePoint, where its storing corporate data such as ISO
documentation and employee information. A team has been working with consult-
ants from Sogeti to implement an out-of-the-box SharePoint environment thats
requiring less than a $400,000 investment over 3 years.
178
Collaboration in the Cloud
But, as anyone whos overseen a collaboration deployment can attest, merely acquir-
ing technology no matter how well suited it is to the job at hand is only half the
battle. Bringing people up to speed on the new tools, showing them how to fnd
information, and work in tandem more efectively takes time. Change is never easy,
says Rose. But we know that a gradual implementation, progressively adding fea-
tures and functionality, will ease the transition and build excitement. The result is
adoption of an improved collaboration environment, which will ultimately result in a
better company. Rose has been encouraged to hear reports that many SharePoint
customers who experience some initial frustration adjusting to the technology, soon
see the technology as a cant-live-without-it tool.
Getting the Most out of SharePoint: Simplicity Breeds Momentum
Advancing SharePoint to that status, however, requires employees get behind the
technology. And Rose says hes learned that when it comes to a collaboration envi-
ronment, marketing and positive reinforcement of the technology is important. To
make a tool like SharePoint really work, employees have to know about it, and they
have to be convinced to use it. To that end, Rose says its critical to keep things sim-
ple, even if SharePoint has myriad capabilities that can be rolled out at once. Things
have to remain simple.
Once the company builds the momentum it needs, the anticipated benefts of Share-
Point run the gamut. Rose expects it to spur big savings by simply cutting the amount
of time employees spend searching. He also believes that the combination of more
timely information and faster responses will lead to improved customer satisfaction.
That satisfaction fgures to rise further a year or so down the line, when ITAGroup
hopes to extend the SharePoint capabilities to an extranet that will enable clients to
log in and approve copy or artwork, access workfows, or simply get the latest data
on their various performance improvement programs.
Perhaps most importantly, SharePoint will gradually help lower the information shar-
ing walls that have existed between ITAGroups teams and team members. And with
everyone on the same page, management will be able to think outside the box more
than ever, armed with a tool that can evolve to make employees jobs easier.
179
8
Social Computing for Business
8.1
Introduction
1
We have been looking at markets, the concepts behind collaboration and
cloud computing. We have explored the anatomy and success criteria of col-
laboration, and we have looked at a model of a mix of Software + Services
that gives us the fexibility needed to achieve it all. In this chapter we will
discuss more scenarios in which Web 2.0 technologies and the model of Soft-
ware + Services can be used inside organizations. The areas and scenarios
discussed are also the areas where you can fnd value, some of which can
perhaps even be included in a traditional business case for a project. A lot
of the scenarios in this chapter revolve around the theme of A New World
of Work.
The New World of Work
2
In a new world of work, where collaboration, business intelligence and prioritizing
scarce time and attention are critical factors for success, the tools that information
workers use must evolve in ways that do not add new complexity for people who
already feel the pressure of an always-on world and ever-rising expectations for
productivity. We believe that the way out of this maze is through integration, simplifca-
tion, and a new breed of software applications and services that manage complexity
in the background, and extend human capabilities by automating low-value tasks and
helping people make sense of complex data.
Bill Gates
8.2
The Emergence of Social Computing
In the current conversation economy, we are seeing enormous changes in
the way that we publish and consume information on the internet. Rather
than simply viewing information on static web pages we are now publishing
1 http://msdn.microsoft.com/en-us/library/bb735306.aspx forms the basis of this chapter. Michael Platt
of Microsoft Corporation is the original author of much of the content that is re-used here.
2 http://www.microsoft.com/mscorp/execmail/2005/05-19newworldofwork.mspx.
180
Collaboration in the Cloud
rich content through blogs and wikis and on photo- and audio- and video-
sharing sites. Instead of solely being consumers of pages downloaded from
the web, people are now sharing, collaborating and creating new content and
entire online communities. Indeed, people are now combining data and con-
tent from multiple sources to create their own custom, personalized experi-
ences and applications.
Many of these evolving concepts and capabilities were dubbed Web 2.0 in
a seminal discussion paper by Tim OReilly in September 2005.
3
In essence,
it is the collective realization that the ability to use the web to write as well
as read rich content, along with support for social networking and the rapid
spread of broadband access, combines to allow people to interact with the
web, online content and one another. At its core this is about fundamentally
changing the ways people interact with content, services and with other
users to provide a platform for harnessing and promoting collective intelli-
gence.
4
Wikipedia defnes collective intelligence as shared or group intelligence that
emerges from the collaboration and competition of many individuals. People
are no longer just passive consumers of content and data; they are active
participants, and in many cases they are creators creating content and
interacting with a multitude of services and people. Sometimes referred to
as the network effect, this increase in participation, collaboration and in
content creation presents new opportunities to involve the end user in deeper
and more meaningful ways.
We are only just beginning to see the opportunity for these emerging con-
cepts and capabilities both inside and outside the organization, but it prom-
ises to have dramatic and long-lasting impact on business. In the rest of this
chapter we will look at more specifc scenarios in which technology can be
used to be productive in Web 2.0, we will talk about the technology side of
the conversation economy, and we will discuss the roles cloud computing and
Software + Services play in the space.
3 http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html.
4 http://en.wikipedia.org/wiki/Collective_intelligence.
181
8 Social Computing for Business
8.3
Collaboration and Social Computing in the Enterprise
Organizations of all types and sizes from startups to Fortune 100 companies
and from all industry verticals have seen the explosive growth on the web
of social and community sites in the consumer space, such as MySpace,
YouTube and the deluge of Web 2.0 sites. They have seen the response by
major web players such as Amazon, eBay, Live and Google and Yahoo! in
adding social and community elements, and they have seen the interest and
demand that this has created. They are now actively investigating and in
many cases building new community-based portals and businesses for
their own organizations; Web 2.0 is moving into the enterprise.
There are two primary areas in which organizations are interested in using
these concepts and capabilities:
Enterprise 2.0: Inside the organization to improve effciency and produc-
tivity; and
B2C 2.0: Connecting with customers to improve proftability and customer
satisfaction.
The use within organizations is commonly called Enterprise 2.0
5
and is
typically the frst phase.
Usage to connect to their customers and consumers is similar to Business-
to-Customer (B2C) activity but with a social and community basis, and may
be termed Business-to-Community or B2C 2.0
6
. Interest in this use of the
community as a customer is rapidly growing. That is one of the reasons why
popular social networks like LinkedIn, Facebook, and MySpace, with all
their customer profles, are worth billions of dollars.
Enterprise 2.0
This is the kind of organization that we described throughout the earlier chap-
ters of this book. It is the enterprise where employees are autonomous and
collaborative and where bottom-up initiatives are well valued. Where so-called
information workers can be in charge of their own user experience and hence
create for themselves a more intuitive and effcient work environment.
5 http://sloanreview.mit.edu/smr/issue/2006/spring/06/.
6 http://msdn.microsoft.com/en-us/library/bb735306.aspx.
182
Collaboration in the Cloud
Business-to-Community (B2C 2.0)
Businesses of all types and sizes, from startups like Plentyoffsh to For-
tune 100 companies such as General Electric, have been keen to enter the
dialogue with consumers and communities using 2.0 tools. While it is
always smart for businesses to keep in touch with potential clients, the
necessity in this case is especially critical: it is a matter of survival but it can
also be an enormous opportunity.
On the opportunity side, the reasons for this interest and activity in the space
are fvefold:
1. Revenue and growth
The opportunity to enhance existing revenue streams and to build com-
pletely new revenue streams by utilizing community and social network-
ing capabilities. In particular, the cost containment of the recent past has
given way to an interest in the business side in innovation-driven growth
and revenue. The rapid growth and innovation in the Web 2.0 space is
seen as something that companies want to emulate.
2. Web-based economies of scale
Organizations see that they can dramatically decrease the cost of capital
equipment and resources by using a web based delivery model to serve
communities of their customers.
3. Flexible employment models
The use of contract and agency staff for delivery allows fexibility and
agility. Agency and contract staff can be thought of as another, specialized
community and so supported like customers.
4. Community creation as evangelism and support
Customers are the organizations best sales, marketing support and devel-
opment resource. The creation of communities effectively outsources, at
a very reasonable cost, all these cost centers. Indeed, with the inclusion
of targeted advertising to the community, the present cost centers poten-
tially become proft centers.
5. Community leader advantage
Community dynamics are such that the frst successful community is by
far the most powerful, so the organization that owns this community is the
one that controls the vertical. For example, MySpace focused on new music
bands and created a community in that space which it now effectively
dominates, so it has become a major force in the music industry. The con-
verse of this is that if an organizations competitors are frst in the com-
munity space, they will have a very signifcant competitive advantage.
183
8 Social Computing for Business
To make the concept of entering the dialogue a bit more specifc, we can
explore fve particular areas where social computing capabilities can be lev-
eraged in working with customer communities:
1. Innovation and New Product Development
As discussed before, open innovation or crowdsourcing are important trends
of the day. A very large percentage of new product ideas and innovations in
organizations come from suppliers and customers rather than from in-house
labs or R&D organizations. These new product ideas are more likely to be
successful as they have come from the end users of the product and are also
typically less cost-intensive. Clearly organizations that can build a system to
harvest these ideas can beneft from these innovations and derive signifcant
benefts.
The use of social computing based customer and supplier communities as
discussion forums and marketing focus groups for new product ideas and
incubation is a powerful, simple and cost-effective technique for gathering
these ideas. Many organizations are actively investigating the use of com-
munity forums and discussion groups to provide new product ideas and uses
in the product development process. Indeed it is possible to envisage a pro-
gram that automatically scans communities for new ideas and sends them to
interested parties.
An additional beneft of this community-based innovation and new product
development is that the customers have a better understanding of the prod-
uct or service delivered, as they were involved in its gestation, so the cus-
tomer uptake of the product is signifcantly enhanced.
2. Marketing
Probably the best-known application of social computing techniques in
organizations is around viral marketing. The examples of community and
rich content (such as video) being used to generate and spread buzz about
products and services are legion. There are two elements to this viral mar-
keting: initial interest generation and then the viral dissemination. The ini-
tial interest generation is best done with the use of innovative image, video
and audio content it is not unusual to get millions of downloads of creative
video within hours or days of their release, and ongoing interest in a product
can be sustained by having an informational or tutorial element to the con-
tent. The dissemination of this material is done by the internet community
at large using chat and messaging, email and community forums. Again this
184
Collaboration in the Cloud
dissemination can be very rapid and widespread. It is not unusual for a new
product or engaging video to be passed to millions of people in hours and to
reach the mainstream media such as TV or newspapers in days.
There are a couple of caveats about viral marketing. Firstly, the target audi-
ence needs to be well understood, and even then the material may not gather
community interest and buzz this is much more an art than a science. Sec-
ondly, an organization cannot control the spread or use of materials; the use
of viral marketing videos in unanticipated ways by the community is well
documented and can cause signifcant side-effects for an organization.
A great example of a viral video is the movie The Machine is Us/ing Us
7
by
the famous cultural anthropologist Michael Wesch. This movie explains in
a nutshell the whole Web 2.0 concept and how it is changing our society. The
video has been viewed more than 8.5 million times.
3. Sales
The cost of sale is normally a non-trivial element of the overall cost of a
product or service. In a Business-to-Consumer organization the community
can act as the collective salespeople, thereby dramatically reducing the cost
of sale, in many cases to nothing. The customers themselves act as spokes-
people and salespeople for the organization. There is no need for a high
pressure and high expenditure sales organization in community-based busi-
nesses, in fact, in many cases it might actually be counter-productive.
4. Support
Support is probably the second most popular area in which social computing
techniques are used. Firstly, there is the use of messaging and chat and other
collaboration techniques for real-time support of their products and services
by organizations. Secondly, there is the use of image capture and video for
problem communication and resolution. Finally and most importantly, there
is the use of community-based product experts and self help discussion
groups. This self-help technique has been shown to work very well in com-
munities such as the shared and open source movement and is a simple and
low-cost way of providing very high-quality support. As with most social-
based systems, however, the actual operation of these self-help groups is not
simple and requires signifcant thought and expertise.
7 http://www.youtube.com/watch?v=6gmP4nk0EOE.
185
8 Social Computing for Business
Support is one of the reasons why Apache and Linux have become so popu-
lar. The hard-core community behind these two open source initiatives is
famous for its online support. If a problem arises, it is sure to be solved
promptly. It is interesting to see that Microsoft picked up on this and has
built a vibrant technical support community for their technologies.
5. Training and Education
Probably the least explored application of social computing in the enterprise
is for training and education. The on-line availability of high-quality audio
and video and other rich media provides a very low-cost and frictionless way
of providing training as well as how to and other learning materials. This
rich content, when integrated with infuential subject matter experts and the
on-line communities and discussion groups, enables a very powerful envi-
ronment for education and training.
8.4
Web 2.0
The recent history of the internet has shown some very signifcant and far-
reaching changes. Ten years ago there were no web-sharing sites or applica-
tions, merely sites composed of static pages and e-commerce. Organizations
had customer-facing websites to connect with internet-savvy consumers and
used the internet as a way to market and sell their products. Internal corpo-
rate intranets were used mainly as a place to post news and policies in the
company portal. More recently, websites have become destinations for com-
munities of users to create and share rich and complex data such as music,
images and video, and to discuss and rate that content.
People are no longer just consumers of content and applications; they are
participants, creating content and interacting with different services and
people. More and more people are creating blogs, contributing to knowledge
bases such as Wikipedia, and using peer-to-peer (P2P) technologies. Some-
times referred to as the network effect, this increase in participation and
content creation presents new opportunities to involve the user in deeper,
more meaningful ways.
There has been a huge amount of discussion on what exactly is meant by
Web 2.0. Tim OReilly originally defned it as the following:
The web as a platform; 1.
Harnessing collective intelligence; 2.
186
Collaboration in the Cloud
Data as the next Intel inside; 3.
End of the software release cycle; 4.
Lightweight programming models; 5.
Software above the level of a single device; and 6.
Rich user experience. 7.
These can be grouped into three areas:
The use of the web as a platform;
The web as a place to read and write rich content; and
The social and collaborative use of the web.
The Web as a Platform
Web 2.0 systems use the web as a platform, conceptualizing the internet as
a huge range of interconnected devices that can provide a new level of rich
immersion for the user, an easy-to-use and lightweight programming model
for the developer and a rapid and fexible deployment mechanism for the
supplier. Web 2.0 uses the web to provide a new perspective for the user,
developer and supplier, a new way of thinking about the internet, all of which
allows new and creative uses of the internet.
It should be noted that an important concept underpinning all connected
systems, which of course includes Web 2.0, is that of a service. A service-
based system supports the concept of separation of concerns by the use of
loose coupling and concomitant message passing. This loose coupling allows
functionality to be created as a service and delivered over a network; so, for
example, diary functionality can be provided by a blog engine and be deliv-
ered as a service to the end user or blogger over the internet. Software as a
Service is this delivery of software functionality over the internet, and it
underpins most Web 2.0 systems today.
Looking at the internet as a platform we can see that it has to provide a
number of important platform concepts such as device independence, rich
and common user interface, a common programming interface and a soft-
ware deployment and management mechanism:
Software Above the Level of a Single Device
We are very familiar with software on a server providing services to soft-
ware on a PC (in Windows or in a browser), which then consumes or displays
187
8 Social Computing for Business
them. While this is a common and well understood model it does not cover
a number of common cases such as peer-to-peer systems or delivery to non-
PC devices like music players, phones or navigation devices. We need to have
a model that includes these cases and covers a higher level of service than
HTTP (the protocol used to transfer the pages of the internet we know and
use) to connect them; it needs to address the concepts of a music service such
as Napster or a communication service such as Skype. We need to have a
model that addresses software above the level of a single device and a single
service, but which includes rich, high level services interconnecting a mesh
of different device types in a symmetric manner.
Probably the best example of this type of high-level service is in Microsofts
game computer, Xbox Live, where gaming services are supplied between
specialist hardware devices working in a peer-to-peer manner. This model
is the general-purpose case of service-based computing and is the Software
+ Services model of computing.
Rich User Experience
The value of rich and immersive user experience has been well understood
in the PC world since the advent of Microsoft Windows, and this has been a
focus of browser based applications for many years. Standards such as Java-
Script and DHTML and technologies such as Flash and Silverlight were
introduced as lightweight ways of providing client-side programmability and
richer user experiences commonly called Rich Internet Applications.
It was a true revolution when a web browser was frst able to provide this
Rich Internet Application functionality. For the frst time, web application
could approach the experience of real desktop applications. Microsoft broke
ground in this feld by porting the familiar email client Outlook to a webver-
sion that very closely resembles the original. Outlook Web Access (OWA) also
used JavaScript and DHTML to provide rich interaction. The collection of
technologies used to provide these rich and dynamic browser-based systems
has been called Ajax, standing for Asynchronous JavaScript and XML. Ajax
isnt a single technology or even a set of new technologies but rather a set of
several technologies being used together in powerful new ways to provide
Rich Internet Application functionality. Ajax includes:
Standards that help styles and presentation (using XHTML and CSS);
Dynamic display and interaction (using the Document Object Model );
Data interchange and manipulation (using XML and XSLT);
Asynchronous data retrieval (using XMLHttpRequest); and
A programming language (using JavaScript).
188
Collaboration in the Cloud
Ajax is an important component of most Web 2.0 applications and is provid-
ing the ability to create web applications nearly as rich and dynamic as Win-
dows-based applications. Indeed, we are now seeing the advent of Ajax-
based applications that can work whilst disconnected from the internet and
so provide offine functionality similar to Windows-based clients like Micro-
soft Outlook.
There are also sets of technology other than Ajax that are increasing the
value of user experience in areas such as communications, voice and video.
Instant messaging (IM) is heavily used in Web 2.0 applications to provide
instant communications, and there is a wide range of agents and delivery
options available for IM systems. Voice-over-Internet-Protocol (VoIP) sys-
tems allow voice and teleconference communication over the internet as part
of the user experience. Finally, the provision of real -time, stored or broad-
cast video rounds out the client experience.
Recently, technologies like Flash and Silverlight have also been playing a big
role in enabling media-rich, interactive user experiences, facilitating sophis-
ticated read-write and streaming scenarios, among others.
The breadth, richness and fexibility provided by these technologies moves
the user interface well beyond a dynamic UI to a fully interactive audio and
video experience, which provides new and powerful ways for people to inter-
act with systems and with one another that are still to be explored.
Lightweight Programming Models
In Web 2.0 the programming models, concepts and techniques are signif-
cantly different from those that have been used before. Whilst they are very
heavily service-based and reliant upon the concept of message-passing using
Representational State Transfer (REST) protocols, they focus on simplicity
and ease of use. This has a number of implications:
Web 2.0 programming is based on the concept of separation of concern
using a loosely coupled, message-passing-based model on top of an inter-
net-based and standard set of communications protocols (http), which is
often called REST-ful programming. It implies notions of syndication and
composition where services are provided without knowing how or if they
are used. This is very different from a conventional tightly coupled, trans-
actional and often object-oriented system. It has a different set of benefts
(such as fexibility and speed of implementation) and challenges (such as
integrity and management).
189
8 Social Computing for Business
The languages (such as Perl or Iron Python) and the frameworks used
are simple and dynamic, which provides a low barrier to entry and re-use
and high productivity. The frameworks have built-in support for common
design patterns such as Model View Controller (MVC) and methodologies
such as Agile. They are quick and easy to pick up, use, and become pro-
ductive with.
Web 2.0 applications are inherently composable and compositable; because
they are built with lightweight programming models and standards-based
services, new applications can be created by composing or mashing-up
present applications and services. Mashups are where applications and
services are composed at the UI; composition is the more general case of
services being re-used.
End of Software Release Cycles and Deployment
The platform concepts behind Web 2.0 strike a new balance between the
control and administrative ease of centralized systems and the fexibility and
user empowerment of distributed systems. Web applications are by nature
centrally deployed, so central services can manage applications and entire
desktops automatically. Software as a Service builds on this concept to pro-
vide the idea of software and services delivery over the internet, and Web
2.0 builds on top of Software as a Service to provide social and content serv-
ices over a web-based mechanism.
This usage of SaaS by Web 2.0 as a deployment and release methodology
provides all the well-known SaaS advantages of simple deployment, mini-
mized management and administration and, probably the most important,
instant update and repair. Thus one of the most-touted features of Web 2.0
(and SaaS) is the concept that the system is being constantly updated and
enhanced, often in real-time in response to users requests. Of course, the
issue with this perpetual beta that the community needs to come to grips
with is what happens when downstream applications rely on services or
functionality that the application is providing.
The Read / Write Web
The second important area of Web 2.0 is the focus on data and content, and
in particular the ability of people to create and interact with rich content
rather than just consuming it. If the original internet provided read access
to data, then Web 2.0 is all about providing read and write access to data from
190
Collaboration in the Cloud
any source. This ability of anyone to create content has caused an explosion
of available content from all sources (and of all types of quality). At the same
time, it has created a whole new set of issues around vandalism and the
integrity of data.
As the bandwidth available to the end user continuously increases, the rich-
ness of the content that can be sent over the internet increases. The original
internet was all about text, but Web 2.0 started with music and images and
moved into voice and video. Now TV and movies are the content areas that
are being investigated as part of Web 2.0.
Whilst people and organizations have been searching, uploading and down-
loading all this explicit data and content on the web they have, all the while,
been creating a huge amount of implicit data showing where they are going
and what they are doing. This implicit, or attention data, of Web 2.0 can be
used to predict future behavior or provide new attention-based features. Of
course the collection, storage and use of this implicit data raises challenging
questions about ownership, privacy and Intellectual Property (IP).
Another issue with the huge amount of data on the web is fnding and navi-
gating it. Search engines use the implicit data to fnd textual data, but they
will not work with audio, image or other binary data. In addition, the search
engine often does not have enough contextual information to provide a valid
result. In these cases tagging the data becomes a valuable way of assisting
with data navigation. Web 2.0 applications use tagging and tag-clouds
extensively as a way of fnding and navigating through the vast amount of
data available on the web.
Tag data is data about data, or metadata. One of the major concerns with data
and content on the web arises from the lack of consistent standards for meta-
data and schema. It is impossible to cut and paste something as simple as an
address on the web because there is no standard format for addresses. We
need to understand the different levels of metadata and have standards for
what that metadata is in order to liberate data on the web and, in particular,
to allow composite applications to compile data. This standardization of
metadata in the Web 2.0 space is similar to the goal of the Microformat
effort.
191
8 Social Computing for Business
The Social and Collaborative Web
The third key element of Web 2.0 systems is the concept of social networks,
community, collaboration and discussion. People naturally want to commu-
nicate, share and discuss; this communication is a key part of understanding,
learning and creativity. The unique element that Web 2.0 brings is that of
social networks and community, which are typically enabled by blogs, dis-
cussion groups and wikis. In Web 2.0 the sheer scale and number of people
on the internet creates an architecture of participation where the interac-
tion between people creates information and systems that get better the more
they are used and the more people who use them. This harnessing of the
collective intelligence creates systems that have more and better information
than any one person could generate; it becomes the wisdom of the crowd.
There are a number of different types of collaboration that can occur in Web
2.0 systems:
Content-based
This is where groups gather and collaborate around a piece of news or
content, typically in a blog or a spaces-type environment.
Group-based
In group collaboration people gather around an idea or interest such as a
hobby and discuss it in discussion forums.
Project-based
In project-based collaboration groups work together on a common task or
project such as a development project, a book, or even something as large
as an encyclopedia using wikis.
All three types of collaboration can be used in Web 2.0 systems, and in many
cases more than one can be used.
Content-
based
Group-
based
Project-
based
Figure 8.1: Different Types of Web 2.0 Collaboration
192
Collaboration in the Cloud
8.5
Software + Services Enabling Social Computing
We discussed Software + Services as the realistic hybrid model to use SaaS
in combination with on-premises software. It provides a model to create
right-sized IT for every user and gives the CIO the power to optimize the
IT service portfolio. Software + Services is the model for situating cloud
computing in a real business scenario.
If we look at collaboration and how cloud computing could help, there are
four main reasons why cloud computing and collaboration is a natural ft:
Autonomous users want self provisioning of tools;
Both are crossing boundaries;
Collaboration is about being part of the conversation economy; plus
Traditional reasons, such as cost or performance.
Self Provisioning
When we want to stimulate bottom-up initiatives, and make units, teams,
projects and people more autonomous in creating value for the company, we
need to give them tools. Traditionally the IT department designed and sup-
plied the tools, but we have seen that the prosumer users demand more
control and faster service. Self provisioning and confguration is of the
essence here. Cloud computing fts the bill perfectly, since a lot of the serv-
ices being offered online are extremely easy to provision, try out and con-
fgure. Most likely, business users in every organization are already using
them.
Crossing Boundaries
The best collaboration is across boundaries: bringing together value from
two different sources to create something new and better. This is hard to
accomplish when the tools to support the collaboration are strictly controlled
from within one organization or unit. If we want to address identity issues,
and answer security and ownership questions, a cloud tool is usually more
suited for this than on-premises, corporately controlled tools.
193
8 Social Computing for Business
Conversation Economy
This is an important reason to use the tools from the cloud. If we want to be
part of the ongoing conversations, and join the discussions in progress on
the internet, then we have to be where the social networks are. And the
social networks are in the cloud. Also, we will start to exploit the benefts
of cloud-served solutions. We could, for example, use LinkedIn to update our
CRM system, or use YouTube to do recruiting, or scan blogs for trends rel-
evant to our business, etc.
Traditional Reasons
The reasons for choosing SaaS, as stated in Chapter 1, are as valid for col-
laborative tools as they are for other tools. If collaborative tools are becoming
part of the IT infrastructure, a SaaS version is most logical. Hosted email
solutions are well accepted, as are collaboration portals, messaging software,
etc.
Figure 8.2: In the Cloud
8
8 http://geekandpoke.typepad.com/geekandpoke/cloud.
194
Collaboration in the Cloud
8.6
The Web as the Hub
The value of the knowledge found in employees heads and in the databases
and unstructured documents found across the organization has been well
known for a while, and there have been many attempts to collect it into
knowledge management systems, with varying degrees of success. Clearly
when people can quickly fnd critical information and subject-matter experts,
and then work seamlessly together, productivity will soar. This has been
diffcult to achieve in the past, but new technologies such as dynamic work-
spaces, wikis, and enterprise searches for people and data may lower the
barriers to knowledge management and provide a platform for collaborating
on complex and creative tasks.
As we noted however, the real barrier to knowledge management is around
social and value issues in organizations rather than technical ones. These
are not addressed by the technologies per se and hence the expectations
from the technologies themselves should be tempered with the right invest-
ments across people and processes.
8.7
In Conclusion Where Do We Go from Here
The most appealing and potentially most rewarding uses of emerging col-
laboration and social computing techniques in the enterprise are in the cus-
tomer-facing areas of organizations. The entire customer relationship man-
agement cycle will be transformed by the tools and techniques that are in
common use in the consumer space. In marketing, the opportunity to exploit
rich, interactive media and to enable a new world of digital customer inti-
macy through wikis, blogs and online communities will provide new ways
of reaching out to and engaging with potential customers. In customer sup-
port, the use of video and other rich media to assist with problem resolution,
and the use of online communities towards self-service-based models prom-
ises to create entirely new models and frameworks for support.
Beyond the customer-facing business capabilities, it is product innovation
where customer involvement and participation in product design and devel-
opment using blogs, wikis, and discussion forums is heralding fundamental
shifts in what is commonly thought of as the co-creation of innovation. The
other business domain that has the potential to beneft from these tech-
195
8 Social Computing for Business
niques is training and mentorship, where the use of rich media, messaging,
and chat and other collaboration capabilities has considerable potential.
Overall, the use of new and emerging social computing and collaboration
capabilities in the enterprise, enabled by a platform of on-premises software
+ cloud-based services, promises to have profound and far reaching effects
on how organizations function, and create fundamentally new and powerful
ways of innovating, marketing and selling to, and delighting customers.
197
Case UVIT
Case: UVIT Embracing Collaborative Technology to Beneft from Recent
Merger
Univ and VGZ-IZA-TRIAS are all active in the insurance business. Univ is an all-
insurance company; the others focus on health insurance. On January 1, 2007, the
companies ofcially merged into a new company with the temporary name UVIT. (For
the beneft of the readers we will use the temporary name throughout this case. The
new name will be announced at the end of 2009.) The core business is to provide
health insurance coverage for 4.3 million people a quarter of the Dutch population.
Their other (non-health) insurance products cover 800,000 insured. This makes UVIT
one of the largest insurance companies in The Netherlands.
After the merger, the companies started a centralization process. The plan is to reduce
the number of ofce locations from 17 to 5. One of these 5 locations will be the new
headquarters in Arnhem, which is scheduled to open in September 2009. This ofce
has a completely diferent interior design. The architects of the building have designed
the ofce with a limited number of foors, leading to a very open work atmosphere.
Merger as a Time for New Opportunities
According to Mr. Jo Knippenberg, CIO at UVIT, the merger ofers an ideal time to
refect. It is a moment to closely examine the existing organizations and think about
what the new organization will look like after the merger. It is a time to zoom in on
the details, when you can look at what went wrong and what went right in the past,
and then take these lessons into account when developing the future organization.
The merger ofers a a unique opportunity to create a new setting. It is a moment to
think about how people work, how they collaborate with people inside and outside
of the organization, and how technology can help. How do you forge all these ele-
ments together to form something that contributes to the greater good: to your cli-
ents, your prospects, to your relations?
Challenges in Collaboration and Corporate Image
Mr. Knippenberg faced a couple of challenges in daily practice during and after the
merger and subsequent reorganization. The frst challenge that arose during the
merger process itself was how to best support communication, because without
communication there is no collaboration, and without collaboration you essentially
do not have a unifed company. A closely related question was how to stimulate and
enable the employees to create efective collaborations among themselves. How do
you make sure everybody has access to the right information, in the correct form, at
the right time and the right location?
This, of course, is not only relevant for employees but just as much for third parties.
The new possibilities here are way beyond the patterns used in traditional outsourc-
198
Collaboration in the Cloud
ing. New forms of collaboration can emerge as the result of the use of new tech-
nologies and tools. It could very well be that the party that is best able to collabo-
rate with his competitor, is the party best positioned to determine the future.
Another challenge that UVIT is trying to solve in the process of the merger is how to
fx the problems with the corporate image. Traditionally, an insurance company is
not a sexy company to work for, rather dusty and stufy instead. This poses chal-
lenges whey trying to recruit new employees, since you also want to attract good
people and young talent. They represent the future of business. How do you create
an environment, a workplace where these people feel at home?
The New Organization
The big question of course was how to respond to the challenges above. One of the
actions after the merger was to reduce the number of ofces. Of the 17, only 5
remained. The new headquarters was designed to ft a completely new philosophy.
As a departure from the old situation, people dont have fxed ofces anymore but
will be equipped with laptops and mobile phones. The idea is to create a more open
and fexible working environment, ofering new options in how to work and collabo-
rate.
Next to this upcoming big-bang change, other modifcations have been made. These
changes were frst implemented with a small group of people before addressing the
larger worker population. First see if the experience is satisfactory, before implement-
ing on a larger scale.
As an example, currently people are using Microsofts Live Ofce Communications
Server product. This product can show the status of people (free/busy), which some-
times produces resistance. Employees sometimes see it as Big Brother is Watching
You. Use of this function is voluntary and not required by the company. Experience
shows that groups start using it whenever they are ready for it. If one sheep leaps
over the ditch, others will follow. And greater adoption immediately leads to new
questions. Why would we only use Live Messenger inside our company and not
directly with our customers and suppliers?
Where Communication Server saw slow gradual adoption, Microsoft Ofce Share-
Point Server was immediately more widely adopted. One of the most interesting
consequences is that during regular meetings attendees no longer use paper. Meet-
ing minutes and notes are directly recorded in SharePoint. Employees, including those
who could not attend, can read back the notes immediately after the meeting. Here
too, the process of adoption is a gradual one. It has to become part of the normal
way to do your job. On the one hand, this of course takes some training; on the other
hand, its a toolbox with a variety of tools from which employees have to select the
right ones themselves.
199
Case UVIT
Social Networks Build the Organization
From the commercial side of UVIT there was a growing demand for Facebook-like
applications. At this point, UVIT still maintained a strictly controlled environment
where it was not possible to use all sorts of applications available on the web. To
meet the demands, a new organizational mindset would be needed. Such radical
changes in policy are more or less prescribed by the outside world. UVIT wants to
fnd a way to accommodate those kinds of options, but this is still undiscovered ter-
rain. Control versus freedom: what is the wise course? UVIT is currently in an explor-
atory phase when it comes to these issues.
Meanwhile, a special UVIT social network was born and is being used frequently by
a small group within the IT department of the company. Every employee is responsi-
ble for keeping his or her profle up to date with relevant information and added value
to the company. Using someones profle, you can directly explore the relations
between colleagues. Who is close to whom? Who is his or her boss? Who is the boss
of the boss?
In the old days, we needed all kinds of organizational diagrams. This is no longer
necessary. The hierarchy has become self-maintained. A new employee joins the
organization via his or her profle and can immediately contribute. New employees
are also immediately part of the organization. An organization is very dynamic. The
organizational movement of people is a dynamic in itself, and this social networking
tool is great way to gain insight into this dynamic.
Technology and opportunities happen to enter your life. The same happens to your
company. As a company, you have two options: you resist or you embrace. At UVIT,
the latter obviously was the case.
Trust Means Everything
UVIT is very aware that only providing the hardware and software will not make a
new company. To create a new frm the whole concept has to become part of the
DNA of the employees. It is a cultural thing, not something ordered by the top man-
agement, but embraced by the people on the work foor.
Trust is of the essence in this transformational process. Without trust none of the
things we have envisioned will happen. We have to earn the trust of our employees.
Both employees and management have to trust each other, trust that we are building
the new company together. Trust is one of the key factors of our new emerging cor-
porate culture.
201
9
Fourteen Questions to Guide the Revolution
9.1
Introduction
Throughout this book, we have been promoting a new way of looking at your
organization, of creating bottom-up management and better supporting
cross-boundary collaboration by using Software as a Service. All bundled
up, it amounts to nothing less than a revolution in the way you do business
and the way you support business with IT. This chapter will help you keep
a cool head by providing you with fourteen questions to continually ask in
order to keep the revolution pragmatic and to facilitate any initiative that will
help to achieve your goals. Fourteen questions to keep in mind to prevent
being swept away by hype.
Most of the answers to these questions will depend very much on your situ-
ation, and on the specifc project or challenge you are trying to address. Still,
we can sketch certain elements that should be considered when answering
these questions.
Questioning Evangelists
The IT industry is composed of a myriad of vendors and service providers,
each offering their own value and point of view. Trying to convince you of
abilities, and optimistic about the future, they will offer to solve all your
problems using the latest tool or insight. So what do you ask when a vendor
talks about a new collaboration solution? What do you say when someone
from the IT department stops by your desk to talk enthusiastically about
the newest project regarding wikis or SharePoint? You can use this list of
questions to keep your feet on the ground. Ask the questions below and lis-
ten carefully to the answers you get and whether the important points are
covered.
If you are not an IT manager but a provider or someone inside the organiza-
tion who wants to see changes in the way collaboration is performed, this list
will help you prepare the answers you will need to convince and involve
202
Collaboration in the Cloud
others. You will have to know the answers since the questions will be asked
eventually, even if not at frst.
The questions and conceptual answers are based on frequently occurring
business-IT alignment issues. They are distilled from failed and successful
collaborations or SaaS projects and from the personal experiences of people
working in the collaboration or SaaS space. Some relate to collaboration spe-
cifcally, while others are SaaS-related.
9.2
The Fourteen Questions to Guide the Revolution
Whats what? 1.
Whos collaborating? 2.
Why collaborate? 3.
Whats wrong with email? 4.
Is technology all we need? 5.
When is the next version due? 6.
What does it cost? 7.
How does this integrate? 8.
Is it secure? 9.
Where do I start? 10.
What is our competitive advantage? 11.
What boundaries are we crossing? 12.
As a service? Not as a service? Mixing Software + Services? 13.
When have I won? 14.
1.Whats What?
What does collaboration mean? What is cloud? And SaaS and S+S? What do
we mean with all the terms? Can we agree on terminology?
Thanks to the state of marketing and the chatty and dynamic nature of the
internet, numerous interpretations will surface for anything new. Conse-
quently, an essential part of any project these days will be to examine the
concepts, assumptions and terminology used. What do the different partners
who are in conversation to create strategy understand the terms to mean?
What defnitions and associations do people use when talking about the
topic? Is collaboration something focused on people or focused on corporate
203
9 Fourteen Questions to Guide the Revolution
relations? Is cloud something cool and user-focused or is it technical infra-
structure? You cannot expect two people to understand a term exactly the
same way unless they have talked about it. As we have seen, even the term
collaboration can cover anything from business-to-business platforms to
email, document sharing or conference-call solutions.
To create this shared understanding of the concepts and terminology, a
brainstorming session, a workshop or ongoing conversation can be very use-
ful. Experience tells us that people-to-people contact works better than read-
ing a website or one person defning meaning for everybody. This book, a
website or an external expert can effectively provide the starting point for
your own discussions.
2.Whos Collaborating?
Who are they? Where are they? What kind of people? Are they from our depart-
ment? Are they only IT people? Whos collaborating with whom? Are they from
another company? In what time zone are they? What language do they speak?
Whos managing them?
Traditionally, collaboration is seen as something between colleagues or
even between people working in one project. As we have shown, collabora-
tion is a much wider feld, addressing all interactions between people (or
even companies), crossing organizational and cultural boundaries.
The question of who is collaborating will give you insight into the chal-
lenges you will or will not face when creating a collaborative culture. Look-
ing beyond job titles or department names and really examining the people
and their characteristics gives you an idea of what you will run into in trying
to stimulate or enhance their collaboration.
Once you have established whether the people belong to one organization or
work across organizational boundaries, you will be able to look into the mat-
ters of provisioning, ownership, and confdentiality.
What to look for in an answer: in trying to formulate an answer to this
question, talk about which people will collaborate, across which boundaries,
and what kind of people they are (technical, business, older or newer gen-
erations, etc.). A good way to defne the different collaborations and see who
204
Collaboration in the Cloud
is involved is to create scenarios: story-like illustrations that describe a day
in the life of the different audiences.
Another way to fnd and defne the different collaborations is to make use of
existing technologies. Tools are available that help you explore your (social)
network at the push of a button. The result of this network crawl can then
be used to visualize the different kinds of relationships that exist inside and
outside your company. The results will surprise you. Some people within
your organization may play pivotal roles as community leaders, of which you
werent aware before.
3.Why Collaborate?
Why would they want to collaborate? Why do we want them to collaborate? Are
they already collaborating? Whats in it for me? Whats in it for them?
People collaborate, by themselves, automatically. They will seek help, dele-
gate tasks and look for contributions from others. When addressing collabo-
ration from a corporate view, the question should be asked at these three
levels:
Why do we need to address collaboration from a business perspective? 1.
What will be the corporate gain for addressing it across the enterprise?
Whats the beneft from a team-perspective of better collaboration? What 2.
will get the project manager or team leader excited about this initiative?
What will motivate an individual to collaborate differently? Whats in it 3.
for the individual user?
If you are missing one of these levels, it will make the adoption of new ways
of collaboration problematic. The goals you are looking for with these ques-
tions can have the form of real business cases: for example, saving time and
money that is currently wasted on ineffective collaborations, or increasing
the quality of work in an administrative environment through improved
communications and response to anomalies. Goals can also be more indirect:
helping recruit and retain people by making their daily activities more fun
and engaging, thus creating a better work environment and better knowl-
edge retention leading to (ultimately) some higher business goals. The cas-
cade of goals must be rooted in reality, preferably confrmed by the actual
people who will be impacted.
205
9 Fourteen Questions to Guide the Revolution
As we have learned from Open Innovation (or Crowdsourcing), at the indi-
vidual level the drivers for collaboration can be very business-like (money,
effciency in achieving goals, doing a better job) or very personal (peer sta-
tus, social interaction, curiosity).
Any answer talks about the goals at the different levels, how they strengthen
each other and how they ultimately contribute to explicit corporate goals.
Every good answer will also include a personal answer for the person asking
the question: and whats in it for you personally is .
4.Whats Wrong With Email?
Why has email worked so far? Will any new solution be better than email? Why?
Will people stop using email? Do you still use email?
Anyone coming in to talk about new ways of collaborating will need to have
a vision of how email fts in the picture. If email remains the preferred
medium, alternatives will never reach full acceptance and maturity. As an
analogy, if we were to give people bicycles but they still wanted to keep their
feet touching the ground all the time because they always have we would
not gain any speed by distributing bikes (if anything, it would slow people
down). The same goes for the introduction of better support for collaboration:
the advantage must be demonstrated, tried and proven to be a true advantage
over email. Document creation in an online environment is much more eff-
cient then sending links, emails and keeping multiple copies, yet only when
this is shown in practice can it convince people to stop using email for this
purpose.
Email itself has been too good for its own good. Its ease of use and wide
adoption have made it the burden of present-day working life for many peo-
ple. There are now even special courses in how to handle email effciently!
In essence, email is an old concept, ported to new technology; the paper let-
ter, replaced by the fax, then by email still sticks to an old distribution model.
You write something, address it, post it, let it go, and wait for someone to
respond or just hope it all works out, depending on the kind of message.
More advanced solutions, as an add-on to email, have been around for a long
time: project management tools, delegating tasks and reporting are examples
found in most present-day email tools. Yet the actual use of these features is
very limited, and they are hardly ever used correctly and to full advantage.
206
Collaboration in the Cloud
Not because the features arent useful, but because nobody ever explained
them, or people never got used to them, or there was no corporate or team
advantage and thus no real support was given to implementing the fea-
tures.
A different way of looking at email is needed in order to move forward. By
asking this question repeatedly you can begin to more sharply defne how
any new solution can and should be used.
An answer talks about the current role and use of email in your organiza-
tion, perhaps the problems of email with regard to process control, version-
ing, knowledge management, governance, etc. It will talk about how different
solutions will take chunks out of everyones email load, leaving email as a
minority medium used only where the other tools and communication chan-
nels do not suffce.
5.Is Technology All We Need?
What else needs to be done? What needs to change? What does your solution
NOT address? How much should we spend besides this solution to get the right
results? What is the most diffcult part?
If a vendor or service provider states that collaboration will be greatly
improved using a piece of software or a service in the cloud, perhaps sticking
to the build it and they will come adage, it clearly shows an incomplete
perspective. A tool or service can defnitely help, but, as we have demon-
strated, it is only a minor part in the larger effort to change how people work
and how we provision IT support for it. Creating a strategy that is founded
(and funded) on the business side of an organization, with a practical
approach to delivering short-term visible results, would be the ideal combi-
nation. A strategy would also include statements as to how to anchor the
collaboration strategy in the organization: whos the owner, what are the
activities that we are trying to improve or support, and how will this evolve
over time.
What to look for in an answer: it will talk about the role and impact of the
tool or the service, the architecture (how the tool or service will ft in an
ever-changing environment), the people (usage) and the change that is
needed in culture and management.
207
9 Fourteen Questions to Guide the Revolution
6.When Is the Next Version Due?
Is this a stable solution? How long before we need to change this to the next ver-
sion? What will be next? Will this work in ten years time? Can we radically
change business processes and structure and still use it?
One lesson from the past is that we can always expect change. Our vendors
will keep offering new features and solutions, but even more importantly,
our business-environment will keep changing rapidly. In a globalized world,
business is changing at real-time speed. Especially in the SaaS world, ver-
sioning and upgrades are a continuous process.
Currently it is hard to change to a different set of tools: user and developer
training, new licensing costs and other investments have to be made. Given
the certainty that the only thing we can count on is change, we need to plan
for change in the IT space, too. We must ensure that either replacing tools
with the latest version (or different tools) is extremely cheap and easy or
that a particular solution will be able to withstand a lot of change going
forward.
Both solutions, easy to change and resistant to change, revolve around
the use of standards and the actual design of the tools and services them-
selves. Also the architecture surrounding the tool or service must be ready
for change. When selecting technology, attention to (open) standards, insight
into future product roadmaps, or testing changeability can help to prevent
getting stuck with any solution. For example, a good way to test the change-
ability of any solution is to start a proof of concept where a radical change to
the confguration has to be made within a minimal timeframe, demonstrat-
ing that future investments can be kept low when changes are needed.
Also, it pays to examine the way a vendor or service provider handles
changes: is there an open forum discussing features and updates, or is it a
closed innovation process? How long are multiple versions supported (if at
all)? How accessible is the service provider for feedback and support? All
these will give insight into the risk of change: their change and your risk.
A lot of software available on the internet is in a permanent beta stage. Can
your company handle that? In the past most companies waited for the next
version or the frst service pack before implementing something. This
attitude might not be wise in the now real-time economy.
208
Collaboration in the Cloud
An answer to this question will show how change will not affect the core
elements of a solution, how new needs can be met with the current tool or
service. Also backward compatibility, open standards and release planning
are part of the answer. Ultimately, the solution should ft your overall IT and
business architecture, which in itself of course is also adaptable to change.
7.What Does It Cost?
How are we paying for this? What are the costs over time? What will it cost to
abandon this choice in the future? Does this make sense from a fnancial plan-
ning perspective?
SaaS is often sold using the payment model: pay-for-use with little upfront
investment. It is often a variable cost, making it attractive to bookkeepers
and giving the illusion of being easy to scale down in times of need. In real-
ity, comparing cost is actually hard to do. How do we get the real cost of
hosting something on-premises and how do we compare it to renting some-
thing as a service, taking into account an uncertain future? When contem-
plating the model of software and services, and fnding the right balance, an
honest comparison must be made. Take into account risks, costs of human
resources, costs of downtime and ongoing licensing, and usage costs for dif-
ferent provisioning scenarios. In particular, the cost of extra support or
unexpected growth in usage can drastically tip the scales in the comparison
if a contract is not carefully screened in the course of this comparison.
When estimating cost we look at the contracts of any as a service offering
and compare it to on-premises numbers and estimates of support, staff, over-
head, etc. Pay special attention to the cost of scaling and exceptions. A useful
method can be to describe several scenarios, then for each scenario estimate
the likelihood that it will become reality, and then calculate the cost (as a
range).
8.How Does This Integrate?
How does the tool or service ft into my existing IT infrastructure? Are we using
the same user database? Is it integrated into my Enterprise Search? How does
it impact my content management system? Is it integrated with my email system?
What else needs to be done to assure good integration? How do we migrate?
209
9 Fourteen Questions to Guide the Revolution
This is one of the hardest questions for any new IT solution, and even more
so for functionality provided as a service. Often the simplicity of the solution
provided in the cloud will look attractive, but soon there will be a demand
from users and management to integrate it with existing systems: perhaps
initially for sign-on credentials but quickly also for integration of all kinds
of other data, such as client information, stock data or internal fnancial
feeds.
When looking at collaboration services, the need for integration with existing
data might not be obvious at frst, but soon it will become evident that it is
closely tied to information management tools (content management, busi-
ness intelligence), governance structures (users, rights-management) and
existing presentation platforms (websites, portals, desktop environment).
The closer systems integrate, the lower the barrier to using the technology
and the greater the chances of widespread adoption. A platform that is dis-
connected from everything else will either slowly die out (due to the diff-
culty of keeping data in synch with other sources) or it might become the
new authority leaving data in other sources more and more unreliable.
Existing basic interfacing standards allow for integration, but beware of
solutions needing lots of manual integration: it might make the as a service
solution more expensive and more diffcult to maintain than something
installed on-premises.
When talking to vendors or service providers or when selecting a service
from the cloud, the options for integrating should be among the most impor-
tant decision criteria. Over time, as the cloud matures, we would expect
more and higher level standards to become available, making integration
slightly easier.
At the same time, this is also an important question to ask your own IT staff,
since their estimate on ease of integration might differ from that of the serv-
ice provider.
What to look for in the answer: it will demonstrate how the technology fts
in with and makes use of existing data, it will show how business intel-
ligence and integration of information will help create better interactions
between people.
210
Collaboration in the Cloud
9.Is It Secure?
Will others be able to access my data? Can my employees do things that are bad
for our company? Will we run into trouble with the auditors?
This question is brought up most often by people who say that SaaS will
never happen. Because how can we rely on the confdentiality or security of
a service running somewhere in the cloud, on physical hardware that is
shared with perhaps thousands of unknown others from countries all over
the world?
Yet there wasnt much concern when the business world introduced the
Blackberry mobile email solution: confdential email fows through servers
worldwide without it causing too many worries. In the end its not just about
security, but about trust and service levels: can we trust the service provider
to observe the terms of the SLA regarding security (and availability, conf-
dentiality and all the other elements that make up an SLA).
You do need to keep asking this question, perhaps not so much as to pre-
vent SaaS from happening altogether, but to make sure that any SaaS solu-
tion you introduce fts corporate policy.
Surprisingly, sometimes the people who are the most notorious detractors
can turn into true supporters if engaged early. An auditor will help fnd solu-
tions to keep an external service conform to auditing rules; a security offcer
can be engaged to scope an SLA to cover the basics needed to keep new
services from compromising corporate security, etc.
10.Where Do I Start?
How do I start? How do I manage this change? What are the frst steps? How
do we maintain progress over time? Is there an easy way in or are you propos-
ing a big bang? How can we be sure every step of the way has value?
As a rule, big bangs dont work. Experience tells us that the best way to
improve IT or organizations is to create an active evolution toward a future
goal, allowing for many small steps and minor (or even major) detours along
the way. Improving collaboration is no different: start small, where the
chances of success are largest and a win is likely. Create support among tech-
211
9 Fourteen Questions to Guide the Revolution
savvy early adopters but aim for greater late majority adoption by the less
tech-savvy users by listening to their demands and feedback. Start small
with a (perhaps self-selected) group of enthusiasts and then spread the ini-
tiative using the early adopters as seeds within new groups. The frst
advances will be in the easy category, perhaps only later involving different
organizations, time zones, languages, cultures, etc.
Also, when trying new ways of collaborating, freedom is key: dont over-
systemize the initial solutions but allow for enough freedom to see what
works best. If the freedom is essential to the collaboration, it might even be
part of the fnal solution. If the freedom is too much for the later adopters,
the early experiences will tell you how and what to formalize. It is important
to note that this freedom is not just in the tools and support but even, and
especially, in the way the collaboration team is managed. Experiment with
different levels of involvement to fnd what works.
The answer to this question for your organization will talk about the scope,
the people and a situation where improved collaboration will provide imme-
diate value to the participants. Expect to think small, to select a small group
of people who will start using the new technology. If they are happy with the
new technologies, they will automatically become your evangelists who will
spread the tool within the organization.
11.What Is Our Competitive Advantage?
What are we doing that competitors arent doing? What are we doing differently?
How is that visible in our IT investments? How is that visible in our systems
architecture? How quickly will this competitive advantage erode?
If you are replacing a proprietary solution with a commodity solution, either
as software or as a service, you need to ask whether you dont squander your
competitive advantage by the move. And vice versa: when looking to fnd
specifc solutions for parts of your business that are defnitely NOT differ-
entiating you from the competition, it wouldnt make sense to build a custom
solution when a commodity is available. Especially when contemplating SaaS
solutions, and the levels and methods of customization, a keen eye is needed
to defne and manage competitive advantage. Most often its not the tool or
service itself that is part of your advantage, but its the way you use the tool:
the processes and confguration that make the end result unique. So if you
212
Collaboration in the Cloud
are in the market to procure a service that allows for NO custom process and
NO confguration, dont expect to beat the competition with it!
As an example, imagine a small web retailer that has thought of a unique
way to checkout and pay for online shopping, while a competitor would dif-
ferentiate on price, assortment, branding, shipping, or some other element.
Our web retailer would probably choose to build or confgure a specifc shop-
ping-cart and checkout solution, while the competitor would be happy to
choose one of the many standard shopping-cart services available. While the
example is one dimensional, when creating a business-and-IT strategy, these
are the choices to be made.
Answer this question by looking at the business strategy and the competi-
tion, and translating it to focus on areas within the IT portfolio that are more
important than others, that have higher priority than others, and should
(probably) be more fexible than others, too.
12.What Boundaries Are We Crossing?
Are we connecting to anybody or anything outside our department or company?
Are we crossing internal or external boundaries? What is the rationale behind
these boundaries? Where do they come from? Will people object to crossing
these boundaries? How can we make it easier to cross?
In business and IT, more often than ever we are crossing boundaries: we are
using external resources, we are working with people from other organiza-
tions. Be it in a supply-chain collaboration, or in a buyer-vendor relation: we
are not simply exchanging money and goods but were also exchanging
information. So when thinking about any project, the specifcs that defne
your interactions with the environment are the ones that ultimately defne
your company. You ask this question to fnd the best model for provisioning
solutions. You also ask this question to get an idea of how diffcult it will be
to create or improve collaboration: the more boundaries you are crossing,
the more work needs to be done to cross these boundaries. If all people col-
laborating report to the same manager, it will be easier than if they report to
different managers, let alone different companies.
In answering this question, look for a description of well-known explicit
boundaries, but also look for implicit or cultural boundaries that might hand-
icap successful collaboration.
213
9 Fourteen Questions to Guide the Revolution
13.As a Service? Not As a Service? Mixing Software + Services?
Cant we host our own? Should we host our own? Should everything that we have
be as a service? Is there an actual business case for SaaS in this situation? How
do you address the insecurities that come with SaaS?
Your instincts might still tell you that, to minimize risk and dependence
upon others, owning and hosting everything in-house or on-premises is
still best. The case for providing Software as a Service has been made many
times over, yet the reality is that owning IT solutions gives the illusion of
greater control. When exploring the right mix between services that are in
the cloud and services that are owned, maintained and hosted internally, a
rational view of costs and risks is essential. Include the actual costs of on-
premises people, hardware, licensing and (increasingly) power and compare
them to the costs of an off-premises solution. Compare the features of generic
solutions with the features of custom created solutions. Compare the risks of
downtime and disasters to SLAs that are not met, etc.
As mentioned before, any conversation around the as a service question
will revolve around setting boundaries: What functionality is generic, what
is specifc to us? It will also talk about the different levels of as a service:
hosting and support on a hardware platform (servers) is a different level
than generic part-solutions (collaboration portals), and is different from a
business solution or service (CRM). The technology-level services might
be easiest to use, but the business-level services will provide the greater
beneft provided they offer the right services needed by your organization.
Finally, keep in mind that the model of as a service is also a valuable model
for IT departments to use in defning and offering their own services. The
choice then becomes not so much between as a service and not as a service
but rather between as our own service and as someone elses service.
What to look for in the answer: it will take organizational strategy and
input as to competitive differentiators to defne what to have and what to
hire, what to produce and what to procure. The answer will defne the
boundaries of the organization-specifc IT.
214
Collaboration in the Cloud
14.When Have I Won?
What defnes a successful implementation? How can we measure success? What
would be the end-goal for this solution? Can we track progress? Who will deter-
mine if this was a success? Are there early warning signs of failure we should
watch out for?
For any project or initiative, the defnition of success is probably half of the
success itself. Once we know specifcally what we want or need, it becomes
easier to get it. Collaboration is an area that is often ventured into without a
clear defnition of success: we want to support people, but we cant predict
how they will adopt it, or even We want to install a portal. While the exact
usage might be unpredictable, and perhaps even intentionally so, there must
be a way to track progress. There must be a way to know if things are evolv-
ing in the right direction, or if perhaps corrective action is needed.
The measure of success for any organization will, of course, depend on
specifc circumstances. At the same time, there should be early signs of
change, in the way people work and the tools they use. Some things to look
at could be:
Email is used less;
When people come to work, they start their portal, tool, collaboration
environment before they open their email;
Users start talking about their collaboration portal;
News and success stories are no longer spread using email but posted in
the right places; and
People start experimenting with new additions to the tool, create mashups
or start requesting new features.
After the new situation is starting to become normal, the real business
benefts should become visible: better knowledge retention, better responses
to exceptions, quicker answers to questions from clients or suppliers,
improved success rates on proposals, etc. Ideally the signs of success are vis-
ible at the personal, team and organizational level.
When answering this, talk about how to track progress, how to correct or
stimulate if progress is not as expected. Look for the early signs of success
and know how to measure business success.
215
Case Toyota Material Handling Europe
Case: Toyota Material Handling Europe Sheds Paper Processes for Mobile
Collaboration
IT Seizes Opportunity to Establish Collaborative Best Practices
A few short years ago, the service operation at Toyota Material Handling Europe was
living in the dark ages, technologically speaking. Toyota Material Handling Europe
(TMHE) began operations in 2006 to manage the Toyota and BT materials handling
business in Europe. With more than 100 years of combined Toyota and BT experi-
ence, they are active in more than 30 European countries.
TMHE provides a complete range of Toyota counterbalanced forklift trucks and BT
warehouse equipment, supported by services and added value solutions. TMHE is
the European regional organization of Toyota Material Handling Group (TMHG),
which is part of Toyota Industries Corporation (TICO), the world leader in materials
handling equipment.
That is, service personnel at TMHE were drowning in paper processes. Technicians
got their monthly maintenance plans on paper. Then they submitted paper work-
sheets with feedback on customer calls, and it took back ofce staf sometimes up
to two weeks to update customer histories, invoices and parts replenishment data.
Whats more, the processes difered by country. And with 4,800 technicians spread
amongst 30 countries, making more then 3.5 million service assignments a year, that
meant a lot of unnecessary complexity as the back ofce was asked to translate
widely varying types of forms and data into useable intelligence about customers
maintenance needs.
The technology team looked upon the situation as an opportunity to implement best
practices that could help standardize data, introduce a layer of collaboration, and give
back ofce staf and feld technicians better access to more up-to-date information. The
result would be improved service efciency, and thus increased service revenue. Because
more than 3,300 of the technicians work from vans, mobility was a key consideration.
Team Approach Yields Streamlined Mobile Process
Working with a team of 10 back ofce staf, service technicians, and IT personnel from
Toyota Material Handling, Sogeti consultants joined representatives from Lawson Soft-
ware and feld service automation specialist Intermec in building an integrated solution
that today combines a Lawson ERP environment, a web-based interface used by back
ofce staf, and a mobile Intermec application built on Microsofts .Net framework.
That application resides on the 2,200 PDAs that have been deployed and are in use by
mobile technicians.
When a customer initiates a call with one of 400 service center personnel and a nearby
technician is located, the service dispatcher is able to immediately push information,
216
Collaboration in the Cloud
such as the customer history and directions, to the customer site, to the technicians
PDA. The back ofce can continue providing the technician with any information he or
she needs, such as safety and inspection rules, or even broadcast bulletins to all mobile
technicians. Conversely, technicians can communicate directly with the back ofce to
provide information, such as a corrected vehicle identifcation number, that can be
instantly updated throughout the system. (The PDA is also equipped with the diagnos-
tic tools and documentation needed for technicians to troubleshoot.)
When a service call is completed, the PDA is used to capture the customers signature
and submit it electronically, along with the job worksheet, directly to the back ofce,
allowing service center staf to review the job immediately to better ensure quality
of service.
System Designed to Combine Standardization and Local Touch
Despite the obvious gains it knew it would achieve in transitioning from paper proc-
esses to automated ones, Toyota Material Handling Europe also made sure to take
into account the myriad of potential cultural impacts such a project can have, says
Bo Sivenius, director of IS promotion. Among the factors considered were:
how a core process is implemented across operations in multiple countries that
are running sometimes widely varying technologies;
how to standardize forms sufciently to create uniformity while also leaving room
for local customization; and
how older employees are afected when asked to embrace a new technology.
Solution Delivers Award-Winning Results
The total project inclusive of a wholesale business process change, extensive educa-
tion and training for all the technicians, and signifcant software and hardware pur-
chases required a substantial, undisclosed investment. It was money well spent,
says Sivenius.
The payof has been quite good, he says. Were being perceived as a more innova-
tive, efcient company.
In addition to improved customer satisfaction, Sivenius says the efort has resulted in
more accurate information, improved cash fow, increased efciency among technicians,
and a 30% reduction in back ofce costs. It also has garnered recognition, as the third
release of the system was named Best Mobility Solution at Microsofts .Net Awards in
Sweden last year. The fourth release, with updated technology as well as support for
additional countries and languages, will go live in the frst quarter of 2009.
217
10
Debunking Collaboration Myths
10.1
Introduction
There has always been collaboration. Our ancestors worked together in their
struggle to survive, and their descendants did the same. Up to now, collabo-
ration has always occurred among small bands huddling together in strong-
holds. Companies, organizations and groups of people act as self-reliant enti-
ties in battle with the outside world. After all, there can only be one best.
The internet has, however, brought about a change. The introduction of new
technologies has caused small cracks to appear in these bastions. New forms
of collaboration have been created by people who are looking beyond their
companies own walls.
This expanded work sphere introduces an extra measure of complexity, as
it involves more than just collaboration between people. It also requires col-
laboration among companies as reciprocating entities that together generate
a completely new chain of value. Furthermore, it requires collaboration
among computers in the form of mashups and the cloud, for example.
The Internet of the future will be suffused with software, information, data archives,
and populated with devices, appliances, and people who are interacting with and
through this rich fabric.
Vint Cerf
1
Extremely wild rumors are circulating about all these new forms of collabo-
ration. This chapter is intended as an antidote to these myths. Each section
will debunk a specifc tall tale that is currently making the rounds.
1 http://edition.cnn.com/2008/TECH/11/02/digitalbiz.rfd/.
218
Collaboration in the Cloud
10.2
The Myths
The Tool Is All You Need
Make me a community is a request that companies are frequently heard to
make. They think that by simply installing a social tool, such as a wiki, blog
or forum, the entire company is immediately transformed, obtaining the
stamp of Web 2.0.
In practice, the process runs entirely differently. Tools do not make an
organization, people do. The employees have to put these tools to use; they
must propagate and spread the underlying ideas.
Companies have a history, a period of existence during which they have suc-
ceeded in creating a certain culture, now more or less inscribed in the com-
panys DNA. And this genetic inscription is not so easy to re-write (or over-
write). It has become a feature that distinguishes one company from
another.
Therefore, change must occur gradually. It can be stimulated by employing
a social tool but must certainly also be reinforced by a small group of people
capable of motivating and inspiring other employees to use these applica-
tions. Only when the number of users of these tools has reached a certain
size, at which time a certain tipping point is reached in the organization,
only then can this behavioral change be written into the companys chromo-
somes and, as a result, a new species of company (with a new form of col-
laboration) be created. It is consequently an evolutionary process and not a
revolution.
Humanity was not created in one day. There is 7 million years of evolution
inscribed in the human genome.
Must Be Invented Here
Many programmers fall into this trap. Code that is written by another devel-
oper and has to be applied to a companys own program never fully satisfes
one hundred percent of the requirements. The code must always be tinkered
219
10 Debunking Collaboration Myths
with in order to make the best possible use of it. The code is made the com-
panys own, so to speak.
This attitude has been adopted by many companies, even in terms of all the
web services that they now use: anything not built by the companys own
IT department cannot be any good.
This view is of course incorrect. Hidden behind service providers are often
communities of intelligent people attempting to earn their living by means
of the service, as incredible as this may sometimes seem. How could such an
industry possibly survive if its practitioners were only offering ramshackle
services? If such were the case, would they not just be digging their own
graves?
In fact, the web runs on trust. Parties throw in their lot together in order to
jointly proft from a given situation. As soon as one of the parties harms this
online relationship, then the defaulting party will suffer the consequences.
The web is especially unforgiving in this regard. It is a big machine that relies
on reputation and holds a grudge; thanks to search engines, past indiscre-
tions are remembered forever. Parties must therefore always endeavor to put
their best foot forward; failing to do this means that they soon will be step-
ping into their grave. In order to earn trust, organizations have to be trans-
parent. Show the outside world what youre doing.
It is certainly good to realize that a great many services exist in a permanent
beta stage; they are never fnished. Millions of people currently depend on
online services, for example for email, that have never been offcially released
from the beta stage of their development. There are often no guarantees.
Data Cannot Be Made Secure (Except Behind a Closed Door)
Many companies are afraid that the internet is not safe. A great deal of money
is spent by IT departments on making company computers secure against
all kinds of external viruses and other marauding threats from outside. The
danger is, however, somewhat of an illusion.
Many employees have complete freedom on their home computers and want
similar freedom at their workstations as well. When the IT department does
220
Collaboration in the Cloud
not cooperate in this regard, then employees are often smart enough to fnd
ways to nevertheless realize their desires.
It would be much better for companies if they schooled their own employees
on the dangers of the big bad internet. Every day sees another new article
posted on the internet describing how yet another company has allowed
sensitive information to leak out. Often, these breaches of security result
from the thoughtless actions of company employees. A slight lapse in think-
ing and information is suddenly available on the street! Companies need to
alert all their employees to all types of dangers that risk loss of information.
Policy must be geared to this point, and this policy must be embedded in
employee minds. As a consequence, security is a continuous process in which
companies are constantly training and retraining their employees.
Tools Change People
Were seeing an evolutionary change. The people in the next generation who are
really going to have the edge are the ones who master the technological skills and
also face-to-face skill.
2
Recent research has suggested that the internet is causing our brains to
function in a completely different manner than the way to which we were
accustomed. With increasing frequency, we are basing decisions on right-
brain activity; creativity and intuition are becoming progressively more
important.
Tools, such as the internet, transform humanity, and humans then modify
their tools. The result is a circle from which there is no escape but that may,
indeed, be virtuous. It is important for humanity to take the lead in this
dance. Without human beings there are no tools. Therefore close and con-
stant examination of human behavior is crucial in order to adapt the tools to
meet human needs in the best possible way.
In the near future there will be all kinds of intelligent tools (agents, bots)
swarming the internet, tools that are intelligent on their own, tools flled with
all kinds of artifcial intelligence that will help us. These tools will facilitate
our on- and offine collaboration.
2 http://www.reuters.com/article/technologyNews/idUSTRE49Q2YW20081027.
221
10 Debunking Collaboration Myths
Tools are therefore subordinate to human beings (extensions of man). They
are only facilitative and can never be dominant.
Collaboration is Difcult
People need each other in order to achieve certain goals. If we did not band
together with other people, we would still all be living in the Stone Age. We
would be cowering in holes in the ground in order to escape as much as pos-
sible from the various threats of the external world.
People are therefore accustomed to working together, which is not to say that
collaboration is easy. Collective action has always been complex, and the
internet has only multiplied the degree of complexity. In a previous age, you
could look each other square in the eye when making a deal; now, you have
to rely on a virtual personality, who might be located on the other side of the
world. How do you build up a relationship with such a remote person in order
to do business together and realize a shared goal?
Examples from practice, such as the online encyclopedia Wikipedia, show
how it is possible to work together on the internet and collectively attain
results. Such web collaborations make completely different demands on com-
panies and their employees. Instead of closed, they have to be open; organ-
ization is no longer top-down, but bottom-up. And consequently, in the year
2009, there is an entire list of traits that employees and companies must now
acquire in order to survive.
The section above has already suggested that an entirely new race of humans
is emerging and that these new men and women are using their brains dif-
ferently than their ancestors did. This development is literally and fgura-
tively an evolutionary process. Companies will therefore have to invest in
training in order to bring these types of employees to maturity and enable
them to realize their full potential.
There Is No Final Solution
Every company is different. What works for one company does not necessar-
ily work for another. In fact, companies can be viewed as a kind of jigsaw
puzzle, so to speak. As result of the most recent technology, the pieces form-
222
Collaboration in the Cloud
ing the puzzle of company proftability can now also come from locations
outside the company itself.
Companies must therefore actively be on the lookout for external pieces that
ft well with what they already have. One assembly of the jigsaw can result
in a picturesque landscape; another might end up as a self portrait, while a
third attempt may yield a cubist interplay of lines.
No single solution can be the right one forever. We live in an around-the-
clock economy in which people are always capable of contacting each other.
The possibility of radical overnight change makes it necessary to constantly
re-examine the ways in which companies must operate. And this continuous
monitoring of feedback also evolves as it adapts to a type of business organ-
ization undergoing constant revision in response to changes in the environ-
ment and in anticipation of future developments. All this looping occurring
as far as possible in real time!
It Must All Go Online
Mashups and clouds are now making it seem as if everyone just simply has
to release everything and publish it on the web. This is of course untrue.
Critical information that enables a company to distinguish itself from com-
petitors is typically information that companies want to keep within their
own walls. There are, of course, unforeseeable consequences of allowing
competitors free access to such information. Commercial distinctiveness is
then instantly lost, and a company is robbed of its ability to provide added
value. Companies must certainly keep a close eye on their own value chains.
Parts of the business process can undoubtedly be easily outsourced. The
issue is therefore to identify the element that can be replaced by a service in
the cloud.
Making this determination could result in the creation of new value chains
extending beyond company walls. In such circumstances, companies must
focus on what they do best, outsource things that others do better, and keep
an eye on the ecosystem of services on offer. A service that is perfectly good
on one day might on any subsequent day be replaced by a still better service
from another party. The feld in which companies are now operating is so
dynamic that they cannot permit themselves the luxury of overlooking any
223
10 Debunking Collaboration Myths
opportunities. The IT department, in collaboration with the business depart-
ment, must constantly be looking out for the next environmental change.
It Is All or Nothing
It is best to begin small. A company cannot, of course, transform itself all at
once. In just procuring the tools, a company is far from fnished its process
of adaptation. It is ultimately the companys people who must be changed,
along with the associated business culture.
A big bang scenario will only run into resistance. It is much more sensible
to follow a gradual approach. Allow the company to frst become familiar
with a blog or a wiki. When one of these tools is accepted by everyone and
people are capable of using the tool on their own, the next tool is then made
available.
Be ready in advance to accept the fact that not every tool will be accepted by
everyone. If such is the case, dont try to enforce acceptance, but withdraw
the tool. Attempt to discover what is causing the resistance; gain consensus
and offer a new tool in order to achieve similar results. Tools might be used
differently than was envisioned. Dont be scared, let it happen, the results
might positively surprise you.
It is a question of trial and error. Web 2.0 might not only transform the
heart of the business but also, most assuredly, the hearts and minds of
employees.
Collaboration Will Not Work in Old-Fashioned Hierarchies
On the web we can fnd all kinds of examples in which people collaborate.
One of the common myths within all these examples is that they only work
within bottom-up organizations. Leaders are no longer needed. The old hier-
archies have to die in order to create a true collaborative organization.
Clearly this is not true. Organizations without leaders cannot exist. However,
the role of a leader whom we have implemented within our organizations
since the rise of the industrial revolution has to change. Leaders can no
224
Collaboration in the Cloud
longer work the old-fashioned way by pushing orders top-down to the work-
ing people.
The new leaders must listen to the ideas of the working people. Encourage
the people and their ideas. Empower them in order to spread and embed
those ideas within the organizations.
Management guru Seth Godin has written a book Tribes: We Need You to
Lead Us
3
about this subject. From his point of view,
Management is about manipulating resources to get a known job done. Leadership,
on the other hand, is about creating change that you believe in.
Linda Dunkel and Christine Arena published a white paper called, Leading
in the Collaborative Organization: How Collaboration Drives Innovation and
Value Creation in Todays Corporations.
4
In it they say,
Collaboration is not about shifting from command-and-control to coax and cajole.
Instead, collaboration is an essential tool for the new kind of business leader the
facilitative leader one who engages relevant stakeholders in solving problems col-
laboratively and works to build a more collaborative culture in his or her organization
or community.
The Credit Crunch Will Kill Collaboration
We are now experiencing diffcult times. Every country, every organization
is facing the fact that the fnancial crisis has vaporized zillions of dollars.
How are we going to survive this disaster?
Organizations now have the choice. Do they stop investing or not? Will they
sit on their money and wait for better times or will they invest in innovations,
hoping that they will be the new leaders in the near future?
Collaboration within and outside the organization can make a huge differ-
ence in these harsh times. By using all kinds of online tools, organizations
3 Seth Godin, Tribes: We Need You to Lead Us, Penguin Group, 2008.
4 Dunkel, Linda and Christine Arena, Leading in the Collaborative Organization: How Collaboration Drives
Innovation and Value Creation in Todays Corporations, Interaction Associates, June 2007.
225
10 Debunking Collaboration Myths
can tap into the collective mind of their customers. Plug in to their knowledge
in order to improve products, invent new ones and survive! Collaboration is
the killer application for murdering the fnancial beast!
10.3
Conclusion
In an interview on November 1, 2008, Wikipedia founder Jimmy Wales stated
that:
Were really just at the beginning, still, of collaborative efforts. In video, right now,
were still back in many ways in the Web 1.0 era. If you look at almost everything on
YouTube, its individuals doing videos, either funny cat videos, or drunk girl videos
seem to be quite popular there. What we havent seen yet in video is large-scale col-
laborative projects.
And with this observation, Wales hit the nail on the head. Considering the
time that has passed since the introduction of the internet as well as the
disruptive effect of this new technology on entire industries, it is impossible
not to conclude that the impact on our society has been enormous. And the
repercussions are only just beginning. Some of the worlds most prominent
companies online have only existed for less than 10 years!
All of us are standing on the threshold of a fundamental transition. The ways
in which we are accustomed to doing business are based on an organizational
form created in the industrial revolution, an historical phenomenon that
reached its zenith at the end of the eighteenth century. The blessings of the
internet have entirely transformed our overall worldview. It is therefore no
longer possible for us to continue following the road that we frst began trav-
elling back in the seventeenth century. We are at a crossroads but do not
precisely know which road to take.
According to Al Gore, the technologies behind the internet can save us all:
Now is the time to really move swiftly, to seize these new possibilities and to exploit
them Web 2.0 has to have a purpose. The purpose I would urge as many of you as
can take it on, is to repair our relationship with this planet and the imminent danger
we face.
226
Collaboration in the Cloud
It is therefore not so strange that a large number of horror stories are now
cropping up. However, we should not let these ghost stories frighten us.
Instead, we need to continue to probe to the very heart of the matter in order
to discover the new types of collaboration that the future has in store for us.
In this way, we will be able to make use of the emerging new practices in our
own companies as quickly and adaptively as possible.
227
About the Authors
Erik van Ommeren http://www.linkedin.com/in/erikvanommeren
Erik van Ommeren is responsible for VINT the International
Research Institute of Sogeti in the USA. He is an analyst, public
speaker and co-author of the books SOA for Proft: A Managers
Guide to Success with Service Oriented Architecture and Open for
Business: Open Source Inspired Innovation.
Sander Duivestein http://www.linkedin.com/in/sanderduivestein
Sander Duivestein is a senior analyst at VINT, the International
Research Institute of Sogeti. He is also an internet entrepreneur.
Prior, Sander was a software architect at Capgemini. He is co-
author of the book Me the Media: Rise of the Conversation Society.
John deVadoss http://www.linkedin.com/in/jdevados
John deVadoss leads the Patterns & Practices team at Microsoft.
His responsibilities include platform and architecture strategy
for the Microsoft application platform and developer tools. He has
over 15 years of experience in the software industry and has
been at Microsoft for over 10 years.
Clemens Reijnen http://www.linkedin.com/in/clemensreijnen
Clemens Reijnen is a software architect at Sogeti and was awarded
Microsoft Most Valuable Professional (MVP) by Microsoft. Cle-
mens has a broad background in software development and
architecture. He also runs a technical blog.
Erik Gunvaldson http://www.linkedin.com/pub/0/103/558
Erik Gunvaldson is a senior program manager for Microsoft
Online Services. He manages the partner, customer, and com-
munity programs of Microsoft Online. He has over 20 years of
experience in IT.
229
Index
A
Ajax 187-188
Akst, Daniel 63
ALIPR 111
Amazon 34, 108, 134-135
Amazon Web Service 67
Apple 66
Application Service Provider, see ASP
Arena, Christine 224
ASP 11-12
attention, continuous partial 115
autonomy 77-78
Azure 166-167
B
B2C 2.0 181-185
innovation 183
marketing 183-184
product development 183
reasons for 182-183
sales 184
support 184-185
training and education 185
Babauta, Leo 142
Barabsi, Albert-Lszl 4
Beckstrom, Rod 77
Bell, Alexander Graham 89
Berger, Suzanne 65
Berners-Lee, Tim 35
Blogger 67
blogging rules 152-154
Bloglines 114
blogs 76, 98
volume 109
bookmarking 107-108
boundaries, crossing 26-30, 212
Brafman, Ori 77
Brynjofsson, Erik 78
bullthorn acacia 55
business reality 1-7
Business-to-Community, see B2C 2.0
butterfy effect 4
C
Carf, Christopher 5
Carr, Nicholas 60
Cerf, Vint 217
change:
managing 210-211
responding to 77-78
Channel 9 153
Chaplin, Charlie 46
cloud (see also cloud computing) 9-30
and mashup 68
defnition 9-18, 202-203
guiding questions 201-214
relationship with SaaS 12-15
stages of adoption 67-68
terminology relating to 14
two dimensions 167
cloud computing:
defnition 9-10
emergence 164-167
enabled by Software + Services
192-193
examples of services 15
Cluetrain Manifesto 57-58, 75-76
Coase, Ronald 27
230
Collaboration in the Cloud
collaboration 9-30
anatomy of 87-124
and innovation 24-26
by whom? 203-204
conversation economy 192-193
costs 208
crossing boundaries 192, 212
dealing with versioning 207-208
defnition 18-26, 202-203
evolving 44
free 24
goals and rewards 146-155
groundwork for successful 125-155
guiding questions 201-214
impact of technology on 42-44
in enterprise 181-185
in nature 56
integration 208-209
joint proposal by two parties 27-28
managing change 210-211
measuring success 214
motivation for 23-24, 204-205
myths 217-226
reasons for 192-193
requirements for excellence 131
role in evolution 55
rules 149-154
security 210
self provisioning 192
shared vision 147
software matrix 121-124
tools 92-121, 218, 220
types of 191
within a project 22
collaborative culture 128, 138-146
collaborative leadership 141
collaborative mindset 142
collective intelligence 180
Collins, Charles 1
communication 87-92
electronic 89-92
tools 88, 92-121
competitive advantage 211-212
Comtesse, Xavier 65
consumer demands unique experience
36-37
consumployee 77
continuous partial attention 115
conversation economy 192-193
Conversation Prism 59, 92
conversation society 162-163
conversations:
markets as 57-58
naked 58-60
ongoing 74-76
society of 56-61
credit crunch 224
crossing boundaries 192, 212
cost 26-30
reality of 29-30
crowdsourcing innovation 24-26
culture:
collaborative 128, 138-146
determined by people 144-146
D
Darwin, Charles 51-54
DataTelephone 90
Debategraph 138
Del.icio.us 107-108
deliverables, building 94-97
deployment and release 189
Digg 67, 107
digital natives 23, 81-83, 115, 145
discovery 109-112
disruption 159-160
Drucker, Peter 33-34, 147
Dunkel, Linda 224
DZone 108
231
Index
E
eBay 34, 108
effciency 47
electronic mass media 163
Ellul, Jacques 39
email 89-90
end of 120
problems 90-92
role of 205-206
versus wiki collaboration 91
Enterprise 2.0 125, 181
evolution theory 52-54
experience, unique 36-37
F
Facebook 34, 67, 104
fax 89
fnancial crisis 1-2, 6-7, 224
fnch 52-53
Fire Eagle 118
frm, new nature of 51-69
fve forces model (Porter) 74-75
Flickr 67
Ford, Henry 36
FriendFeed 34, 100, 118-119
G
Gartner Hype Cycle 67-68
GEN-Y-ers 23
goals 147-155
Godin, Seth 5, 7, 224
Google 130
Google App Engine 67
Google Maps 67
Gore, Al 225
government, competetion in 29
Groove 95-96
H
Hamel, Gary 62, 84
Holland Casino 71-72
Huang, Jeffrey 65
Hype Cycle (Gartner) 67-68
Hyves 34
I
IBM Cloud 67
IBM Many Eyes 138
ICQ 97
ideation 24
identity 128, 133
Illich, Ivan 18, 60
industrial revolution 36, 46-47
innovation 24-26
consumployee as source of 77
new age of 62-63
of management 84
instant messaging 97, 100, 188
integration 116-119, 208-209
interaction 97-99
internet, infuence on business 2-3
interruptions 114-116
invisible hand 44-45
iPod 66-67
Israel, Shel 76
IT:
consequences of technological
innovations 82-84
facilitating knowledge-building 83
ITAGroup 177-178
iTunes 66
J
Jaiku 100
232
Collaboration in the Cloud
K
Kennedy, Dennis 125
knowledge:
building corporate 83
building 94-97
convergence of 35-36
knowledge management 94
collaborative 80-81
Kondratiev, Nikolai 40-41
Kondratiev Wave 41
Krishnan, M.S. 62
L
leadership, collaborative 141
Levine, Rick 56
lifestreaming 59, 101
LinkedIn 103, 105-106
Live Mesh 67, 96
Locke, Christopher 56
Long Tail 63
Lorenz, Edward 4
M
Mackenzie, Deborah 43
management:
future of 62
innovation of 84
Management 2.0 61-68
Many Eyes (IBM) 138
Margulis, Lynn 55
marketing, viral 183-184
markets:
as conversations 57-58
changing 74-81
Marx, Karl 36
mashup 63, 68, 116-118
integration 116-119
Maslow pyramid 148-149
mass media, electronic 163
McLuhan, Marshall 39-40, 61, 87
media 162-163
media revolutions 163-164
Meltdown Monday 1, 5
Metcalfes law 101
microblogging 98-101
Microsoft Groove 95-96
Microsoft Live Mesh 67, 96
Microsoft Popfy 67, 117
Microsoft SharePoint 71-72, 125-126,
157-158, 177-178
Microsoft Virtual Earth 67
mindset, collaborative 142
Modern Times 46
Morse, Samuel 89
MSN Messenger 100, 114
MySpace 34, 104
myths 217-226
N
Naked Conversations 58-60, 75-76
news feeds 113-114
notifcation 112-116
interruptions 114-116
O
Offce Communicator 113
open innovation 24
OReilly, Tim 185
organization:
and collaboration 18-26
autonomy 77-78
impact of change 73
responding to changes 77-78
Orlikowski, Wanda 139
Orr, Julian 146
Ozzie, Ray 159, 166
233
Index
P
Page, Larry 130
paradigm shift 34
Perez, Carlota 42
Pipes 67, 117
platform concepts 186-189
Plato 38
Pony Express 89-90
Popfy 67, 117
Porter, Michael 63-65, 74
Prahalad, C.K. 62
presence, reporting on 99-101
printing press 163
productivity 73-84
improving 78-80
programming models 188-189
prosumer 36
publishing company 157-158
R
Rasmussen, Chris 91
rating 107-109
REAAL Verzekeringen 49-50
real time 60-61
relationships 101-109
Representational State Transfer
(REST) 188
reputation 107-109
REST 188
revolution:
industrial 36, 46-47
media 163-164
technological 33-48
rewards 129, 147-155
Rich Internet Application 187
Richardson, Adam 66
Rifkin, Jeremy 63
RSS 113-114
rules 149-154
blogging 152-154
S
SaaS 159-175
choice for 213
conceptual map of 16-17
costs 208
dealing with versioning 207-208
defnition 165, 202-203
downside 14
emergence 164-167
examples of services 15
integration 208-209
managing IT focus 166
managing risks of software acquisi-
tion 165
relationship with cloud 12-15
security 210
service-level agreement 134-136
terminology relating to 14
upside 13
Satir Change Model 5-6
Schumpeter, Joseph 42
Scoble, Robert 58-59, 76, 153
search engines 110, 190
Searls, Doc 56
security 210, 219-220
self provisioning 192
service as a service 16-17
service-level agreement 134-136
Service-Oriented Architecture, see
SOA
service providers, map of 17
services, mixed with software 159-175,
213
Shared Service Center 11
SharePoint 71-72, 125-126, 157-158,
177
Sifry, David 152
Simon, Herbert 3
six degrees of separation 106
Smith, Adam 44-45
234
Collaboration in the Cloud
SNS 105-106
SOA 174
evolution of 161-167
social bookmarking sites 107-108
social computing:
areas of use 183-184, 184-185
emergence 179-180
enabled by Software + Services
192-193
expectations 194-195
for business 179-195
in enterprise 181-185
social networks 34, 67, 102-108, 191
Social Networks Software (SNS) 105-
106
social structure 101-109
social technographics ladder 145
society of conversations 56-61
Socrates 38-39
software, mixed with services 159-175,
213
Software as a Service, see SaaS
software matrix 121-124
Software + Services model 159-174, 213
enabling social computing 192-193
implications 170-174
principles 168-170
Solis, Brian 59, 92
speed of business 60-61, 74-76
Spencer, Herbert 54
starfsh 77-78
status, reporting on 99-101
Stimmt AG 31-32
stock market 1-2
Stone, Linda 115
StumbleUpon 107-108
survival of the fttest 54
Sydved AB 85-86
system as product 66-67
T
tag-cloud 80-81, 190
tagging 97, 110-111, 190
Taleb, Nassim Nicholas 5
Talpa Creative 26
Taylor, Frederic Winslow 45-46, 139-
140
Taylorism 45-46, 140
technographics ladder, social 145
technological revolutions:
impact 33-48
six 40-48
technology 206
adoption curve 43
and trust 133-134
impact on collaboration 42-44
impact on community 34-37
infuence on business 2-3
negative consequences 37-40
telegraph 89
telephone 89
telex 90
Thamus, King 38-39
Thomas, Jesse 59, 92
Thoth (god) 38-39
time-place matrix 121-122
time-way matrix 123
TiVo 34
Toffer, Alvin 36, 60
Tomlinson, Ray 90
tools, collaborative 92-121, 133
TopCoder 25
Toyota 79
Toyota Material Handling Europe
215-216
transparency 60, 130
trust 128
and technology 133-134
levels 132
235
Index
model for 129-138
need for network 137-138
shared model of 149
trusting information 136-137
trusting people 130-132
trusting websites 134
Trustsaas.com 135
truthiness 60
Twirl 115
Twitter 34, 99-100
type letters 163
U
user experience:
multi-headed 173-174
rich 187-188
user profles, heterogeneous 172-173
UVIT 197-199
V
value, source of 76
value chain:
by Porter 64-65
unbundling chains 63
unbundling 64
Value Chain 2.0 65-66
viral marketing 183-184
vision 147
W
Wales, Jimmy 225
web:
as hub 194
as platform 186-189
collaborative 191
evolution of 162
read / write 189-190
social 191
Web 2.0 11, 175, 180, 185-191
communication tools 92
defnition 185-186
focus on data and content 189-190
platform concepts 186-189
programming models 188-189
stages of adoption 67-68
types of collaboration 191, 191
Web 3.0 112
web feeds 113
web media 164
Web Science Research Initiative 35
Weinberger, David 56
Wesch, Michael 184
Whittaker, Steve 92
wiki 95
collaboration 91
defnition 95
empty 127
Wikipedia 34, 67, 116, 137
Windows Azure 166-167
Windows Live Photo Gallery 110-111
Woloski, Matias 16-17
work, new rules of (Babauta) 142-144
X
Xbox Live 187
Xobni 118-119
Y
Yahoo! Fire Eagle 118
Yahoo! Pipes 67, 117
Yammer 99
YouTube 34, 67, 109