Collaborative Online Lists
Everyone uses lists. Some of us are more serious about using lists but we all use them. We use them for keeping track of tasks we need to do, shopping for groceries, maintaining contact information, and in hundreds of other ways. We also use lists when we work with others (for example, on a project team or with colleagues in our workgroup). Lists are important for keeping track of the work we are doing together, for sharing information, and so forth. Collaborative online lists are simply lists that are easily accessible and can be maintained by multiple people.
Perhaps the most popular list-editor is Microsoft Excel. Of course, this use of Excel does not exercise any spreadsheet calculation feature. Excel simply makes editing lists easy. A quick browse through Microsoft’s online Excel template catalog reveals a number of list-only templates.
However, the problem with using Excel to manage a list, such as project team’s issue list, is that it is stored in a file and files can be black holes of information (recall that I hate files). Files tend to be treated as personal items and not easily shared. A project’s administrator may keep a list of issues and send it out just before a weekly meeting but that is about as much sharing as we see when lists are kept in files. Need to find out about a particular issue before the next meeting? Well then call the project administrator on the telephone.
Collaborative online lists avoid this problem by being stored online so they are easily accessible and the responsibility for updating them can be shared. The good news is you may already have the most popular online collaborative list solutions running within your intranet. Lists can be found in collaborative workspace products such as EMC/Documentum eRoom (where lists are called databases), Lotus Quickr, or Microsoft SharePoint.
If done correctly, collaborative online lists can support both emergent and hierarchical uses. For example, I know of a large company that was going through a significant downsizing. They were running SharePoint on their intranet and someone created a list to capture information about people leaving the company. It started filling with names and became quite popular. That is, until HR shut it down (I suppose there are other lessons to learn here). Nevertheless, this is a good example of an emergent online list.
Collaborative online lists can also support hierarchical use cases. For example, large development efforts often consist of many teams within a hierarchical reporting structure. Imagine having a workspace for each team and each one maintaining a list of issues in a common format. These lists could then be rolled up and consolidated to provide managers with a broad overview of all issues (yes, culturally, this may be challenging). eRoom provides a similar function with their “Enterprise Database” function.
If list items have unique URLs they are easier to reuse. For example, you could use social bookmarking systems to bookmark and tag an issue (or any type of list item) and associate them with other related web pages or sites on the intranet. This way an issue within a list can become part of a larger enterprise knowledgebase.
Collaborative online lists are a lot like wikis. I view wikis as replacing Word files and collaborative online lists as replacing lists kept in Excel files. In both cases, information is easier to access and uniquely addressable (and, hence, easier to share and recall).
However, there are a few things collaborative workspaces can learn from wikis, the biggest of which is security. Often times the default security of a collaborative workspace limits access to no one, except those specifically invited to the workspace. Wikis tend to be open from the start. However, wikis marketed to enterprises can also be tied down, just like the traditional collaborative workspace. So, this isn’t necessarily a technology problem.
This is a repost of a blog originally posted on the Collaboration and Content Strategies Blog