Skip to main content
Version: 2.0

Encouraging Ethical Decision Making

For two decades, I’ve led engineering teams through countless technical challenges. But the hardest challenges aren’t always about code; they’re about choices. Choices made under pressure, with incomplete information, and often with significant consequences. As engineering leaders, we spend a lot of time defining what to build. We need to spend just as much time cultivating how and why we build it – focusing on the ethical foundations of our decisions.

Too often, “ethics and compliance” feels like a check-box exercise. We deliver training, write policies, and hope for the best. But ethical behavior isn’t about blindly following rules; it’s about internalizing a framework for making good choices, even when no rule explicitly covers the situation. It’s about fostering a culture where people feel empowered – and obligated – to do the right thing, even when it’s hard.

The Illusion of Control & The Power of Choice​

Methodologies alone aren’t enough. We can impose processes, dictate standards, even build sophisticated monitoring systems. But these tools are ultimately ineffective if the people using them don't choose to prioritize ethical considerations.

I've seen this firsthand. Years ago, I led a team developing a feature for a social media platform. The initial design prioritized engagement above all else – maximizing clicks, shares, and time spent on the platform. It worked, but data quickly revealed a troubling side effect: the algorithm amplified polarizing content, contributing to echo chambers and increased user anxiety.

We had a policy about responsible design, but it was easily circumvented by the pressure to deliver results. The team hadn't consciously chosen to prioritize user well-being. They’d optimized for a single metric, ignoring the broader ethical implications.

This incident solidified a key lesson: Ethics isn’t about control; it’s about influence. We can't make people be ethical. We can only create an environment where ethical choices are the easiest, most natural choices to make. It's about encouraging a proactive consideration of the impact our work has on others.

Building a Framework for Ethical Decision-Making​

So, how do we shift the focus from compliance to choice? Here's a framework I’ve found effective:

  • Lead by Example: This sounds obvious, but it's crucial. If you consistently demonstrate ethical behavior, even when it’s inconvenient, you set the tone for the entire team. That means admitting mistakes, prioritizing transparency, and advocating for responsible design.
  • Normalize Ethical Discussions: Don't treat ethics as a separate topic reserved for annual training. Integrate it into your regular team meetings and code reviews. Ask questions like: “What are the potential unintended consequences of this feature?” or “Who might be negatively impacted by this design choice?”
  • The Benefit of Others Lens: Consider the impact of your work on all stakeholders – users, colleagues, the company, and society as a whole. Before launching a new feature, have the team brainstorm potential negative impacts and mitigation strategies. It’s a critical practice to proactively anticipate how our designs might affect those beyond our immediate team.
  • Empower and Protect “Voice of Conscience”: Create a safe space for team members to raise concerns without fear of retribution. A culture of psychological safety is paramount. I’ve had engineers push back on designs they felt were exploitative, and I always supported their courage, even if it meant delaying a launch.
  • Focus on “Why” Not Just “What”: In technical design reviews, spend as much time discussing the rationale behind decisions as you do the technical implementation. Why are we building this feature? What problem are we solving? What are the ethical considerations?

Technology as an Enabler of Ethical Choice​

Building a culture of ethical choice isn’t solely about process; technology can actively support our efforts. We can leverage “nudges” – subtle changes to the environment that encourage desired behaviors – to reinforce ethical considerations within our workflows.

For example:

  • Automated Ethical Checklists: Integrate checklists into your CI/CD pipeline that prompt developers to consider potential ethical implications of their code.
  • Real-Time Impact Assessments: Develop tools that provide data on the potential impact of new features on different user groups.
  • Transparency Dashboards: Make data on the ethical performance of your products publicly available.

These tools aren't about imposing restrictions; they're about making ethical considerations more visible and accessible throughout the development process.

The Ongoing Responsibility​

Fostering a culture of ethical choice isn’t a one-time fix. It’s an ongoing process that requires constant attention, reinforcement, and adaptation. It requires us, as engineering leaders, to move beyond simply enforcing rules and instead focus on cultivating a sense of shared responsibility and moral courage within our teams.

The best "methodology" isn’t a set of rigid procedures; it’s a commitment to doing the right thing, even when it's hard – and empowering others to do the same.

Now, let's challenge ourselves: Share this article with your team and start a discussion about how you can collectively foster a stronger culture of ethical choice within your organization. Evaluate your current processes to identify areas where you can empower your team to make more informed and ethical decisions.