Ben McCallum's Blog

Dissecting ASP.NET MVC3, CSS3, HTML5, jQuery and a whole lot of other things ending with numbers…

Archive for the category “Wiki”

LibGuides – Enterprise 2.0 for the Library

Currently I am completing a Request for Proposal document outlining a web 2.0 implementation plan for the QUT Library. After investigating the Library’s current situation and identifying the tools they are currently offering their clients, I have come across one in particular which I am going to discuss in this post. This tool is known as LibGuides.

LibGuides is a software package developed by Springshare, a company who has made it their goal “to develop practical web 2.0 applications built specifically for libraries and educational institutions,” (Springshare, 2009). LibGuides is a “web 2.0 content management and library knowledge sharing system” that can be used to create attractive, multimedia rich web pages to share resources, content and knowledge collaboratively amongst users. LibGuides puts the power of content creation in Librarian’s hands. It provides a flexible and easy to use interface from which Librarians can create customised pages specific to the content they wish to display.

Below is a fairly long and unintersting video about the uses and benefits of LibGuides… but if you don’t feel like watching it all (Iwon’t blame you) I’ll give you the low down of how LibGuides works, what it offers and the benefits it provides.

How does it work?
The benefit of LibGuides comes from the ability for Librarians to customise the look and feel of the website and add content modules to the page similar to MySpace’s Profile 2.0 system. Dragging and dropping modules onto the page is simple and these modules range from plaintext modules to fully-fledged RSS modules, multimedia modules, Delicious tag cloud modules and so on. These modules or widgets depending on what you prefer, can be further customised to enable commenting, polls and so on to enable participation from its users.

What does it offer?
LibGuides offers Librarians with an unlimited potential to create meaningful, attractive and useful content for their clients. With the ability to drop LibGuide modules onto the page, multimedia, tag clouds, polls, commenting systems, social media integration and sharing are all at the finger tips of the Librarian without the need for profound technical knowledge.

What are the benefits of LibGuides?

  • Integrating and embracing Web 2.0 technologies such as Twitter, syndication in the form of RSS feeds, social media sites such as Facebook, wikis and blogs has never been easier and with thousands of pre-made templates designing is even simpler.
  • Creating communities, sharing resources, monitoring usage and catalysing learning is much easier.
  • Receiving user opinions and running polls or questionnaires is as simple as dropping a module onto the page and customising a few fields. But for advanced users, customisation is powerful and can be used to adjust the appearance, look, behaviour and content of a module.

All in all I believe LibGuides is a huge step in the right direction for Libraries wanting to embrace web 2.0 concepts. It offers more flexibility and control in areas such as subject guides, learning portals and so forth allowing content to be customised and encouraging, enhancing and increasing collaboration and sharing in ways that Web 2.0 can only offer. You can try out LibGuides in use at the QUT Library’s subject guides:
Or if you are looking for more information on LibGuides you can visit their website at:


Grassroot Enterprise 2.0 projects lead to success

I’ve previously written about adoption of Wikis in company intranets. What I found quite interesting was that Disney’s wiki started as an unsanctioned effort at speeding up and increasing the productivity of their internal faction. It was later recognised as a valuable tool by the higher ranks and upgraded to fully accommodate for their needs. This kind of Enterprise 2.0 stories are often called grassroots stories. This means that the employers have addressed their needs and then the project has risen up through the ranks and recognised by those in authoritative positions. A recent article in the Social Computing Journal found that:

  1. Underground efforts yield big results – Companies are turning a blind eye to underground social software efforts until they prove their worth, after which they integrate them more thoroughly.
  2. Front line workers are driving the vision – Many senior managers still consider social tools something their teenagers use. Young workers, who do not need to be taught or convinced to use these tools, expect them in the workplace.
  3. The business need is the big driver – Social software is not about the tools, it is about what the tools enable the users to do and about the business problems the tools address.
  4. Communities are self-policing – When left to their own devices, communities within enterprise intranets police themselves. Workers tend to retain their professional identities, leaving little need for the organization to institute controls.
  5. Organizations must cede power – As companies have been learning from using Web 2.0 technologies to communicate with their customers, they can no longer fully control their message. This is true, too, when Web 2.0 tools are used in internal communications.

What many people would consider a rare occurrence is now being realized as commonplace. Employees are demanding social media enters their working lives and are even taking their own steps to ensure it is incorporated into their work. It’s an interesting find and I look forward to sharing any other news on the topic that I find.

Discussion on Failures in Adopting Enterprise 2.0

