> How can an organization complete the most goals in the least amount of time, eking out enough surplus to keep the crank turning? Thin rules may be quicker to infer results from than thick rules, though they are likely to be wrong in unsatisfying ways. Which region may work best for this goal? How should rules be designed and optimized for speed?
These questions focus too much on speed. Rules aren't a technology for going as fast as possible, they're for going as fast as necessary to make good decisions. Speed helps adapt to a changing environment, but only up to a point. And goals are usually not a checklist to be weighed by the bushel. Instead I prefer the framing of decision trees rooted in a single goal that you hit or hit not. There is no partial credit.
> How can an organization complete the most goals in the least amount of time, eking out enough surplus to keep the crank turning? Thin rules may be quicker to infer results from than thick rules, though they are likely to be wrong in unsatisfying ways. Which region may work best for this goal? How should rules be designed and optimized for speed?
These questions focus too much on speed. Rules aren't a technology for going as fast as possible, they're for going as fast as necessary to make good decisions. Speed helps adapt to a changing environment, but only up to a point. And goals are usually not a checklist to be weighed by the bushel. Instead I prefer the framing of decision trees rooted in a single goal that you hit or hit not. There is no partial credit.