Master-SharePoint.com

User Non-Acceptance or resistance when adopting new systems and processes implemented using SharePoint can be quite common. Factors such as the computer skill level of end users and the process of implementing change in general can stop a user from wanting to use a new system or solution in SharePoint. If an existing system is replaced by one that uses SharePoint as a platform, many users will resist the change as they are comfortable with existing processes even if they are not efficient or effective.

There are a number of techniques that can be used to help improve the level of User Acceptance of a new system or process in SharePoint, such as working closely with the end users, or champions of a concept or idea to ensure that the system satisfies the needs of the individual as well as other. Knowing what people want, existing processes followed and how day-to-day work is completed can also assist, as it allows a solution to be designed an developed using SharePoint that is tailored to satisfy expectations of end users as well as higher level goals and objectives. Seeking out champions within a business is can be valuable when developing a solution, as they generally have a more passionate approach to strategic problem solving and being part of the process of developing innovative and effective ways to complete work more efficiently. These champions will often help others during the initial stages after the solution is put into production, and on an ongoing basis.

Part of the role of a developer or solution architect if available is to determine if the time and resources required to develop a solution is weighed up against the potential returns or cost savings that will be a result of implementing the solution. For example, if something is to take weeks to develop, but will provide minimal benefits a small number of users then the time would be better spent developing a solution for a larger number of users that may take a day or less to complete. The extent of customisation or development required to develop a concept or idea into a technical solution using SharePoint will vary between requests as well as the type of organisation with SharePoint.

SharePoint User Acceptance

It is not only important to involve users in the design and development phase of a solution, but to involve users in a test phase prior to implementing the system is essential to provide valuable feedback that may be required to fine-tune functionality or the user interface. Having users test the solution who have no have not been intimate with the development process is important as they will be able to provide a different opinion to that of the developers, as it will become harder for developers to put themselves in the shoes of end users after spending a considerable amount of time developing the solution.

See a more detailed incite on User Acceptance of Systems such as SharePoint, with a large number of end users.