Bill's Notebook

The recent media frenzy over the latest social media offerings introduced at SXSW last week demonstrates that collaboration is one of the app themes for 2011. This isn’t the first time collaboration software has been the “next big thing’” I remember back in the early 90′s when computer-supported work applications were all the rage (remember when “Lotus Notes” was first rolled out). Organizations threw a lot of money and resources at early collaboration systems but many were failures from the beginning.

The failure of many early collaboration systems to catch on was perplexing because software packages for individuals and organizations were doing well. What was it about developing software for groups that made it so different from developing software for individuals and organizations?

In 1994, Dr. Grudin (a computer scientist from the University of California) published an article that answered that question with the simple observation that groups were just different from individuals and organizations. How they are different is explained in his eight challenges for developers:

1. Who Does the Work and Who Gets the Benefits. Ideally the labor in operating and maintaining the groupware application must be roughly equal among the group members. In reality this is rarely the case. Consider a project management application where the team members are required to update it regularly with progress reports, performance data, and other data. A good deal of the team member’s team is compiling information and feeding the system while the project manager just has to spend a minimal amount of time reading reports the system generates. The team member sees only a burden from the software and soon starts to avoid doing this extra work which leads to poor reports causing the Project Manager to quit relying on the system for information. Soon, no one is using software.
2. Critical Mass of Users. The collaboration software field is filled with a number of different platforms for collaboration. Many offer similar features and each has its enthusiastic community of supporters. In large government agencies you can see several collaboration systems in various pockets of the organization that don’t communicate outside of their pocket. Ironically the systems that exist to promote collaboration often end up promoting organizational silos as the various groups argue that their system is the best solution.
3. Social, Political, and Motivational Factors. Dr. Grudin gives a great example of this challenge when he describes the failure of meeting management software. It assigned meeting rooms based on priority but quickly became useless because no one wanted to admit that their meeting was anything but “high priority.” As Dr. Grudin explains, collaboration software can only model a rational workplace but actual workplaces are much more complex due to organizational culture.
4. Exception Handling. We rarely work the exact way that is described in our work processes. Collaboration software built only based on the documented office procedures is seen as too rigid and not able to handle the flexibility required frequently at work. Just think of how often you don’t have a typical day at work and have to improvise a work solution. Now, imagine trying to program that into software.
5. Decreasing the Communication and Coordination Load. Organizations are designed to reduce the amount of communication and coordination needed to do the job. How many times have you said that you could get more done if you were not interrupted so often? Of these interruptions, how many were due to email, phone calls, a colleague stopping by to talk, etc.? Sometimes you can over-collaborate and this often is the result of poorly-designed groupware.
6. Hard to Evaluate Groupware. It is difficult to test groupware because the group dynamics are so hard to replicate. It can take several weeks of careful observation to fully understood how a group works and software designers just don’t have the time or expertise to fully evaluate how their software will aid in collaboration. Often the groupware vendor blames this on poor user training and will continue the same type of software with better tutorials and help aids but never realizing that the fundamental problem is that people just don’t like collaborating the way the system is forcing them to collaborate.
7. Intuitive Decision Making. Because of the nature of our work we often have to make decisions based on little evidence and thus we rely heavily on our intuition. Groupware applications rarely support intuitive decision making but rather force users to input great amounts of data so that a fully-reasoned decision can be made. Often we do not have all of the data and a decision must be made quickly so we abandon the groupware application to use a simple spreadsheet or other individual application to support our intuition.
8. Managing Acceptance of the Groupware. Too often I have seen a collaboration solution launched where the users are expected to adapt themselves to how the software works rather than the software adapting to the way the group works. There is a particular system at my work which is universally despised because it practically handcuffs a group of users to a cumbersome and protracted painful process. I’ve only used the system once but that was enough for me to avoid ever having even to click on the program icon.

Despite these principles being over sixteen-years old I still see the same mistakes being repeated in today’s Web 2.0 collaboration tools. I also see where companies have put these principles into practice and have made great collaboration software that has endured and grown in popularity. I fully suspect that Google engineers must have memorized these principles when they developed their Google Docs system. You can also see these principles at work in the various products from 37Signals and Zoho.

I leave a final exercise for the reader: how many of these principles does SharePoint violate (if any)? Or does SharePoint violate new principles of collaboration software?

Reference:

Grudin, J. (1994). Groupware and Social Dynamics: Eight Challenges for Developers. Retrieved at http://research.microsoft.com/en-us/um/people/jgrudin/past/papers/cacm94/cacm94.html.

First, a quick disclaimer: I am currently on a six-month detail for OPM’s Open Government Team. Yes, I am bragging but I also want to stress that anything I write on my blog is just my personal opinion and does not reflect the opinions of OPM, the Open Government Team, or anyone connected with the OPM Open Government effort.

Now on to the topic. There is a lot of cynicism both in and outside of government concerning Gov 2.0 and Open Gov. I believe most of this comes past government reform efforts which had, at best, mixed results. In my first round as a Federal employee I was involved with Gore’s Reinventing Government effort. Reagan had a blue-ribbon commission on reform as did Nixon. Government reform has been a continuing effort since Wilson and Taylorism. I believe they even found evidence of government reform efforts in Ancient Egypt (I wonder how you tell a god-emperor he or she needs to go “lean”).

So, with this long history of government reform which has some brought some innovation but disappointment what makes Gov 2.0 and Open Gov different? And is this difference enough to make a real impact? To me there are three major reasons why Gov 2.0 and Open Gov will succeed and succeed big:

1) Government is re-engaging their citizens. Public agencies can no longer operate as vending machines where citizens put in tax dollars and out pops government services. Agencies are becoming transparent and accountable for how they spend tax money and are encouraging citizens to become part of providing government services. Think of Dr. Noveck’s Peer-to-Patent program and the recent SeeClickFix programs.

2) Democracy is changing. I have written before about the emergence of monitory democracy and the recent events in Egypt, Libya, Yemen, and other Middle Eastern countries just demonstrates the desire for democracy and how media-rich nations empower citizens to grow democracy. Even in well-established democracies citizens are no longer content to vote for a representative and then trust that the government will operate in their interest. People want to speak directly to agencies that affect their lives and are demanding the right to monitor even the inner workings of the Federal, state, and local governments.

3) Balance of Information Power has shifted. Before the Open Data movement, government essentially held all the cards when it came to information about what government did and how it operated. Yes, there were investigative journalism articles, legislative hearings, and the occasional FOIA request but obtaining government information that wasn’t selectively released by agencies was difficult to obtain for the average citizen. Now, thanks to the Internet and Social Media technologies it is easier to gain access and to aggregate data sources to give a more complete picture of what government is doing. The Balance of Information Power is shifting in favor for the citizen and will continue to shift that way as government engages citizens and as monitory democracy evolves.

In Gov 2.0 and Open Gov the citizen is no longer a customer who passively receives government services. Past reform movements were built upon the vending machine model and that is why they didn’t deliver as promised. Gov 2.0 and Open Gov are built upon engagement and collaboration and that is why they will prove to be more successful.

What do you think? Are these three reasons valid? Are there better reasons for why Gov 2.0 and Open Gov will succeed? Or is Gov 2.0 and Open Gov just like previous government reform efforts?