We are pleased to present below all posts tagged with 'Governance'. If you still can't find what you are looking for, try using the search box.
When introducing SharePoint, start with something that will benefit all users, and that is easy to manage. Start with Document Management. Here are 6 steps to get started with SharePoint for document management.
Does it feel like "collaboration" technology is disrupting your workplace instead of making it more productive, efficient and engaged? You're not alone.
In this article, I will introduce you to 5 different tools and methods you can use to gather SharePoint user adoption information so you can continuously monitor and improve your SharePoint intranet.
Sometimes saying "yes" to make your CRM users happy can create unnecessary complexity that chips away at the user experience and, ultimately, hurts adoptin. In this article we'll look at some helpful questions to ask before adding a new field to CRM.
Enterprise social communities have enormous potential for sharing knowledge, discovering new innovations, and boosting productivity. But without proper governance, they can start strong and end in a confusing and overly-complex mess! In this article I explore some practical tips for social community governance.
One of the things that I think most companies struggle with is governance, specifically in context of an intranet. If you read my blog you know I talk about mostly SharePoint, but good governance can and should apply to really to any platform.
We actually devote a whole section of our Building a Better Intranet workshop to governance because it’s that important, and yet so many companies don’t even think about it. In today’s post I wanted to pull out 3 tips that are important aspects of balanced governance.
No, that doesn't say Government gone too far (though that would certainly make for a very debated article). In our daily work, we see a lot of governance plans, and oftentimes an organization will come to us to help them “untangle” their governance plan, or with a challenge such as user adoption, that ultimately leads back to a governance issue. What I want to discuss in the article is something I have been seeing for the past few years, and talk about often. Governance that goes too far.
If you’ve been wanting to get some more information on SharePoint 2016, today’s recap is for you! I’ll briefly review some tips from the great duo of Todd Klindt and Shane Young on upgrading to SharePoint 2013, then I’ll dangle some awesome new not yet released tools for Dynamics CRM and Office 365 straight from the mouth of the great Girish Raja. I then got some great insights from the master Spence Harbar himself on OneDrive for Business migrations, then rounded out the day diving deep in the new hybrid search service application for SharePoint 2013 / 2016.
In today's tales from the field, I take you through each session of my day, but also give you a quick look back at something I omitted from the day 1 keynote. The sessions cover the gamut from information architecture and governance, to search, to OneDrive for Business and best practices for farm solution development.
I know what you’re thinking: we already have a project team, do we really need another formal team? After all, that only means more meetings, tasks, documents to write and manage, decisions to make, consensus to get, etc. My answer is a resounding yes, you most certainly need this team. But here’s the truth – while extremely important to the success of the project, this doesn’t have a to be a huge undertaking. This blog entry details 3 practical steps for you to begin building a SharePoint Leadership Team today.
Many organizations believe that thorough training is the only step necessary to ensure user adoption. That assumption could not be more wrong. Effective user adoption begins at the planning stage of a project, and is threaded throughout the life cycle. And the adoption process continues well beyond the initial training sessions.
When it comes to writing documentation, it is unfortunately one of those things that you will get to tomorrow, gets pushed because this server was down, or Bob needs his password reset. But I believe it’s important to at least have some form of documentation. This is important because:
Customer relationship management (CRM) projects are particularly difficult to successfully deliver. In fact, research into CRM project failures over the last 10 years has consistently found a failure rate between 30% and 70%. A quick scan of the proposals that we have delivered to new clients for CRM projects over the past 12 months shows that fully 59% of new clients who approach us are dealing with a need to administer CPR on their CRM implementation. This is true across all CRM products (we have seen failed CRM projects across virtually every CRM solution on the market). In this article I’ll take a look at one of the most frequent causes of failure that we have encountered and will offer some guidance for avoiding this (or for recovering if you’re already there). I will also be doing a deeper dive into this topic during our CPR for CRM Webcast.
In our day-to-day client work, one topic we are very passionate about is user adoption. We talk about this topic both internally and externally on a daily basis. After all, we should never forget for whom we are solving problems and building solutions. Put another way - if a car manufacturer builds 1,000 cars and no one buys them, then what was the point?
Although the idea of user adoption is not a new idea, we consistently find our clients asking for more ways or better ways to get users to “use the system.” Depending on the scope of the project, we always recommend some level of governance and training for our clients to get the most from their implementation. These are critical pieces of the overall solution that we feel play a significant role in whether or not the product is accepted or rejected by the users.
In addition, with the recent release of SharePoint 2010, this topic has once again become a priority for many of our clients looking to implement this new version. While superior to the previous version in far too many ways to mention here, the user interface has been completely enhanced with the “Ribbon” interface first seen Office 2007. For users of SharePoint 2007, this will be a slight learning curve to use the new interface, but as with Office 2007, once learned the productivity and efficiency will increase exponentially.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.