If you missed any previous part of this series, you can read them here.
In the series so far, we've talked about how accountability, quality,
appropriateness and restrictions have all been key drivers for why we need to
focus on governance for Microsoft SharePoint within our organizations.
To continue this series, I want to focus on another key area called
Discoverability. What does this term mean? It is the quality of the content
being discoverable (able to find information) within SharePoint.
Unfortunately, this also happens to be one of the biggest pains within
Now, you would think with an enterprise search engine, managed metadata
service application, content types with site columns, and versioning that
this wouldn't be so difficult. In reality, however, it can often make this
harder than just searching on a file system because the search cra... (more)
*If you missed part one of this series, you can read it here.
So far in this series, we've looked at business requirements that drive
governance - including accountability, quality, appropriateness,
restrictions, discoverability, and compliance. In this article, I wanted to
touch on how training requirements - and lack of them - can affect governance
In my travels, I speak with many large enterprise customers who often spill
the beans on the issues they are having with relation to SharePoint. One of
the biggest things I encourage is to get details on their plans a... (more)
In this post, I will cover adoption - one of the key things to be aware of
when you're aiming for high adoption levels is that without focus on the
aforementioned requirements, adoption will be low. I've been writing these in
order for a reason - in order to drive high adoption levels, you must be able
to address the other seven business drivers first.
Adoption is one of the key ways to measure the return on investment, and
overall success, for SharePoint as a service within an organization. What do
we mean by SharePoint adoption? Different organizations measure adoption in
How often has this happened to you: You're working on a project that needs
feedback from other members of your organization. You send out an email with
your project attached, asking some of your colleagues to respond with any
feedback they see fit. Soon after, you get multiple emails from various
colleagues offering suggestions and changes. Now you've got to aggregate all
of the suggestions back into your original document, hoping that none of them
conflict since your colleagues have no idea what they each suggested.
Sure, you'll likely get all of the information you need, but is ... (more)
If you've missed any previous part of this blog series, you can read them
When people think of "compliance" from a Microsoft SharePoint perspective, it
can mean a lot of things to a lot of different people. Every organization
will have different considerations for compliance: Essentially, which
regulations they need to comply with according to their specific industry
vertical, including HIPAA/HITECH, DOD 5015, Section 508 and WCAG 1.0 and 2.0.
There are two main drivers for compliance I see in organizations for
SharePoint, due to the risk of non-compliance and subsequent l... (more)