In an ideal world, architectural principles that optimize long-term, enterprise-wide value would guide IT decisions. And those architectural principles, in turn, would reflect the needs of the business. But years of speaking with clients about their real-life situations have demonstrated the reality of how those decisions are often made. Decision making in a sub-optimal or unbalanced environment requires a bit of extra foresight. Politics is the art of the possible, so in these cases, central IT decides to just let SharePoint in rather than fight it.Collaboration and Content Strategies Blog: Is SharePoint Inevitable for My Organization?
Well an interesting article, but one that shows gain the point why Microsoft has risen to such domination. Opposition to MS technology generally comes from a "architectural principles" concept without looking at the economics. The main point I would make for at the least doing a PoC of MOSS for ANY organisation is simple: Collaboration is a growing business need. In 5 years time most knowledge worker will have some SharePoint experience, how much do you want to spend training when it starts becoming re-training?
Blogged with the Flock Browser