Technologist’s Hippocratic Oath

March 9, 2018 Mariesa Dale

An optional oath for building ethically considered experiences.

“Our very lives depend on the ethics of strangers, and most of us are always strangers to other people.”
— Bill Moyers, Former White House Press Secretary

Technologists today wield a powerful tool. We are designing, prioritizing, and putting things out into the world, affecting people we have never met. We are on their wrists, in their laptops, in their pockets, and thus, in their heads. Sometimes the ethics are in clear black and white, but at other times it can be a bit more complicated.

I was lucky to be in the audience to witness Alan Cooper’s recent talk at Interaction 18, which he kicked off by asking a room full of technologists to imagine some scenarios, including the following:

  • You are the data analyst that helps build a nearly-perfect targeted ad platform that powers a billion-dollar business. But then foreign hackers use it to influence a presidential campaign and attack a representative democracy.
  • You write a machine-learning spell-check algorithm, the best in the world and deployed globally. But one day it auto-corrects some prescription drug names into different drug names, causing harm to innocent people.

The point of examples like these are not to blame the technology or it’s makers. The point is to illustrate the responsibility we bear for what we make. As Cooper says in his talk, we move forward not just by patching holes in current technology, but by preventing these kinds of abuses from being an option in future technology.

Which brings us here.

Everyone draws their lines in different ways and perhaps there is a spectrum of what is reasonable when implementing influential products. That’s exactly why technologists must seek to educate themselves on the patterns they are implementing in order to understand their psychological influence and other outcomes where intended use is not always the same as the reality of the user experience. Not only that, but we should feel empowered to speak up to authority when something crosses a line.

Even with the formidable power we wield on day-to-day lives as engineers, designers, product managers, data scientists, etc., there is very little education and oversight on ethics in our industry. And I’m not the only one having this moment of introspection — it’s felt all over, from an iPhone creator to Y Combinator’s leader and more.

This discovery process drove me to understand better those industries which do incorporate ethical standards into their professions, and led me create a version of the physician’s Hippocratic Oath, but for technologists. While this is not the first pledge for tech employees, and it will not be the last, it is part of this new world where we can no longer be ignorant of our responsibilities and the potential ramifications of our work.

Originally this was a personal endeavor, made as a standard that I could adhere to myself during a period of especially consequential design work. But as I’ve slowly widened the circle of colleagues I’ve shared it with, some of them have also found value in it. Perhaps you will as well.

Technologist’s Oath:

I swear to fulfill, to the best of my ability and judgment, this pledge:

I will remember that users, individually or collectively, are not numbers or a goal, they are people and must be respected.

I will respect the hard-won professional and creative gains of those technologists that came before me, and I will gladly share my knowledge with future generations.

I will apply my abilities for the benefit and value of the end user, and I will advocate when the goal of a product comes into conflict with this.

I will remember that there is art to technology as well as science, and that empathy, craft, and remaining mindful about the consequences of my decisions outweigh the importance of my technical knowledge, the impulse for financial benefit, or allure of status.

I will not be ashamed to say “I don’t know,” nor will I fail to call upon my colleagues when the skills of another are needed for deeper critique or diversity of thought.

I will respect the need of my users to maintain healthy relationships with technology. For every problem I attempt to solve, I will strive to directly connect with the audience of the solution I create.

I must tread with care in matters of life balance and manipulation, ceasing involvement when ethical dilemma or moral recklessness arise.

I will strive to positively influence the lives of those impacted by the technology I build, but I acknowledge that it may also be within my power to negatively impact a life to serious consequence; this awesome responsibility must be faced with great humbleness and awareness of my own limitations.

I will remember that I do not build merely platforms, applications, or websites but that my work affects human beings in the end, whose capacity or ability to use my creation may affect their family, economic stability, or mental well being. My responsibility should include any directly related outcomes, if I believe I have crafted a truly ethical product.

I will prevent exploitation of users whenever I can, for prevention is preferable to extrication.

I will remember that I remain a member of society, with special obligations to all my fellow human beings, those sound of mind and body as well as the disabled or moderately impaired.

Above all, I understand that I am the gatekeeper; placing greater concern in the consequences of the technology I build over that of obeying authority. If I do not violate this oath, may I enjoy life and my craft, respected while I live and remembered with esteem thereafter. May I always act so as to preserve the highest standards of my calling and may I long experience the joy of helping those who explicitly or implicitly seek my help through the experiences and products I help put into the world.

You can share this pledge, or fork it into your GitHub profile, or rebound on Dribbble.

Change is the only constant, so individuals, institutions, and businesses must be Built to Adapt. At Pivotal, we believe change should be expected, embraced, and incorporated continuously through development and innovation, because good software is never finished.

Technologist’s Hippocratic Oath was originally published in Built to Adapt on Medium, where people are continuing the conversation by highlighting and responding to this story.

Using VMware’s Harbor with PKS (and Why Kubernetes Needs a Container Registry)
Using VMware’s Harbor with PKS (and Why Kubernetes Needs a Container Registry)

Container registries add important security features to Kubernetes. This post details how Harbor, part of P...

Use Value Stream Mapping to Guide Your Software-Driven Future
Use Value Stream Mapping to Guide Your Software-Driven Future

Value stream mapping is a proven way to improve the pace and reliability of software delivery. This blog su...


Subscribe to our Weekly Newsletter

Thank you!
Error - something went wrong!