Sharks in Engineering Waters

How Conflict Contributes to Healthy Tech Teams

Many engineers initially perceive visible conflict as an uncomfortable state to be eliminated or avoided – a sign that something is wrong. However, this perspective misses a crucial insight. Conflict is not a symptom of a problem but a necessary component for achieving excellence together.

What we call "conflict" in organizational communication doesn't mean hostility or dysfunction; it implies a difference of opinion, priorities, or agendas. The need for different perspectives is precisely why we are all here. You're in the room for your perspective and have a professional obligation to provide it.

A Misunderstood Indicator of Health

Sharks have acquired a fearsome reputation among various populations as apex predators. Yet, marine biologists recognize that the presence of sharks is one of the most reliable indicators of a healthy ocean ecosystem. Their absence typically signals a disturbing imbalance in the underwater environment. This understanding has led to a paradigm shift in marine conservation, where protecting sharks is increasingly viewed not just as species conservation but as ecosystem management. 

Similarly, conflict in engineering teams has earned an undeserved negative reputation (of course, there are situations where a toxic culture weeps the reputation is sows). Many leaders mistakenly work to eliminate visible disagreement, creating an artificial peace that masks deeper problems. But just as shark populations indicate thriving oceans, visible conflict often signals a healthy engineering culture where team members care deeply about outcomes and feel safe enough to voice dissenting opinions.

Forward-thinking engineering organizations don’t simply tolerate disagreement or manage it as a necessary nuisance. Instead, they recognize that healthy conflict is central to creating environments where technical innovation thrives. Just as marine conservation has evolved to protect sharks for their ecosystem-wide benefits rather than only the species itself, good engineering leadership nurtures productive conflict for its organization-wide benefits rather than resolving individual disagreements.

Our Professional Obligation

When you withhold your perspective during technical discussions, you're not just being passive—you're actively depriving your team of your expertise and insights. Research by Kathleen Eisenhardt and her colleagues at Stanford University suggests that high-performing technical teams engage in what they call "cognitive conflict" - substantive, issue-oriented differences in perspectives and opinions. Their studies found that teams engaging in frequent but constructive disagreement made better decisions and developed more innovative solutions than teams that avoided conflict.

Silent teams might appear harmonious on the surface, but this harmony often masks deeper issues: fear of speaking up, disengagement from outcomes, or lack of diverse perspectives. As organizational psychologist Amy Edmondson notes in her research on psychological safety, "The absence of conflict is not harmony, it's apathy."

There's an important reciprocal relationship here: while individuals have a professional obligation to contribute their perspectives, organizations have an equal responsibility to create environments where it's safe to do so. If you're in an organization where speaking up is punished or ignored, the problem isn't your reluctance to contribute—it's the toxic ecosystem. The obligation to speak up exists within the context of psychological safety. Fix the environment first, then expect the voices to follow.

The Real Problem: Underdeveloped Communication Skills

What technical organizations typically lack isn't the creative tension that drives innovation but the communication skills necessary to harness this tension productively. Engineers are trained to solve technical problems, not necessarily to navigate the nuanced interpersonal dynamics that emerge when strong-minded individuals collaborate. Conflict resolution expert Robert Bales' Interaction Process Analysis states that teams need both task-oriented and socio-emotional communication skills to function effectively. While engineering education emphasizes the former, it often neglects the latter.

Creating Conditions for Healthy Conflict

Just as ocean ecosystems require specific conditions to support shark populations and overall marine health, engineering organizations need an intentionally cultivated environment where productive conflict can thrive. Psychological safety is at the core of this ecosystem – the foundation upon which all other elements depend.

Psychological Safety

Psychological safety, extensively researched by Edmondson at Harvard Business School, creates the essential bedrock for productive conflict. In psychologically safe environments, team members believe they won't be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes. Google's Project Aristotle confirmed this, finding psychological safety the most important factor in effective teams – more important than technical expertise or project clarity.

Within this secure environment, four interconnected elements work together to nurture and channel productive conflict:

Leadership

Leaders establish the flow and direction of conflict by creating clear "rules of engagement." An organization’s leadership shapes how conflict moves through the organization. If you’re not the official leader, you can still drive change in how your team experiences conflict. Drawing on Deborah Tannen's work on conversational styles, here are some initial strategic communication steps that teams can take to encourage and protect healthy conflict:

