I believe that for the most part we are trying to use git as a chainsaw. The problems that we have run into usually stem from hand-jammed scripts that attempt

I believe that for the most part we are trying to use git as a chainsaw. The problems that we have run into usually stem from hand-jammed scripts that attempt to automate the process of creating release branches (hotfixes, etc). Not to mention the original workflow using git wasn't to actually use feature branches (either locally or remotely) and just use it like Subversion. Since we've introduced the git-flow scripts this has become easier because we can "abstract away" all of those operations. But this really just moves the cheese because then a majority of your developers may not understand how and what to actually do if presented with a real issue with git.