In Part 1 of my series titled Inadequate Resources to Support the Implementation, I spoke about the large amount of risk that companies are taking on due to the ease of entry into the SharePoint Administrator’s role.  In Parts 2 and 3, I explained how the SharePoint Administrator’s role was never clearly defined and that most of us lack a true identity.  In Part 4 of this series, I examined the expectations from the business perspective, and in Part 5, I’ll share my solution on how we can all fix this problem.

Part 5: My Proposed Solution

This is my final installment in this series.  I have spent weeks discussing why SharePoint implementations fail, and it is time for me to provide you with my solution.  Up until this point, I’ve explained that in order to implement SharePoint effectively, you MUST take a business-focused approach.

It is detrimental to implement SharePoint into your organization based solely upon a limited number of exciting features or functionalities.  The most effective way to implement SharePoint into your organization is to evaluate the current state of the business as a whole (e.g. existing processes, requested improvements, collaborative needs) and implement SharePoint-based solutions to support and enhance those critical business processes.  

You do not bring SharePoint into your organization because you want to utilize one or two features or functionalities for your personal or departmental gain.  You bring SharePoint into your organization because you want to solve or enhance critical business problems throughout your entire organization. 

The facts of the matter are as follows:

• For years, companies have been implementing SharePoint solutions without thinking of the business first.  Real-world experience tells me that I should plot my course BEFORE I run my race.
  
• For years, the qualifications for playing the role of the SharePoint Administrator have gone undocumented.   Apparently all it takes is an employee’s enthusiasm to learn the technology combined with the business’ desire to launch the technology.  Unfortunately, sometimes the business is unable to, or doesn’t recognize the need to hire qualified resources.   We all know that just because you WANT TO BE a professional football player in the NFL, doesn’t mean that you WILL BE good at it.

For years, our SharePoint Implementations have been undersupported, understaffed, and ineffective in solving critical business problems.  It is time to reset expectations for what is required to properly implement SharePoint within an organization.  

My Proposed Solution: ADEQUATE Resources to Support the Implementation

I propose a team of individuals working together to “effectively bring SharePoint into the organization.”  This team is made up of three very important roles:

The SharePoint Administrator

DESCRIPTION:  The SharePoint Administrator will be responsible for the implementation and configuration of the physical environment that will support the business needs defined in the deliverables created by the SharePoint Architect.  TASKS:  The SharePoint Administrator is charged with the installation, physical deployment, data management and recovery, and farm-level administration of the SharePoint Implementation.    BACKGROUND: This individual must be technically sound in the areas of server setup, deployment, administration, networking, database administration, and security.  A solid development or application background may also be of benefit. Most importantly, it is imperative that this individual holds a strong understanding of SharePoint Administration.

 

 

The SharePoint Architect

DESCRIPTION:  The SharePoint Architect will be responsible for ensuring the design and definition of the Farm’s Information Architecture and Site Taxonomy mirror the business’ goals, processes, and personality.  TASKS:  The SharePoint Architect will be tasked with the planning, requirements gathering, and management for the farm’s Information Architecture, Site Taxonomy, and Security model.  They will translate business requirements into SharePoint functionality, and work with executives, departments and teams to understand and define the SharePoint Solution. BACKGROUND: A successful SharePoint Architect is someone who has the ability to understand the technology of SharePoint, while simultaneously understanding how their business works.  This individual must be energetic, pro-active in nature, process-focused, and demonstrate excellent presentation, communication, documentation, and problem solving skills.  The foundation of skill sets associated with a Business Analyst, Project Manager, or Solution Architect can provide a solid beginning for a budding SharePoint Architect. Most importantly, it is imperative that this individual holds a strong understanding of SharePoint Architecture.

  

The SharePoint Evangelist

DESCRIPTION:  The SharePoint Evangelist will be responsible for the business’ education, adoption, and governance in support of the SharePoint implementation. TASKS:  The SharePoint Evangelist will be tasked with designing and developing creative approaches to deliver SharePoint-related training and education for business owners and business users.   This role will also be tasked with leading the definition and education of a governance plan designed to ensure the long-term viability of the implementation. BACKGROUND: This individual must thrive in situations where the odds are against them.  They must have incredible presentation, communication, time management, and problem solving skills.  They must enjoy educating others and not be phased by conflict or confrontation.  A business analyst, helpdesk, educational, or support background may provide a solid foundation for success as a SharePoint Evangelist.  It is IMPERATIVE that this individual holds a strong understanding of SharePoint Features.

