Governance is something that companies tend to think about on their second implementation of SharePoint.
Sometimes you have to go through the pain of difficult navigation (without a defined information architecture), tons of out of date content (without a content retirement policy), or searchability nightmares (after dumping gigabytes of unstructured data from a fileshare into SharePoint) to understand the value of a planned approach as opposed to a wild-west greenfield deployment.
There are certainly some templates from the likes of Joel Oleson and Paul Culmsee at the Governance Resource Center on TechNet, but dropping a 50 page governance document on a team that hasn't worked with SharePoint before will just cause eyes to roll back in heads.
Are there any useful strategies for communicating the importance of building even basic governance into a SharePoint implementation?