Hey all, author of Designing and Engineering Time here. I am now a startup evangelist with Microsoft, but very happy to revisit this timeless (no pun intended) topic.
Remember that there is not only just actual duration vs perceived duration, but also how much users are willing to tolerate a delay, and whenever I get a question on how much people are willing to tolerate, I always ask if the users know/appreciate the value/return of what they are waiting for.
The delta between what was perceived and what they expect or are willing to tolerate, I submit, regulates user satisfaction. Some techniques manipulate perception, others manipulate tolerance (or expectations) - both are as effectively as actual code refactoring - but sure as hell cheaper.
Happy to share PDFs of the book and chat more. Ping me @steveseow
Remember that there is not only just actual duration vs perceived duration, but also how much users are willing to tolerate a delay, and whenever I get a question on how much people are willing to tolerate, I always ask if the users know/appreciate the value/return of what they are waiting for.
The delta between what was perceived and what they expect or are willing to tolerate, I submit, regulates user satisfaction. Some techniques manipulate perception, others manipulate tolerance (or expectations) - both are as effectively as actual code refactoring - but sure as hell cheaper.
Happy to share PDFs of the book and chat more. Ping me @steveseow