I’ve been reading lately, a tonne of articles discussing why Enterprise 2.0 projects sometimes fall short and why sometimes what sounded so good at first suddenly fell in a big heap of over-hyped software. In this post, I’m going to discuss 3 reasons why Enterprise 2.0 can fail. Check out: 14 Reasons Why Enterprise 2.0 Projects Fail – for a more indepth discussion. A lot of my ideas for this post came from here and it has some very good links to other articles.

1. The tool isn’t sharp enough

Every company has its own requirements when it comes to Enterprise 2.0. The fact of the matter is Enterprise 2.0 giants such as Microsoft Sharepoint (the most popular E2.0 tool on the market) are made to satisfy the masses and appeal to the largest audience possible. What they don’t provide are solutions to individual companies that quite frequently need something specific to their business domain. More specifically, the tools are there, they just aren’t customised enough making it an eternal struggle for the users to make it fit. If your business requires something different to the masses, it could be worth investing in something with more than just the default settings enabled.

2. Spend some money

Not usually what your CEO would want to hear but a lot of Enterprise 2.0 projects fail because no one knows what they are doing. Spend some money on giving basic training about social media tools and what Web 2.0 or Enterprise 2.0 is. Of course, this varies greatly on the context and employees in your business. Usually there will be a portion of a company’s workforce who are keen forerunners in adopting these tools and will learn themselves. But the older ranks will be skeptic and giving them basic information about how “users add value” will get them interested and using the tools in the right way.

Dion Hinchcliffe puts it well, “Understanding what tags are and how they help users locate content later on, publishing frequently requested information in blogs, teaching that wiki editing is safe and that it’s virtually impossible to harm them are all key learnings that many less-social media literate workers will greatly benefit from and can actively address many upfront barriers to adoption.”

3. Why do we need this?

Starting an Enterprise 2.0 project without having a clear idea of what it is going to be used for and what problems it will address is like an 80 year old buying a high-end computer with quad-core processing to read emails. Don’t get sucked in because everyone is doing it. Have a clear purpose and know what it is you are hoping to achieve. That way employees also know what to use it for. There will always be employees who invent great ways to use a tool however to encourage uptake, market it as a solution to an age-old problem that everyone encounters on a day to day basis. For instance, “Don’t send each other a billion emails a day and spend your whole day reading emails. Instead, use a wiki or update your status to let your colleagues know what you are doing.” Everyone hates a full inbox so the interest will rise.

These are just 3 reasons why Enterprise 2.0 projects fail. Of course every failure has its individual reasons but these ones I found quite interesting and possibly more fitting to a wider number of cases. And finally, slightly off topic but entertaining none the less.. here is a list of the “Nine worst social media fails of 2009…thus far“.

Feel free to add comments 🙂 and let me know of any E2.0 fails you have heard of.

Zoho Projects Review


For this post I’ve decided to do something a little different. I’m going to do a review on a product called Zoho Projects. This is a project collaboration tool designed specifically as a business app. I’ve done this review using the “one free trial” that comes with registering to use Zoho products.

Who/What is Zoho?

Zoho is a relatively new player in offering online applications. However, they offer a comprehensive suite of web-based applications for anything from word-processing, powerpoint creating to project management, web conferencing and invoicing. You can check out the Zoho Corporation about me section here, or visit their web app. home here. Registration is free, and you can use your exisiting Google, Google Apps or Yahoo! account to register also.

The Low-down on Zoho Projects

The interface for a project is rich and simple to use. It provides easy access to a diverse set of tools related to project management and collaboration. Each user has their own dashboard and can upload some details about themselves to their personal profile. They also have a status update field much like Facebook and Twitter that lets them update others in the project about what they are doing in less than 140 characters. The dashboard displays all project members’ updates and  latest activities whilst also providing access to an RSS feed to receive these updates in an external RSS reader. See the dashboard below:


As you can see Zoho Projects offers the following sections: Tasks and Milestones, Calendar, Meetings, Reports, Forum, Wiki, Chat an Users.

Tasks and Milestones
In the Tasks and Milestones section you can create Milestones. Under each Milestone can lie several task lists which each contain a number of tasks. Each of these can be allocated to a project member and assigned dates to be completed. In addition, tasks can be given dependencies so that one must be completed before the other. The milestones are then reflected on the calendar showing when it is due. The dashboard updates section highlights new tasks and they are also feed into the RSS feed.

The meetings section lets users arrange meetings. The meetings have a time and date associated with them and can be allocated to specific users in the project. Notes can also be attached to the meeting for further detail. The calendar displays upcoming meetings and status and RSS feeds are updated with new meetings.

