Earlier quoted context omitted.
But rule-based processing was exactly the requirement. Why should the workflow automation come up with rules on the fly, when the rules were defined in the business process requirements? Aren't the deterministic rules more precise and reliable over the rules defined by probabilistic methods? Autonomy/automation makes sense where error-prone repetitive human activity is involved. But rule definitions are not repetitiv…
Sometimes the rules are not as easy to define ahead of time. As an example imagine having to categorize some sort of text based requests etc. Or decide what the next step should be based on freeform text, images, etc. Hardcoded rule based would have to try and attempt to match to certain keywords etc, but you see how that can start to go wrong?
Then over time their is a type of entropy with all business processes.
If we don't figure out dynamic systems to handle this it is hard to see how we get a giant productivity boost across the economy.
There is also the problem that what percentage of people even have exposure to the concepts of dynamic systems? When I was in college, I distinctly remember thinking dynamic systems, "chaos theory", was some kind of fractal hippy pseudoscientific fraud best to ignore.
I think of how often I hear the average person use language from probability theory but never from dynamic systems.