{"id":338,"date":"2011-03-24T16:29:00","date_gmt":"2011-03-24T16:29:00","guid":{"rendered":"http:\/\/joapen.com\/blog\/2011\/03\/24\/working-on-end-user-adoption\/"},"modified":"2011-03-24T16:29:00","modified_gmt":"2011-03-24T16:29:00","slug":"working-on-end-user-adoption","status":"publish","type":"post","link":"https:\/\/joapen.com\/blog\/2011\/03\/24\/working-on-end-user-adoption\/","title":{"rendered":"Working on end-user adoption"},"content":{"rendered":"
<\/a><\/div>\n

We\u00b4re working on a project where a solution is implemented on SharePoint.<\/p>\n

Last week I was on customer office assisting to the presentation of the solution.<\/p>\n

Apart of the details related to the project, at the end of the meeting I had the opportunity to talk to them about the users and their feeling about the tool.<\/p>\n

At this point they were seeing that the application still has some visual aspects to be improved, but in addition the usability seems to be one of the main concern. I was asking more about it and finally the main issue I see here with end-users is adoption.<\/p>\n

I asked them<\/u>: If this tool would be done in Lotus Notes, should we have any problem?<\/p>\n

Answer<\/u>: no, we have thousand LN applications, they know how to do it.<\/p>\n

For me the obstacle is not the application, the obstacle is that this is the first SharePoint application for this 300 potential users.<\/p>\n

Customer does not want to have thousand of help documents to introduce the application. I agree with them: they should not work on help documents to explain how to navigate on SharePoint and how to find the properties of a document, check out a document or other type of standard actions.<\/p>\n

My recommendation was to work with the people to adopt the SharePoint environment before to start working with the application:<\/p>\n