For you business owners out there, I’ve created a visual diagram to communicate the distribution of skill sets that I believe are required for the SharePoint team members.  For each role, a series of skill sets are represented as 3-D blocks.  The depth and breadth of that team member’s skill set will be represented by the length and width of the block. This is represented here.

Each of these individuals will have a specific focus within the SharePoint arena, yet they will work together as a team to “effectively bring SharePoint into the Organization.”  The days of a single SharePoint Administrator tasked with carrying the unattainable expectations of the business on their back must come to an end. 

In Conclusion

This is the solution I am proposing.  If you know me, you know that I am a very passionate person when it comes to SharePoint.  I am so passionate about this message, that you will see me support it in every classroom I teach, and every presentation that I deliver.   We have suffered too long from inadequate resources to support our implementations.  It is time for all of us to make a change.

Thank you very much for taking the time to read my blog posts on this topic.

Matt

Filed under: Uncategorized

Hi everyone,

I’m so excited; I just had to post this topic to my blog.  I’ll be teaching my SharePoint Planning and Administration Bootcamp publicly in Anaheim, California in two weeks (from April 27^th to May 1^st). SharePoint Experts has been to Anaheim before, but never like this.  Class will be held at Disney’s Paradise Pier hotel.  That’s right!  We are in the park! 

Over the past few months, I’ve been working diligently to update my class materials, and have rewritten the foundation of the class to cover Windows Server 2008. I’ve also produced a lot of new material surrounding performance and optimization of SharePoint.  On top of that, I’ve got another year of exciting real-world experience to share.  If you’ve paid close attention to my blog, or have seen me speak at a conference as of late, you know that planning SharePoint is still my bread and butter, and is taken very seriously in my class.

• If you are an Administrator, and you want to solidify your SharePoint Administration skill set, this class is for you. 
• If you are a Business Owner, and you want to see the big picture perspective, I'll show you. 
• If you are an Architect, and you need to design your implementation properly, you’ll learn it here.
• If you happen to play ALL of these roles, this class definitely for you!  Sign up now!

While in Anaheim, I’ll be teaching alongside Dustin Miller and Heather Solomon.  Dustin will be teaching the Original SharePoint Bootcamp, and Heather will be teaching the SharePoint Branding Bootcamp. 

To find out more, or to sign up, visit http://www.SharePointBootcamp.com.

See you in Anaheim!

Matt

Filed under: Uncategorized

I’m in Montreal this week to present two sessions at the SharePoint Summit.    There are a lot of great vendors in the exhibit hall, and the presentations that I’ve attended thus far have been standing room only!  This is turning out to be an incredible experience!

If you are familiar with my style of presentation, you know that I focus on the business first, and take the extra steps necessary to make the audience as comfortable and entertained as possible throughout the session!  A SharePoint Experts presentation wouldn’t be complete without additional bonus content provided to you via my blog.  Here it is!

For those of you who attended my sessions at the Summit, I’d like to take this opportunity to personally thank you.  If you found my real-world experience to be of benefit, and are interested in applying the lessons you've learned to your own implementations, I’ve posted the bonus session materials below:

Session 1.2 – MOSS 2007 Deployment Planning:
Maximizing User Adoption Through Proper Information Architecture
References found here.

Session 7.1 – MOSS 2007 Deployment Planning:”
Planning Your Intranet Solution Around Your Business
References found here.

Thank you for the opportunity to contribute to to the SharePoint community!

Matt

Filed under: Uncategorized

In Part 1 of my series titled Inadequate Resources to Support the Implementation, I spoke about the large amount of risk that companies are taking on due to the ease of entry into the SharePoint Administrator’s role.  In Parts 2 and 3, I explained how the SharePoint Administrator’s role was never clearly defined and that most of us lack a true identity.  In Part 4 of this series, I’ll examine these expectations from the business perspective and uncover just how outrageous this role really is.

Part4:  “SharePoint Administrators are NOT Superheroes!”

 

I really want to emphasize the outlandish expectations that the business has historically held for SharePoint Administrators. 

 

A Business Analyst:

