It was Sharepoint 2010.
If you have a globe-spanning company with a multitude of business units offering a wide offering of products and services you really need an extremely flexible system -- preferably one that is object-oriented from the ground up using tagging and multiple taxonomies. That is not Sharepoint. The best solution I've seen so far is Adobe (nee Day) CQ5. You can describe an object by tag values with the object connected to branches of more than one taxonomic tree. Try to do that in Sharepoint.
With users using search as their default reserach method (and bearing Pirolli'sapplication of Charnov's Minimal Value Theorem) to how users find information a faceted search system starts to look like a valid option as the main navigation. Again not Sharepoint's strong suite.
Despite MS PR Sharepoint is best used for internal document management. It is not designed to be highly flexible, nimble or freindly. Sharepoint may be OK for an Intranet or simple website. Sharepoint also has a strong positive in the huge number of pre-existing plug-in modules and a sizeable number of developers/partners supporting it. Finally, Sharepoint is natively supportive of a .NET infrastructure which is very popular with enterprise level IT folks.
CQ5 for example is Java-based. It can work in a .NET world but not as a native.
Sharepoint 2010 is not a bad product, but MS and its partners oversell it like crazy for very inappropriate projects. 2010 has also decoupled Sharepoint the engine from thee front end. This allows you to use an alternative publishing system -- either off the shelf or purpose built.
If you need to share content between instances, update content across instances from a central "master" source or need powerful rules-based dynamic web publishing I would say look elsewhere -- that's not Sharepoint's gig.
PLEASE NOTE THESE ARE MY PERSONAL OPINIONS BASED ON MY PERSONAL EXPERIENCE AND NOT NECESSARILY THOSE OF MY EMPLOYER
