Customization necessary in some cases
Posted: Tue Jan 07, 2025 9:20 am
A successful external SharePoint project
Symon GarfieldIn the breakout session of Symon, the keynote speaker from earlier in the morning, he showed the same slides as during the keynote session. This time, however, there was much more room for questions, discussion and depth. Symon again walked us through his reasons why his SharePoint projects fail. His reasons hardly deviate from existing lists, such as the well-known list of The Standish Group. What Symon emphasized even more compared to this morning was that the adoption of SharePoint must be part of your project plan. You have several techniques to ensure this:
Awareness
Communicate to your users that there is a problem with the current situation. There is a problem, so there needs to be a change. Involve your internal communications department in this!
Availability
Make sure the first impression is really good. If the first impression is bad, it is difficult to get people back into a positive mindset. For example, you can provide a first step-by-step plan that people follow (for example, creating a team site) and that they think after 15 minutes “hey, that's cool!”. You can also clear the environment every day, so that people can 'play' in the environment without any limits and don't have to worry about breaking anything.
Usage
Make sure you have a good manual, good frequently asked questions and don't forget: make sure the helpdesk is well instructed. You can also work with training videos.
Adoption
Make sure your employees keep using SharePoint. You do this by making SharePoint part of the work processes. For example, make a SharePoint training part of the introduction process for new employees.
Experiences with SharePoint as a basis for a website
During the breakout session 'Experiences with SharePoint as a basis for a website', Ruud Evers , senior content manager, gave a look behind the scenes at healthcare insurer VGZ . VGZ uses SharePoint as a CMS for their websites. At the moment, five primary websites (including one mobile website) and over 3000 microsites are managed via SharePoint. During the session, Ruud gave a number of beautiful and concrete examples of the VGZ website(s).
VGZ chose SharePoint because of its extensive end-to-end management capabilities. In SharePoint, it is possible to manage all sites from one platform. This ensures uniformity and consistency.
VGZ uses many of the possibilities of SharePoint. saudi arabia phone data For specific issues, they develop a custom solution within SharePoint. An example of this is a website module for taking out insurance.
VGZ Sharepoint
Disadvantages of SharePoint as a Content Management Solution
VGZ experiences a number of disadvantages when using SharePoint as a CMS solution. For example, the management of external web links is not included in SharePoint as standard. As a result, when URLs change, you have to adjust this manually in the various website environments. It can also take up to 24 hours before a change is implemented online. This can be adjusted manually. In addition, SharePoint is not yet optimally set up for search engine optimization. Finally, SharePoint 'conjures' with HTML/Javascript source code, which causes strange results.
Symon GarfieldIn the breakout session of Symon, the keynote speaker from earlier in the morning, he showed the same slides as during the keynote session. This time, however, there was much more room for questions, discussion and depth. Symon again walked us through his reasons why his SharePoint projects fail. His reasons hardly deviate from existing lists, such as the well-known list of The Standish Group. What Symon emphasized even more compared to this morning was that the adoption of SharePoint must be part of your project plan. You have several techniques to ensure this:
Awareness
Communicate to your users that there is a problem with the current situation. There is a problem, so there needs to be a change. Involve your internal communications department in this!
Availability
Make sure the first impression is really good. If the first impression is bad, it is difficult to get people back into a positive mindset. For example, you can provide a first step-by-step plan that people follow (for example, creating a team site) and that they think after 15 minutes “hey, that's cool!”. You can also clear the environment every day, so that people can 'play' in the environment without any limits and don't have to worry about breaking anything.
Usage
Make sure you have a good manual, good frequently asked questions and don't forget: make sure the helpdesk is well instructed. You can also work with training videos.
Adoption
Make sure your employees keep using SharePoint. You do this by making SharePoint part of the work processes. For example, make a SharePoint training part of the introduction process for new employees.
Experiences with SharePoint as a basis for a website
During the breakout session 'Experiences with SharePoint as a basis for a website', Ruud Evers , senior content manager, gave a look behind the scenes at healthcare insurer VGZ . VGZ uses SharePoint as a CMS for their websites. At the moment, five primary websites (including one mobile website) and over 3000 microsites are managed via SharePoint. During the session, Ruud gave a number of beautiful and concrete examples of the VGZ website(s).
VGZ chose SharePoint because of its extensive end-to-end management capabilities. In SharePoint, it is possible to manage all sites from one platform. This ensures uniformity and consistency.
VGZ uses many of the possibilities of SharePoint. saudi arabia phone data For specific issues, they develop a custom solution within SharePoint. An example of this is a website module for taking out insurance.
VGZ Sharepoint
Disadvantages of SharePoint as a Content Management Solution
VGZ experiences a number of disadvantages when using SharePoint as a CMS solution. For example, the management of external web links is not included in SharePoint as standard. As a result, when URLs change, you have to adjust this manually in the various website environments. It can also take up to 24 hours before a change is implemented online. This can be adjusted manually. In addition, SharePoint is not yet optimally set up for search engine optimization. Finally, SharePoint 'conjures' with HTML/Javascript source code, which causes strange results.