By automating these tasks, you’re taking the burden off of your IT department to manually perform each one, while empowering the end user to take some control of their own content
For example: when should you bring in the end users for their perspective on your SharePoint strategy?...End users who participate in the design of a system are more likely to support that system
My name is Larry and I am an end-user”. “Hi Larry”, the group responds……… Believe me; it takes a fair amount of courage or perhaps stupidity to acknowledge your membership in the end-user community in a public forum like this
I believe this is something missing from the community and I am hopeful this will help in the development of not only SharePoint end-user training for your organization but Train-the-Trainer and Power User Training for which EPC Group finds so valuable to ensuring a succesful SharePoint Implementation
no search term matches found in comments.
So community, what do you think about these approaches to making end users happy?...#questions #sharepoint #ScanningandCapture #katyperry #SharePoint #behavioralconditioning #end-users #training
This blog provides discussion around key ECM and records management design issues that cause end-users the most change impact. The suggested approaches have the objective of minimizing end-user impact to create a user-friendly system that will remove change barriers and greatly increase sustained end-user adoption. -- Change Barrier 1 - Excessive Metadata Entry One of the biggest impacts on the end-user when implementing an ECM system is the time it takes for end-users to enter metadata
If you look at the overall budget to implement a best practices SharePoint 2013 or 2010 implementation, is 5% of it around driving end users to actually use SharePoint?
This is directed RIGHT at end users (yes you, reading this at work), vendors please follow along, and be prepared. I really hope that you all have learned just how amazingly powerful your voice is as a single end user given social media
By this I am referring to fact that there may actually be more steps to accomplish the same functionality, as perceived by the end user
In both cases, the goal is to simplify, automate, and guide the end user's activities as they interact with SharePoint