Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Instead of maximizing “benefit - cost” I would recommend maximizing “cost/benefit”.

The former will bias towards big tasks with big payoffs, but often there are small tasks with extremely good ROI, which will get lost if you just look at the magnitude of the net benefit.

But, +1 to the general approach of trying to put a number on it. Remember though, your numbers are uncertain, beware the McNamara fallacy.



I'm assuming that's accidentally inverted? Maximizing cost/benefit yields the most costly task for the least benefit.


Ha yes, ROI would be benefit/cost. Thanks!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: