I don't see how that's perception then? It was just made inefficient on purpose.
If I have to walk to the luggage area 10min and wait another 10min for my luggage it's not the same as if i walk 5min to the luggage area and wait 15min for my bag.
Yes, total time is the same but one scenario is acceptable because it feels inevitable and is under control (cannot personally move across space/time faster) the other is not because it feels like it could be improved (staff could unload bags faster).
The perception angle is: customers are less unhappy waiting the required 20 minutes for luggage to show up, if they're doing something else during that time.
In this example, the passengers are still waiting while moving (the wait for luggage is 20 minutes either way), they just don't perceive that portion of the waiting as intolerable.
Bringing it home to elevators, the situation is pretty much the same, only in reverse: someone who waits 2 minutes for an elevator and 1 more once aboard it to get to their floor, likely perceives their 3 minute total wait as less tolerable, than if they waited 1 minutes for the elevator plus another 2 once aboard.
Sure, but the perception is in accord with reality and in my opinion unchanging since the actual time waiting for luggage has been effectively reduced.
The only difference is the reality has been falsified
I think the best way to go about this is to start with a manually coded codebase outlining the basic structure of your app (even if ported from some other project) so that you basically define the code "palette" and THEN using AI to add features / edit stuff.
It won't do everything exactly the way you would've coded it but I find this model much better at setting and maintaining "guardrails" for your codebase so you don't find yourself wondering how it all fits together.
Such a shame because I hate the bigger size phones and I want a headphone jack!
reply