As a SharePoint Administrator, you may be asked to take on the role of a Business Analyst by planning your implementation.  This means gathering requirements for feature specific functionality.  You have to be able to look at a business problem, and propose a solution using a specific technology.  You also need to be able to create and deliver professional looking documentation such as proposals, project plans, presentations, and often training material.  Most likely, you’ll be asked to facilitate meetings with Business Owners in order to present that material.  

A Solutions Developer:

As a SharePoint Administrator, you may be asked to take on the role of a Solutions Developer when growing your SharePoint implementation.  This would entail the understanding of the roles played by the current applications within your organization.  You may be asked to evaluate an existing set of applications for a possible integration into SharePoint. 

A SharePoint Architect:

As a SharePoint Administrator, you may be asked to take on the role of an Architect when planning your implementation. This may involve the knowledge to properly define the logical topology of your SharePoint Implementation.  Planning the appropriate Sites, Site Collections, Web Applications, and Shared Services Providers with an eye towards the big picture will allow you to evaluate the future effects of decisions made today.  This will be extremely important in your success as a SharePoint Administrator, because often times, it is your recommendation that gets implemented.  

A Hardware Administrator

As a SharePoint Administrator, you may be asked to take on the role of a Hardware Administrator when building out your implementation.  Though you may or may not be the one ordering the hardware, or even setting it up, it is important to understand the hardware options to support your implementation.  You have to understand the SharePoint server roles, and the opportunity costs associated with selecting specific chipset architectures and other hardware components such as memory, disc space, and storage. 

A Security Administrator

As a SharePoint Administrator, you may be asked to take on the role of a Security Administrator when setting up and installing your implementation.  You’ll need to understand how SharePoint secures information at the farm, site collection, site, list, and item level.  Depending upon the complexity or scope of your implementation, you may need to understand the different security protocols and possible risks within your network.  You may need to institute multiple authentication methods across your implementation and interface with multiple back-end credential stores. 

A Network Administrator

As a SharePoint Administrator, you may be asked to take on the role of a Network Administrator when planning your implementation.  You may be the one called upon to suggest an appropriate server topology to support your implementation. When you get beyond the single box, or sandbox implementation, you’ll need to learn about intranet, extranet, and internet options.  You’ll need to understand DMZ configurations and additional hardware components that interface with, and protect your implementation.  You’ll need to learn how to setup and even troubleshoot network connectivity issues.  This can be a tall task for anyone new to network administration.

A Database Administrator

As a SharePoint Administrator, you may be asked to take on the role of a Database Administrator. You may have to understand proper SQL Server setup and disc configuration.  You could be responsible for the backup and restore processes, and the evaluation of database logs and performance tuning.  In the event of a disaster, you need to have the processes in place to recover your data within predefined service-level agreements. 

A .NET Developer

As a SharePoint Administrator, you may be asked to take on the role of a .NET developer.   In many cases, you may not be the one doing the development, but it is important that you understand what functionality is available out of the box, what is configurable through the UI, and what would have to be developed using the object model. You’ll need to understand when to deploy features , a custom web part, or a custom configuration.

A SharePoint Evangelist

As a SharePoint Administrator, you may be asked to take on the role of an Evangelist throughout the lifespan of your implementation.  You'll be challenged with the task of evangelizing the capabilities of MOSS 2007 throughout your organization.  You’ll need to be able to handle a multitude of technical and non-technical questions about your SharePoint implementation.  You’ll need to understand available features and functionalities, and communicate effectively to all types of personalities.  As an evangelist, you may be asked to assist in gathering requirements, leading training sessions, ensuring governance practices are followed, or providing demos.  You’ll also need to understand the current status of your implementation. 

Ok… take a breath.  What you just read were 9 separate roles that when combined, commonly equate to the SharePoint Administrator’s role.  

It is overwhelming.

It is daunting.

For 99% of SharePoint Administrators out there, it is unattainable.   

Because the title of our role has the word “Administrator” at the end of it, the business often looks at SharePoint Administrators and sees the glass half empty.  “If the portal is down, you’d better understand why it is down, and you’d better know how to fix it.  If the portal is up, you’d better be available to handle anything we can throw at you.”  It may sound harsh, but many SharePoint Administrators feel this way towards the business they serve.  We walk around with this badge… or shield… or curse that reminds us somehow, we need to dawn a cape and save the world when the business is in distress. 

