By &quot;business process workflows&quot; I&#x27;m referring to things like:
- I need to request vacation time, and my supervisor needs to approve it, and the request&#x2F;approval record needs to be kept
- This contract needs to be reviewed by me, then my division leader, then the law department, then we wait for the other company to sign it, and finally the President signs it
- I need to submit a reimbursement request. A clerk will review it for completion, then pass it on to a financial analyst, who passes it on to....<p>And we&#x27;ve all seen workflows that have a few caveats (if this person doesn&#x27;t approve, then this procedure happens) or a single point of failure (someone is out of the office for a week so it doesn&#x27;t move).<p>Many software applications have workflow designers built in - some basic, some advanced, but they&#x27;re often specific to that application. I&#x27;m wondering:<p>a) Do you use a generic workflow tool that you like?
b) If you were to design a generic workflow tool today, what would it look like?
Ask HN: What would business process workflow tools look like in 2016?