What do you like best?
Git is very widespread. I think nearly every developer has some experience with it, so it makes a good medium for exchange of and collaboration on code. Its popularity also makes for the availability of a lot of documentation and help. And it does the job for which it is intended.
What do you dislike?
My biggest complaint, in my own opinion only, is that resolving merge conflicts is harder than it should be. Also there seems to be more "religious wars" than there should be about how to accomplish some fairly common tasks. Lastly, at least in my own experience, discoverability (search) stinks.
Recommendations to others considering the product
Can't go too far wrong with Git, unless you really need to squeeze the last ounce of goodness from your version control system, in which case you'll want to investigate whether some of the more modern alternatives fit your needs better.
What business problems are you solving with the product? What benefits have you realized?
Git, along with some continuous deployment tools, gives us a single source of truth for our software; a focal point for discussion; a process by which experienced developers can help those with less experience in a particular area. Its popularity makes it easy to bring new people on board. The Gitflow workflow that we use helps us manage our development efforts and keep straight our various software versions.