Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

CHAPTER 10: Governance, Adoption, and Training - Pg. 189

C H A P T E R 10 Governance, Adoption, and Training Mary, Mary quite contrary, how does your garden grow? With silver bells and cockleshells and pretty maids all in a row. --Nursery Rhyme The focus of the material we've covered in this book so far has been on how to design and build a SharePoint solution that meets the needs of your users and stakeholders. But what happens after that? You've created a great navigational structure, you've designed functional and usable pages, and you have created metadata that make your information easy to find. Do you just hand over the keys to your users and say "Done!"? I hope your answer to that question is "No." Your beautiful site is like a garden, it will soon become overgrown with weeds, and all the carefully cultivated plants will die if they aren't taken care of. Tending your SharePoint garden is an ongoing task; you need to assign people to care for it and care about the outcome, and they need to be people who know what they are doing. To stretch the gardening metaphor a little further (maybe too far?): You also can't just hand over shovels and seeds to people who are going to fill in some of the empty spots you have left for later expansion. The work they do has to fit in with the original plan so that the whole system will fulfill its purpose and so the garden will "make sense" to those who use it. This chapter discusses three main elements that work together to ensure your SharePoint garden flourishes after delivery day: governance, adoption, and training. These three elements are deeply intertwined: Governance helps to drive adoption, as does training. The training function can be used to enforce the governance policies, leading to a better, more efficient environment, which is, in turn, more likely to be adopted. Governance and Adoption While thinking about SharePoint governance, remember (from our discussion in Chapter 4): There is a difference in approach between what I've labeled as above the line versus below the line. Above the line refers to the portal areas that contain content meant to be carefully controlled; it is consistent and reliable. It is content prepared by relatively few for consumption by relatively many. Below the line is where collaboration takes place, and it has to allow for less control and more freedom. This is where work-in-process happens, and there may be many private areas, or at least areas that few people visit except those on a particular team or on a particular project. 189