Why SharePoint Professionals Are So Bad

Someone asked on Facebook:

“SharePoint Peeps. (primarily consulting) I have been doing an increasing number of interactions with the trusted SharePoint admin at a variety of customers. Maybe I am just being negative but. I am seeing a disturbing trend of a lack of real “expertise” in this arena. Is this just me, or are you seeing the same thing? Are you out there with these customer SharePoint folks thinking wow these people have it together or are you walking away thinking “who ties these peoples shoelaces for them?” or somewhere in between?”

Here’s my response and rant.

I’m still not sure you’re really serious about your question, but in case you are, as someone who has been actively engaged in the training space of SharePoint for a number of years, including building a university solely dedicated to SharePoint with a bachelor level track in training SP admins, let me just say this in as plain text as possible:

The average SharePoint professional, whether developer or administrator, is so poor at their job that, if their skill levels were applied to other areas, such as hairdressing or fixing your car, you would run away and live like a hippie for the rest of your life.

“Screw the do, I’m walking home”

The fact that SharePoint even functions to some extent is a credit to Microsoft’s development skill, not those who run or build on it. Sure, it has issues with the code base, but it’s a very complex animal and even getting an animal to walk, much less do all the tricks that SharePoint can do, is incredibly difficult.

Sadly, Microsoft took that skill and hid it away in the latest versions so SharePoint hasn’t really evolved. Like a dog, they took SharePoint behind the shed and shot it. They then brought back the skin saying “Look, SharePoint isn’t dead, it has just evolved into this nice rug”. Then they claim that they did this because everyone wants rugs.

Back to your question, keeping up with SharePoint is a full-time job and then some. Paradoxically, that is because SharePoint was never allowed to mature before it was replaced with a new version and the marketing department (including its field operatives, the MVPs) started focusing solely on “the new way to pet Lassie”.

Of course, people need to eat, and as such, they tend to do what their bosses tell them to do. Those bosses are people too, and people have an innate tendency to believe everyone else knows more than they do. As such, when the marketing department says “Everyone needs rugs, we’re now a rug company” then those bosses dutifully tells their employees to start shooting every dog they see.

So, SharePoint admins and devs, who want to eat, start shooting dogs and turning them into rugs, which initially are really poor rugs because nobody has any idea what a dog rug should look like. Developers have to learn tanning, and admins have to turn from caring and nurturing dogs to being interior designers.

However, as they get a bit of experience and start creating beautiful rugs with nice tints of color and practical shapes, Microsoft brings out a new strategy. The trend now is hardwood floors and nobody wants rugs anymore. In fact, it was a really bad idea in the first place.

Now, this happens at such a pace that by the time everyone starts to learn how to shoot dogs and turn them into rugs, there’s a new fad coming. Because it requires extensive investments in learning, usually done at the employee’s private time or at the cost of quality of their work or life, the employees get increasingly de-motivated. “SharePoint is hard” and “SharePoint sucks”, not because it actually is hard or sucks (c’mon, you have to spend a couple of weeks training to get a job; how hard can that be?) but because they’re constantly told to retrain to cater to the latest and greatest flimsical fad.

So, yes, you’re right. SharePoint admins suck. SharePoint developers suck. I’ve even worked closely with those considered the best in the business for years, and you’d be scared shitless at how little many of them actually know outside a laser focused area.

It’s not their fault, though. It is a fundamental flaw in how SharePoint is sold and how Microsoft promotes its strategy, as if SharePoint is indeed the core business of all its users and thus warrants the massive investments in training that it requires.


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

Why I am Leaving SharePoint and Why You Should Consider It Too

It’s no big secret that over the previous months, I’ve done less and less SharePoint related work. That is because I’m leaving SharePoint as a career and I’m here to tell you why.

I’d like to start, however, by saying what are not the reasons I’m leaving SharePoint.

It’s Not About SharePoint

I’ve had heated debates and flame wars with people who say that I’m leaving because SharePoint is such a shoddy product.

SharePoint is a great platform. The way it enables businesses to build solutions to give them advantages quickly is amazing. I’ve seen people build solutions in an hour that has saved businesses days or weeks of work. I’ve seen companies utilize SharePoint to see completely new business areas and make a killing over their competitors. I’ve seen and had clients send me gifts for saving employees and jobs.

So no, SharePoint isn’t a bad platform. It is an awesome platform.

It’s Not About the Community

