In this article, I give you some practical structure and tactics you can use to achieve effective SharePoint governance.
In football, how effective and successful will a team be at winning if it doesn’t have structured sub-teams? Imagine a football team with no defensive line, offensive line or special teams. What if sometimes the quarterback played the role of wide receiver, linebacker or kicker? How effective would that team be? What if the team had no planned plays, never practiced those plays and had no coaches or clear direction?
The truth is that, while the raw talent and skills of players is important, the team structure, patterns and practices are just as important.
Author Note: The talent, experience and skill of SharePoint staff are all important factors to a successful SharePoint implementation. Keep in mind that any talented person would prefer to come into (and remain within) an environment that is well-run and ready for growth versus one focused on fighting fires and extremely disorganized.
Now take a look at your internal SharePoint environment. How clear are your teams? How clear are people’s roles in relation to SharePoint? Do you have clear plays that people can execute with minimal hesitation or without excess deliberation? Do you have clear direction and priorities as well as communication? How effective are your SharePoint team members in meeting business needs and business demand?
By the end of this article, I may not be able to give you all the answers to the questions above, but I hope to at least add clarity and give you some practical structure and tactics you can use to achieve effective SharePoint governance.
In particular I will provide answers to the following key questions:
- What is effective SharePoint governance?
- How should I structure my governance teams?
- How does business strategy fit into SharePoint governance?
- What should my governance teams be doing?
Let’s start with what “effective” SharePoint governance is, and what it isn’t.
SharePoint Governance is Not SharePoint Insurance
The majority of governance discussions, presentations and even “implementations” of SharePoint governance have something in common: Mitigating risk. Like an insurance plan, the governance structures, documents and processes are put into place with an emphasis on reducing the risk of common-cited issues such as site sprawl, quality deterioration, end user frustration and SharePoint priority paralysis.
- Site Sprawl: This is a result of un-managed sites and content not being periodically reviewed for accuracy and relevance.
- Quality Deterioration: This is often a result of good initial planning, population and vetting of content by experts, but a failure to ensure continued editorial processes around content within the portal.
- End-User Frustration: This risk has a variety of possible causes. Most often end-user frustration is a result of end users not understanding the business purpose, alignment or benefit of using the platform or is a result of inadequate technology support services being provided.
- Priority Paralysis: This is a result of not having clear decision-making authority/ownership and escalation procedures so that conflicts are resolved in a timely manner. Often it can be a symptom of a larger issue of poor alignment and business strategy as well.
While mitigating real SharePoint risks is important, (and is a result of effective governance), it shouldn’t be the focus.
Instead, key to effective SharePoint governance is to think of it less as “SharePoint insurance” and think of it more as “a way to make your SharePoint investments more successful.” Effective governance is actually more about increasing organizational performance, capability and capacity then it is about mitigating risks.
The simplest way to achieve this result of “making your SharePoint investment more successful” is by creating clear teams, roles and getting those teams to share and work on optimizing existing processes, and leveraging existing (and future) resources to their maximum potential. Just like our football example, if we have specific teams sharing and practicing/working together, we can be more effective than the unstructured alternative.
The Importance of Governance Teams
So what are the strategic and tactical governance teams that are necessary for Effective SharePoint governance?
- Business strategy team
- Solutions/technical strategy team
- Tactical operations team
- Tactical development team
- Tactical support team
Each team is important and has been broken out for a reason. It is possible and acceptable that you have one individual who plays multiple roles on multiple teams. It’s still important for them to understand that they are wearing different hats when playing each role, and have different responsibilities and concerns.
The Business Strategy Team
Perhaps the most overlooked team, this could be called a committee (I even had one company call this the “Executive Enterprise Collaboration and Communication Steering Committee”), but the naming doesn’t matter as much as what this team accomplishes.
Business Strategy is a Part of Effective Governance
Often businesses focus on the technology and solutions when they discuss governance and forget about how important it is to have the business provide clear objectives, priorities and direction for the technology leadership to develop their solution roadmaps and multi-year SharePoint strategies.
The biggest offender for these scenarios is when the business comes up with vague business objectives like “enhancing collaboration” or “automating and improving business processes” and assumes that by using these “positive” statements it will provide the direction necessary for its SharePoint or enterprise content management implementations.
If you take the example of “automating and improving business processes,” that objective is difficult to measure. How do you know when you have successfully automated and improved business processes? What kind of business processes? Which processes? What about these processes are the existing pain points/issues right now? By getting down to a much more specific level, it begins to become obvious what potential solutions SharePoint (or any technology) can provide.
The only way to achieve a measurable level of success (and to be able to define clear solutions) is when we break down these vague objectives into real business concerns, issues, challenges, and pain points and then address them through technology leadership.
The Solution (Technical) Strategy Team
This team defines, aligns and prioritizes the technology solutions based on the business objectives and input from the business strategy team.
They are also responsible for leading the technology enterprise strategy within the company ensuring that a clear platform classification schema has been put into place.
As an example, it’s this team’s responsibility to enforce whether SharePoint will or won’t be the primary document management or application delivery platform for the enterprise. For more information on the importance of defining what SharePoint will and won’t be used for, please read this post on SharePoint is not a silver bullet.
Alignment Between Business,Technology Solutions
Now that we understand how to define business objectives so that they can be measured, we can start coming up with many ways in which we can use technology (namely SharePoint) to help achieve these objectives. When we begin discussing the business requirements that relate to a clear and well defined objective like “automating and improving the onboarding business processes that are paper-based, which are managed by HR…” most technology architects or leaders will begin thinking about how they can use different features and capabilities of the technology platform to support or improve that process.
Once we come up with our solutions, there is an additional challenge of prioritizing which solutions should be developed and implemented first. We can use the importance (and business value) of each objective to help define the priority for our proposed solutions. The easiest way to visualize this is by using a table method where we map our identified objectives to our identified solutions.
- SharePoint is Back, Yammer... Not So Much
- 3 SharePoint Paths for the Next 10 Years
- Microsoft Beats Amazon in Cloud Storage [Infographic]
- Why Companies Can't Afford to Go Overboard with Analytics
- Groups for Office 365 Transforming Collaboration
- Everything Bill Baer Has Shared About SharePoint
- How Marketing Content Wastes Money