Most CMS packages get purchased for departmental installations. Then, when buyers wish to extend content management capabilities to other departments -- let alone the entire enterprise -- developers have an exercise in refactoring: making the implementation (not to mention the content!) more abstract and re-usable. This is supposed to be the forte of object-oriented languages (like Java), and the CMS packages that employ those languages, and the wonderful IDEs that automate this process. But refactoring is never easy, and a lot still hinges on your broader development methodologies. Adherents of scripting languages (e.g. the Perl beneath Interwoven or the Python powering Zope) argue for rapid application development; the OO people retort that this approach won't scale. We tend to believe the latter camp. But perhaps the bigger issue, as Infoworld's Jon Udell points out, is how to better incorporate business people into process modeling...
Read Udell's Article on Refactoring