And still, Git, compared to most centralized VCSes, forces you to consciously design the versioning workflow. Where will the repositories be, who pushes where under what circumstances, what repo makes the golden releases, will you merge the upstream into feature branches or will you rebase, all that.

That makes it harder to introduce Git in an organization where nobody brings along enough Git experience to design all that upfront.

Just grab the gitpro book and spend 3 minutes copying one of the diagrams and the description (or use the website).

I understand what you're saying: I have helped some friends who were that guy trying to bring it in.

It's easy to use Git in exactly the same way you would use SVN with a single central repository.

Looking into what you said, that is what happened.

I'd always heard that said about the tool we used today to point out "It does way too much for a single SCM, you have to find what YOU need a SCM to do and use that".