Microsoft Office 2010 vs. Google Docs conversations aren’t just happening in the break room. Microsoft and Google themselves have taken some careful shots at one another over the last few months – the most explicit of which include Google’s claim that Google Docs makes Office 2003 and 2007 better (don’t adopt Office 2010) and Microsoft’s counter blog claiming “that’s not true.”

If Google Docs and Microsoft Office 2010 were as similar as tom-ay-toe and tom-ah-toe, we could simply lean back in our chairs and laugh at this whole thing. Problem is, they’re not. There are still differences between the two’s capabilities. Here’s the skinny:

Google Docs. An innovative, free way to create, edit, and share documents online. The browser-based office suite includes slimmed-down comparisons to Microsoft’s Word, Excel, and PowerPoint – which allow you to do almost every basic operation you need.

The advantages:

The disadvantages:

  • Lacks formatting and template abilities compared to Office 2010
  • Lacks ability to open/save a wide variety of file types
  • Lacks integration with most enterprise IT platforms
  • Still depends heavily on an internet connection

Office 2010. Microsoft’s freshest batch of office tools – Office’s power set (Word, Excel, PowerPoint) plus OneNote, Publisher, Visio, etc. – accompanied by the debut of the online versions of Word, Excel, PowerPoint, and OneNote. Similar to Google Docs, these browser-based versions offer higher quality tools with lower quality collaboration. Their web apps marketing video indicates they’re meant for on-the-fly editing.

The advantages:

  • Scalability of the software – i.e. the ability to perform high-level operations
  • Broad formatting and template ability
  • Integration with Microsoft SharePoint; online 2010 version a la Google Docs
  • Established enterprise reputation

The disadvantages:

  • Software and licensing costs, plain and simple
  • Alleged “forced integration” with other Microsoft products – a claim Microsoft has reversed and applied to Google

Who Wins? That depends. As you can see, Google and Microsoft’s business suites have pros and cons over one another – the most notable of which is Google’s outright victory from a cost perspective. Businesses who don’t need extensive document formatting options may benefit from Google Docs while businesses who use their office suite for high-level operations may not.

One of the more “on the fence” issues here is security. The security of Google’s business suite has been questioned consistently in recent months. Those questions, however, are beginning to taper off as more large public agencies adopt Google Apps for Business as their office platform. Notable recent adoptions include Boise State University, the District of Columbia, the City of Orlando (FL), Kansas, and New Mexico.

The biggest news here occurred this Tuesday, when Google announced Google Apps for Government – an Apps Premier edition that meets the US’ federal security requirements. The new edition received an FISMA-Moderate rating from the National Institute of Standards and Technology (NIST) – meaning it’s authorized to host sensitive (but unclassified) data if stored on servers within the United States.

While Google Docs doesn’t yet have an excellent reputation in terms of security, these recent adoptions indicate they’re gaining ground. The fact that most federal and public agencies are strapped for cash and looking to cheapen technology costs, however, doesn’t allow us to let go of our questions just yet.

That being said, the gap between Google Docs and Microsoft Office still remains – though it’s narrowing by the day.


In our last Cloud post (Cloud Computing Risks and Rewards) we discussed a number of Cloud risks related to security:

These risks don’t “demonize” the cloud – but rather raise some critical questions regarding the protection of company data that’s migrated to cloud servers. The security of the cloud is still a bit (forgive the pun) cloudy to most – and may integrate well with existing security policies, protocols, and infrastructure.

Christofer Hoff – who offers excellent cloud perspective in his blog Rational Survivability -
claims it’s not the nature of cloud computing businesses should be worried about, but rather how companies implement and manage cloud computing.

“We’re struggling less with security technology solutions (as there really are few) but rather with the operational, organizational, and compliance issues that come with this new unchartered (or pooly chartered) territory,” Hoff wrote in his post Security and the Cloud – What Does That Even Mean?

Hoff’s quote pinpoints the simple source of our worries: we’ve developed a standard for IT security and compliance that’s being disrupted by something new. The question now is not whether companies should migrate to the cloud. The question is how our existing security methodologies will translate and apply to cloud computing. Since no industry standard for cloud security compliance has been adopted, organizations must steer their own ships as they sail toward cloud solutions.

Four ways organizations can retain appropriate data security as they implement elements of the cloud:

  1. Policy reviewing. A few thorough reads of your cloud provider’s policy will likely explain the rights they reserve to store and protect your data.
  2. SAS70 and PCI Compliance. As we said in our last post, SAS70 and PCI compliance policies may uncover details that aren’t specified in service agreements. They’re standards for cloud peace of mind.
  3. Choosing a public, private, or virtual private cloud. Public clouds allow secure employee access to company data from any system anywhere. Private clouds are more costly, granting access from company systems or systems within the company’s LAN network, providing greater control over data resources and security. Virtual private clouds use a public cloud infrastructure in a private /semi-private manner, providing more balance between cost efficiency and security.
  4. Leveraging ITIL methodology. ITIL offers a one-size-fits-all starting point for IT methodology. As more business adopt cloud applications, businesses will have opportunities to apply ITIL methodology to a new generation of computing.