• Define what productive conflict looks like for your team. Here are some examples from Discernible clients: 
  • Team A: Productive conflict means challenging technical approaches with specific concerns backed by data or experience. When disagreeing with a proposed solution, we articulate the risks we're worried about or the constraints we're considering rather than simply rejecting ideas. We focus our disagreements on the work product's alignment with our reliability standards and user needs, not on preferences or style. 
  • Team B: Productive conflict looks like rigorous questioning of assumptions behind models and analyses. We expect team members to ask 'How did you arrive at that conclusion?' and 'What alternative interpretations might explain these results?' Constructive disagreement involves suggesting additional tests or controls rather than simply criticizing work. 
  • Team C: Productive conflict in our design reviews means bringing up potential failure modes, integration challenges, or maintenance concerns early in the process. We differentiate between 'must fix' issues that violate requirements or create safety concerns versus 'could improve' suggestions. When raising issues, we articulate the specific impact on system performance, user experience, or manufacturing costs. 
  • Team D: Productive conflict means proactively challenging security assumptions and threat models rather than waiting until after implementation. When questioning a security approach, we articulate specific vulnerabilities or attack vectors we're concerned about, rather than making vague statements about 'bad security.' We distinguish between high-priority issues that create immediate risk exposure versus security debt that should be addressed in future iterations. 
• Establish frameworks for raising and addressing disagreements (provide team members with concrete steps to get started since not everyone comes equipped with these skills, which sets clear expectations and removes uncertainty about how others will respond when concerns are raised).
• Articulate what success means in conflict resolution for your team (collective advancement, not individual victory). Here are examples from the same clients as above:
  • Team A: Success in our conflicts means we've thoroughly examined multiple approaches before choosing a direction, with everyone having had the opportunity to raise genuinely considered concerns.
  • Team B: We know our conflict is healthy when it leads to more robust findings, documented limitations, and clearer communication of uncertainties in our analyses.
  • Team C: Our conflicts are working well when previously unseen problems are caught early and when critiques lead to measurable improvements in the final design rather than just changes for the sake of change.
  • Team D: Our conflicts are constructive when they lead to stronger security postures and maintainable solutions that don't unnecessarily impede business operations. Success means we've thoroughly evaluated the security/usability tradeoffs and can clearly explain our risk-based decisions to both technical and non-technical stakeholders.
• Model healthy conflict behaviors, demonstrating that disagreement is valued and expected – showing where you draw boundaries around unproductive conflict so team members understand both the importance of speaking up and the guardrails that keep discussions constructive.

Communication Frameworks

Communication frameworks provide the structural support where conflict interactions can safely occur. These frameworks give team members concrete tools to navigate difficult conversations productively.

Two powerful frameworks to consider include:

• Nonviolent Communication (NVC) by Marshall Rosenberg, which builds interactions around:
  • Observing without evaluating
  • Identifying and expressing feelings
  • Connecting feelings to needs
  • Making clear, actionable requests
• Crucial Conversations by Patterson, Grenny, McMillan, and Switzler, which offers structured approaches for high-stakes discussions where opinions vary and emotions run strong

Reward Systems

Reward systems determine what behaviors flourish or diminish within the organization. Traditional reward systems often inadvertently nourish conflict avoidance while starving productive disagreement. The result is a culture where problems remain hidden, diverse perspectives are suppressed, and teams produce mediocre solutions that nobody strongly opposed rather than excellent solutions that were thoroughly vetted and improved through constructive challenge.

You can redirect these flows to recognize and reward behavior that:

• Identifies important disagreements early
• Navigates technical conflicts with respect and professionalism
• Reaches decisions that incorporate diverse perspectives
• Learns collectively from conflicts and improves your conflict resolution processes

Implementation

Finally, implementing this ecosystem requires systematic, adaptive approaches. 

Here are a few suggestions for organizations who want to ensure productive conflict can thrive within their team: 

• Assess current conflict patterns using tools like the Thomas-Kilmann Conflict Mode Instrument, a five-category scheme for classifying interpersonal conflict-handling modes: competing, collaborating, compromising, avoiding, and accommodating. 
• Train teams in specific communication frameworks like NVC or Crucial Conversations
• Create explicit norms around constructive disagreement (you can use the steps outlined in the “leadership” section above)
• Institute regular retrospectives focused on conflict processes (All good communication is deliberate. You will not be effective accidently.) 
• Recognize and celebrate examples of well-managed conflict 

Your Perspective

Remember that you weren't hired despite your unique perspective – you were hired because of it. You're not fulfilling your professional responsibility when you remain silent in the face of potential issues or alternative approaches. The most successful technical organizations don't eliminate conflict; they cultivate environments where conflict is a catalyst for improvement rather than a source of division. In doing so, they unlock their teams' diverse perspectives and expertise, driving both technical excellence and organizational health. Just as sharks are essential to ocean ecosystems, professional disagreements are vital to your organization's health. Your perspective isn't just welcome; it's necessary.

If your interested in strengthening your team’s skills in communicating and navigating conflict, ask about Discernible’s customized programs, team workshops, and individual coaching here.