8 Reasons why SharePoint is Bad for Your Business

SharePoint has received a lot of hype recently, and it seems that everyone is jumping on the collaboration bandwagon. I say you’re all bonkers, so I’ve decided to put together a list of reasons why SharePoint will really hurt your business.

1. If it worked in ‘98, it should work today

Come on, learning new stuff all the time takes a massive amount of effort. Training people to work in a different way costs money.

Why not just get to know the existing technologies instead? ASP is a great idea. CGI hasn’t lost its touch. Stop forcing progress on everyone.

2. Why would you need yet another way of sharing content?

There’s Flickr, YouTube, SlideShare, FaceBook, and I’m sure there’s at least one or two more. I don’t need yet another place to store or share my documents.

All the talk about storing content in-house is fine until your house burns down and you loose all your data, and from what I’ve heard, backing up a SharePoint server is really difficult for someone who has never done it before.

Besides, I know how to share a document on the file server. Leave me alone!

3. Efficiency leads to job loss

If everything was automatic we wouldn’t have any jobs. Having more efficient business processes leads to layoffs and that is a bad thing for people in these troubled economic times.

Take one for your country and print one copy of this page to everyone in your organization. Then, send said copies by postal mail to all the employees. You’ll keep the paper industry, the postal service, and a lot of stamp designers happy and in business.

4. No built-in support for real-time movie sharing

There’s no way you can hook your camera into SharePoint and have it stream whatever you like onto people’s browsers. I mean, if you want to invest in collaborative technologies, the least one should expect is to be able to send live images to however you want. At any time. Preferably even if their browsers are closed.

SharePoint can’t do that. Feature lacking just doesn’t cover it.

5. Extensibility? Bah, extend this!

Why would you want to extend a bad product? That only means you get more of the bad product, right? And if SharePoint was so great it should solve all your problems, so why would you even need extensibility?

I say: Give me a solution that can solve or my problems out-of-the-box, or give me nothing.

6. SharePoint isn’t open source

If you can’t see what goes on under the hood, how can you be expected to know what will happen? I don’t care if you can reflect the files and see that way, because that means you have to install a program to see the source code.

Can you imagine the disaster that would happen if there was a bug in SharePoint? The whole economy would collapse. You just can’t trust a piece of software you haven’t written yourself.

7. SharePoint consultants are expensive!

You can hire three self-taught PHP developers for the price of one really good SharePoint developer. Three times the number of people means three times more work done, right? You should measure employees by quantity, not quality, especially when you consider item 3 in this list.

Keep more people in jobs and go with a legacy system requiring more maintenance.

8. SharePoint requires your organization to have a plan

I have installed SharePoint and I didn’t get rich. Sure, now someone tells me I need a purpose, and that I actually have to know which business problems I want SharePoint to solve _before_ I go for SharePoint.

I’m busy, and you are likely too, so worrying about business problems and planning ahead is just too massive an undertaking.

Well, I hope I have set the record straight on how many problems you will have if you want to go down the path of SharePoint.


(In case you don’t realize, this is a sarcastic post. SharePoint is only bad for your business if you approach it the wrong way, have the wrong expectations, or just don’t realize what SharePoint can do. Stop posting ridiculous comments about my heritage; my mother is not a goat)

Found this article valuable? Want to show your appreciation? Here are some options:

a) Click on the banners anywhere on the site to visit my blog's sponsors. They are all hand-picked and are selected based on providing great products and services to the SharePoint community.

b) Donate Bitcoins! I love Bitcoins, and you can donate if you'd like by clicking the button below.

c) Spread the word! Below, you should find links to sharing this article on your favorite social media sites. I'm an attention junkie, so sharing is caring in my book!

Pin It

Published by

Bjørn Furuknap

I previously did SharePoint. These days, I try new things to see where I can find the passion. If you have great ideas, cool projects, or is in general an awesome person, get in touch and we might find out together.