1. Click SITE ACTIONS in upper right
2. Click CREATE
3. Click CUSTOM LIST in fourth column
4. Name list and assign attributes
5. Click CREATE

More SharePoint how-to’s on our blog or on our YouTube channel.


ROIs matter most in high-effort, high-impact business decisions. Today, we put SharePoint ROI to the test.

Typically, the ROI from SharePoint depends on how it’s used. As Robert McDowell said in his book In Search of Business Value: “Technology provides no benefits of its own; it is the application of technology to business opportunities that produces ROI.”

There’s always buzz in the BPM world about how great information architecture/content management can drive organizational efficiency. Google’s “Return on Information” (ROI) Whitepaper explains why. Vendors have cited Google’s study to justify out-of-the-box document storage systems, relaying Google’s claim that an average employee spends 16 percent of their week searching for information (compared to Microsoft’s 30% estimate) – and that only one in five searches yields desired results. Companies have flocked to content management solutions to increase efficiency and provide for better project management with version-controlled documents and more organized collaboration. PM solutions like Basecamp have sprouted from this.

SharePoint has shown up as a project management and content management solution. Companies have leveraged SharePoint’s ability to:

  • Manage projects individually using customizable project pages
  • Develop project-specific document libraries with version control
  • Manage tasks/consolidate team collaboration
  • Improve employee productivity
  • Aggregate critical enterprise information
  • Provide fast, easy access to content

While these are legitimate SharePoint benefits, they account for only a fraction of what SharePoint was designed to offer. SharePoint is an enterprise platform. While it can be leveraged as a PM platform, using SharePoint solely for PM isn’t likely to yield the satisfying, long-term ROIs the business is looking for.

The highest SharePoint ROI occurs when the organization realizes SharePoint’s purpose and gradually adopts it as a platform that supports:

  • Content management
  • Process automation
  • Systems integration
  • Custom application development
  • Specific solutions (ex: RFP/Lead Management system for Sales, employee time log system for Accounting)

SharePoint’s options are limitless. The organization can integrate a SharePoint workflow, library, or collaboration portal for just about anything they want.

Today, however, the SharePoint ROI question may not center around how much/how little it will be used. The question is whether to adopt SharePoint or a combination of web-based applications for specific needs – something addressed in Forrester’s assessment of SharePoint 2010 adoption. Quick-fix 2.0 apps are the make-or-break factor here. While SharePoint has evolved over the last decade, it failed to keep up with the enterprise’s leveraging of social computing.

This issue, however, comes back to the original question: why are you using SharePoint? If you’re in the market for an out-of-the-box, quick-fix project management system, then a web-based software-as-a-service (SaaS) that integrates well with collaborative software is a great solution. If you’re looking for something that integrates well with existing systems and provides for better performance measurement over time, you’re clearly batting in a different ballpark. The ways you measure ROI for these two options are different.

We usually expect out-of-the-box, SaaS solutions to have better adoption rates (they look pretty), and therefore a faster ROI. We can measure its success by how much it improves productivity. SharePoint, however, is not a quick fix. In this way, adopting SaaS is like renting an apartment – you get what you need on a monthly basis, but you can’t knock down any walls or add that new patio you’ve been wanting. Adopting SharePoint is like building a custom home – you start off with an empty lot, and design and build the house to fit your wants and needs. And if you get tired of the linoleum floors you put in the kitchen, no problem. It’s your house. Rip ‘em up!

The ROI of SharePoint is up to you.


Method One:

1. Click the drop-down arrow on the document
2. Click CHECK OUT
3. Open document for editing by clicking the drop-down menu
4. Click EDIT IN MICROSOFT WORD
5. Edit document
6. In Word, click the top left menu
7. Under PUBLISH, click CHECK IN
8. Enter latest version comments
9. Click CHECK IN or OK

Method Two:

1. Click document name in SharePoint
2. Select EDIT, click OK
3. In Word, click top left menu
4. Under PUBLISH, click CHECK OUT
5. Edit document
6. Under PUBLISH, click CHECK IN
7. Enter latest version comments
8. Click CHECK IN or OK

You can always correct any mistakes by closing your document and checking in/out from the SharePoint page.

More SharePoint how-to’s on our blog or on our YouTube channel.