Live data from Hacker News

When It's Bad to Have Good Choices

newyorker.com

71–80 of 89 posts

Re: When It's Bad to Have Good Choices

#71
Cognitive dissonance is a similar concept that is not new.

http://en.wikipedia.org/wiki/Cognitive_dissonance

As quoted from that article:

"Cognitive dissonance is also useful to explain and manage post-purchase concerns. If a consumer feels that an alternate purchase would have been better, it is likely he/she will not buy the product again. To counter this, marketers have to convince buyers constantly that the product satisfies their need and thereby helps reduce their cognitive dissonance, ensuring repurchase of the same brand in the future."

Sounds like the writer is referring to cognitive dissonance.

Leon Festinger published his work on cognitive dissonance in 1959 making his discovery 11 years before Lipowski's publication in 1970 (as referenced by the article). Festinger in my mind is the godfather of this theory. Anyone agree?

http://en.wikipedia.org/wiki/Leon_Festinger

Re: When It's Bad to Have Good Choices

#72

There are a couple of popular TED talks about choice. http://www.ted.com/talks/barry_schwartz_on_the_paradox_of_ch... It's something to keep in mind with your development work as well. Let's say you create an application to minify javascript. Your app has an input field, and a button that says 'Go', and that's it. Very simple, no confusion, people love it. However, you notice 5% of people don't use the app, because t…

Personally, while the research is interesting, I think it's also being far too overused as justification to remove/not add options. The common counterargument of "just use another product that does have the option you want" often turns out to be as fruitless - that other product may not have some option you want (that this one does), due to the same reasoning! I also fundamentally disagree that removing choices is a…

> I also fundamentally disagree that removing choices is a good thing

You may want to revise that perspective. Besides constraints being key to creativity, they are also key to good design. Every design needs to limit options.

Additionally, it doesn't directly follow that society will have their decisions made by other people; and to the extent that it does, it's not necessarily a bad thing.

Once again: fewer options -- constraints -- are key in creativity.

Re: When It's Bad to Have Good Choices

#73
This is why I hate that cinemas offer a choice between 2D and 3D. I just want to see whatever the director intended and not have to try to hunt down which version is 'better'.

Offering a choice makes going to the movies socially into an awkward experience. Inevitably there are people with diverging strong opinions and suddenly a social get together turns into dispute mediation. I think that if there was only one option, people would just deal with it.

Now I dread inviting certain people to the movies because I want a social experience without endlessly dragging up the 2D vs 3D debate.

Re: When It's Bad to Have Good Choices

#74

I was ecstatic when I got my first job offer. Then I got a second. And a few more rolled in. Choosing became the most stressful part of the job hunt. The companies I didn't pick made monster gains in the stock market --30% in one month. Cry me a river, right?

I feel realizing that one's stressing over "first world" types of problems just makes it worse by adding shame to the mix.

Re: When It's Bad to Have Good Choices

#75
post #36
post #25

Earlier quoted context omitted.

I've seen the "satisfice rather than optimize" meme a lot recently. I think it's a pretty weak argument. The problem is that there is still a potentially massive amount of calculations and predictions (about costs, opportunity costs, trends, etc.) required to choose a reasonable acceptability threshold. If you take more time to gather this relevant information you can probably choose a better acceptability threshold.…

It's not one argument. In its simplest form, take the digital camera megapixel race. Who in their right mind does anything useful with 20 megapixels, where most are buried in the noise levels for all common applications? Does that really need to be "optimized" further, even if it means quality and storage both suffers? A lot of real problems worked on in the industry could be described like that.

But if the satisficer's acceptability threshold is 25 megapixels, they're still not happy, and if their acceptability threshold is 0.5 megapixels, they'll be using a very noticeably poor camera.

Re: When It's Bad to Have Good Choices

#76

Earlier quoted context omitted.

Personally, while the research is interesting, I think it's also being far too overused as justification to remove/not add options. The common counterargument of "just use another product that does have the option you want" often turns out to be as fruitless - that other product may not have some option you want (that this one does), due to the same reasoning! I also fundamentally disagree that removing choices is a…

> I also fundamentally disagree that removing choices is a good thing - the research says it makes (most?) people feel better, which suggests that they don't want to think about making any choices because it is somehow difficult for them and causes anxiety. Logically, this means they would be most satisfied and happy if they didn't have to make any choices or do any thinking at all, and something/someone else made al…

Note: “equivocating” does not mean “equating”.

Re: When It's Bad to Have Good Choices

#77
I wonder if this phenomenon might be the primary factor in certain kinds of delayed marriage. I'm thinking, for example, of two people in their late 20s who have been dating for 5 years, figure marriage is in their future, but don't "feel ready".

Re: When It's Bad to Have Good Choices

#78
post #31

Earlier quoted context omitted.

paulsutter gave a good answer to this elsewhere in the comments. But I would add this: All other things being equal (or roughly equal), pick one at random. Sure, there's opportunity cost, but there are also costs way beyond the time you take fretting over a decision. You said it yourself: You're "crippled" by anxiety. How is that better than making a random decision? Or just going with your gut?

