Glossary » 123
2-second rule
A loose principle that a user should not need to wait more than 2 seconds for certain types of system response, such as application-switching and application launch time. The choice of 2 seconds is somewhat arbitrary, but a reasonable order…
Read more »3-click rule
The principle that access to any feature of an application, or each logical step in a process, should require no more than 3 clicks. Applying this principle can be tricky because of the ill-defined nature of what constitutes a primary…
Read more »80/20 rule
A principle for setting priorities: users will use 20% of the features of your product 80% of the time. Focus the majority of your design and development effort (80%) on the most important 20% of the product.
Read more »