I refuse to work without it, which means anyone involved in the project must also use it. It's just good practice.
That's a GREAT attitude, right up there with 'not my job!' :-)
The best way of getting buy-in is using something like TortoiseGit or TortoiseSVN to integrate version control into Explorer (assuming Windows). It takes time to see real benefit if you're not used to the version control paradigm. Tortoise at least makes it easy to work with VCS with the mouse. A simple "Right Click -> Checkin" is all it takes.
For this reason, I've been looking to implement transparent version control in TortoiseGit on every file close. If you give someone a branch to work on, and then every write/close becomes a commit operation, then at some point you as the developer can merge their branch without worrying about the consistency of the entire repository, and they can get on with the business of doing what they do without having to know about version control.
I have this same problem with a huge set of audit documents that I can't get people to version control, so we have 50 versions of the same document floating around that are all subtly different.