From our experience and the many conversations with have with our customers: it depends.
We use both git/GitHub and LayerVault internally to build software, including the site where you're reading this very comment.
For tracking ideas and capturing the creative process, LayerVault or a tool like it is better. It's designed to set-it-and-forget-it while you work. Organizing your work is something you do after your work is done.
Git, or even naming you files "final-final-final," require you to stop thinking about creation and be more deliberate with your file management. For many situations, this is not a bad thing. There's a reason why we use git to track code, and other tools to track design. The place where that line gets a little fuzzy is when you are translating designs into code, or shipping designs to a production environment.
On the whole, using a version control system is never a bad proposition. It takes a little bit of work to give you peace of mind and a lot more flexibility.
From our experience and the many conversations with have with our customers: it depends.
We use both git/GitHub and LayerVault internally to build software, including the site where you're reading this very comment.
For tracking ideas and capturing the creative process, LayerVault or a tool like it is better. It's designed to set-it-and-forget-it while you work. Organizing your work is something you do after your work is done.
Git, or even naming you files "final-final-final," require you to stop thinking about creation and be more deliberate with your file management. For many situations, this is not a bad thing. There's a reason why we use git to track code, and other tools to track design. The place where that line gets a little fuzzy is when you are translating designs into code, or shipping designs to a production environment.
On the whole, using a version control system is never a bad proposition. It takes a little bit of work to give you peace of mind and a lot more flexibility.