About seven years ago I was part of a star tup of technical writers for military manuals. I had worked with this group at our previous company and the group had many of the same problems, lost files, changes occurring that 'just happened', incorrect versions for delivery. The files were in SGML/XML, with supporting graphics, so a little different but the users were not software types who are used to digging in and figuring out tools.
When the company was setup, I was designated as the software support/IT person and I put my foot down, we were going to use version control. I selected SVN, using the TortoiseSVN client and I set up the first repository. We also had to share data with another company so I had to do some training and also provide support for this company long distance.
The first few months were a never ending set of complaints of how hard it was to use SVN, why is there is an error message when I try to commit, this is painful, we should go back to using a shared server drive, etc. I stood my ground and waited.
Then, it happened, one of the authors had accidentally overwritten a file that he had spent 2-3 days working on. In addition, the tech writers were learning a new way of tagging so there had been a lot of restarts and do overs and no one wanted to start from scratch. I came over, asked him when he had last committed and if he was okay with over writing the current file. He said yes, so I pulled out that last good version. After the tech writers looked over the file, he reached over and kissed me, a first for me. There were some more incidents of changes, someone overwriting another files, but most of the writers had some benefit after several months of use. After that, the complaints went down and we continued using the system I had setup.
Later on we used SVN to share files with the other company, including Excel documents used for tracking, a Word document for the style guide and other things. Now, 7 years later, the tech writers ask me to set up an SVN project when we start something new because it has saved them a lot of grief over the years.
In addition, the other company is now slowly implementing throughout their company because they have seen the difference it makes. I talked to the manager we had worked with a few years ago, she asked how difficult it was to setup. She wanted to set it up for other projects because she had noticed they never lost files, they always had the right version for deliveries unlike other projects. I was amazed to hear that entire directories had disappeared on other projects and they had no way of telling who had caused the problem
I have looked at other document management solutions over the years and I have been interested in possible solutions but SVN has always won out because of 1) No licensing costs required and 2) Low maintenance for myself and training time for the tech writers. I hate to spend a lot of extra time tweaking things, just because and the other company doesn't really have a lot of resources for that either so SVN works for our situation.
If our projects grew to a larger size, I could see looking at other options, but that would also mean that we would have more money for software licenses, help, etc. If it's a small business, without a lot of budget or expertise for version management or document management, there are worse things to use than SVN with the TortoiseSVN interface.