Precisely specify the need


The ‘dimensions’ for each feature must be precisely and entirely specified. It may be the image compression rate for the graphic interface, the maximum response time for a HTTP request or the number of items displayed in a list.
By ensuring the ‘dimensions’ and requirements for each feature best fit its purpose, you can avoid unnecessary quality. This is the opposite to usual convention. If it is not specified, the minimum quality or quantity should be used. For example, if the number of items in a list to be displayed is not specified, then it should be limited to 5, or the maximum number of items that can be displayed on the target application’s smallest screen.

Potential saving: Microsoft Research has shown that by changing the number of items displayed on the Bing’s results page, the underlying physical infrastructure (the number of servers) can be reduced by up to 80%.

This best practice should only be applied if it is coherent with your project's specifications.
Under CC-By-NX-SA license