The first part of this article looked at how a CMS project differs from other projects. This part will look at how the transition from traditional web publishing processes to a CMS world changes people’s lives, and how to best hand-hold them trough the transition. It also looks at how the processes transition is best managed (which at the end of the day is also more about people transitioning than artifacts moving through process).
In the first section, I’ll describe why the transition is something that needs particular attention at all, and why failing to do so will put the success of your CMS journey at risk
After that, we’ll take a closer look at some examples of processes that change.
Finally, I’ll offer suggestions how to soften the risks and make the transition from traditional web publishing to the CMS world enjoyable for everyone.