This might not help you articulate anything, but maybe you'll enjoy these quotes from the anti-Sharepoint community. Some are quite passionate rants.

This is from notes I pasted together a few years ago when I was faced with instructions from above to "just use Sharepoint" (hahaha) instead of researching other tools. Sorry for the lack of attribution for many of them -- I never expected to share the stuff:

The difference between wikis and sharepoint is that sharepoint sucks. http://discuss.joelonsoftware.com/default.asp?joel.3.66103.7

the SharePoint Wiki sucks. http://sharepoint.nailhead.net/2008/04/sharepoint-community-kit-wiki-or.html

This product sucks. Seriously. It is the most uninnovative product ever to come out of the muckhole the is Redmond.

The Sharepoint Wiki is an abomination.

This wiki implementation is most likely the worst ever released as a commercial product.

All in all if there is one thing I can say for sharepoint's wiki implementation it is a very sorry excuse for anything trying to resemble a wiki. http://www.pseale.com/blog/SharePointWikisAreAwesomeISwear.aspx

the Sharepoint Wiki is horrible. I'd go so far as to say it's about the most un-wiki-like wiki I've ever had the horror of working with. http://stackoverflow.com/questions/116012/what-is-the-best-aspnetmssql-based-wiki

Sharepoint's wiki functionality is bad enough that it actively harms progress. It is literally a leg dragging in the water behind the canoe, making everyone work harder. The best description I've heard of Sharepoint is that it's like a developer with ADD was working on it. Yeah, he has great ideas and makes a good start but before he finishes the feature -- OOOH, A PUPPY! Now wait, where was I? Right, working on a new feature. And then another puppy comes along. People have spent a lot of money on this product but really have little to show for it. When people say "Sharepoint has made Microsoft a billion bucks!" all I have to say is "Yeah, and that Enzyte guy made a lot of money, too, but his male enhancement products are still a scam." http://sharepoint.microsoft.com/blogs/lliu/Lists/Posts/Post.aspx?ID=2

I tend to agree that Sharepoint sucks. Using it is like closing your eyes, holding your breath and spinning around for thirty seconds. When your done you dont know where you are, you are very dizzy, and feel like you might throw up… I might create something in one place, but cant delete it or rename it there. After 15 minutes of searching, I cant find the same tool I used yesterday to do one thing or another. Its like that house in 13 Ghosts, everything SEEMS to move around on you… What really bothers me is this is not version one. It is a great idea gone horribly implemented.

…STAY AWAY… Sharepoint can be an incredibly useful tool, but in any office where I’ve seen it deployed, it’s acting merely as a web-based front-end to the file-system. If that’s all you’re going to be using it for, you might as well just use the file-system, via Explorer and mapped drives, and do away with the glorified front end.

…I hate Sharepoint with the passion of 10,000 burning Lotus Notes users

… Honestly, I found Sharepoint so inadequate and typical of a first generation MS product that I could only shake my head at it. If it was made by anyone else than MS and had to compete on its merits I suspect most of us would have never even heard of it

I’m a software developer (ASP.NET primarily), and the company I work for is going goofy over Sharepoint. But I knew I couldn’t be the only one who thought the interface was too cumbersome. It takes me several minutes of mucking around in non-intuitive menu structures to find things. It violates just about everything I ever learned about creating clean, easy-to-use web interfaces.

http://nkilkenny.wordpress.com/category/collaboration-tools/sharepoint/

a) I do sharepoint for a living. Somebody either shoot me or offer me another programming job in Boston. b) I'm about to do Sharepoint for a living. Fuck. <bang>

I love how every feature in Sharepoint is absolutely terrible, yet the whole package somehow always makes businesspeople moist.

I'm just saying that any stand-alone implementation of anything in Sharepoint is going to be worlds better. Sharepoint tries to be everything to everybody all at once. It's like a Swiss army knife, where no one tool is really as good as the dedicated version of a knife or a file... but you get them all in one place.

I just went to a 2 day conference on "Intranets & The Public Sector". 75% of people there were using Sharepoint for their intranets. It blows and sucks at the same time, but the business world loves Microsoft. http://www.reddit.com/r/programming/comments/78h7d/yet_one_more_reason_why_sharepoint_development/

Me being the lucky one in my small little group of the global orginization gets to update the part of the wiki for our business unit, and guess what... Sharepoint sucks hairy donkey balls! You are wondering why? - No linking to anchors in a document - No table of contents generation - No deadlink checking - No way to create a link back to the refering document - No way to import existing pages - No way to export pages - All inline CSS code is blown up as much as possible - Produced HTML code is deprecated

"The Community Kit for SharePoint is a set of best practices, templates, Web Parts, tools, and source code that enables practically anyone to create a community website based on SharePoint technology for practically any group of people with a common interest." http://www.codeplex.com/CKS

PointCross Releases Catalyst for Building Business-Ready SharePoint Solutions in 1/10th the Time http://money.aol.com/news/articles/_a/bbdp/pointcross-releases-catalyst-for/244437?referer=sphere_related_content

(What the fuck good is a "toolset" like SharePoint anyway, if it requires another company to create another "toolset" on top of it to help you build a useful appplication? The whole MS development industry often seems like a big job security circle-jerk for Aspy architecture astronauts who couldn't care less about creating something usable by other humans. All the obtuse, self-referential MSDN documentation reads like techy postmodern literary criticism predicated on the reader already being an expert in every relevant subtopic.)

Why is there even such a thing as a "Sharepoint developer?" Why do so many of these developers spend hundreds of hours trying to wrestle this alleged fantastic "collaboration and productivity" tool into being able to accomplish anything useful? Why are there dozens of weblogs full of incredibly byzantine "Sharepoint developer" tips and tricks and book excerpts trying to explain how to make it do the most rudimentary things? Why are these people spending their professional lives trying to make a silk purse out of a sow's ear? Have they never even used another team collaboration application? I can log into Basecamp or PBwiki (or Intervals or Commonspot or SocialText or...) and immediately be collaborative and productive.

I suspect that applications like Sharepoint and many of Microsoft's various "vaguely-defined server" products are simply facades, tools to prop up the job security of the leagues of MS developers who continue to push the never-ending implementation of such products despite the dismal track record of success.