When, I think of SharePoint workflow I think of a business process that is automated, like taking the need for feedback on a file or approval of an item out of your email and into a place where it is easily tracked, monitored, managed and reported on. We are bombarded with so many emails everyday, it is hard to keep track of tasks we receive via email and while we often use it to store approvals and copies of files, it was never intended to be used that way.
By taking the file we want to collaborate, putting them in SharePoint and starting a feedback workflow, we can ensure it is routed to the appropriate parties, that everyone is working from the latest version of the file, send automatic notifications as users complete their feedback tasks and ultimately store their task completion for compliance and reporting purposes.
Much like forms, workflows have improved from SharePoint 2010 to workflows in SharePoint 2013. The SharePoint Workflow manager was introduced and allows for an organization to run this process on its own server and therefore run many workflow processes simultaneously without worrying about bogging down the rest of their SharePoint solution, which was a problem with workflows in SharePoint 2010.
SharePoint comes with a few out of the box workflows and with just a little knowledge transfer your business users can easily implement them to handle simple feedback and approval tasks in a more automated and efficient way. It can help your team identify bottlenecks and improve corporate compliance.