Live data from Hacker News

Why the last 20% of work takes the same amount of time as the first 80%

matvoz.com

1–10 of 55 posts

Re: Why the last 20% of work takes the same amount of time as the first 80%

#6
I knew a manager whose favorite saying was that we just needed to do the 20% of the work that got us 80% of the way there.

Well, needless to say, he never got a minimal viable product out there.

It definitely makes sense to be "lean" and not do anything that doesn't need to be done, but if you're lean you still need to complete 100% of the MVP.

Re: Why the last 20% of work takes the same amount of time as the first 80%

#9

Simple, when you said you where 80% done...you actually weren't (presuming your metric is time).

How to measure a project's progress? If time is your metric, then the last 20% should be done in 20% of the total time. (And that's right, when the OP says she was 80% done, she actually was 50% done.)

If your metric is something else, what could it be? And perhaps it is not the best metric after all: a loading progress bar that goes quickly to 80% and then slows down (by a factor of 4) until the end may not be the best progress bar after all.

I guess that the difficulty is to get a precise idea of the time you need to finish something.

Re: Why the last 20% of work takes the same amount of time as the first 80%

#10

Simple, when you said you where 80% done...you actually weren't (presuming your metric is time).

You have a very good point; it can be very difficult to judge how far you are through a project. In retrospect, time is often the best metric.
Post reply on HN