I’ve been on this Super hero kick as of late, so please allow me to indulge myself.  If you’re old school, then you know that even the Green Lantern, who held power; limited only by the imagination, was powerless against something so simple as the color Yellow!  If you consider yourself new school, you’ve read Alan Moore’s WATCHMEN and you know that even if superheroes did exist, they’d just be ordinary people, with ordinary problems, and our lives wouldn’t have turned out any better or worse than they already did.

Note to Alan Moore: Please do not be offended by Matt Passannante’s one sentence description of one of the greatest texts written by man.

 SharePoint Administrators are NOT superheroes!  Superheroes do not exist. 

The business has to stop seeing the SharePoint Administrator role as an endless well of expectations and abilities.  At the same time, SharePoint Administrators need to understand their limits and work effectively within them. 

This has been a very intense series of posts for me to author.  I promise that my next post in this series will offer up a solution and level-set expectations for both Administrators and Business Owners.

Thank you for reading.

Matt

Filed under: Uncategorized

In Part 1 of my series titled Inadequate Resources to Support the Implementation, I spoke about the large amount of risk that companies are taking on due to the ease of entry into the SharePoint Administrator’s role.  In Part 2, I explained how the SharePoint Administrator’s role was never clearly defined and that most of us lack a true identity. In Part 3 of this series, I’ll provide you with some visibility into these overwhelming expectations.

Part 3: “I really don’t remember signing up for this.”

Depending upon a multitude of factors such as your company’s size, your outlook on training, your boss’ outlook on training, your technical background, the scope of the implementation, and of course the timeline and available budget J, the requirements to effectively bring SharePoint into the organization can be drastically different from one implementation to another. 

Most of the SharePoint Administrators that I have spoken with describe the business’ perspective as, “You are the SharePoint Administrator. If we have a problem with SharePoint, we are coming to you.”  This makes sense right?  If you have a problem with your paycheck, you go to Finance.  If you have a question about your benefits, you go to Human Resources.  It just makes sense that if you have a question about SharePoint; you go to the SharePoint Administrator.  Right?   Keep reading please.

In the examples above, you are bringing your problems to a member of a department, and not an individual.  If you have a payroll issue, you will more than likely be transferred to a payroll specialist.  Often times, the subject of your query is handled by a separate entity or company altogether. Within a single department (e.g. HR), you might have a Benefits Coordinator, a Personnel Manager, and an Employee Relations Manager.  Depending upon the size of your company, you might even have a Vice President to oversee all of these roles.   Where a department can have multiple resources; each focusing on a specialized aspect of that function, your SharePoint implementation often has only one person to handle all of the questions thrown at them.

If you haven’t figured it out yet, a large majority of people in the SharePoint Administration role are suffocating under the ridiculous expectations and crushing responsibilities involved in their daily activities.  I am NOT proposing that SharePoint become its own division within your company.  I am simply making the point that our SharePoint implementations need more than just a SharePoint Administrator.  Let me prove my point.  We all love tests, right?  Let’s take one now. J No cheating and eyes on your own paper.  Begin!

SharePoint Test

1.       Can we integrate our current time application into our SharePoint implementation? 2.       Can you explain the relationship between Shared Services Providers and Web Applications?  I’d like to know why you’ve chosen the site taxonomy and high-level information architecture that you have put in place. 3.       How many servers will I need to purchase to support my SharePoint implementation? 4.       Will our SharePoint implementation be secure?  5.       Will I be able to login from home?  If not, why? If so, how? 6.       What is our disaster recovery plan in the case of an emergency? 7.       How do I change the color scheme? Also, I don’t like the layout. Can I change that? 8.       What is SharePoint?  (You are asked this question in an elevator, and have 20 seconds to answer) 9.        How do we derive “value” from our SharePoint environment, and how do we define a successful implementation?

If you have the ability to answer each of these questions, in great detail, and without hesitation, then congratulations, you are in what I like to call, “The 1% club.”  Here is the key to your locker.  Your member’s jacket is hanging in the foyer. J

For the other 99% of the SharePoint Administration community out there, who were not able to answer each of these questions fully and with confidence, DO NOT feel bad.  In my experience, the 1% club is filled with a select few individuals who have dedicated their careers to SharePoint Administration.

