There's been a lot of anti-SharePoint buzz in the Enterprise 2.0 blogosphere as of late. Most of the negativity is based on the fact that MOSS 2007 is seriously lacking with respect to social computing features. Not even Microsoft debates that point anymore. The following is an excerpt from a blog post by Oscar Berg of The Content Economy that summarizes this position very well:

"SharePoint / MOSS 2007 is designed for the (Windows) desktop and for collaborating on office documents inside the corporate firewalls. It is not designed for collaboration in broader terms - not even for simple file sharing if it goes across corporate firewalls. Furthermore, it is not designed for the web, it has only rudimentary Web 2.0 features and tools (such as blogs and wikis), it is not built with Web 2.0 technologies, and it lacks core Web 2.0 qualities such as ease-of-use. Despite all this, SharePoint is platform with a lot of capabilities which can be extended and leveraged through customization, third-party tools and complementary products and services. The key problem is just that many of the companies that have bought SharePoint 2007 believe they got more than just the basic capabilities out-of-the-box. They might not be ready for additional investments. This will most likely hold back the value they can get from their original investment in SharePoint."

Oscar's position should not come as a surprise any of us who are familiar with both Enterprise 2.0 and MOSS 2007. Here are my thoughts:

• MOSS 2007 is not a good choice for an Enterprise 2.0 platform. It is a good choice in meeting much broader collaboration and content management requirements. So if you're looking for the latter, either accept SharePoint as a weak Enterprise 2.0 platform or plan to augment SharePoint with best-of-breed Enterprise 2.0 add-ins and tools.


• The Enterprise 2.0 features in MOSS 2007 (i.e. blogs, wikis, profiles, etc.) they are infinitely more than what a lot of enterprises have today. Therefore, MOSS 2007 may still represent an important step in the right direction toward Enterprise 2.0.


• Enterprise 2.0 is really more about a cultural shift in the way we do work than it is about implementing a specific set of technologies. This cultural shift is necessary regardless of the technologies we implement. Based on the maturity level of most companies, SharePoint may adequately support their Enterprise 2.0 cultural shift.


• While MOSS 2007 is a weak Enterprise 2.0 platform, I hold out hope that future versions of MOSS improve significantly. While I don't expect MOSS 14 to be perfect, I do expect that it will meet our Enterprise 2.0 requirements for the next few years.


• Although my preference is to use MOSS 2007 out-of-the-box, there are times when 3rd-party add-ins make sense. The MOSS wiki, for example, is particularly bad. The Kwizcom WikiPlus add-in is a good example of what Microsoft partners are doing to take advantage of MOSS's current shortcomings.

Are you concerned about MOSS 2007's social computing limitations? Or do you agree with me that it is good enough for where most of us are at right now?

Gartner predicts that by 2012, 20% of the commercial email market will shift from premise-based to Software-as-a-Service (SaaS). This is up from only 1% in 2007. Of course, email is only the beginning. Instant messaging/ presence, team workspace, productivity tools, and more are starting to be offered as SaaS from the likes of IBM, Microsoft, Google, and others. If you talk to the vendors, they're ready for you today. They have invested hundreds of millions of dollars into new data centers. They have tweaked their software to support an SaaS model. And, they are actively recruiting customers to make the switch from on premise to SaaS. Are you ready to go? How will you know when the timing is right?

While I am convinced that SaaS is real trend that will eventually pay-off. I'm not convinced that it is right for everyone, not yet. Beyond the hype, each SaaS opportunity must be evaluated on its ability to reduce long-term expense while sustaining quality and compliance. Every company must define what quality and compliance is for them. SaaS is not fully prepared to meet everyone's definition of quality and compliance for a price that is less that what they are paying today.

Here are five actions we can begin now to help us prepare for SaaS in the future:

1. Transition to "Out-of-the-Box" - The reason that SaaS vendors can offer communciation and collaboration services at a lower cost than many premise-based solutions is that they can recognize massive scalability. This can only be accomplished through shared, multi-tenent infrastructures. It also assumes that all of these tenents are using the same "out-of-the-box" software. If you have customized your on premise solutions to meet your company's special business requirements, it will be difficult to upgrade, let alone migrate to SaaS. Make "out-of-the-box" a design principle going forward. It may require altering some business processes. However, it will ultimately position your company for future cost-cutting options such as SaaS.


