The lesson I learned was: Prescribe everything about the workflow because nobody is going to learn git. They'll skim your baby's-first-commit page on the internal wiki, but you better put everything important above the "push" section of the tutorial because that's where they'll stop reading.

All the nice flexibility of git just becomes risk. By the time you have enough structure in place that your team isn't shitting up the repo left and right, you might as well be back where you started: source control you hate, with zero flexibility, and you're secretly using git locally on the sly.

The only person who bothered learning git was a summer intern. And he mastered it, so I know it's not that hard if you're still willing to learn.