Perceived Performance

An office building got complaints about slow elevators. The owners priced out expensive mechanical upgrades. Then someone installed mirrors in the lobbies instead, and the complaints dropped immediately. The story may be apocryphal in its details, but the principle is well documented: how long something feels and how long it actually takes are two different numbers, and the gap between them is a design opportunity. That insight produced skeleton screens, optimistic UI, and progress bars that quietly accelerate at the end, and research stretching back to operations work in the 1980s on why waits feel long.

For anyone building a product, this is a case about the slowest moment in your user's experience, and whether it is genuinely slow or just feels slow because nothing is communicating that progress is happening. It sharpens what to do when actual speed is expensive and hard to win. What makes a wait feel shorter without lying to anyone, and the hard limit on how far perception can carry you before real engineering has to take over, is the part the app saves for you.