2. Know your cost - It is impossible to know whether SaaS provides value unless you understand your current cost structure. SaaS vendors can assist you in developing a Total Cost of Ownership (TCO) model that incorporates all of your platforms costs. Remember, that acquisition and implementation are usually a fraction of the cost of ongoing support and maintenance. As you track your costs against that of SaaS, you will be able to forecast the point at which SaaS may be viable, from a cost perspective. However, cost is only part of the consideration.
   
3. Understand Your Requirements - Besides cost, you must know what requirements must be met to consider SaaS viable. Here are some questions you should ask: How will you integrate your applications? Do you need encryption? Do you need directory/security integration? How will you manage single sign-on? Do you have legal hold and discovery requirements? Do you have records retention requirements? What are your message hygiene requirements? Do you have special regulatory requirements? Are you able to use a shared infrastructure? How will you manage storage limits? What are your service level requirements? How will the support structure work? How will you coexist between on-premise and SaaS solutions? There are probably many more. Devote plenty of time to understanding the minimum requirements that SaaS must deliver to be viable.
   
4. Monitor the Marketplace - The SaaS vendors will provide you with an impressive list of customers already using their services. However, you will quickly notice that there are few if any government agencies or financial services firms represented. Most of the large early adopters have been from the manufacturing industry, which is often early at realizing cost benefits. Manufacturing is also less regulated than government and finance. Keep a close eye on the marketplace and when you start to notice the regulated industries jumping aboard it will signal that SaaS vendors have reached an appropriate level of maturity for most industries.
   
5. Start a Small Pilot - The best way to start to experience the benefits and drawbacks of SaaS is to start using it. Ideally you could identify a small number of people who could switch completely to a SaaS-based solution. However, there are some potential challenges for these people. For example, will they be able to access your corporate directory? Will they be able to do a free-time search? Will they be able to IM people on the on-premise platform? If the pilot people are separated too much from everyone else, they will not be able to effective evaluate it. The lessons learned around coexistance will be directly applicable to your future rollout. Coexistance may even be your long-term strategy if you opt for a hybrid approach where some users connect to premise-based services and others to SaaS solutions. You may need to do a small pilot every year to get a sense for how SaaS is evolving to meet your needs.

Although we're starting to see some companies make the leap to SaaS, it is still relatively immature. By following the guidelines above, you will be better positioned for making the SaaS decision when it truly benefits your company. For some of you, that could be many years from now.

Are you considering SaaS? What have you done to start preparing?

Recently, I started keeping track of my personal collaboration rules. Although I hadn't written them down previously, these are principles that I try to live by. This list is probably not inclusive of all the rules I subconsciously and consciously live by as I try to be good collaboration citizen. However, they are the ones that came to mind:

1. Capture once - There's nothing more wasteful than capturing the same information multiple times. Copy and paste makes that easy within the electronic world. However, what about when you're in a meeting and collaborating on a whiteboard or flip chart? Someone has to recapture that content electronically. This is wasteful. What about taking meeting notes on a paper notebook prior to distributing them electronically? This wastes time too. While there are some situations when you have to capture information more than once, you can eliminate most of them by making some minor changes to the way you work. Instead of using a physical whiteboard in a meeting, use an electronic tool on a laptop that can be projected. Or ask everyone to bring a laptop to the meeting and collaborate over a web conference, even though everyone is in the same physical conference room. Instead of carrying around a paper notebook, take your laptop to your meetings. Store meeting minutes and other sharable content in a blog or wiki, and then email the link.


2. Process once - How many times have I looked at an email just to defer action a little longer. Each time I have to reread it, I'm wasting time. If an e-mail requires action, and you do not have time to complete it immediately, copy the e-mail to a calendar entry, and schedule an appropriate amount of time in the future. Include some brief notes at the top of the calendar entry to quickly remind you of exactly what is needed, so that you don't have to reread the entire email.


3. Resist printing - Okay, we all know that printing kills trees. Paper documents tend to accumulate, take up space, and increase the amount of refuse for which we're responsible. Paper cannot be easily secured. It can fall into the wrong hands. There is no log to know who else may have seen the paper. There are really very few instances when printing to paper is a good idea. Resist printing an agenda or other meeting materials that end up in the trash within minutes of being created. Ask yourself whether this document, if printed, will remain useful and relevent for more than a week. If the answer is no, then figure out a way to meet your need without printing.


