<aside> ▶️ Productivity soars when a computer and its users interact at a pace (<400ms) that ensures that neither has to wait on the other.

</aside>

The Doherty Threshold is the idea that users and systems shouldn’t have to wait on each other. At first, I didn’t really understand how this would be applied, as surely there are instances where a system will take a long time to do something, but actually, this then relates to the visibility of system status. It’s important to consider the length of a task that will take a system, and what sort of visual feedback is required. If a system will only take a maximum of 10ish seconds to complete, then a spinning loading animation would be appropriate, but if it may take a minute or two, then a progress bar with percentage would be needed. This way, the user isn’t left guessing as to what is going on and is getting continuous feedback. This was interesting to me and something I probably hadn’t really considered before, but have done without knowing. Understanding this will help me to make sure to consider the length of processes and what design elements would be appropriate.