- podcast
- research
- search
- security
- technology
- video
- AIM
- Alfresco
- Collaboration
- ECM
- ESX
- Hyper-V
- IE8
- Internet Explorer
- Iomega
- Linux
- MIX08
- Microsoft
- NAS
- Nokia
- REV
- S60
- SaaS
- Sharepoint
- Silverlight
- Sony Ericsson
- VMware
- Windows Live
- YouTube
- advertising
- backup
- beta test
- blogs
- convergence
- display
- enterprise
- humans
- instant messaging
- multimedia
- networking
- open source
- phishing
Achieving Sustainable SharePoint Governance
This is not an IT story, it's a business story. Customers often hear only the high-level, feature-centric, compelling version of the SharePoint story: SharePoint does document management; SharePoint does workflow; SharePoint does collaboration, etc. But what do these features really mean from a business perspective, and how can a business prioritize, operationalize manage them—all while ensuring that SharePoint continues to satisfy strategic business objectives and most importantly, that it's adopted by your users?
The SharePoint Double Fantasy
SharePoint consultants, engineers, and developers tend to believe that end users will:
- Love SharePoint. We love SharePoint! We believe our users will, too. We believe people will naturally use the system as originally conceived, designed and delivered. After all, why wouldn't business users flock to use a centralized portal? Why wouldn't they want to use online workflow approvals? Why would people still send documents as email attachments when they have SharePoint?
- See the light. We dream that—given the opportunity—end users will adapt and change to become good "SharePointers." In other words, rather than following their pre-SharePoint procedures, they'll quickly learn to open a browser, do a document search, open the found document, update it, send it for approval all centralized, and all through the browser!
Reality Check
But the double fantasy isn't how most people think or behave, much less work. That's not a slam against users; by nature, humans are creatures of habit. With the rush of daily business demands, old habits prevail. The first reality check when deploying SharePoint is to accept that fact. Deploying SharePoint without a structured SharePoint governance model will eventually lead to a return of the old, ineffective, decentralized information management habits you're seeking to solve.
Governing SharePoint requires a clearly defined and managed governance model consisting of user, contributor, approver and senior stakeholder roles, each with specific responsibilities and procedures.
SharePoint Touches the Entire Enterprise
SharePoint, and by extension portals, are not IT projects, they are strategic business and information management projects. Cross-functional governance is the key to implementing and maintaining an effective SharePoint portal. The best and most deeply embraced sites are owned by HR, Communications, or some other non-IT organization. IT is one of the key stakeholders, but the ongoing business information management should be assigned to a different body, outside of IT.
One large Canadian insurance company with 35,000+ users had the best model I've experienced. The governance model was led by a cross-functional Executive Steering Committee, while the site was managed by a collaborative and accountable Working Committee. Figure 1 illustrates the entire model.
TAGS:
portal, SharePoint, governance
Most Popular Stories
- 1 Use jQuery to Kill Spell Checker in SharePoint Lists
- 2 Developing SharePoint Solutions in Visual Studio Using WSPBuilder
- 3 Building SharePoint Suggestion Boxes and Soliciting Anonymous Feedback
- 4 Leveraging SharePoint as a Document Management System
- 5 Provide SharePoint Single Sign-On with Active Directory Federation Services
- 1 Building SharePoint Suggestion Boxes and Soliciting Anonymous Feedback
- 2 Leveraging SharePoint as a Document Management System
- 3 Solve Item-Level Permission Performance Problems in SharePoint
- 4 Provide SharePoint Single Sign-On with Active Directory Federation Services
- 5 SharePoint 2010 Makes the Link to LINQ
- 6 Developing SharePoint Solutions in Visual Studio Using WSPBuilder
- 7 Use JavaScript to Hide SharePoint's Quick Launch Bar


While Java helps in fulfilling the promise of "write once, use anywhere", there are practical concerns developers need to address in developing their code, whether it's porting from another language, working in the best IDE or optimizing for today's multi-core computing environments. This eBook will help you in understanding these issues and how you can get the most out of your Java code.