Live data from Hacker News

Common-knowledge effect: A bias in team decision making

nngroup.com

41–50 of 59 posts

Re: Common-knowledge effect: A bias in team decision making

#41
post #21

Familiarity is a huge factor in decision-making. Apple, a multi-billion dollar company, made the Apple Watch to track your health. Something was missing for half of the population: cycle tracking. No decision maker was familiar enough with women's health to understand the importance of aligning cycle information with other health information.

People keep repeating this story, but is there any real evidence to support that this was actually an oversight, and not a deliberate decision? Apple has a long history of making decisions that seem to go against what users want, like removing the headphone jack, and making a wireless mouse that can't be used while charging. Both of these decisions were made deliberately and intentionally. For the headphone jack, it…

did not see any of the large companies include such a simple and obviously useful app. my guess is it's too much responsibility and lawyers are against it

Re: Common-knowledge effect: A bias in team decision making

#42

Familiarity is a huge factor in decision-making. Apple, a multi-billion dollar company, made the Apple Watch to track your health. Something was missing for half of the population: cycle tracking. No decision maker was familiar enough with women's health to understand the importance of aligning cycle information with other health information.

> Something was missing for half of the population: cycle tracking Can a watch detect this? What does that add vs an app that a cycle is input into?

The watch doesn't necessarily detect cycles directly. Cycles can influence things a fitness watch traditionally tracks. There was no option for input in the OS.

Re: Common-knowledge effect: A bias in team decision making

#43

Does anyone actually believe that teams make better decisions than individuals?

Depends on situation and conditions. In this UX case, assuming that information is ready, a team of 10 UX experts with similar expertise and have been working together for some time will reach the good decision.

A team consist of CEOs, managers, devs, UX, marketing/sales & finance won't get the same level of decision assuming the information is ready. However they'll be useful for information / idea gathering / brainstorming when the information is not ready, for a single person / team to make decision.

My past experience sums up to this:

* Team of similar expertise & knowledge: good & fast on decision making, lack on seeking knowledge in other part of expertise

* Team with variety of expertise & knowledge: will make slow & bad decisions more than good or fast one, in exchange of decent chance of knowledge sharing for each expertise

Of course the quality of each member, how can they work as a team, whether they have hidden personal agenda / hating each other plays part in the quality and speed of decision making too

Re: Common-knowledge effect: A bias in team decision making

#44
post #40

Earlier quoted context omitted.

> Anybody who tries to score points by pointing out weaknesses is toxic to open and honest collaboration. probably well intended, but no.

You might want to elaborate

S/he probably means you should be able to point out weaknesses. But that's another thing from doing it in a scoring-points way.

Re: Common-knowledge effect: A bias in team decision making

#45

Does anyone actually believe that teams make better decisions than individuals?

I'd say teams are way more likely to avoid clearly bad decisions.

Now your statement is so clearly absolutist in its tone, so to speak specifically, I would say teams will largely point to the best outcome eventually but often pays the bill in over lost efficiency.

Individuals make bad takes, sometimes they have personality issues, sometimes then have a terrible day and are dialing it in at work who knows. What I know is that it's less likely that an entire team are living their worst day at the same time which could lead to catastrophically bad decisions.

Re: Common-knowledge effect: A bias in team decision making

#46
post #11

This study is comparing individuals having complete knowledge vs. a team with individuals having incomplete knowledge. Yes, the communication complexity tax must be paid. What am I missing?

you're missing what the summary says: teams often make worse decisions than individuals by relying too much on widely understood data while disregarding information possessed by only a few individuals

This is a group effect quite often seen in other places.

Tornado chasing is a good example. Take an experienced tornado chaser near a storm, and they will commonly back off at a safe distance when things are looking sketchy.

But if you take that same chaser and put them in a group of people of varying skill levels they can get complacent and stay in a dangerous area much too long. Because the low skilled people are commonly worse at identifying dangerous situations, they don't begin to worry/panic in situations they should. The higher skilled people will commonly ignore their own feelings in that case, probably because of some kind of innate human group dynamics, where we see those people being call and think they are misjudging the situation.

Re: Common-knowledge effect: A bias in team decision making

#47
post #10

>> Deliberating in person isn't superior to online. According to research by Simon Lam and John Schaubroeck, virtual teams are more likely to overcome the common-knowledge effect compared to face-to-face teams, perhaps due to easier access to notes and materials. That was an interesting observation, although the study didn't mention that another confounder could have been non-verbal communication often being much mor…

Yes and the section "Team Decision Making" is really unclear about how exactly "Afterward, team members got together and were given 10 minutes to share, discuss, and determine the best project" happened:

- were each participant's rank, credentials, job title, age, experience visible ("7% Execs, 4% Prod/PM, 4% Marketing, 44% Designers , 23% UX Researchers, etc.")? Were the participants or their ranks known to each other beforehand?

- was it a roundtable? huddle? debate? unstructured free-for-all? egalitarian? squabble? shouting-match? Did they take a show-of-hands (or voice-vote) at the start and/or end to find out who chose which option?

- how exactly did the discussion dynamic go, which people or considerations dominated it, how did people decide who to let speak or listen to? Did people defer to the perceived expert/ highest ranking person/ perceived spokesperson for the majority opinion/ loudest person, or not? There can be multiple cultural and nonverbal factors. Were the Designers (or UX Researchers) more influenced by their peers than other people? Did participants make statements like "in my X years experience as Y, criterion Z is important"?

- I think the researchers (Nielsen Norman) should have run multiple controls where the same group of people get the same statements, but then vary both the "discussion" format and participants (e.g. different subsets of 7 from 9) to see how much that influences the outcome. And then do it on Slack and/or Zoom (both text-only, voice-conf and video-conf) and measure the influence of that too. Or even old-school (asynchronous email): limit the "discussion" to each participant can write one group email to everyone else, then they have 10min to individually consider their decision. And also measure whether it's influenced by whether they're anonymous, or sign their full name, or include job title.

Re: Common-knowledge effect: A bias in team decision making

#48
post #10

>> Deliberating in person isn't superior to online. According to research by Simon Lam and John Schaubroeck, virtual teams are more likely to overcome the common-knowledge effect compared to face-to-face teams, perhaps due to easier access to notes and materials. That was an interesting observation, although the study didn't mention that another confounder could have been non-verbal communication often being much mor…

Is that a confounder? I think that's an essential difference between the online and in-person experience.

Re: Common-knowledge effect: A bias in team decision making

#49
post #21

Earlier quoted context omitted.

People keep repeating this story, but is there any real evidence to support that this was actually an oversight, and not a deliberate decision? Apple has a long history of making decisions that seem to go against what users want, like removing the headphone jack, and making a wireless mouse that can't be used while charging. Both of these decisions were made deliberately and intentionally. For the headphone jack, it…

> I can easily imagine that Apple omitted period tracking intentionally to position these products as aimed at young professionals who take their health and fitness seriously, […] not menstruating women. Yup, like for example Mikaela Shiffrin who doesn’t take her fitness seriously [1]. Or Wimbledon tennis players [2]. Not like those young professionals… 1. https://time.com/6279881/periods-sports-gender-bias/ 2. https…

Of course there's overlap. The idea is that they are avoiding the overlap, even though it would be a good feature.

Re: Common-knowledge effect: A bias in team decision making

#50
It seems like a rather artificial scenario due to the available information being explicitly written down? And yet they reproduced the effect. That’s pretty interesting.

Would it still happen if people were told what the experiment was about and they came up with a strategy first? One strategy might be to copy everything they got to their notes and combine them at the beginning of the meeting.

I wonder if there’s a lesson in that for real life.

Post reply on HN