Well ... there are lots of considerations that you're not outlining. They include security requirements (who can use the app and how), compliancy requirements (what laws govern it), access requirements (where and how will people be using it), content requirements (what's going to be put on there).

Ultimately, sharepoint is a tool, and your requirements will dictate whether it's the right tool for you.

I've seen sharepoint work in massive distribution without too much ado. Every large system like that has it's share of problems.

As an alternative, check out Documentum.

http://www.emc.com/products/category/subcategory/documentum-platform.htm
Permalink | Report

Sharepoint definitely has its possibilities for Large Enterprise, but as you noted, it does seem to work better for smaller teams/workgroups across that Enterprise, but then those teams have a platform for sharing their work company-wide if they wish (security settings can allow for this or for a team-private site).

The largest consideration is someone to run the particular SP site that knows what they are doing. My employer allows teams and workgroups within to create their own SP sites - but there is little to no management from IT regarding those sites. Some are wonderfully done, others end up a mish-mash. To avoid this, I would recommend some sort of training be available to those who want to start an individual or workgroup SP in your company - even if it is only a quick online tutorial.

In the end, a Sharepoint site is only as useful as the content therein, and that content must be marketed out to the target audience. If you plan on having one site for 50k+ users, the content on it needs to be timely and applicable to the majority of those users and they must be kept aware of the site, or it will lie unused.
Permalink | Report