Discover and Recover

September 24, 2010

Softening strict requirement of optimality can make problems tractable. Put it another way it is more important to quickly narrow the search for an optimal solution to a “good enough” subset than to calculate the “perfect solution.” Ordinal (which is better) before Cardinal (value of optimum).
Compare the two scenarios presented below:

  1. Getting the best decision for certain – Cost = $1m
  2. Cost = $1m/x – Getting a decision within the top 5% With probability = 0.99*

In real life, we often settle for such a tradeoff with x=100 to 10,000

For systems that are not life-threatening, the focus should be on fast fault detection and mitigation (discover and recover) instead of exhaustively trying out every possible scenario which will make the system perfect but at such a cost that forward progress turns glacially slow. At which point your quicker, nimbler opponents will run over you with their faster product cycles.

People constantly deceive themselves into thinking that by paying much more they are getting a 100% solution but in reality you never get a true 100% solution, so its really a choice between different levels of less than perfect.

*Under independent sampling, variance decreases as 1/sqrt(n). Each order of magnitude increase in certainty requires 2 orders of magnitude increase in sampling cost. To go from p=0.99 to certainty (p=0.99999) implies a 1,000,000 fold increase in sampling cost.


Cardinal vs Ordinal work by Dr. Yu-Chi Ho

Satisficing (wikipedia)