What are the most common biases that lead to conflict in network engineering?

1 Confirmation bias

Confirmation bias is the tendency to seek, interpret, and remember information that confirms one's existing beliefs or assumptions. For example, a network engineer may favor a certain vendor, protocol, or design over others based on their previous experience or preference, and ignore or dismiss evidence that contradicts their choice. This can lead to suboptimal solutions, wasted resources, and resistance to change. To avoid confirmation bias, network engineers should seek diverse perspectives, challenge their own assumptions, and test their hypotheses with objective data.

2 Anchoring bias

Anchoring bias is the tendency to rely too much on the first piece of information that one receives when making decisions or judgments. For example, a network engineer may estimate the cost, time, or complexity of a project based on the initial proposal or budget, and fail to adjust their expectations when new information or challenges arise. This can lead to unrealistic deadlines, scope creep, or overspending. To avoid anchoring bias, network engineers should gather multiple sources of information, update their estimates regularly, and set realistic goals and contingencies.

3 Availability bias

Availability bias is the tendency to judge the likelihood or importance of something based on how easily it comes to mind. For example, a network engineer may overestimate the frequency or severity of a certain problem or threat based on their recent memory or exposure, and neglect other factors or scenarios. This can lead to misallocation of resources, overreaction, or complacency. To avoid availability bias, network engineers should use reliable data, statistics, and trends, and consider alternative explanations and outcomes.

4 Framing bias

Framing bias is the tendency to be influenced by the way that information is presented or worded. For example, a network engineer may be more likely to agree or disagree with a proposal or suggestion based on how it is framed in terms of benefits, risks, or options. This can lead to biased evaluations, misunderstandings, or missed opportunities. To avoid framing bias, network engineers should focus on the facts and logic of the information, and ask for clarification or rephrasing if needed.

5 Groupthink bias

Groupthink bias is the tendency to conform to the opinions or decisions of the majority or the leader of a group, and suppress one's own doubts or objections. For example, a network engineer may go along with a plan or policy that they disagree with or have concerns about, because they want to avoid conflict, criticism, or isolation. This can lead to poor quality, errors, or ethical issues. To avoid groupthink bias, network engineers should encourage diversity, dissent, and debate, and seek feedback from outside sources.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?