The cutoff between under-automating and over-automating is very abstract. While business rules and IFTT allows automation teams to provide significant value to their users, they sometimes struggle in deciding when they are over-engineering a process. As complexity rises, so does the Total Cost of Ownership, including development, maintenance and support, whereas marginal derived value decreases.\u00a0 Moreover, these rules may also sacrifice flexibility for repeatability, which is something that we do not always want.<\/p>\n
This begs the question “How can we better define the automation cutoff and how to best involve end users in this kind of decision making?<\/p>\n","protected":false},"excerpt":{"rendered":"
The cutoff between under-automating and over-automating is very abstract. While business rules and IFTT allows automation teams to provide significant value to their users, they sometimes struggle in deciding when they are over-engineering a process. As complexity rises, so does the Total Cost of Ownership, including development, maintenance and support, whereas marginal derived value decreases.\u00a0 […]<\/p>\n","protected":false},"author":4,"featured_media":0,"template":"","tags":[10,11],"cma_category":[7],"cma_difficulty_level":[],"class_list":["post-76","cma_thread","type-cma_thread","status-publish","hentry","tag-automation","tag-rad-tools","cma_category-rad-tools-low-code-application-development"],"yoast_head":"\n