SharePoint Governance and Information Architecture Master Class, Why You May be Stupid, and How to Fix That!

If you are in the UK on November 22-23, 2010, or even if you are elsewhere, and you want to understand governance and information architecture in SharePoint, you may be about to be insulted. Chances are I am about to call you stupid, but the as the loving and gentle soul I am, I will also tell you how to rectify that situation.

My buddy Paul Culmsee is holding an information architecture master class in the UK in a couple of weeks. Paul has asked me to help promote the event, and that’s what I’m about to do. So, without further delay, let me tell you a bit about Paul and why you should attend his class.

Let’s do the brief version first, in case you’re in a hurry. If you’re in the UK at the time, or even if you are elsewhere, and have even the slightest interest in learning governance and information architecture in SharePoint, and you are not attending that event, you are stupid. Plain and simple.

To not be stupid, hurry along and book your seat, it only takes a couple of minutes.

To those who are still here, I’ll tell you why that first batch of people are stupid if they do not attend.

A few years back when I started our with SharePoint for real, I wanted to accomplish what every other SharePoint professional wants to learn, namely how to make SharePoint not look like SharePoint.

I’m likely just like you, so I went to the best friend I have for solving these difficult tasks, namely Google. Paul’s site came up, and from that point on, I knew I had found gold, both in Paul and in SharePoint.

Little known fact: A major reason why I started writing about SharePoint is that I was so inspired by Paul’s writing.

Paul is a funny guy and highly intelligent. He possesses both the technical skills (he’s a bit rusty, but don’t hold that against him) and the business understanding that makes him able to work in an area that is absolutely vital to SharePoint success. The combination of humor and intelligence is also very important in accomplishing what I find is extremely difficult; that of writing and explaining advanced topics in a way that makes it easy for others to understand.

Throughout the years, I’ve been fortunate to talk a lot with Paul, and we’ve had some pretty interesting discussions about all sorts of topics. I still find reading his blog to be one of my favorite chores, and I look forward to reading and learning from him, simply because of his clear and understandable way of explaining.

I still remember fondly when we discussed for hours what governance is and we sort of arrived at a conclusion that is is whatever you decide it to be, as long as everyone understands the same thing. How cool is that? Governance is whatever you want it to be. This is a perfect example of the simple but powerful truths that I find extremely fascinating.

Enough about Paul and me, let’s talk about this event of his. A while back, must be closer to a year ago now, Paul came to me with his f-laws idea. I won’t even begin to explain all of the details here, but I’d venture as far as saying that this is the gold standard for governance in SharePoint. He wanted my feedback which I gladly supplied, and since then, Paul has kept me up-to-date on the progress. I’ve seen some pretty raving reviews of his classes already, and I’m far from surprised.

Sadly, this isn’t a topic that I’m dealing with on a regular basis, so I’m not going myself. However, if I had not been a die-hard developer, working primarily on delivering the systems that people like Paul governs, then I’d sell vital parts of my anatomy to be able to go.

You can though! And you should. In fact, you’d be pretty daft to miss this opportunity. Paul is coming to Europe to hold a master class in SharePoint governance and information architecture. I wish that I had some way of magically transmitting my confidence in the value of this class to you, because I know this will be one of those events that will drastically change your views of those topics.

The event page really explains the details of the event, so let me just do what I am supposed to do, and highly, highly recommend that you take whatever measures you need to attend that class.

You won’t regret it.


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

If you learn only one thing about SharePoint…

A few days ago… Frankly, that makes absolutely no sense because the majority of people will read this article at an arbitrary point in time, in which ‘a few days ago’ will likely be weeks, months, or years ago. Let me start again.

I was talking to a non-SharePoint friend who was fascinated with SharePoint and its raving success. Being an IT person, he does understand tech stuff, but seeing SharePoint as it is most commonly presented, he never saw the huge killer-app that many SharePoint professionals know it is.

“So”, he asked me, “in a single statement, can you tell me what SharePoint is?”

I’ve thought a lot about this in the past and have read a lot of suggestions. I’m not saying that everyone is wrong, but all the explanations I’ve seen are still not accounting for the success of SharePoint.

My response this time, as I think I’ve responded every time, is this:

SharePoint is a database.

It is nothing more and it is nothing less.

You can call it a lot of things, a collaborative solution, a development platform, an enterprise content management system… None of these, however, are accurate, any more than you can say that SQL Server is a game, just because someone uses SQL Server to store game data. Nor do these explanations explain why SharePoint is so powerful and has received the adoption it has.

So how does the glorified database explanation account for these thousands of end users, developers and other professionals loving so passionately a series of bits? I think it has to do with simplicity.

I think, and this is just my personal opinion, that when you want to understand something, you need to understand the basics first and then move from that basic to the more advanced. You can’t understand quantum physics unless you know the basics of Newtonian physics. You can’t understand graph mathematics unless you understand basic math.

Building on that analogy, there’s nothing preventing you from using both quantum physics and graph mathematics, or at least reap their benefits, even if you don’t know the first thing about why that damn cat is both dead and alive. To use something, you don’t necessarily need to understand how it works. You flip a switch and light comes on. You dial a number and someone answers. Who cares what electricity really is or why your voice travels thousands of miles in a fraction of a second.

This accounts for SharePoint as a user adoption thing. Users merely see it work. They click a button and some poor bastard gets a new task. They drag an icon and an invoice gets sent to a recipient.

I’m starting to lose myself a bit from the original statement, that SharePoint is a glorified database, so let me get back to what the heck I was talking about.

You see, all of the stuff that SharePoint does is related to information, which is just a marketing term for data. A page is at its core just information. An invoice is just a series of columns defined in a schema we call ‘Invoice’. Tasks, contacts, documents, everything that we see as complex entities with behavior, appearance, and all the other stuff, it’s all just data.

Now, I’ve made this claim to some pretty hard-core SharePoint experts, and they immediately start comparing SharePoint to SQL Server and claim that SharePoint is nothing like that, and although there are technical differences that makes the use of these two types of databases different, at its core, SharePoint is very much the same as SQL Server is at its core. It’s a matter of data, stored in lists in the case of SharePoint or in tables in the case of SQL Server. Items in lists are rows in tables. Columns in items are columns in rows. Views in SharePoint are views in SQL Server.

The similarities do not extend forever, and both SQL Server and SharePoint has distinct differences that makes them each suitable for a specific type of task. For example, SQL Server has nothing that compares to content types, while SharePoint lacks a clear counterpart to stored procedures. These are just features of the platform, however, and doesn’t change the fact that both platforms serve one purpose, which is to store, manipulate, and retrieve data.

Once you understand that SharePoint is a database, you can start to understand why it is so powerful. SharePoint takes data driven application development and solves all the ugly stuff that you’d normally need to consider as a developer. Further, it takes all of this and makes it readily available to users of all skill levels. This is where SharePoint clearly distinguishes itself from anything else; it is equally friendly and powerful to end users and first tier developers as it is to hard-core programmers like myself.

So, despite what many of my colleagues claim, I’ll still stick by my simple explanation that SharePoint is, at its very heart, a database.

Why is this a critical factor in SharePoint’s success? Well, we live in what is lovingly called the Information Age. Much of our society revolves around gathering and processing data. If you have a tool that makes that process easy, stable, and understandable to a lot of people, you have a winner. That’s exactly what SharePoint does, and that is why I argue that SharePoint is the killer app that it is.

Agree or disagree? Let me know… You know where the comment box is.


Pin It