The problem is that these are all “introductory” or “leading” questions for a SharePoint Administrator. The subject matter in the test above was derived in under a minute and represents some of the most common questions posed to SharePoint Administrators on a daily basis.  Each question in the test represents a different background or technical foundation.  Your first response is to think, “Oh, those are easy questions.  Any SharePoint Admin should be able to answer that.”

If you are a business owner, and you truly feel that way about the SharePoint Administrator’s role, then let us look at the test again and uncover the real expectations.

SharePoint Test

1.       Can we integrate our current time application into our SharePoint implementation? (This question references Solutions Development.)  2.       Can you explain the relationship between Shared Services Providers and Web Applications?  I’d like to know why you’ve chosen the taxonomy and site structure that you have put in place. (This question references SharePoint Architecture.) 3.       How many servers will I need to purchase to support my SharePoint implementation? (This question references Hardware Administration.) 4.       Will our SharePoint implementation be secure?  (This question references Security Administration.) 5.       Will I be able to login from home?  If not, why? If so, how? (This question references Network Administration.) 6.       What is our disaster recovery plan in the case of an emergency? (This question references Database Administration.) 7.       How do I change the color scheme? Also, I don’t like the layout. Can I change that? (This question references Development & Customization.) 8.       What is SharePoint?  (You are asked this question in an elevator, and have 20 seconds to answer) (This question references SharePoint Evangelism.) 9.        How do we derive “value” from our SharePoint environment, and how do we define a successful implementation? (This question references Business Analysis.)

 By not defining the role of the SharePoint Administrator, the business has come to expect that a SharePoint Administrator should carry each of these skill sets. It is my opinion, that the following picture accurately represents the real-world expectations of the SharePoint Administrator.     

Unfortunately (and I am truly saddened to say this), I think there comes a time in every SharePoint Administrator’s career, when they realize that this is the expectation that has been placed upon them, and they have to make a decision about their career.  In my heart, I feel that there is something very wrong with this picture.  How do you feel about it? 

Stay tuned for my next post in this series as I will be discussing each of these expectations in more detail.  After that, I will be proposing my solution to fix this. On a more personal note, I know that your time is precious, and I want you to know that I appreciate you reading the posts in my blog.    

Thank you,

Matt

 

Filed under: Uncategorized

In Part 1 of my series titled Inadequate Resources to Support the Implementation, I spoke about the ease of entry into the role of the SharePoint Administrator.  Way too often, it is on a whim or in passing that someone is asked to “dabble” in the setup or site provisioning of SharePoint.  Little did we know, sometime over the next year of our lives, we’d be asked to pose for the cover of Van Halen’s 5150 album.  That’s right people.  We back Sammy in this blog! J

In Part 2 of this series, we uncover the giant pink elephant in the room that everyone seems to be so reluctant to confront.

Part 2: The oversight we’ve been paying for all these years

 

I had mentioned previously that SharePoint Administrators originated from some very diverse backgrounds. In the past year alone, I have taught SharePoint Administrators whose backgrounds (i.e. roles held prior to becoming a SharePoint Administrator) were as follows:

 

Account Manager

Administrative Assistant

Application Developer

Business Analyst

College Graduate with a Degree in Horticulture
… Seriously!

CRM Administrator

Database Administrator

Executive Administrative Assistant

Information Manager

IT Consultant

IT Administrator

IT Manager

IT Support Consultant

Junior Analyst

Marketing Assistant

Network Administrative Assistant

PBX Operator
… Yeah!  The phone guy!

Project Manager

Sales Manager

Senior Account Executive

Senior Analyst

Senior Consultant

Senior Technologist

Solutions Developer

Systems Administrator

Technical Intern
… Very Secure!

Tier 1 Support Specialist

Tier 2 Support Specialist

…Isn’t this starting to feel like an infomercial on the Jerry Springer show? 
“In two quick years, you can train to be an…”

SAP Manager

Securities Admin

Security Manager

Server Administrator

Vice President

Web Designer

Web Services Developer

… and more.

 

WOW!  That is quite an exhaustive list, huh? It was only within the last year that I started keeping track.   Doesn’t it seem a little odd, that almost anyone and everyone is being asked to play the role of a SharePoint Administrator these days?   This isn’t anything new.  From what I can tell, this has been the norm since SharePoint’s inception.

