My own approach i describe as multiobjective optimization but more based on simulated annealing/statistical mechanics) and deals with 'stopping times' rather than 'fail rates' though they are closely connected. I think maybe many EA affiliated people will not go through that whole paper--at least the few i've met. (I was told to get a CS degree either at UCSF where i had a job in theoretical biology or stanford, so i chose the 'stopping time' or 'fail rate'. I was pretty succesful at failing. Completed failing at 4 projects in 4 months. Condoleeza Rice also teaches at Stanford now---she helped win the war in Afghanistsan, Iraq, etc. No, good deed goes unrewarded.
Even smart people will often intuitively (that is to say, without realizing it, or only dimly realize it) shy away from the part of the project that would provide information that would tell them they're doing the wrong thing. This is part of the value of things like gantt charts and other project maps in that even though the plans they are typically used to generate fail when colliding with reality, they can alert you to ways you are fooling yourself about the most uncertain parts of a project.