Elizabeth Loftus first documented the misinformation effect in the 1970s through her research on eyewitness testimony. In her initial studies, participants watched videos of car accidents and were later asked questions containing misleading information. She found that this misleading information was often incorporated into their memories of the original event.

Later research expanded on these findings, showing that the misinformation effect occurs not just in experimental settings but also in real-world situations. Studies in the 1980s and 1990s demonstrated how media coverage, leading questions, and conversations with others could alter people’s memories of events they had personally experienced.

The strength of the misinformation effect depends on various factors, including the time between the original event and exposure to misinformation, the source’s credibility, and the individual’s confidence in their original memory. Research has shown that even when people are warned about the possibility of misinformation, they can still be susceptible to its effects.

For software teams, misinformation can significantly impact decision-making and project outcomes. When team members discuss past projects or previous decisions, their recollections might be influenced by subsequent conversations or documentation that contains incorrect information.

For example, during retros, team members might misremember the events that led to a particular problem, especially if there have been numerous discussions about the issue with different interpretations. This can lead to incorrect root cause analysis and ineffective solutions.

The effect can also impact documentation. If we don’t record decisions or rationalize them immediately, our memories might be influenced by discussions or assumptions, leading to inaccurate reporting and potentially misguided design decisions in the future. This can impact everything from roadmaps to user research.