The Ethics of Expertise: When You Know More Than Your Stakeholder

What moral obligations arise when you know more than your stakeholder?

The same obligations that arise in any relationship of information asymmetry: the duty to inform honestly, the duty not to exploit the knowledge gap, and the duty to advocate for the stakeholder’s genuine interests even when those interests conflict with what is easiest for you.

A product manager asked me if we could add a real-time analytics feature to our platform. I knew we could. I also knew that doing so would require architectural changes that would increase our infrastructure costs by approximately $14,000 per month and introduce latency into our existing batch processing pipeline. The stakeholder did not know this. They saw a feature request. I saw a tradeoff.

I had 3 options. First, say “yes, we can build that” (technically true, ethically incomplete). Second, say “yes, but here are the costs and tradeoffs” (honest and complete). Third, say “no, that is not feasible” (dishonest, but convenient). The ethics of expertise require the second option. It is also the most uncomfortable, because it forces a conversation the stakeholder did not expect and a decision neither party fully controls.

Why does the technology industry lack a professional ethics framework for this?

Because software engineering has not codified the fiduciary duty that medicine and law have developed over centuries. There is no engineering equivalent of “informed consent” for technical decisions with business consequences. The result is ad hoc ethics that depend on individual character rather than institutional structure.

Medicine developed informed consent because patients died when doctors made decisions without explaining them. Law developed fiduciary duty because clients were harmed when lawyers prioritized their own interests. Technology has not yet had its equivalent defining crisis, the moment when the absence of professional ethics becomes undeniable. But the privilege escalation problems in AI-generated code suggest that moment is approaching.

I have worked in 7 organizations. None had a formal framework for how technical experts should communicate risks to non-technical stakeholders. Every organization relied on the individual engineer’s judgment and communication skill. This is like relying on individual doctors’ judgment without requiring informed consent. It works when the individuals are ethical. It fails catastrophically when they are not, or when they are overworked, rushed, or incentivized to suppress complexity.

What would a professional ethics of technical expertise look like?

It would require three things: informed consent for technical decisions with business impact, a fiduciary duty that prioritizes the stakeholder’s long-term interests over short-term convenience, and institutional structures that protect engineers who deliver uncomfortable truths.

• Technical informed consent: Before any decision with significant technical tradeoffs, the stakeholder receives a plain-language explanation of the costs, risks, and alternatives. Not a 40-page technical document. A clear, honest summary that a non-expert can act on.
• Fiduciary framing: The engineer’s loyalty is to the stakeholder’s genuine interest, not to the easiest implementation. This means sometimes recommending against what the stakeholder wants, because what they want is not what they need.
• Protection for candor: Engineers who honestly communicate technical risks should be protected, not penalized. The infrastructure of psychological safety is a prerequisite for ethical expertise.

What happens when expertise ethics are absent?

Decisions are made on partial information, costs emerge as surprises, and trust erodes. The stakeholder who discovers they were not informed about a known risk does not blame the system. They blame the expert. And they are right to.

I witnessed a situation where an engineering team knew that a proposed feature would require 6 months of maintenance effort that the product team had not accounted for. The engineers did not communicate this clearly because “the product team would not understand the technical details.” The feature launched. The maintenance burden materialized. The product team was angry. The engineering team said “we tried to tell them.” But they had not tried hard enough, and the failure was theirs. According to professional ethics frameworks, the expert bears the communication burden, not the non-expert.

This principle extends to the relationship between stakeholder communication and information design. The quality of your communication is your responsibility, not your audience’s.

“The expert who withholds information because the stakeholder would not understand it has failed their ethical obligation. It is the expert’s job to make it understandable.”

The information asymmetry between technical experts and their stakeholders will only grow as systems become more complex. The ethical framework for managing that asymmetry will either be developed intentionally, through professional standards and institutional structures, or it will be developed reactively, through lawsuits and regulations after harm has occurred. The choice is ours. And the first step is recognizing that knowing more than your stakeholder is not a privilege. It is a responsibility.