The successful roll-out of an easy to use collaborative system within an organisation can work to improve staff productivity and other facets of the company including staff engagement and knowledge. A Wiki is a perfect tool to fill this E2 void in any business.
A Wiki can provide access for all staff members to areas such as:
- People expertise
- Expertise in processes- previous troubleshoots, training updates
- Documents and resources–Make hidden data shared to drive collective intelligence
- Enhanced search–Quickly provide relevant resources for the individual
- Essential information such as rosters/meetings/calendars
The ability to streamline information and expertise provides great opportunity for an organisation to get the most out of their staff, however there are always problems associated with implementing collaborative tools. Some disadvantages users found when using wikis consisted of the following:
- Spam
- Inappropriate and incorrect language and content
- anyone being able to edit content
- Info displayed in an illogical manner
Although these are real issues, a few simple strategies such as making sure the 'rules of conduct' are monitored and enforced, as well as appointing a wiki 'champion' to observe participation and help other employees contribute can work to iron out the inevitable bugs that will occur.
Wikis and Brisbane Airport
As discussed in my previous post, Flight Centre has successfully implemented a Wiki into their IT collaboration architecture. This has worked effectively to connect geographically dispersed employees and encourages faster innovation by being a working source for troubleshoots and previously encountered issues.
In the context of our case study, Brisbane Airport could utilize a wiki in order to improve:
- HR procedures- Rosters, leave requests,
- Communication with outside providers and contractors- Specific How to guides for individual businesses accessing the airport (i.e where to get a security pass).
- Staff Training- Both direct airport employees and other. The airport could use the space for initiation procedures, with management able to streamline the process through the collaborative tool.
- Back of house procedures- the space could be used to refine work practices. Monitored by management to insure uniform adoption of any changes.
- B2B customer service- a place for outside providers to voice their opinions/ideas about interactions with the airport.
- Union information- meetings, issues etc.
Can you think of any other ways the airport could benefit through the use of a wiki? Do you have experience using a Wiki within an organisation? If so, i would love to hear your thoughts on my strategy and how it compares.
Thanks for reading!
Justin.