Governance is, without doubt, a big, hairy topic, but it’s made worse because the community has blurred concepts of governance with concepts of management. The way you deploy, secure, configure, and audit a service is—in services outside of SharePoint—called management. These are operational issues and one of the major concerns in operations is making operations more manageable—more automated.
Management is, in my opinion, close to the technology, as opposed to close to the business. It’s not a problem, then, that IT is responsible for managing a service like SharePoint.
A problem arises, though, when decisions about the architecture, configuration, and administration of a service are based only on how to make the service most manageable. What you end up with is a “locked down” service that can’t respond to the changing needs of a dynamic business.
A chasm grows between the business and the service. Users can’t get what they want done, and SharePoint’s reputation is sullied, even though it’s not SharePoint’s fault… it’s a systemic fault.