Tag Archives: adoption

My Users Don’t Like SharePoint Because it’s a Complete Mess

This is Part 2 of my series on ‘My Users Don’t Like SharePoint…’

Let’s take the Ford Mustang metaphor from the opening post. I get my 2013 Mustang, and it’s shiny and beautiful.

Credit Ford.com

I then welcome my three children into it, and let them have their way. We go to McDonald’s, they get Happy Meals. I assume they know not to make a mess, so I leave them in my new car as I run into the store (no I don’t really, that’s not safe, but for the sake of the example). I come back a little later and much to my surprise, my car is a mess! French fries on the floor, wedged between the leather seats, ketchup smeared on the windows, salty finger prints on my dash and stereo, chocolate milk in the carpet, apple juice splashed on the ceiling… a complete mess.

Credit City-Data.com

I’m too busy to clean it out, I have other projects around the house I need to take care of. A week goes by, things really settle in, a nice odor forms and now no one wants to drive in my new Mustang, even the kids who made the mess! Should I call up Ford and scream at them, tweet hatred and complain about their sucky car?

If this rings a bell for you and your SharePoint implementation, there’s still hope. Depending on how long the milk was soaking in the carpet, you may have some heavy cleaning to do, but it’s possible! This by far is one of the most common issues I’ve come across.

Define a plan.

First thing you’ll want to do is reorganize things virtually, make a plan. Ignore what SharePoint is doing now and layout the perfect environment. Using Excel or your app of preference, layout the ideal topology: sites and sub sites, libraries, folders and files. Include metadata, if you’re using it, permission and navigation considerations. Define what the perfect world will look like. Who has access to what, where, and how much access should they have?

Here’s a basic example. Starting with something like this can help get the wheels spinning.

Once buckets are defined, people can select where things should go. You’ll see Secure sites in there. These are the private department specific work spaces and the goal there is to farm out what the secure site would look like to that department. Provide them this basic template and have them define what they want to see.


Governance, the art of governing what your users can do, might be a scary word, and is by far the largest challenge with information management (regardless of SharePoint, governance is an issue across the board, more on Joel Oleson’s blog), but it’s critical for a successful SharePoint deployment.

Taking the same document we had above, let’s add a few more columns to include basic governance. Who can access what bucket:

Pretty straight forward. There are many methods of defining governance and taxonomy, I find starting in Excel is fastest and easiest.

Microsoft’s site has a lot more on governance: http://technet.microsoft.com/en-us/sharepoint/ff800826.aspx. Go ahead and search for ‘sharepoint governance‘ and you’ll find some great articles by others.

Still not convinced governance is necessary? Check out my other post on governance.

It’s okay to have a growing document defining your governance. Clearly defining your buckets is a great first step, but applying permissions to each bucket and site will help keep sites clean. Once you have a clear, or clearer, plan on your permissions, execute it!

Clean up, clean up, everybody clean up!


Go-Slow-Horn-Caution-Sign-S-1962Pull in a few key players to assist. Giving them ownership of their own data will reduce your load as well as give more users buy-in (aka user adoption). Use the plan you defined and slowly begin to move data around, reformatting sites and libraries. SLOWLY.

Don’t spend a weekend and bust it all out. Monday will be chaotic as your users panic, scouring through your nice new layout cursing SharePoint.  Go slow, let everyone know what you’re doing. Get your users involved in cleaning up their sites and libraries. Assign owners to reorganizing their sites and libraries.

Consider a 3rd party tool like ControlPoint from Axceler (why?) . Their solution makes moving entire lists and libraries a snap. There are other solutions out there, I’ve only used (and subsequently fallen in love with) ControlPoint.

As you clean up, it is now:

Time to govern.

SharePoint is a large application, it can do a whole lot, real easy. As a result, some SharePoint implementations suffer from having too many people mucking around with too many features (remember letting my kids run wild in my Mustang? A complete mess.). I have seen implementations where whenever a user felt like it, a new list was born, a new library created, sub sites abound, pages were rearranged with new web parts and views on a whim. It can become a collective junk drawer. This drove the end users, the consumers of the information, NUTS. Everything is everywhere and is hard to find and manage.

In your document, you began to define groups and their level of permission to sites, libraries and lists. Begin to apply those changes as you’re building it out. For starters, change permissions on the HR site so all users have read only access. That will immediately stop a bulk of your users from messing with your changes as you go. When you create or manage libraries, update permissions accordingly.

Make sure to review the previously mentioned Microsoft site for more on governance. Do it right, the first time, it’s worth every little bit of effort.

You can always have some fun (the only way us IT people know how).

Clean out the site owners group and site collection administrators list, leaving yourself of course. See who screams “I can’t create another list!”. That’ll help you identify who’s making the mess and give you a start to discuss and help guide them in doing it right (per your governance).

If you hit a library that you’re unsure about, I’d bet that has become the junk drawer. See who cares it’s missing by removing all permissions (except your own of course). I’ve done this a few times, and those libraries will site dormant for 6-9 months until the customer says, “fine, we don’t need it, trash it”.

Til next week, Happy SharePointing!


My Users Don’t Like SharePoint…New Series!

SharePoint gets such a bad rap.

I’ve been collecting thoughts, tweets and blog posts complaining about SharePoint, and I’ve discovered a common theme, or themes: Haters gonna hate; legitimate bugs or issues; and poor implementations. I want to tackle the one item I feel like we can actually do something about, poor implementations.

Before I dive into what I’ve found, let me say this first: SharePoint is a platform, a framework, a foundation. Like a blank canvas awaiting an artist’s creativity, SharePoint can be implemented like a two year old using finger paints or by a master who has years of artistry expertise. And this is where the haters scream the most. You wouldn’t implement a new ECM, CRM or ERP without proper training and understanding what it can do and how you can customize it if necessary. Why do we think SharePoint can be implemented without knowing anything about it? I know Microsoft has done their share of pushing it into corporations, and actually selling it as ‘easy’…  Gah, it’s frustrating…

Would someone take finger paints and try to paint something like:

Three Gables by Joyce Wood

‘Three Gables’ by JoyceWood.com

I wouldn’t. I would learn to paint, spend years understanding colors and techniques. My mother is an artist (a great one I think, check out her stuff here ;), and for me to sit down, for the first time, and expect to pump out art like she does is ridiculous, down right crazy.

As silly as that may be, this is happening all around the world within companies using SharePoint. SharePoint needs to be understood and applied correctly, and then, with knowledge and insight can it be formed into something beautiful. I’m not talking just branding and design, I mean the overall business architecture and information management within SharePoint.

One more analogy…

Credit Ford.com

Think of the amazing Ford Mustang. Beautiful car, classic American muscle. This car fresh out of the factory is near perfection. It’ll move, and move real fast. It’s slick, sleek, sexy, and powerful. Like SharePoint, if the car isn’t taken care of, it can become a terrible waste of money that no one even wants to drive.

What would happen if you took this great car, and never gave it an oil change? It’s not the car’s fault it won’t run, it wasn’t taken care of, it wasn’t properly maintained. What if I put oil in the gas tank? Ouch! SharePoint is a lot like the Mustang. It’s an amazing piece of software, a powerful platform, but if it’s not implemented correctly it won’t run properly and everyone gets mad.

Enough on my rant. You already have SharePoint, and your users don’t like it. However it was implemented, by who and when, it needs help. Don’t play the blame game, let’s fix it! I believe you have earnestly done your best in trying to make it a good solution, but without training or knowing what you don’t know, it’s difficult.

I will attempt to extract the common issues I’ve seen and heard, and see if we can’t improve our SharePoint implementations together. I am targeting administrative and end user frustrations. Are you a developer? Sorry, I won’t be going into great developer detail herebut I think the series can still apply. Check out my other post on keeping a love hate relationship with SharePoint. Developer headaches in SharePoint abound.

Here’s what to expect. My users don’t like SharePoint because:

This series will tackle the above statements, guiding and exploring what can be done to fix it. And finally we discuss collecting feedback, be proactive instead of reactive.

Don’t see your pain points above? Am I missing something? If you think there’s another good reason users don’t like SharePoint, leave me a comment below and I’ll check it out. I will gladly adjust my list and provide as much help as I can!

Til next week, happy SharePointing!