The SharePoint community is dwindling and has been for years. I’d be tempted to blame it all on Twitter buying up Tweetdeck because after Tweetdeck was nerfed to promote the silly web client, the once vibrant Twitter conversations in the community has gone away.

However, the community still exists. It’s far more fractured now, spanning a range of sites including, but not limited, to Twitter, Faceboook, Yammer, and various web sites and other platforms.

I once wrote that community isn’t defined by technology but by people. The SharePoint people that comprises the community are still there. They’re just a lot harder to find and it’s more difficult to keep up with what’s going on now that there are 10+ newsfeeds to follow.

It Is About the Future

SharePoint is dying, and don’t give me that “it’s not dying, it’s turning into something else” because that’s the same as saying that Michael Jackson isn’t dead, he’s just turned into daisy fertilizer.

Sure, SharePoint is turning into something else, which means that there’s a new way of solving every problem, using a new set of tools, in a completely new game. That’s fine, but it’s not SharePoint anymore.

As a SharePoint professional, you’re asked to relearn everything you know, basically taking your productive skill set back to zero and start building again. You’ve learned plenty of transferable skills, but you can also transfer those skills anywhere you want.

The new paradigm of SharePoint isn’t SharePoint anymore. It’s no longer about using technology creatively to gain a competitive advantage, it is about getting the latest commodity that everyone else has too.

Commodities can never be a competitive advantage.

So ask yourself this: You have a completely blank slate in front of you. Everything you know is wiped clean. You need to spend the next two-three years at building a new skill set.

What is it about the coming paradigm of SharePoint that makes you want to start writing “My new career as a SharePoint something” on that blank slate?

The technology certainly isn’t unique anymore. There are five dozen alternatives to virtually any part of the new SharePoint now, and even Microsoft encourages you to pull in components from varying sources when you want to build something.

Is it brand loyalty? Are you really willing to bet the next years of your future just to remain loyal to a brand that has a decade long track record of changing just as you gain any reasonable amount of proficiency? If so, you’re certifiably insane and you can stop reading right now.

It’s About Fun

The main reason I’m leaving SharePoint, however, is that it’s no longer fun. Part of the challenge of being a SharePoint developer is overcoming adversity and finding creative solutions to problems using an at times limited set of tools in innovative ways.

That was just the first step. What is utterly fascinating with SharePoint is that you can then take those skills and be incredibly valuable almost anywhere you go. Even when you’re charging your clients hundreds of dollars per hour, you still produce more value than that, at least if you know your trade.

So it’s not just a personally interesting challenge, it is a profitable one for all parties involved.

That is no longer going to be the case. SharePoint hasn’t evolved in the areas that matter so after many years, I’ve seen and solved virtually every problem there is.

When I now get a request for work, I can usually compose the solution entirely using code I’ve already built. I can take an existing taxonomy description and turn it into a fully content type enabled SharePoint structure in minutes, maybe an hour. I have so many workflow templates and have done event receivers so many times, I can probably fix your business process in a day, including writing out the training documentation.

It’s become a matter of producing rather than creating. I’ve become an assembly line worker rather than a developer. I no longer need to think and I have great fun thinking.

So, What Now?

I’m deeply fascinated by many things. I’ve already worked for a few months in the startup community both to learn and to offer insights from my experience as an investor and as an entrepreneur. Maybe I’ll pursue a career helping startups succeed.

I’ve also wanted for decades to get into game development. Over the previous months, I’ve built a platform for interactive story telling called Wizh. It’s in closed beta now and I work on it as much as I can because it brings back the fun.

Wizh is built on top of an interactive story engine called, creatively enough, ISENG, and I see huge potential in using ISENG in everything from story driven games, interactive fiction, and other entertainment areas, but also as an engine powering training, education, user experience testing, and more.

ISENG is to games and entertainment what SharePoint workflows are to business processes, to put it into language my SharePoint savvy audience can understand.

I’ve kept up with my students over the years but lately have seen that most of them want to learn things outside of SharePoint so I’ll probably refocus my mentoring efforts into a broader area of development.

I’ll probably also offer the odd opinion piece on SharePoint, but it won’t be my career anymore. This blog will retain it’s existing content but I’ll start adding other pieces of writing that interest me. If you want to tag along, you’re more than welcome.

Of course, if you have a great idea or need an experienced developer, entrepreneur, and architect, I’m all ears and would love to hear your thoughts. Maybe you’d like to partner with us in developing Wizh? We are always looking for interesting ideas, especially if you can help us fund the development.

That’s it. I’m done. .b has left the building. Talk again on the outside.

Pin It