> Amount of work done is a poor way to phrase it. Amount of work done is a poor way to phrase it. I mean something more along the line of "business value produ

> Amount of work done is a poor way to phrase it. Amount of work done is a poor way to phrase it. I mean something more along the line of "business value produced". My previous job was leading a team responsible for scaling a Postgres cluster with ~1PB of data. A number of big wins would come from relatively small changes. You can apply the post just as well to finding the biggest wins in the shortest amount of time.