Hacker News new | ask | show | jobs
by ThrustVectoring 4146 days ago
Since you want to do the features with the highest impact per unit effort first, the units used for estimates don't matter. You could replace a time estimate with a number between 1 and 10, and that's equivalent for prioritization purposes.

As long as you don't let the difficulty numbers get translated back into dates, you get the best of both worlds. You don't waste time on projects that aren't worth doing, and there's no deadlines and estimates to cause friction.