Automation eliminates value but not risk: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{a|design|}}If you can automate something, you can’t monetise it. You automate, therefore, as a ''defensive'' strategy: because everyone else is automating, and if you don’t, your unit cost is higher. But (rigorous and competently executed) automation can remove ''micro''-risks — risks that are intrinsic/internal to the process being automated; you can iron out the inconsistencies, foibles and errors of the [[meatware]] — but not the extrinsic risks that arise from the interaction of your new automated process with the outside world. those are [[emergent]] risks, impossible to see at the level of the process (certainly when a machine is carrying out that process), but that are a function of [[complexity]]. | {{a|design|}}If you can automate something, you can’t monetise it. You automate, therefore, as a ''defensive'' strategy: because everyone else is automating, and if you don’t, your unit cost is higher. But (rigorous and competently executed) automation can remove ''micro''-risks — risks that are intrinsic/internal to the process being automated; you can iron out the inconsistencies, foibles and errors of the [[meatware]] — but not the extrinsic risks that arise from the interaction of your new automated process with the outside world. those are [[emergent]] risks, impossible to see at the level of the process (certainly when a machine is carrying out that process), but that are a function of [[complexity]]. | ||
{{sa}} | |||
*[[Proprietary information]] | |||
Revision as of 17:18, 23 February 2021
|
The design of organisations and products
|
If you can automate something, you can’t monetise it. You automate, therefore, as a defensive strategy: because everyone else is automating, and if you don’t, your unit cost is higher. But (rigorous and competently executed) automation can remove micro-risks — risks that are intrinsic/internal to the process being automated; you can iron out the inconsistencies, foibles and errors of the meatware — but not the extrinsic risks that arise from the interaction of your new automated process with the outside world. those are emergent risks, impossible to see at the level of the process (certainly when a machine is carrying out that process), but that are a function of complexity.