[carlosjobim]

I think that's more of pseudo-science. I've never heard anybody express any distrust for a service just because it's fast.

Let's say you go to a store and ask if they have a certain product. The clerk says "Sure, here it is". Is that worse than saying "Hmmm, I have to check in the warehouse first"?

[kepler]

A more suitable comparison might be this: envision yourself at a Michelin-starred restaurant, placing an order, only to have your meal instantly served. This leads to a crucial question: would you prefer to represent the immediacy of a fast-food establishment or the meticulousness of a Michelin-starred restaurant? Ultimately, HCI aims to create solutions that mirror the conceptual models of the real world.

[carlosjobim]

Funny example! I used to work in a place like that, and we could make many plates extremely fast, and sometimes getting a head start from overhearing the clients order while they were still talking to the waiter. And yes, sometimes we would wait a little bit to get the food out, just because it would be weird for the client to get his food instantly.

But apart from that, clients usually appreciated getting their food about twice as fast as they would normally expect. As long as the quality is there, nothing is wrong with speed. And a restaurant is kind of a poor comparison, since cooking is always time dependent, while other goods can be ready for purchase at once.

[kepler]

My point is, context shapes the approach in computer interaction. Certain actions like ordering Uber involve wait and load times, while others don't. Theee is no one-size-fits-all solution. The system should harmonize with the user, bridging the gap between existing conceptual models.

[carlosjobim]

If we go back to the original example. Some hotel booking aggregators still show the fake "Looking for best deals..." popup or screen. The largest aggregator Booking.com doesn't show any such thing, but instead loads the results as fast as it can.

As for disorienting, there are ways to avoid that without slowing the user down - I think in almost every situation or use case.

[somat]

On the other hand I can imagine there being some sort of study that claims that having to "check the warehouse" makes the client now invested in the process and more likely to complete the sale.

I get it, sales and marketing are an essential part of doing business, you will not have a business if you can't sell anything. But it is an inherently evil practice, the whole goal is to coerce somebody into doing something they would not have other wise done. When kept to a moderate amount this is not a problem, the business sells things the customer gets things, everybody is happy. But sometime the marketing department can push thing to a very unhealthy level, psychological manipulation, dark patterns, obsessive tracking, etc.

[lexicality]

Wrong analogy, imagine you ask where the butter is and they answer "aisle 14" and turn away before you even finish speaking. The butter might be there, but it will feel at least a little like they were saying anything to get rid of you.

Humans want things to operate at human speeds and computers are way faster than that.

[JohnFen]

> The butter might be there, but it will feel at least a little like they were saying anything to get rid of you.

But that's because you're interacting with a human and that sort of behavior from another human typically indicates a kind of hostility.

Interacting with software is nothing like interacting with a human, and doesn't trigger those human social cues.

[carlosjobim]

If the software is fast, you ask for the butter and he puts it right in front of you. I say fast interactions and response is always better than slowness or fake loading screens.