Moral Technologists – Who We Are

Moral Technologists is an ethics advisory firm. We help organizations that build, use, or fund powerful technology with the decisions that law and compliance policies leave open. This includes choices about whether to build a feature at all, the values which it should encode, what it will change, and how it will impact internal and external stakeholders.

These decisions are made every day by engineers, product leaders, counsel, and executives, regardless of whether they call them ethical decisions. Our work is to make sure that they are made deliberately, early, and collectively, with ethical foresight and judgment. Convening these groups early reveals viable options that neither group would find alone.

In our experience, technical teams lack a shared vocabulary for resolving ethical tensions across engineering, product, and legal functions. We work cross-functionally with engineers, product leaders, counsel, and policy staff to treat the human impact of their systems as a core technical discipline. Our goal is to build lasting internal capability with you.

Our Focus

Organizations have a wide range of mechanisms available to support responsible innovation. The formal ones, so-called hard controls, are the explicit plans, policies, and procedures, including codes of conduct, ethics and compliance training, and review boards that assess products against principles, security, and privacy standards. The informal ones, soft controls, are the values, expectations, and assumptions that prevail in an organization without being written down.

While necessary for risk management, these controls usually intervene only after engineering teams have already settled core technical commitments. The choices that determine a technology’s impact happen much earlier across multiple levels: in product teams scoping a design, in procurement teams selecting software to adopt, and in executive leadership approving contracts or funding ventures. Together, these distributed commitments establish an organization's trajectory and ethical posture. Across these settings, standards vary widely. Engineering sees the decision through scale and performance, product through adoption, legal through regulatory exposure, communications through reputation. Each view is accurate, but they do not capture the whole picture alone.

Moral Technologists works where those crucial decisions are made. We connect the teams designing and deploying systems with the leaders accountable for their legal, regulatory, and reputational consequences. Together, we resolve immediate technical dilemmas while establishing the internal practices organizations need to evaluate future technologies independently. The result of our approach is a decision every function involved can stand behind, because each helped shape it. It is written into the documents your teams already use, with a record of how you reached it.

Typical Situations That We Help With

Here are some examples that illustrate the kinds of questions that we help with:

You are designing, launching, or investing

• Your team is designing a model whose outputs will shape consequential decisions about people who will never see it. Engineering, product, and legal each see part of the problem.

  Which affected perspectives must you bring in before core screening criteria are locked

• Your R&D lab is commercializing a breakthrough technology ahead of any established industry standards or regulations.

  How do you gauge public acceptance before launch, and how should those expectations alter your product specifications?

• Your launch date is set with a strong business case, but some of your best engineers are uneasy.

  How do you tell an objection that should stop you from one you can address after launch?

• You ship the same product in thirty international markets with contrasting legal regimes and cultural expectations.

  Did your team default to headquarters' legal assumptions about privacy and fairness, and how do you audit for local conflicts?

• You are considering an investment in a company whose AI could take over service work such as customer support, claims handling, and bookkeeping across an industry. If it succeeds, many of those jobs will disappear.

  Which part of that outcome falls on you, and what should you ask of the company before you proceed?

A customer or the public is pressing you

• A defense or policing customer wants your technology.

  On what terms, if any, do you take the contract, and what are you still responsible for once they have it?

• A newly deployed system causes public harm, prompting immediate scrutiny from regulators, your board, and the press.

  Can you explain the decisions that led here, and what will you change before the next launch?

• Your largest customer asks you to switch off a safeguard and says a competitor will sell them a version without one.

  Where is your red line, and how do you explain it to the customer?

You are bringing new technology into your organization

• Your research teams want to use generative AI for hypothesis generation, but senior researchers worry the tools compromise scientific rigor.

  How do you separate valid discovery acceleration from statistical noise, and what verification standards will you mandate before publishing?

• You plan to use AI across your organization, and it will change or remove work your employees value.

  Which tasks should change, how much discretion should people keep, and what say should they have in the redesign?

• Your agency is procuring technology to make the public safer.

  Which uses can you justify to the people it affects, and at what point does protecting them become paternalistic control?

Your decisions are adding up to a direction

• You have grown quickly, and people who joined for what you stood for are leaving.

  How do you keep your founding commitments at scale?

• Every compromise seemed reasonable during design and building.

  Taken together, would you have chosen where they have led you?

• Others in your field watch what you do and typically copy it.

  What long-term industry precedents and regulatory scrutiny are your current technical choices creating?

How We Work

We work at different stages and in different situations. Some engagements concern a single decision, such as a launch, an architectural choice, a contract, or an investment. Others concern decision rules for engineers, technology strategy, or research on what an emerging capability will change for your organization. In every case we bring the people who design, build, and research together with the people who make the legal, risk, policy, and executive decisions, and where a perspective is missing from the room we bring it in ourselves.

Depending on the engagement, we do the analysis and advise, or we guide your team through the reasoning so that the conclusions are its own. Our work typically has four steps:

1. Make assumptions explicit: We state, or help your team state, what the plan takes for granted, namely whom it serves, what counts as success, and which values it already encodes.
2. Widen the view: We evaluate the technology from the standpoint of the groups whom it will affect, including edge cases, vulnerable groups, and secondary users whom nobody had in mind when it was scoped.
3. Work through the tensions: We identify where objectives conflict, such as fairness and accuracy, or data utility and privacy, and we ask first whether a change in the design dissolves the conflict. We weigh the trade-off with reasoning tools from ethics and we write down why the balance falls where it does.
4. Commit: We turn the conclusions into commitments owned by the people who will act on them, written into the documents that they already work from, including product requirements, engineering acceptance criteria, risk frameworks, policies, and UX research plans for subsequent operationalization.

This work strengthens your existing governance. A decision that every function helped shape reaches formal review with clearer documentation, fewer objections, and less of the late-stage rework that stalls a launch.

Our Services

We provide external soft controls. Our approach is based on the Moral Imagination method, which we developed with Google’s AI teams over a decade and validated through peer-reviewed research. Since then we have adapted it for research institutions, public bodies, and companies that develop, use, and sell technology.

We also design governance structures and help set technology strategy, but we start from a different place than most AI governance and strategy consultancies. Where they typically begin with the structure, such as a risk framework or a strategy template, we begin with what is at stake in your decisions, for whom, and which values conflict, and we build the rules or the strategy from there.

Formats

Clients can enter through any of these formats, and engagements often combine them. An advisory session can show that a question needs a full analysis. An analysis can supply the questions and scenario material for a workshop. Recurring issues from analyses and workshops can become organization-wide rules through governance.

Engagements usually begin with an orientation call to define project scope and immediate priorities. Six months after implementation, we can return to assess how decisions are holding up in practice and help teams course-correct.

Our Team

We have extensive experience at the intersection of technical development, law and policy, and academia, and we translate between ethics and engineering practice. We work independently from reporting lines and delivery incentives which allows us to challenge assumptions that are difficult to raise internally, and to provide a second opinion on contested decisions.

Our founding partners are: