SharePoint does’t suck. You suck! Getting past the SharePoint stigma, 5 tips!

One of the greatest points made during a presentation was a simple and succinct point:

SharePoint doesn’t suck. You suck!

Thanks Dux for that quote.

Captain America says SharePoint does not suck

The reason that is such a good point is that SharePoint is not the reason for your troubles, it is not the reason you have challenges.  The reason is solely on the Administration and team who built, manage, deliver, and support SharePoint.  Sorry guys and gals, but you are now under the bus.

Passing blame will solve nothing, so get over that quickly we need to get our users back on board, and get some wins in the SharePoint column. So let’s talk tips to getting them back.

Tip 1: Learn what the business thinks of SharePoint

Identify what your users really don’t like, or have challenges with.  Rumors, and complaints don’t cut it.  Do analysis and research, and document this.  You will need this ammo for your strategy, and you will need this to get funding and buy in from the person with the money.

Don’t promise anything during this discovery, you will just get yourself in more trouble later, if you don’t deliver.  This does give your users a sense you are trying to make change, make things better, give them HOPE!

Tip 2: Miscommunicating SharePoint

Quit using SharePoint to CYA!  I cannot count the times I have heard a Support Tech or and Administrator say the reason something does not work is simply “SharePoint”.  That is like saying guns hurt people, really, I have never seen a gun jump off the table and hurt a person.  It does take an act to make the pain, so don’t perpetuate the stigma of “SharePoint did it!”  Remember my first point, it was likely deployed, designed, or built to perform a task.

Now I am not saying you did it.  Remember a company is a living creature, it grows, and changes.  Thus a solution you created for one person or team 3 months ago could be antiquated or just plain wrong for the business now.  SharePoint needs to evolve with your org.

Tip 3: Communicate what SharePoint can do!

Come to the table.  In many cases the stigma the business has is actually completely wrong.  SharePoint can do it, and even Out of Box sometimes.  So sit with your users and see what they are doing with SharePoint.  I am amazed at how often administrators deploy and forget a Team Site.  Take the time to go back, set a few hours a week to meet with teams using SharePoint, and offer tips, training, suggestions, support in a face to face environment.  Many times this defuses the issues, and gives them a face and context to the challenges they experience.

Tip 4: SharePoint Discussion Boards!

Give your users a outlet! By providing a Discussion Board, or Forum that your support team can moderate, you get two things.  First your users can socialize the challenges, giving you and the community a way to answer issues “visibly”, not in a support queue silo.  How many times do people ask the same question?

Second the Discussion topics, give you information for your SharePoint Knowledge Base or Wiki.  Take those gems of information and communication and create a way for folks to look up answers.  I even like to let Product Champions and lead create entries, they are the troops in the field.

Your users will see this as a method to grow the tool, and a Jedi Mind trick to get them to use the tool and collaborate.

Tip 5: SharePoint Branding and Naming!

In many cases the name of SharePoint is burned or forbidden in your company. So re-brand.  Common if Chrysler can do it, you can.  If Coke can come back from New Coke, so can you.  Many times a branding effort that you use with your products can be applied to SharePoint.  Giving it a new look that matches the companies styling.  A catchy name like:

The Portal, My Company, The Communities

Simple I know, but it works.  Look at my post about SharePoint Adoption for other tips.

Extra tip: Hire an outside consultant

Sounds like a job pitch, but seriously.  In many cases the users in the organization see you or IT as the bad guys.  So going in you are already fighting an uphill battle.  By bringing in a outsider, you can defuse that issue right away.  They don’t have the history or the bias as an employee.  Nothing like Fresh Eyes on a Problem!


Keep in mind that in many cases the Stigma of SharePoint is cultural or based on a past experience you will have to overcome.  So you have two real options.  Try and change the mind of your users, or try and convert them.  Pick which camp you want to be in and embrace it.  Plan for a long trip as getting over any Application or Solution stigma can be as long as waiting for the users to retire and be replaced.  Just remember that when someone in the halls ask you:

Why does SharePoint Suck?”   Respond in your head “SharePoint doesn’t suck. You suck!


10 Replies to “SharePoint does’t suck. You suck! Getting past the SharePoint stigma, 5 tips!”

  1. I am trying to transit from Lotus Notes world to Sharepoint world. I am experienced LN developer. And… I feel that I constantly hit wall with my head trying to work with Sharepoint. When I was starting Notes development in ’96 I got one book from official LN course, one month to get familiar with it and I WAS able to deliver applications. For now – after about one month I am not able to obtain basic functionality like editable columns available for specific persons. In Sharepoint world you have to use 4 enviromnents – browser, Sharepoint Designer, Visual Studio and PowerShell. In Lotus you use ONE, just one designer for everything.

  2. Are any of you guys actual developers? I’m here to tell you, SharePoint sucks. Sorry, it sucks. I’ve heard this “it isn’t SharePoint’s fault, it’s the administrator’s fault or it’s the install or…” bit 100 times, and it’s lame. If SharePoint was worth a poop, it wouldn’t be so difficult and rare to find a magical combination of install and administration that would make SharePoint the genius software you’re insisting it is. There seems to be blog after blog after blog apologizing for SharePoint, and they all basically blame the user for trying to use SharePoint beyond its capabilities. That’s ridiculous. As long as you use a piece of software within’ its capabilities, NO software sucks! I mean, look at MS Paint. As long as you don’t want to do anything outside of the capabilities of MS Paint, MS Paint is the IDEAL graphics program! But… for most graphic designers, MS Paint doesn’t cut it. Then again, nobody is complaining about how bad MS Paint sucks because companies aren’t being sold on the idea that MS Paint is some God-sent, be-all-end-all one-stop shop for graphics needs. SharePoint IS being sold that way. It’s a one-stop collaboration tool, and it is mediocre at BEST in everything it does. RARELY does its capabilities actually fulfill a requirement set. People just assume that “SharePoint can do anything,” and when they find out it can’t, rather than hold their advisers accountable, the burden gets placed on US developers to make a square peg fit into a round hole. And, not only does SharePoint consistently NOT deliver a comprehensive solution to a requirement set, it doesn’t even appropriately accomplish what it’s supposed to be able to do most of the time!!! I constantly get error after error when trying to accomplish simple tasks, I get inconsistent results, unintended consequences… design manipulation is FAR more difficult than it needs to be, and file manipulation is ridiculous!

    Albert Einstein always said, “Insanity is when you repetitively do the same task and expect different results.” Well obviously, Mr. Einstein has never worked with SharePoint.

    1. Very interesting point of view. I wanted to include this persons comment as this is a great example of the different points of view related to SharePoint. I am not going to debate a comment, but do appreciate your point of view…..I would like to say that if it was not such a great platform would it be a billion dollar solution…no, it is it critical to point out something you said. Requirement Set…I agree that if SharePoint is oversold, or is sold as a “can do everything” it will fail you. No software is limitless, you need to consider that when you start bending, extending, and doing things no others have tried this is called Experimental. The person who sells it to you saying it can do everything is absolutely telling a half truth….IT CAN with a COST. That is the part most people leave out. It requires alot of talented folks to achieve some requirements, and that pool of folks is very small.

      Thanks again for this comment. Well worth the discussion.

    2. I am afraid I have an opposite point of view! It depends how good you know SharePoint and if you use SharePoint properly and develop different pieces and components with ‘SharePoint’ mentality, you will never ever get any random error! I’ve been developing with SharePoint since 2003 and been working with SharePoint since 2001 and saying this based on my personal experience!

  3. Pingback: URL

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s