How to avoid collaboration snares

Collaboration software designed to help project teams work together more efficiently is widely used in the private sector and beginning to make inroads with federal and state governments. One popular tool is Microsoft’s SharePoint software. But while applications such as SharePoint offer the potential for increased efficiencies, program managers must watch out for some pitfalls when they prepare to get a project off the ground, warned Scott Lock, principal consultant with Excella Consulting

Lock said setting up a SharePoint or any other collaboration software project is less about the technology and more about the underlying information architecture and governance. By making the experience user-friendly and seamless, he noted that customers would be more likely to adopt SharePoint. He warned that the advantage and disadvantage of SharePoint is that “you can do a lot out of the box.” But without strong information assurance and governance practices, there will be customer dissatisfaction.

A common failing in both the commercial and private sectors is a lack of prioritization in projects, Lock said in an interview. He explained that it is ultimately the organization’s responsibility to prioritize activities such as whether it is more important to identify all the people involved a project or to document all of the effort’s goals.

Federal agencies often need the advice of an outside vendor when attempting to set up a collaboration project or an information-sharing web page, he said. Lock added that he had yet to see a situation where the clients and end users were ready to set up a collaboration system by themselves. “In any effort you need a coach — whether it’s strong software development practices, accounting governance or golf — the best in the world have coaches. … It all boils down to having a strong lead to guide them through the process,” he said.

Prioritization is the key best practice for a successful SharePoint implementation in state and federal government, he said. After prioritization, attention must be paid to information architecture and governance. Managers should also take time and care to understand how they will roll out a program. “Know the problem you’re trying to solve. You can throw all the hardware you want at it, you can have all the bells and whistles and stand it up and say ‘OK here you go. Start using this.’ But if throw it over the fence, the adoption will be horrific,” he said.

Lock explained that “big bang” rollouts often fail. He said that managers should focus on small, typically department sized rollouts. They must demonstrate that they can successfully collaborate or build something, such as an application. Helping to solve business problems and demonstrating value will also help spur adoption, which will attract departments and groups within agencies. “If you don’t have users, then you don’t have people who are going to adopt and make it breathe,” he said. Lock estimated that about 20 percent of the government market is now using the Microsoft product. SharePoint 2010 recently received approval for use across the Defense Department.

Who's Fed 100-worthy?

Nominations are now open for the 2015 Federal 100 awards. Get the details and submit your picks!

Featured

Reader comments

Mon, Aug 23, 2010 Ethan New York

...About big releases being a recipe for failure: I would agree that big rollouts are much riskier, and all of the Fortune 500 companies I work with do "soft" launches -- essentially making the tool public but not telling anyone. I did read a good article that supported big rollouts: that article's point was that for collaboration to really take off and be successful, you need lots of users. A mini-rollout just doesn't deliver on that. I'd be interested in hearing other points on this. Best, Ethan http://sharepointsupported.com

Mon, Aug 23, 2010 Scott Lock

To the point, it doesn't take a programmer to use SharePoint but it does take a good, strong lead running point. That same Soccer Mom has to make sure that everyone understands the teams goal, what their roles are, and what is important to track. Then that Soccer Mom needs to make sure they have the tools to do that effectively. It's true that SharePoint isn't the only game in town (Google Docs, Google Apps, pick-a-cloud) but the point is that it doesn't HAVE to be the hardest.

Fri, Aug 20, 2010

Even Soccer moms, with no programming experience, do team collaboration sites faster and easier using modern web tools available on the Internet.

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above