This week’s
QOTW comes from Dion Hinchcliffe’s Enterprise
2.0 blog on CNET’s News.com. His latest post, called “Enable richer business
outcomes: Free your intranet with Web 2.0,” discusses the role of Web
2.0 within the context of traditional enterprise IT systems and software and “…how Web 2.0 seems to directly address a lot of issues with
existing software models in the enterprise.”
In his blog,
Hinchcliffe references Andrew McAfee’s article on Enterprise 2.0: The Dawn of Emergent Collaboration (in
MIT Sloan Management Review), which he says is “…one of
the most compelling descriptions of the use of Web 2.0 in the enterprise”
and then goes on to comment on it, saying:
It's about
enabling rich, dynamic outcomes from our IT systems, which we are now learning
by watching what's happening today out on the Web, are still too structured,
rigid, and make too many upfront assumptions to enable effective levels of
innovation, viral adoption, and increases in productivity. This is only exacerbated
today by the need for increasingly dynamic collaborative business software to
access the potential of things like tacit interactions, which is the core activity of
productive business work…
Of course,
the practice right now in most enterprises is to have a great deal of structure
and control in our IT systems. The revolution that the PC originally
ushered in, putting the choice and control of IT systems in any user's hands —
and making a mess for the IT department along the way — has fortunately or
possibly unfortunately been largely cleaned up. Things are so tidy and
well ordered that one could argue it's almost antiseptic, even antithetical, to
the creativity and innovation that are hallmarks the most valuable business
activities.
We're now
learning that the barriers and harmful upfront control that traditional IT systems
— admittedly which most of us thought was a good thing for a long time — are
often actually hampering effective work and putting up barriers to the
possibilities and potential of less structured, emergent systems that co-evolve
with their users.
Having said
all that, Hinchcliffe then prescribed six important factors that can help IT
teams strive towards
2.0—here’s a brief summary:
2. Zero Training/Simple: Any barrier
to use means that automatically fewer people will use the application or its
more complicated features…
3. Software as a Service:
Online software,
with its functionality and information available on any computer, home or work,
anywhere in the world, day or night, is the most productive and useful software
possible…
4. Easily Changed: If a user can't easily make the
necessary change to the structure or the behavior of a system, he or she must
have an expert — usually in the IT deparment — to do it, and get in line to
wait for it, not to mention pay for it…
5. Unintended Uses: Preconcieved notions about how an
IT system will be used can cut it off from the most valuable uses down the road…
6. Social: Enterprise Web 2.0 software
enables pull-based systems that enable people to come together and collaborate
when they need to and are entirely uncoupled when they don'…
Finally,
Hinchcliffe ends off with this to say:
At the risk
of sounding silly, and having seen with my own eyes the value of the this type
of software in many if not most business situations, I am here putting out the
call to demand easy access to intranet blogs and wikis. Yes, demand them,
and start using them, introduce your colleagues, and you'll be surprised at
what springs forth. And lastly yes, Web 2.0 in the enterprise is
certainly much more than just blogs and wikis, but if you don't have them, it's
clearly an excellent place to start.
All this
really made me think of a recent experience I had, when I was trying to
implement an enterprise-wiki solution as the underlying infrastructure for a
secure extranet site to support some external contractors. When the contract
for this wiki solution was reviewed by the IT department, the first thing that
came back was an immediate (negative) reaction because they thought the
solution might be suspiciously similar to MySpace.com
and would therefore not be allowed.
Although I
was eventually able to convince them that it was not a MySpace-type solution (and neither was that its intended purpose),
what it really demonstrated to me was that—just as Hinchcliffe described in his
blog—ironically, instead of being the key supporters of moving towards
Enterprise 2.0, traditional enterprise IT groups may in fact be one of the
biggest barriers to achieving it. Sigh…












Recent Comments