I believe that this diversity in experience is an assisting factor as to why so many SharePoint implementations are failing to reach their potential within their organization.  In the grandest of senses, we are taking the most important information throughout the company, and hosting it centrally for everyone to access.  Depending upon your background, experience, skill set, and your thought process on how best to accomplish this, the road required to complete this task can be drastically different than someone else’s.  This isn’t a bad thing… In fact, it is almost expected.  The problem occurs, when you ask each of these people to play the role that has never been defined in the first place.  

Double doors open.  Enter Pink Elephant.

The SharePoint Administrator’s Role

 

OK, so there is a pink elephant in the back of the room.  Is anyone going to acknowledge it?  No?  Ok.  I’ll take the leap of faith here and say something that will probably frustrate a lot of people.  I’m saying this because it needs to be said.  We need to deal with it, solve it, and move on.   Here it goes.

“The SharePoint Administrator’s role has never been clearly defined.”

Did someone mention a pink elephant standing in the back of the room?  I don’t see him anymore. 

It is easy to find a definition of a SharePoint Administrator’s role in any book out on the shelf today.  Ask any SharePoint Administrator whether or not that definition fits their current role, and I’m betting you’d be hard-pressed to hear a positive response.  The definition in the book often serves more to scope the chapters of the book, than it does to actually define what the role actually requires.   

Don’t get me wrong, there are some seriously talented people in our SharePoint community.  MAD PROPS to Shane, Todd, and Steve for creating a quality resource that should stand the test of time for many Administrators!        

From a real-world perspective (and at SharePoint Experts, EVERYTHING we do is based upon our real-world perspective), the term “SharePoint Administrator” is not simply:

“…a technical resource responsible for keeping the SharePoint environment up and running”

Over time, the role has morphed into:

“…the person responsible for effectively bringing SharePoint into the organization”

The lack of definition surrounding the role, and the impossible expectations demanded by the business has truly diluted our identity as SharePoint Administrators.  Until we can fully understand the root cause of the problem (which we will discuss in this blog) and we can identify a plan outlining the role of the SharePoint Administrator (which again… we will), SharePoint implementations run an exponentially higher risk for failure due to the expectations of the business and the inadequacies of the person playing the role of the SharePoint Administrator.

Stay tuned for my next blog post in this series as I will uncover these seemingly impossible expectations that most businesses have for their SharePoint Administrators.

Matt

Filed under: Uncategorized

Filed under: Uncategorized

 

We all like game shows. right? Let's play one now.   I'll dawn a long-neck microphone, put on my finest pinstripe suit, and even color my hair a peppered gray.  Get ready to battle it out with the rest of the contestants.  In my best Alex Trebek voice.

“Here is the answer.  A company with a SharePoint implementation employs this type of resource.“

If your answer is “A SharePoint Administrator,” you are incorrect!

If your answer is “What is. a SharePoint Administrator,” you are correct.

If you were playing as Sean Connery, we would have also accepted:

(In classic Connery voice) “Your Mother, Trebek!  Ha Ha Ha HA HA HAAAA!“

Chances are, if you have a SharePoint implementation in place within your organization, you have someone on staff playing the role of the SharePoint Administrator.  Let's get serious and talk about the role of your SharePoint Administrator for a little bit.   

I am the Director of Implementation Services and the Author of the SharePoint Planning & Administration Bootcamp for SharePoint Experts.  I train 100's of SharePoint Administrators each year. This is a very diverse group of people, coming from a very diverse background.   Most people that I've educated about this role, never even planned on being a SharePoint Administrator in the first place. 

In every public class I teach, I have a discussion with my students about how they became a SharePoint Administrator.  Without fail, the following interaction takes place:

(Me in my teaching voice): “So you show up to work one day, and you're doing your job.  Maybe you are a business analyst, and you are working on a project plan.  Maybe you are in support, and you are working on an open case or two. Maybe you are a Systems Administrator, and you are going through some logs to check for any issues that arose over the last shift.  All of a sudden, you receive a tap on your shoulder.  You turn around, and it is your boss. 

“Hello There.  How are you today?” your boss says calmly.

“I'm fine,” you respond.

