People spend too much time on decisions with equally satisfying outcomes
robkhenderson.substack.com
robkhenderson.substack.com
If an option is perceived to be significantly better, then the decision can be made quickly.
Otherwise more study is required to decide which is better, or if they are actually indistinguishable.
It's the same reason why more trials of an experiment are required to reject the null hypothesis when the effect of the experimental variable is very weak. This is analogous to considering the options in your mind until you decide the difference between them is too small to matter. That takes time!
Sometimes after deep thought, you may decide one of them is actually better, but not by very much. Obviously you could argue that time is wasted for such a small benefit, but it's not a paradox.
Introductory statistics tells us we can never prove the null hypothesis; all we can do is reject or fail to reject it. In other words, you give up on the attempt only after deciding extended study is unlikely to reject it.
it's because people have the irrational belief that their thinking and reasoning more about a problem/decision makes their outcome better.
I think the common symptom found in software is design analysis paralysis. A software team end up using tonnes of time fretting about design choices (often as a committee), rather than just use that time to implement one of the designs. The (ir)rational idea that by reasoning about the design up-front, one saves the (potential) time lost in reimplementing a different design in the future!!
The result is engineers sat around muttering "I told you so" to themselves and wasting weeks debugging and hacking around bugs.
In some cases we've deployed, found horrible problems that were completely unexpected and switched course.
Additional time spent agonizing would just have delayed getting us to the point where we learned those things. The critical information we needed to make that decision wasnt going to reveal itself with additional introspection.
This isnt to day when a dev waves a big red flag in the beginning you should ignore them, though (ever). But, I find that waving that red flag doesnt ever inhibit delivery speed whereas multiple people agonizing over decisions where the information to determine the "right" one usually does.
Also some people strongly prefer action over deliberation, especially by a committee so there is also a psychological cost to the team to consider.
With software and a capable team, there can still be an illusion that decisions are cast in stone and can't be changed later, while the opposite is true.
Implementing a solution that is almost there and then making corrections can be both more satisfying and lead to very good results. This of course requires the psychological freedom an flexibility to quickly acknowledge errors in thinking and design and not holding on to "the plan" too tightly.
i'm not sure this is correct. i bet it often comes down to whether we've found an [emotionally] satisfying answer/outcome.
If you have no way of knowing which choice is better then you would flip the coin of course. The problem is there typically is a way to possibly learn more about which is better, AND HOW MUCH, by studying the choices. The "How much" -part is crucial. One choice might lead to core meltdown.
Often such study does not provide any further information about which is better. But it might. You just don't know. Except if you are lucky and the answer is immediately obvious.
So if it looks like you have two choices A and B, it is more typically the case that you in fact have THREE choices:
1. Choose A
2. Choose B
3. Spend more time studying which is better, and how much, A or B
If the choice doesn't matter much, then both options are equally good.
E.g. "should I get this pair of shoes or that? I like both".
Just get one and get on with it.
"Should I go to Paris or Vienna for a short trip?"
Just pick one and get on with it.
Still people obsess for these kind of choices for needlessly long...
The case discussed, were people waste time they shouldn't, is (a) when the choice doesn't matter much or (b) when you do know that either option would be more or less fine (which is basically a variant of (a)).
If (c) you can't tell if they're equally good AND chosing the right one does have a BIG impact, then this case doesn't fall under the advice of TFA or what we discuss here.
Rather, it's an "ipportant choice" and people should think it over...
Based on my own experience as a SW developer I have found that more often it is hard to know beforehand whether a design-choice matters much or not, and how much.
I suppose that is also the reason for much of "Technical Debt". People make less than optimal design choices not because they are bad designers, but because trying to evaluate the benefits of each choice would be too time-consuming.
You spend a fixed amount of time, if no choice could be made during this period, then flip the coin.
The fixed amount of time could be as short as five seconds. Or the amount that makes sense to you, and you feel comfortable with. If it's one week for you, then it is.
It's of course possible to be wrong in either direction -- this difference matters though i think it doesn't and vice versa -- but in general, we tend to be pretty good about taking seriously the things that really are serious, but pretty bad at not wasting time on things that don't matter much. This shows up in the paradox of choice, but really just imagine someone hemming and hawing over two brands of cereal in the aisle at Trader Joe's and you get the picture.
So the practical problem isn't really "how do you know until you analyze," because we more often fall into opposite the trap and waste time systematically attempting to optimize choices where there is little value to be gained. We should step back in more cases and remind ourselves that most differences make no difference at all. Save your time and energy for the ones that do.
Big decisions are often like icebergs. Most of the important stuff is hidden below the surface. No matter how much you analyze the tip you still have an essentially 50% chance of getting the decision wrong. It's really hard to make a major decision knowing that you have a 50% chance of getting the decision wrong, but over-analyzing the tip of the iceberg is not going to improve your decision making.
There are a lot of insightful heuristics from decision making that can make big decisions much better/easier/etc.
I don't think people would spend any more time on big decisions if they made faster/fewer decisions with little "value" to gain, if anything I think their habit of making fast decisions would mean they spend less time/worse on the big ones!
And no doubt that sometimes it's just nice and pleasurable and interesting to deliberate over anything at all, making small things grand, but it's also good to know when it's actually optional.
The reason "obvious" choices are "easy" is not because of the difference in actual utility, but because of the difference in "obviousness". I.e. it relates your observation to the probability that it does indeed relate to a difference in utility of not.
Therefore, two options with "similar visible utility" require more effort discerning whether the "actual" utility is also small, or you're about to make a very big mistake based on superficial notions of "no visible difference".
I content that given knowledge of actual equivalence, the paradox goes away and choices become trivial again.
A good example is phone contracts (at least in the UK). You'll spend far more time weighing options if they're bundled with all sorts of dark pattern magic like "first 3 months free then £X plus promo vouchers in select stores", compared to when you only have the annual price to compare between two choices. But it wouldn't matter if that price difference is £100 or £1.
A) the benefits are higher than you think: e.g. little did you know it but they have an unusual mouth microbiome which means some toothpastes will work and the rest will turn them into a wimpering ball of cavities within the week. They don't quite remember /which/ ones though and are trying to figure that out.
B) the costs are lower than you think: this friend is funemployed and has nothing else they would rather be doing with their time, in fact they find a great deal of satisfaction from knowing they have "optimized" every area of their life by spending more time on their decisions.
At which point both of them will have been upgraded with different ingredients.
> Sometimes after deep thought, you may decide one of them is actually better, but not by very much.
I feel like the value here is simply not for the decision at hand. It's that you learn something for future decisions.
When the options are very close, there's not much value to be gained for this decision, but it indicates there is something new to learn. When the options are obviously far apart, there's nothing to learn.
I've thought about this on and off in the context of poker. When you're playing 24 tables at the same time you simply can't waste focus in the moment on the close calls unless the pot is big. Instead, analyze the things you think are close calls offline.
1. That the decision-making activity itself is wasteful. 2. That the decision-making time would, if not consumed by decision making, be spent elsewhere in a more productive manner.
These are hardly safe assumptions. The discussion itself can be enjoyable. The faster decision making can create less certainty in the decision and encourage regret, or create conflict with others. The time gained may not be spent in any productive manner but instead be wasted elsewhere.
I'm not sure which decision is better, considering they are so different and probably are not comparable. I just chose to do a postgraduate degree that seems more interesting, and leaves me more options later, rather than going to the industry which can make more money.
To dive into your setting: one challenge is that there are multiple optimisation strategies. Do you want to avoid risk as much as possible? Do you want the largest possible income? The highest job satisfaction? The best career path? Etc.
Note that even if you pick one of these as your sole optimisation factor, the choice is not clear. Eg. an industry position can make more money... or you have not-great luck, a string of mediocre jobs with little career growth and little payout. Or even bad luck and end up in jobs where you're a bad fit, learning nothing of career value to you and burning out repeatedly.
On top of that, any advice from experience would be tainted by survivor bias and its inverse; that is, "i liked the outcome, so do that" / "i hated that outcome, so don't do that".
Lastly, it isn't even clear (not can it ever be determined) that the downsides of choice paralysis are worse than the downsides of making the "lesser" choice. Maybe driving people this mad beats having to live in their couch for 6 months. Or maybe it doesn't.
In the end, your alternatives present a very complex scenario, in which no alternative can be fully explored without committing to it.
"Sometimes the decision-making process itself is pleasurable. Even if all outcomes will be equally rewarding, spending time discussing options with others or privately mulling them over might be satisfying."
Web-design is another good example. There are typically so many ways of accomplishing something, that I actually don't spend much time thinking about it. But then later I found I could have done simpler and better with another approach.
Giving "free" choices to users just makes it more confusing. It's better to have one way of doing things than three that are kinda like the same but don't offer many advantages.
Optional for optional's sake doesn't help.
I think when coding the only "decisions" to be made were whether to make things public or not, whether to use pointer receivers or not (even that wasn't usually a decision), and how to do error handling (no language is going to do that for you).
Go was at version 1.5 (2015) when my copy of The Go Programming language was release and there has been exactly ONE major language feature: Generics.
Here's from my Go notes on releases:
Releases: https://go.dev/doc/devel/release
(Since 1.5, my book's version) 1.9: type aliases, type T1 = T2 (Since 1.12, when I last learned Go) 1.13: number literals improved, godoc removed from core: go get golang.org/x/tools/cmd/godoc godoc 1.14: overlapping interfaces, https://tinyurl.com/2fcyrnqm 1.17: slice to array conv https://tinyurl.com/y3xvpwud 1.18: GENERICS
“You didn’t even look at the back of the menu!!”
“Good point. I’ll start reading menus from random locations each time.”
Mine is:
'I like being surprised, if you have any love it or hate it "controversial" items I'd like to try that, otherwise surprise me :-)'
Along with a genuinely friendly demeanor it is almost always a delight.
Worst case scenario they just give me the most popular item on the menu, occasionally I get something weird tasting but never bad and always fun.
No menu required.
That's my hack when life is demanding that I make too many decisions and I'd like someone else to be taken care of that at meal time.
(Only when the server and environment doesn't seem soul crushing/crushed, I would never do this at a chotchkie's.)
Apparently they get sent back more often than they're eaten. I thought it was delicious (certainly not good if you don't like tripe!) and demolished it. The waiter confided that it's the one food that most reminded him of home, which was a human moment I still remember that I wouldn't have had if I'd ordered a steak frites.
We once had to shop for new curtains to decorate the new home we bought together. We walked into this giant store with 500 options and I directly walk to a rack and point at my preferred choice. She's puzzled and navigates the store for a full hour only to come back and confirm it to be the most favorable choice, much to her disgust.
At restaurants, I decide in less than a minute, which puts this hilarious time pressure on the other to make a choice. It completely ruins the "fun" ritual of pondering over choices and debating pros and cons with each other.
It's not that I'm some expert fast decision maker, it's pure and raw indifference.
For instance ask the waiter if he tried the items on the menu and pick the one he likes the best. (And if he didn’t tried most of them because he is new which one is the most popular). If it’s tech go to your best guy about the topic and ask him what you should pick.
It works well if you are good at choosing the right person. And for most not that important things since the person already have more information than you it will be better than flipping a coin.
Not sure that will do the trick... Imagine a long list with the only two satisfactory items being right next to each other... You'd almost always end up with the first in the list.
Picking a random direction is slightly more robust, but still fails sandwich scenarios... You need to shuffle the menu entirely somehow...
Or should the headline be “People Correctly Avoid Spending Too Much Time On Obvious Decisions”?
That's the premise of the article, yes.
As others have said, this isn't really a paradox. But it's interesting if you continue testing it with more and more trivial decisions. I think you probably reach a pleateau at some point, and actually one the decision reaches a certain point in triviality, decision time may actually decrease. The real factor here is humans' difficulty in quantifying the relative importance of things, especially their own opinions.
I read an article simular to this written by Oliver Burkeman a few years back and I was an eye opener for me, from which the above quote comes.
In short, if faced with two choices, the 'difficult' decision is the one where the answer is not clear and if that is the case, then it doesn't really matter so much the decision that you make, because you cannot know ahead of team or both options are equally as good, so most decisions should be easier, because either there is a clear choice, or there isn't but waiting longer to make it simply because it's not clear doesn't make a difference.
Article for reference: https://www.theguardian.com/lifeandstyle/2018/oct/19/this-co...
That last paragraph-sentence was very difficult to parse. I think it must be close to 100 words long!
The candy bar exercise is a good example of when it’s irrational.
The problem is that similar-seeming outcomes may be just that: _seemingly_ similar.
The university decision is a bad example of when it’s irrational. The search space is infinite, the variation in possible outcomes is high, and it’s very easy to overlook one or more critical factors.
The skill is then to be able to identify the threshold when all outcomes can be considered well-understood and when time spent deciding costs more than time sooner started.
When things are moving slow and surprises keep popping up, one could be acting irrationally in the way the author describes. When things are moving fast and surprises are minimized, no need to worry about spending too much time decision-making.
Then I discover the alternative is unsatisfying as well. Which causes me to spend time trying to understand why.
This seems rational and predictable. It would be wild if people spent more time evaluating decisions between vastly different values. “People spend too much time” on choice paralysis because they’re overwhelmed by too many hard to distinguish things.
The point is not that it's hard work to distinguish between similar option, the point is that people do it even if its clear it has no benefit from the very start. That's irrational. People even take it so far as to miss out on money straight in front of them, see dot counting experiment.
"Most people buy this product after viewing this listing"
They got rid of it, presumably because people started to only buy that item. But man it's hard to chose products now.
That way eventually I will eat all the favs, or I will learn some new information and realise that some are actually more or less desireable than I have thought.
You could try to pick the best option quickly based on immediately available/easily discernible information with the acknowledgement that you could be wrong, but it likely won't matter if you are.
While most of the examples in the article fall under "don't waste time on decisions that don't matter", one of them certainly does not: which university to attend. That is where you will live and work for the next 4-5 years. Given two equal status choices I would put a lot of research into the decision. Mainly to try to uncover anything I would strongly dislike - and have to live with - about either choice.
> If two gyms are equidistant from your house and you’re single and looking to meet someone, perhaps it would be wiser to join the gym that is next to a cafe or a grocery store.
If two gyms have nearly equal luck distributed across different categories, one might have more opportunity potential. If both gyms are next to a cafe or grocery store, perhaps it would be wiser to join the gym whose reviews and other online commentary, according to a semantic analysis, suggest people encounter new experiences there.
Simply put, given a continuous function mononically increasing from 0 to 1, given any degree of discernment X there will be some radius interval Y in which the function is closer than X to 1/2. And people won’t be able to tell for a while what’s better.
If you add random perturbations people will still be sitting there for a while figuring it out, because it could go either way.
Like a pencil which is almost perfectly balanced will take a long time to “figure out” which way to fall.
The interesting thing is that even if you had a timer to go off that said “if you haven’t made a decision by time Z, then choose the first one” there is also a nonzero probability that you won’t be able to tell whether you haven’t made a decision! It is also ambiguous. Read the paper… it took me a while to get it as I corresponded w Leslie about it
A software project may be late because it spent too much time to choose how to proceed. But it might also be late because it spent no time on choosing the best design to begin with and just chose a very bad design and went with it.
That is why my favorite metaphor for software design is the game of Chess. Every design choice you make may lead to a winning position, or losing position. If you lose you may be able to "play again". But maybe not, because of budgetary constraints.
There's just no Silver Bullet that would make you win in chess every time. But you can win sometimes, and get better at it.
The Sally-Ann problem is used to test "theory of mind" in autists: the subject watches Sally place a ball in box A and leave the room. Ann enters the room and removes the ball, placing it in box B. Sally returns to the room, looking for her ball. Which box will she open first?
Those supposedly without "theory of mind" will answer box B, because that's where the ball is. The correct answer is box A, because that's where Sally thinks the ball is.
For the scientists, the Kit-Kat and the Mars bar are equivalent, so taking a long time to choose between them is irrational. But what matters is not whether they are equivalent, it's whether they are equivalent to the chooser who must stop and consider their preferences before making a choice.
Maybe we should just strip this back to actual facts. Scientists observed that subjects in a trial typically spent 250ms longer choosing between a free KitKat & Mars bar (that they may receive after the experiment), than they did on choosing between two groups of random dots on a screen.
I would consider myself "filthy rich" when food just appeared for me.
The general problem of making choices with limited information reminds me of a thought experiment from business school: suppose you have a startup that's worth $5B if it succeeds or costs $1B if it fails. You could just try it, and succeed with 50% probability, or you could run a test that tells you for sure whether it will succeed or not. How much should you be willing to spend on that test? The expected value is $2B up front, but $5B if you know it will succeed, and you have a 50% chance that the test comes up positive, for a $2.5B expected value if you can run the test for free. That means you should be willing to spend up to $500M on the test! Hence venture capital.
So just decide by flipping a coin and move on to productive work!
Only applicable to certain cases, of course.
“Value” here means how much participants said they would be willing to pay for each item at the start of the study.
When shown a disfavored food alongside a favored food, people chose fast. When shown a favored food alongside another favored food, people took a while. But this is irrational (at least in the economic sense).
When making decisions, we spend too much time choosing between options with roughly equal utility.
How is this a paradox. I don't get it. Of course, if having to choose between a king-size KitKat vs. kid size Reece's or kid size Snicker's most will choose the KitKat because it's bigger, but otherwise will deliberate longer between the roughly equally-sized candy. Because they are not homogenous except for size. If they were identical, then it would be the same. Food has many other values besides utility, such as taste, which cannot be inspected in the same way size can be.
I can disprove the hypothesis above with a counterexample:
Which is the better deal if you're buying gasoline? 500 liters for ¥10000, or 100 US gallons for US$500?
The difference is huge. There's almost a factor of 10 difference in price per unit volume. But you have to spend significant time to figure out which is better. And it's easy to make the problem harder.
So the answer to the OP's question is no; if people take a long time to decide it doesn't necessarily mean that the options are roughly equal.
Abstract: Buridan’s principle asserts that a discrete decision based upon input having a continuous range of values cannot be made within a bounded length of time. It appears to be a fundamental law of nature. Engineers aware of it can design devices so they have an infinitessimal probability of not making a decision quickly enough. Ignorance of the principle could have serious consequences
It's also about what parts of both the cities I'd enjoy. Overall, they might be the same. But if I like some specific aspect let's say history, Rome is better. If I like diverse cuisines for instance, them Barcelona is better.
Plus there is always the implicit third option of "stay home and save all that money for something else", which also has to be considered.
"You just want us me make a decision and get it over with!"
"Yes! Exactly!!!"
Just thinking about it raises my anxiety and sense of hopelessness.
There's even a lived experience in where spending too much time deciding on one option leads to the same outcome anyway.
I've always believed that deciding early allows you to walk and eventually run if you start to experience success in that path.
Abundance of choice is just noise. Having less in life means you can do more.
If I’m happy, decision made. But if there’s a pang of regret or whatever… that means you actually prefer the alternate so should do that.
Admittedly I’m talking about stuff on the level of “What should I do for lunch” and not, say, career decisions
Heat pumps are trendy now, but with power blackouts in EU right now it feels like a really bad idea. Same with pretty much everything else.
So all options are not equally good. They are all equally bad.
The blog post could be better written though - it's super choppy.
I guess the problem is that people don't know what's important.
How long did it take people to choose between two disfavored options?
struck me as pretty creepy.
One classic result from biophysics is that, if all of your decisions have a fixed level of difficulty, then what the author suggests is (mathematically) proven to be suboptimal: if a decision feels more difficult, you actually should spend more time on that decision. (Keywords to search for: drift diffusion model[2], sequential probability ratio test[3])
The technical term for what the author is suggesting one should do (not spending so much time on decisions with equal outcomes) is an "urgency signal", or just "urgency" for short. If you are using an urgency signal, then you will spend less time on difficult decisions (i.e. ones with near equal outcomes) than you would without an urgency signal, but still more than you would easy decisions. (For easy decisions, you spend approximately the same amount of time regardless of whether you have an urgency signal.) In the extreme case, for an infinitely strong urgency signal, you will spend equal time on both easy and difficult decisions. (See Paul Cisek's work, e.g., [1].) Conceptually speaking, you need time to detect that the current decision has near-equal outcomes.
It was only recently (mathematically) proven that if you have different levels of difficulty in your decisions, it is optimal to use an urgency signal [4,5]. So since most sequences of decisions aren't all equally difficult (as in the study referenced here), in practice, people will use an urgency signal in decision-making.
Of course, both the desired accuracy and the urgency signal depend on how the decision is being evaluated: if your goal is to make an accurate decision (e.g. buying a house), then you will have a weaker urgency signal and require more evidence before you make a decision. By contrast, if you prioritise decision speed, you will show more urgency signal and require less evidence to make a choice. (The technical term is "speed-accuracy tradeoff".)
Current work suggests that when you are making some decision for the first time, you will not use an urgency signal, but as you become an expert at making those decisions, you will gradually develop an urgency signal [6]. This makes sense conceptually: if you know approximately how hard you can expect these decisions to be, you will recognise the situation where they have approximately the same utility and adjust your strategy accordingly.
[1] https://www.jneurosci.org/content/29/37/11560
[2] https://en.wikipedia.org/wiki/Two-alternative_forced_choice#...
[3] https://en.wikipedia.org/wiki/Sequential_probability_ratio_t...
[4] https://psycnet.apa.org/fulltext/2017-16730-001.pdf
[5] https://link.springer.com/article/10.3758/s13423-017-1340-6
[6] https://www.sciencedirect.com/science/article/abs/pii/S00100...