The reports section presents the user with a number of charts and such to document current task lists and milestones. These can be separated into each user and presented as bar graphs, Gannt charts and so on.

The forum section is just like any other standard forum platform allowing forum posts and users to reply to posts.

The wiki section allows users to create pages and edit them like any wiki platform. Nevertheless, the Zoho Wiki has powerful word processing tools available from the custom GUI at the top of the editing pane. This allows for complete manipulation of the wiki content. RSS feeds are available for all pages so users can subscribe and receive updates. Comments can also be posted on individual wiki pages for feedback and collaboration amongst workers.

Chat enables users to communicate via an Instant Messaging service. It is similar to a group chat in any messenger service such as Windows Live Messenger. You can also send files to other people in the chat.

This section is for managing the users associated with the project. Users can include employees, contractors and even the clients. This is the one-stop hub for viewing fellow employees profiles and communicating directly with them. Having clients as users is useful for gaining feedback from them by communicate directly to better understand their needs.


I think Zoho Projects is an extremely powerful tool for managing projects. The wide range of useful and applicable tools it offers its users are both powerful but at the same time extremely simple to use and navigate. I believe that this web application would be useful for small businesses and project teams. Whether it can handle extremely large project teams is another issue but I think it could quite possibly do the job. Just like all the other applications Zoho offers, this tool has exceeded my expectations and I will quite happily use it in the future. This tool is a prime example of an Enterprise 2.0 tool because of the intergration of many web 2.0 features such as: status updates, RSS feeds, wikis, and so on.

Wikis in the Enterprise

What is a wiki?

Wikis were first introduced in WikiWikiWeb a website designed by Ward Cunningham in 1995. A wiki is the term given to an online document that many people can collaborate on. That is, they can edit, update, delete, add pages/links, change content and so on to wiki pages. The most common and well known wiki is: Wikipedia.

What is an Enterprise wiki?

Infoworld declared 2004 as the Year of the enterprise Wiki, as wikis began to emerge in businesses across the globe. Bascially, a wiki that is used for conducting work in an enterprise is an Enterprise wiki.

What is so great about wikis?

  • Collaboration. Participation. Harnessing collective intelligence (Tim O’Reilly)
  • Wikis provide users with simple and easy to use methods of content creation via a wiki markup language.
  • Linking -> An important part of the SLATES paradigm in Andrew McAfee’s blog, wikis make linking to other wiki pages easy by stripping it down to the bare essentials in the Wiki markup language. Provides an easy ability to forge deep interconnections between data sources.
  • Edits and history of the document is tracked so you can return to previous versions and look at differences between versions.
  • User access control: Wikis can have the power to allow and deny users. Users who are not registered can be disallowed the ability to edit. Registered users will have their username fixed to edits so that these changes can be tracked to particular users.
  • Modern wikis can integrate with other tools such as e-mail, RSS and blogs.

Weaknesses of wikis?

  • Giving many users access relies on their ability to contribute effectively and advantageously.
  • Spamming can be possible when masses of users can contribute anonymously.
  • Control is sacrificed for empowerment, that is managers lose control while users take/get control.

Businesses using wikis?

  • Disney:
    Disney’s Digital Media faction started using a wiki when its team decided they needed a tool that matched their department. They needed speed and collaboration, so they create an internal website without consulting their boss. They just did it. The project was not seen as defiance of their management but rather a tool to enhance their performance and better use the resources of their 150-strong team. Reader here – Online version of the magazine article.
  • Dell:
    Socialtext co-founder discusses how their product helped Dell:

    “The second use case is a participatory knowledge base. So at Dell, for instance, we did a knowledge base for their call center. Their call center handles exceptions. That’s what they do all day long. Answer a call, hear the problem, look for an answer, and then they don’t have the information. Now, [with a wiki], they tap the informal network that exists inside the call center and document the solution. 99 percent of the pages created [on the wiki] and tagged allow the call center to go from 20 clicks to find information to four, substantially decreasing search costs and decreasing the average call time by 10 to 20 percent.” (Source: Discussing the role of enterprise wikis).

  • Yahoo:
  • “…we use TWiki internally to manage documentation and project planning for our products. Our development team includes hundreds of people in various locations all over the world, so web collaboration is VERY important to us. TWiki has changed the way we run meetings, plan releases, document our product and generally communicate with each other. We’re great fans of your work!” (Source: The Yahoo Twiki success page).

  • Others:
    See the Twiki (Wiki product provider) customer list with quotes from users of the software. Customers include: Nokia, Yahoo!, Oracle, Trend Micro, Sony, United States Coast Guard, Allergan, etc.

Post Navigation