“Listen, we'd like to move forward with a new technology called Microsoft SharePoint.  We are looking for someone to champion this effort for us.  Anyway, we were all sitting around in the conference room, thinking about who could help us, and your name came up.  I know that what you are currently working on is very important, but we just want to get a SharePoint site up and running here within the next few days.  Do you think you would be able to help us out?  I promise that this won't take more than 10% of your time.“

At this point, your boss is staring you down; focused intensely on your eyes. The thought that you are currently 110% allocated to your current role is exploding inside of your head, yet your desire to portray a team player makes you crack a smile as you say, “Sure.  That sounds fine.  I'll look into it.“

Depending upon your boss' level of excitement, you might even hear this closing statement.  “Thank you.  We really appreciate it!  Why don't you head to the bookstore during your lunch break and buy a book on SharePoint.  I'll even make sure you can expense it!“

Now, before I go any further, I need to let you know that it is at this point in the class, that I pause to look at my students in the classroom.  Without fail, the room is silent.  The student's faces are filled with dismay, as it appears I've just shared the contents of their childhood diaries.  I say in a stern and passionate voice, “If this has happened to you, please raise your hand!“ 

Time. after time. after time, an overwhelming majority of students raise their hands.

“Look around.” I say calmly.

 As they look around the room, they begin to cringe and even chuckle.  They suddenly experience what I like to call, Band-Geek Syndrome (BGS) or Theatre Geek Syndrome (TGS). 

Just like band geeks or theatre geeks in school, we all saw ourselves as outcasts at one time or another until the day we picked up that instrument or took to the stage, and found our calling. Some of us even went so far as to win a National Championship Percussion Title! J  . But I digress.  

See, SharePoint Administrators are just like band geeks or theatre geeks.  Historically, the SharePoint Administrator role has been one of isolation.  There has really never been a clear cut direction for the role of a SharePoint Administrator, and we often feel lost or confused about our education, expectations, and activities.   The moment we find out that there are other people who have had similar experiences along their road to becoming a SharePoint Administrator (however crazy and outlandish their road may seem), we find great comfort in our historic similarities and our confidence-level skyrockets.

It is such an immense relief to know, “Hey. I'm not crazy.  I've been banging my head against this stuff like everyone else!” Once you accept this realization, your road to understanding the role of the SharePoint Administrator becomes much more manageable.

The question I have for you is, "Am I preaching to the Choir?" 

Stay tuned as we continue to investigate the role of the SharePoint Administrator.  I might just change your perspective as we uncover why and how this role needs to change.

Matt 

 

Filed under: Uncategorized

The term failure is a harsh word. Regardless of how you may view the term in your personal or professional life, in SharePoint terms, I equate the word failure to any SharePoint implementation that does not meet its full potential within an organization.  For those of you who know me, you know that I have very high standards for both myself, and my work.  When I think about SharePoint Implementations over the past 7 years, the word failure jumps to the forefront of my mind.  This action occurs because it is only on the rare occasion, that I see an implementation of SharePoint meet its true potential within an organization.      

I believe that most SharePoint implementations fail (.to meet their true potential) due to a series of similar pitfalls. From my real-world experience, some of the most common causes for a failed SharePoint implementation orbit around the following:

 Inadequate resources to support the implementation
 A lack of planning
 Improper expectations as to SharePoint's role within the organization

I am not one to simply point out a problem without also providing supporting details around a solution. This blog doesn't simply complain about a problem.  It offers a solution as well. J  Through a series of blog posts on the topic of why SharePoint implementations fail (. to meet their true potential), I'll be explaining common pitfalls, discussing real-world history, and explain the impacts these pitfalls can have within an organization's SharePoint implementation. 

From here on out, I'll try to explain things from the perspectives of both the SharePoint Administrator, as well as a business owner.  Finally, I'll provide possible avenues for improving upon these pitfalls and provide guidance as to how these problems can be avoided in the future.

Stay tuned!

 

Filed under: Uncategorized

Hello,

I would like to thank everyone who attended my session titled DM200 - MOSS 2007 Deployment Planning. Presenting at the SharePoint conference was a dream come true.  For those of you who are intereseted in the roadmap documentation, I've posted it here. 

Please let me know if you have any comments or questions.

Matt

 

 

 

 

 

Filed under: Uncategorized