I think it's naive to assume that simply making a random decision would remove or reduce anxiety. Anxiety doesn't only come from the fear of regretting your decisions; it also comes from the fear of receiving a negative outcome, even if that outcome was "chosen" by a coin flip or a third party. Hence people are anxious to receive news after a job interview, or a call about a loved one's medical condition, despite bot…

It's not that making a random decision will remove or reduce anxiety. It's that making a non-random choice 1) won't improve the predicted outcome and 2) won't reduce or remove the anxiety either.

Given the alternatives of either 1) not making a decision, 2) drawing out the decision for a long time, or 3) failing to act in time on the option, simply making a random initial commitment addresses the decisionmaking aspect.

Many decisions are capable of being reversed or changed later. If you're ever in a situation where you must decide (stay or jump from a burning building, say), there's still likely to be an option which is least bad. Even those who jumped from the WTC on 9/11 were making a decision. The outcome wasn't optimal, but in the circumstances, it may well have been preferable to the alternative.

Re: When It's Bad to Have Good Choices

#79
I see a lot of decisionmaking especially as it's foisted on the public in commercial choices to be largely false alternatives.

That is, there are a large number of options presented, under the guise of "choice is good", for which the ultimate effects of the outcome are "it doesn't matter".

The choices are also often not presented in a way that makes discriminating between alternatives straightforward. I'm reminded of a financial news program whose sponsor for a time was a credit card company bragging about "over 3,000 choices for consumers" in credit card options. That is, frankly, stupidly excessive.

But there are ways to present choices in a way which offers a very high level of tailoring of options without overwhelming the user with those options. I like to use the example of automobile heating/cooling controls common in the 1980s-1990s (the tendency toward thermostatic controls is changing this now).

For American car manufacturers, the preferred style was a heat control lever which went from low to high, a fan switch, usually with "flow", "lo", "med" ,and "hi" settings, and a vent + AC selector. This would allow for dash, floor, or defrost vents to be selected, as well as another addition set of vent settings in which AC was enabled. The presentation always struck me as confusing, and there were a number of vent/AC settings which weren't reachable.

This is pretty typical: http://www.autopartsdb.net/images/productimg/C/CX1884.JPG

Imports from Japan and Europe typically had four controls: a fan switch, a heat slider or dial, and a vent selector, plus an independent AC control. The method seemed a lot more sensible to me: are you hot (turn up the heat) or cold (turn on the AC), how much air do you want flowing (fan) and where do you want it (vent selector). Figuring out how to set the controls always seemed far more intuitive to me than the American controls.

Typical: http://www.autoecu.com/images/ebay/01%20-%2007%20TOYOTA%20HI...

One more recent modification is that often the AC is automatically activated (and sometimes cannot be deactivated) when defrost is selected, as the humidity reduction tends to improve defrost performance.

There's a similar design issue I've noticed particularly with clothes washers, where one style seems to specify the type of article you're washing: "knits", "delicates", "colors", "whites", and the other the specific wash conditions you want: water temperature, a

See: http://content.aolstatic.net/ProductImages/rvLarge/ZWG6141P_... (article descriptions)

vs. load size, temperature, options, and agitator settings: http://www.ajmadison.com/ajmadison/images/large/GTWP1800DWW_...

My observation is that I know the settings I want to apply, and where "outcomes" controls are specified, I've got to translate these into the settings I hope to achieve. What I prefer are options which allow me to select for settings, preferably along a range (e.g., heater intensity, fan power).

Another point is that in consumer goods, the distinctions between products very nearly always simply doesn't matter.

In a Starbucks world, there's a coffee roaster I love which has an exceptionally simple product line. Light roast. Dark roast. Regular. Decaffinated. And you can get your beans whole or ground if you like. But basically four choices. The beans are, of course, excellent.

I've elected for choice in many food purchases by avoiding mainstream grocery stores (the news late this week of P&G killing off a bunch of brands strikes me as comically irrelevant). While I've fewer "options" than MegaMonSantoFoods when shopping at Trader Joes, what I do have are generally simpler, less expensive, less processed, and healthier products. I've long since abandoned prepared breakfast cereals for oats (and add my own nuts, dried fruit, or other ingredients as I prefer). Fresh fruit and vegetables, meat, dairy, and eggs are generally non-branded. Store products for cleaning, or vinegar and baking soda (both of which are surprisingly difficult to find in straighforward bulk forms) work fine. And the costs are lower.

My personal sense is that branding jumped the shark somewhere in the 1970s to 1980s, though we're only just starting to be aware of this in a broader sense.

Re: When It's Bad to Have Good Choices

#80
post #33

This article focuses on the choice you have as a consumer. Which brand, which flavor, which stack of hay? But I observe a similar crippling effect when working on software. Every step along the way of producing a software product involves making an incredible amount of choices. Choices like, 'what platform?', 'what programming language?', 'which algorithm?', etc. I believe that the the freedom we have as a software e…

Anecdote/data-point 90% of my side-projects never got out of "playing with the tech stack" phase.

It is definitely not optimal, but is pretty common methinks.

Post reply on HN