"Technology is not neutral. Whoever builds it decides who it serves."
Interfaces designed to trick user clicks (dark patterns). Personal data shared without real consent. Algorithms calibrated to exploit human anxiety or hide fees at checkout. Technology can be an extraordinary tool for efficiency and liberation, but it can also serve as a mechanism of manipulation. The difference is never in the compiler or the database: it lies in the moral choices of those who design, approve, and build.
Throughout a career in technology and business, every professional inevitably encounters grey zones: moments where a technical or contractual loophole allows for easy short-term gains at the expense of customer or partner trust. It is precisely at these crossroads that the character of a leadership and the longevity of a company are defined.
The newspaper test
Before implementing a dubious business rule, approving a silent data collection, or exploiting a contract loophole, apply a simple filter that I call the newspaper test: if the behind-the-scenes details of that decision were to appear explained on the front page of a newspaper tomorrow morning, read by your customers and your family, would you feel pride or shame?
If the immediate response is discomfort or the need to invent technical excuses, stop. What needs secrecy against the user to work is rarely a good business.
Three common dilemmas and the excuses that numb the conscience
When technical or commercial teams cross the ethical line, they almost never view themselves as villains. They use three classic rationalizations to outsource their own responsibility:
1. "It is what the client or the board asked for"
Meeting goals is part of the job, but when you technically know that an implementation will lead the end user astray, expose sensitive data, or create a hidden security risk, blindly executing in silence is outsourcing your professional ethics. Mature professionals have a duty to warn about the consequences.
2. "Everyone in the market does it"
Statistical normalization is not a moral justification. If five competitors use tricks to prevent a client from canceling a subscription, the practice remains dishonest and shortsighted.
3. "It is not illegal"
Legislation always trails technology by years. The fact that a technical loophole has not yet been explicitly prohibited by law does not make it correct. Legality is the minimum baseline to avoid being sued; ethics and good faith are the foundation of trust.
The economy of trust: what Kenneth Arrow, Covey, and Elinor Ostrom say
Treating ethics merely as a nice philosophical discourse is an error of economic analysis. In 1972, economist Kenneth Arrow, winner of the Nobel Prize in Economics, demonstrated in the classic study Gifts and Exchanges that trust is the invisible lubricant of any economic system. According to Arrow, practically every commercial or technical transaction possesses some degree of information asymmetry; if each party tries to exploit all available loopholes, the entire system stalls in audit costs, litigation, and paralysis.
Later, Stephen M. R. Covey synthesized this effect in management with a direct equation in the book The Speed of Trust (2006): when trust in a team or company decreases, speed drops and cost rises. Lack of ethics functions as a hidden tax charged on every meeting, every contract, and every line of code.
Similarly, political scientist Elinor Ostrom, laureate with the Nobel Prize in Economics in 2009 for her work Governing the Commons (1990), proved that sustainable environments of high cooperation do not survive solely on good intentions: they demand clear rules, transparency in monitoring, and real consequences for opportunistic behaviors that attempt to gain an advantage at the collective expense.
How to build an ethical culture in practice
For integrity to be part of daily engineering and not just a plaque in the reception area, three practices are non-negotiable:
1. Open discussions in product design
Create explicit space in architecture and product reviews for the team to ask: "Is this transparent with the user?" Questioning the ethical or privacy impact of a feature should be treated as professional diligence, never as insubordination.
2. Diversity of perspectives at the table
Overly homogeneous teams share the same blind spots. People with different backgrounds, life experiences, and educations spot collateral risks that would go unnoticed by a closed group.
3. Visible consequences and leadership coherence
If someone reports an unethical practice or a serious governance failure and nothing happens (or worse, the whistleblower suffers retaliation while someone who hit the target using dirty shortcuts is promoted), the real message sent to the entire company is crystal clear: ethics here is just theater.
The mark left on your career
Companies change owners, products go offline, and technologies age, but your name and reputation stay with you throughout your professional life. Shortcuts based on loopholes may seem smart at month-end closing; in the long run, they destroy the only asset that cannot be bought back: the credibility of your word.
Build systems, contracts, and decisions that you would be proud to explain in detail to your children. This remains the best management filter I know.
Continue deepening: read also Categorization and Priority and Culture that Secures or Sabotages. Also learn about work in Executive Engineering Leadership and the Case Studies.
References and verifiable readings
- Arrow, K. J. (1972). Gifts and Exchanges. Philosophy & Public Affairs, 1(4), 343-362.
- Covey, S. M. R. (2006). The Speed of Trust: The One Thing That Changes Everything. Free Press.
- Ostrom, E. (1990). Governing the Commons: The Evolution of Institutions for Collective Action. Cambridge University Press.
Good ideas keep the conversation going.
Share this article or publish the visual deck to your Stories and Feed.

Cesar Zanis
15+ years leading software architecture, database performance, FinOps, and applied AI across enterprise operations. Built and scaled an engineering organization from zero to 20+ developers.
Enjoyed this article?
I publish practical analyses on critical systems architecture, Cloud FinOps, data, AI, and engineering leadership directly on LinkedIn.
Continue Reading
Take this analysis further with data and sources
All visual cards of this article are ready above to share on your Stories, Feed, WhatsApp, or LinkedIn with full sources.



