4 ms·
No one has yet managed to build the workflow management that is needed for this. The best efforts I have seen to date are Docracy and Contractual.ly. But neithe
by zekevermillion 10y ago
No one has yet managed to build the workflow management that is needed for this. The best efforts I have seen to date are Docracy and Contractual.ly. But neither quite got it right. It is an interesting problem, and seemingly straight-forward to solve, yet it is a graveyard of failed attempts so far...
- Jtsummers 10y agoIs the workflow uniquely complex? It was never my job but I've seen (trying to remember what we used) some pretty complex workflows for handling requirements documentation, testing, and code development (reviews and such, specific tasks handled in JIRA) handled pretty effectively. Would've been one of the Telelogic (now Rational) tools.
- zekevermillion 10y agoI doubt the workflow could be any more complex than what you have seen. In many ways, it should be less so. There are some nuances, however. Partly the problem is the extreme egos involved in many business negotiations. Every communication sent has to help the sender to look good. There has to be a bias against publicizing changes before the author is done. There also has to be flexibility to override approvals. A lot of big deals would never close if someone had to take personal responsibility for waiving closing conditions that aren't satisfied at closing.
- Jtsummers 10y agoRegarding hiding changes until they're done, that shouldn't be in feasible except that you (or your counterpart) may not want to use a system owned by the other, because you lose that guarantee. A third party hosting it could offer that (naturally), but takes on extra liabilities with securing the documents in progress.