4. Don't use email to collaborate, use it to communicate - Email is a terrible collaboration tool, but an excellent communication tool. When it comes to collaboration, email tends to create more work, and lacks critical context. Take this scenario: We are working as a team to write a proposal. Someone writes a first draft and emails it to the rest of the team. Each member of the team marks up their copy and emails it back to the original sender. That person is now responsible for integrating the individual input from each person on the team. This is inefficient on multiple levels. Obviously it is for the person who compiling the feedback. However, it is also inefficient for the other people who are providing feedback without knowing how their team members are responding. It's very possible that they are coming to the same or similar conclusions. It is much more effective and efficient to work as a team on a single, shared copy of the content. Wikis are perfect for this use case. So, next time your about to send an email, ask yourself whether this is a simple, isolated commnication, or a collaborative effort that would benefit from having a dedicated virtual workspace.


5. Send links, not attachments - Nothing eats up disk space on email servers faster than attachments, especially if you're not sharing a single-copy message store. Think about it, everyone person on the distribution received their own copy of the attachment. What a waste! Instead, store your attachments in a place accessible by others and send a link. An additional benefit is that you can update the document and ensure that anyone who later follows the link from an email is getting the most up-to-date version.


6. Store in a searchable, linkable repository - Unfortunately, most people use email as their personal content store. The problem is that I may have some content that someone else could really use. However, if they don't know me, they will never find it. We simply don't allow other people, especially people we don't know, to search our email. A better approach is to store content that has value to more than just yourself, in a location that is accessible and searchable by others. A good solution for this is the public area of your SharePoint MySite.


7. Be a sharer, not a hoarder - Times are certainly changing. We used to value people because they knew stuff that no one else knew. They were the experts. Now, the more we share, the more we are valued. As we share what we know, others can become co-contributers. This results in a product that is better than any individual could have accomplished on their own.


8. Use real-time communication, instead of email and voice mail, to reduce cycle time - Voice mail and e-mail are slow. It usually takes at least 24 hours to hear back from someone. If you end up going back and forth for several cycles, you could waste days or weeks. Instead, leverage presence to see if the person you need is available right now. If so, use instant messaging, or ask if you can call her on the phone, if that is more appropriate. You can even setup an instant web or audio conference if there are multiple people that need to suddenly work together. Be the one to stop the email/voice mail tag game.

I'm sure there are other rules I'm forgetting. Do you disagree with any on this list? Do you have other rules of your own you would like to share? Let me know.

First there was email, then instant messaging, and now its micro-blogging. The most famous micro-blog, of course, is Twitter. This platform is primarily a messaging service for sending and distributing short (140 character max) to your social network. In Twitter lingo, these short messages are called "Tweets." People subscribe to (or become a "follower" of) the tweet streams that interest them. What started out as a simple and novel application, has turned into a powerful platform.

Wired Magazine's Michael Calore recently wrote about new and creative approaches to exploiting Twitter. He cites examples such as having your washing machine send you a tweet when it completes the wash cycle, controlling light switches from a mobile device, and being alerted when your plants need water.

What could the enterprise application of Twitter or micro-blogging be? Here are some ideas off the top of my head:

• System availability monitoring - Receive information about system availability, performance, and capacity.


• Business process monitoring - Receive process metrics and alerts.


• Project status reporting - Receive notification of changes in project status, issues, and changes.


• Emergency broadcast system - Notify employees of emergencies and provide them with instructions and updates.


• Internal communications - Provide employees with motivation, encouragement, announcements, and brand messaging.

What ideas do you have? Do you know of any companies that are using micro-blogging in the enterprise?

Here is a list of conferences that look interesting to me. I've attended AIIM, Gartner, and Enterprise 2.0 in the past. Right now I'm leaning toward attending Enterprise 2.0 this year. Am I missing any? Let me know.

Given the current economic climate, companies may try to save money by cutting out conferences. While it is certainly prudent to scrutinize requests to attend conferences, it would be a mistake to simply eliminate them all together. Here are five unique benefits of attending live conferences:

