bookmarking. It was recommended that
bookmarking should become a feature of the ‘to-be’
portal. If the results have the capability of showing
which other users already have certain key words in
their bookmarking lists, it is likely that highlighted
users will possess other bookmarks relevant for that
search. The Cognez tool was recommended for this
task. It was also suggested that a policy should be
introduced for the tagging of discussion forum
threads.
Personal Network Capability. The ‘as-is’ portal
neglected to display the links between users of the
personal network facility. It was recommended that
a Social Network Analysis (SNA) tool should be
used to discover network hubs and key people inside
the organisation based on their network use.
Use of Wikis for Group Document Authorship. It
was recommended that the organisation should use a
wiki for the group authoring of documents such as
best practice guides where experts could add and
review document contents in an interactive fashion.
It was also recommended that this authoring method
could also be used for more formal documents. Such
documents require a final quality review by
definition, but group authorship through wiki
technology provides added value in a number of
cases:-
Best practice documents elaborated
between colleagues in the same ‘skills
network’
Technical documentation, user-case for
customer relationship management, project
life-cycle management among colleagues in
the same project team
Job profile description developed among
colleagues from different departments
possibly located in different offices
Contract development between the case
study organisation and its supply chain
partners
Project requirements, specifications,
contract details etc. which may be
developed in collaboration between the
case study organisation and its customers
White papers, strategic discussions, etc.
between the case study organisation and its
partners
Improvements on Email Management. It was
identified that employees in the case study
organisation experienced email overload. This
problem was seen as key, by the case study
organisation, creating difficulties in their
collaboration and communication processes.
Certainly the use of technologies such as RSS and
wikis (mentioned earlier in this section) can be used
to divert and manage a large amount of email traffic.
To address this it was suggested that the
organisation could utilise a social networking
platform, such as Face book to organise and filter a
large proportion of the email communication.
Limitations. It must be noted that there were a few
limitations encountered in the implementation of
these recommendations at the case study
organisation. For security purposes the case study
organisation limited the online methods for
communication between users. Instant messaging
was not allowed and blogging and media sharing
platforms were also limited. Also the introduction of
new email practices did not end the practice of group
emails.
5 CONCLUSIONS
The landscape overviews provided by this research
can help industrial organisations to better understand
the opportunities offered by Web 2.0 technologies
and drivers and constraints behind their adoption by
industry. Even with the continual evolution of
technology the principles behind the landscape
overviews remain relevant.
REFERENCES
Daniel, D., 2007. Seven Ways CIOs can introduce Web
2.0 technologies into the enterprise. CIO Business
Technology Leadership. Available at:
www.cio.com.au/index.php/id;1146975385 (Last
accessed: 8 January 2010)
Hoover, I., 2007. Web 2.0 tools in business: Proceed with
caution - enterprise 2.0 must overcome concerns about
security and ROI to gain a foothold in business. Bank
Systems & Technology, 44(4), pp. 41.
O’Reilly, T., 2005. What is web 2.0, Available at:
oreilly.com/web2/archive/what-is-web-20.html (Last
accessed: 8 January 2010)
Robinson, H.S., Carrillo, P., Anumba, C., and Al-
Ghassani, A., 2005. Knowledge management practices
in large construction organizations, Engineering,
Construction and Architectural Management, 12(5),
pp. 431 – 445.
Wiens, J., 2007. Is web 2.0 inherently insecure? Network
Computing, 18(7), pp. 22.
Wittemburg, K., 1995. Group asynchronous browsing on
the world wide web, Proceedings of the 4th
International World Wide Web Conference 1995,
Boston, MA.
WEBIST 2010 - 6th International Conference on Web Information Systems and Technologies
378