Thanks for this reminder, SP B and B and thanks to VP at LC for reblogging this very helpful post. It’s a reminder to all the SharePoint peeps. If you can’t get beyond #1, your hopeful project doesn’t have a great chance in H3!! Don’t get me started about folders…
Microsoft SharePoint is a very popular system for building collaborative intranets in organizations large and small. It is a very flexible platform, and it’s relatively easy to build a site with lots of features such as document libraries, task lists, calendars, and the like. Many organizations, however, jump right in without understanding the ins and outs, and without understanding how existing process might need to change to make their SharePoint site all it could be. Without that understanding and effort, you might end up with a bad SharePoint implementation.
What’s the downside of a bad SharePoint implementation?
It’s a truism in life that people don’t like change. If they see no advantage to SharePoint, they will drag their feet in using it. If it’s difficult to use, they won’t use it. The key to having a successful – and helpful – SharePoint implementation is
View original post 831 more words
Shewrite63 