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
different ways:
Size of Data in SharePoint
Reduction in file share data size Reduction in attachments in emails and
email traffic due to collaboration Average number of concurrent users in
SharePoint during work hours Average number of unique visitors per work day
Engagement of employees from al... (more)
In a webinar entitled ‘Business Drivers and Checklists for Successful
SharePoint Governance', Randy Williams, SharePoint MVP and AvePoint
Enterprise Trainer & Evangelist, and I discussed the business drivers that
come from individuals outside the IT department for SharePoint as a service
within an organization. These drivers often result in policies being defined
to set the expectation with the business and to focus alignment with the IT
department.
Over a series of posts, I will focus on horror stories, from some of our
8,000+ customers we have here at AvePoint, which provided ... (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
for SharePoint.
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)
If you've missed any previous part of this blog series, you can read them
here.
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)
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
organizations t... (more)
Jeremy Thake is AvePoint's Chief Architect. Jeremy’s 10-plus years of experience in the software development industry, along with his expertise in Microsoft technologies, earned him the label of “expert” in the global SharePoint community. He was named a Microsoft SharePoint MVP in 2009, and continues to work directly with enterprise customers and AvePoint’s research & development team to develop solutions that will set the standard for the next generation of collaboration platforms, including Microsoft SharePoint 2013.
Charles Araujo
Emily Jackson
Brendan Harding
