Comments about

>Opposition to centrally imposed tools, framework,
>approach -- want to do it their way

The "imposition" is due to:
- the content has to be published on the web using the corporate image of the institute
- the institutional content has to be accessible and available to EVERYBODY for multiple purposes (a news should be available for the web, for an newsletter sent via email, for the RSS system, etc.) and this requires centralization in a unique datasource (our databases)
- there is huge effort to centralize data within a single centralized "Institutional Databases", and decentralization process could run against it.
- different technology/framework, etc. require support and definition of its institutional life cycle: installation, customization, maintenance (backup, human resource allocation to support it, updates, training, etc.).
- approval process tools could not work on decentralized systems
- web master could find problems accessing decentralized systems
- several decentralized systems could create confusion of roles: content providers that spend time trying to find out bugs, customizations that produce content not compatible with institutional image, etc. etc. etc.