1. Assessing the Marketplace - Conferences are an efficient way to learn about industry trends across the breadth of the conference scope. In less than a week you can pick up a good sense of what's hot and where things are heading. Most of us simply don't make the time during our regular jobs to research and think about the breadth of where the marketplace is going.


2. Networking with Attendees - Most companies of similar size share the same struggles. And yet, they are all at different places on the maturity continuum. It's highly likely that you will find other attendees who have successfully solved the problems you're working on right now. Similarly, you may be able to help someone else. It's great to build a list of peers whom you can tap on occasion. Social tools are making it easier than ever to maintain connections after these brief encounters.


3. Interacting with Industry Experts - Only at a conference will you find lots of experts in one place, and willing to share their knowledge for free. Make a list of all the big questions you would like to ask experts at the conference. Attend sessions that align with your questions. Ask your questions in the session, or after the session, if they are not covered in the presentation.


4. Connecting with Vendors & Solutions - Say what you will about vendors at conferences. However, I always walk away having learned about a few companies and offerings of which I was not previously aware. I've been able to solve real problems with solutions I found only as a result of attending a conference.


5. Thinking Creatively - When I'm at work, I'm focused on completing quality deliverables by their deadlines. My creativity increases exponentially when I'm at a conference, away from the normal office distractions, and surrounded by new ideas, new people, and a new environment. I always come away from a conference with pages of new ideas.

Lately, I've been wondering whether the current economic and environmental challenges will make live conference a thing of the past. Have conferencing, social networking, and virtual worlds matured to the point that a virtual conference can deliver the benefits above? I have my doubts.

Having just gone through an RFP for hosted audio and web conferencing, it is obvious there is a gap between what vendors can deliver today and what I would like to see. Here's my wish list:

Integration between on premise and hosted conferencing platforms - At the end of the day, our end-users should not have to decide whether to use the on premise conferencing tool or the hosted conferencing tool. From their perspective, there should either be a single tool or a seamless integration between the on premise and hosted solutions. My vote is for the latter. Of course, we could architect an on premise solution that could meet our peak utilization requirements. However, that would result in too much unused capacity. Alternatively, we could switch to a 100% hosted conferencing model. However, that would cost a lot and may not integrate well with our other unified communication and collaboration platforms. That's why my preference would be for a hybrid approach that leverages the best of on premise and hosted conferencing solutions. The on premise solution would handle "normal" meetings, and the hosted solution would handle large meetings, or those with special requirements. The problem is that I still want it to be seamless for the end-user. I don't want them to have to decide when to use on-premise versus hosted conferencing. In a perfect world, a unified interface would allow me to schedule a meeting, and based upon the size of the meeting and other factors, the system would know whether it should be scheduled on premise or "outsourced" to the hosted platform. Unfortunately, today's on premise solutions do not know anything about the existence of a hosted solution, and visa versa. Surprisingly, even vendors that sell both on premise and hosted solutions, such as IBM and Microsoft, do not offer such integration today.

Integration between conferencing platforms and SIP-based presence - Conferencing platforms are a critical piece of the Unified Communication and Collaboration puzzle. Nonetheless, many vendors still position their conferencing platforms as stand-alone applications. For example, conferencing platforms do not currently have the ability to exchange SIP-based presence information in a federated model. My real-time communicator client should tell me when someone may not be available because they are attending a conference. I should not have to rely upon the person to remember to change their status. Additionally, I should be able to see a person's presence information within a web conference meeting room.

True VoIP integration - Most web conferencing solutions require that you simultaneously employ a separate audio conferencing solution. In many cases the vendors have made this interaction relatively seamless. However, there is still a dependency up a separate, and in virtually all cases, analog audio conferencing system. The separation between the web and audio components complicates authentication, recording, and reporting. Additionally, it results in having to pay a carrier on a per-minute basis for usage. Some day, in the not too distant future, I would hope to be able to leverage VoIP-based conferencing across the internal IP-network or the Internet. Sure I know that several web conferencing platforms support some number of VoIP sessions natively. However, nowhere near the capacity necessary to meet an enterprise's audio conferencing needs. I would also like to see a much tighter integration between audio and web conferencing, to the point that we no longer feel a need to distinguish the two, and just call it "conferencing."

What's at the top of your list? Do you know of any solutions out there that can already realize my wishes?