19 thoughts on “8 Reasons why SharePoint is Bad for Your Business”

  1. While I realize that the sarcastic approach was the raison d’être of this post, I would have liked to see some more real SharePoint cons on the list.

    Here’s a few from my own drawer:

    1) SharePoint’s support of non-IE browsers is horrible. Show me just one other CMS which hasn’t got a cross browser-enabled Rich Text Editor

    2) Poor multilanguage support. Variations and language pack doesn’t do the trick

    3) CMS functions below standard – where’s the serverbased imagescaling, the ability to use css-classes or just inline styles, or the one click edit.

    4) Mixing content and structure in the database. Why is that good?

    5) Anyone heard of AJAX?

    6) Accessibility – where’s the option to add keyboard shortcuts, to use valid (or just slightly modern) html.

    7) Support for redirection – try moving a wikipedia page and watch how nicely the old url redirects

    8) Empower the users – let them see the file type extension if they prefer that, let them specify a date and time without using dropdown controls.

    I’m sorry if I’m spoiling the humour – I not just here to rant about SharePoint, and I can surely find lots of good reasons to use the current version. But I do hope that somewhere within the Microsoft SharePoint Team, there are people dedicated to improve the product – I believe there are plenty of things to do.

  2. Gyros:

    I see the validity in some of your concerns. And, unless your name is Andrew Connell, you’ll probably agree that SharePoint as a CMS is… lacking.

    However, SharePoint is not a CMS. Complaining that SharePoint lacks certain CMS features is like saying Toyota Avensis is a bad car because it never won LeMans. Avensis was never built to win LeMans, but is perfectly capable of going around the circuit.

    Show me the CMS that does workflow, BI, Excel-like Services, Office integration, file- and records management, business process management, etc…

    For item 2 in your list, language integration is a developer problem more than a platform problem. Remember that SharePoint is not a product but a platform. MOSS is a product, and may lack in certain areas, but SharePoint as such relies on ASP.NET resource files, even extending resource usage into CAML as well.

    As for item 4, personally I don’t care about how the database is structured. I don’t work with the database, I work with the object model because I believe in the OO concept of hiding details I don’t need to know. You find limitations like when you add massive amounts of metadata in your lists or content types, but that begs the question: Why do you need so much metadata? I’m not saying that’s the only problem, but likely, the times you hit SharePoint limitations because of the database structure you are likely facing a totally different issue, perhaps in the architecture of your solution.

    And yes, SharePoint supports Ajax. No, it doesn’t ship with Ajax, but that’s simply because Microsoft hadn’t released ASP.NET Ajax when SharePoint first shipped. But yes, you could, and might want to, add ajax yourself, just like you can to any other ASP.NET application. Or, check out the SharePoint AJAX toolkit at http://www.codeplex.com/sharepointajax

    To support keyboard shortcuts… Have you tried hitting ALT+/ to open the site settings? Or ALT+I in a list or library to open settings there? Or ALT+N to create a new item? SharePoint relies on ASP.NET to provide the AccessKey for shortcuts. Add them or don’t, it’s up to you. Want to use different shortcuts? I’m certain you’ll find a suitable Ajax solution to fix that for you, so why not just integrate that in your SharePoint solution?

    As for decent HTML, well, after spending the last nine months searching, I have so far only found custom view grouping that forces non-compliant HTML on you, the rest is up to you. If you’re saying that the OOTB HTML is horrible, well, I’ll direct your attention to item 5 in my list and remind you that SharePoint still is not a product. Consider the OOTB site definitions as product demonstrations rather than products.

    I don’t care what it’s being marketed as.

    And if you want your users to be allowed to show file extensions, why not just make them a column or field type that does just that? It shouldn’t take you more than a couple of hours to do so, which is the whole point of the ‘extensible’ part of SharePoint. You, as a developer, is empowered to empower your users.

    I’ll draw a blank on the redirect issue, however, as I haven’t really spend time researching that exact topic.

    So yes, SharePoint Wikis may suck at redirects.

  3. What’s really sad about this is that those with pre-defined opinions probably won’t even read the entire article and if you compare it to some of the other ones out there some of the points are actually reflective of misguided opinions.

    The scary part is that I have heard all of these arguements more or less MORE than once. :S

    Good post though, funny and witty.

  4. this is the most radiculous post I ever seen … you must be working at 5 self taught developers shop creating blogs for unemployed lawyers and real estate agents … learn something about big business before poluting internet with your thoughts

Leave a Reply

Your email address will not be published.