A good article by Nitin Mehta on motivation for content migration. My experience has been the same. A few lessons learned:
1. Make sure you have a motivation for a migration. It is not enough to say I want to standardize on a specific platform if you have not committed a strategy and resources to it.
2. Make sure you are gaining value. Standardizing is not enough. Value can be in terms of better content control, easier content creation, better content search and analytics, and what have you. Whatever it is, estimate ROI gains.
3. Make sure the scope is understood or you could end up spending a lot of content that is no longer useful. Keep the users involved.
4. Don’t just pick a solution vendor. Have your incumbent vendor involved in the project. I bet you that you can find better Sharepoint or Oracle expertise from an incumbent resource than you would from Microsoft or Oracle. The incumbent knows your content and processes and they may be able to do a better job.
Read more...
1. Make sure you have a motivation for a migration. It is not enough to say I want to standardize on a specific platform if you have not committed a strategy and resources to it.
2. Make sure you are gaining value. Standardizing is not enough. Value can be in terms of better content control, easier content creation, better content search and analytics, and what have you. Whatever it is, estimate ROI gains.
3. Make sure the scope is understood or you could end up spending a lot of content that is no longer useful. Keep the users involved.
4. Don’t just pick a solution vendor. Have your incumbent vendor involved in the project. I bet you that you can find better Sharepoint or Oracle expertise from an incumbent resource than you would from Microsoft or Oracle. The incumbent knows your content and processes and they may be able to do a better job.
Read more...
RSS Feed