Ethical AI is not a compliance checkbox you tick after launch — it is a set of requirements you treat like reliability, usability or security, from the first sprint to production monitoring. That is the core of "Ethics by Design" (EbD): incorporate ethical principles into the development process so that, as Philip Brey and Brandt Dainow put it in their AI and Ethics paper, "the final tests for ethical compliance should be mere formalities to confirm what has been monitored and built into the system from the beginning." This guide translates that methodology into concrete actions developers can take to protect user autonomy and privacy.
Introduction: Beyond Compliance – The Ethics by Design Imperative
The European Commission's Horizon ethics guidance describes the central approach plainly: "The aim of Ethics by Design is to incorporate ethical principles into the development process allowing that ethical issues are addressed as early as possible and followed up closely during research activities." The guidance is explicit that this applies to any development methodology — AGILE, V-Model or CRISP-DM — and should be tailored to the type of system, since ethical risks differ between the research phase and deployment.
In my experience reviewing AI projects, the failure mode is almost always the same: ethics arrives late, as a review gate, when the architecture is already fixed. The EbD approach inverts that. Brey and Dainow note it "is not something which can be isolated from the rest of the developers, but requires a cultural adjustment so that it permeates the entire development organisation." For a developer, that means ethical requirements belong in your backlog, your specs and your test plans — not in a policy document nobody on the team reads.
Understanding Human Agency: Autonomy, Freedom, and Dignity in AI
Before the checklist, the "why." The EU guidance grounds six general ethical principles in the Charter of Fundamental Rights, and the first is respect for human agency: "human beings must be respected to make their own decisions and carry out their own actions," which "encapsulates three more specific principles, which define fundamental human rights: autonomy, dignity and freedom."
Brey and Dainow's framework turns these values into design requirements. An AI system "should not be designed or used in a manner which deprives people of the ability to make decisions which they should be able to make for themselves," nor "in a way that results in the reduction of basic human freedoms, including freedom of movement, assembly, speech and information." In practice, that means users must be able to understand what the system does, retain control over decisions that matter to them, and have genuine options to opt out or override. The second principle — privacy and data governance — holds that people's rights to privacy and data protection "should be respected at all times."
The Ethics by Design AI (EbD-AI) Development Lifecycle
How do you operationalize this? Brey and Dainow propose a generic model of AI development tasks, then a mapping procedure: "Map the tasks described in the generic model into one's chosen methodology. Determine which ethical requirements are relevant within each stage of that methodology. Use this to create a list of ethical requirements for each stage." The tasks need not follow a strictly linear progression — in an AGILE environment, some phases iterate multiple times.
The essential move is scope: EbD-AI takes ethical issues into account "throughout the entire development process, treating them just like any other 'more technical' requirements." The EU guidance adds a practical tool for the data stage: "Datasheets for Datasets can be employed to assess the ethical characteristics of data." Its summary of requirements is blunt — AI systems must not negatively affect human autonomy, freedom or dignity, and must not violate privacy and personal data protection.
Ethics by Design AI Development Checklist
The table below maps the abstract principles onto verifiable actions at each lifecycle stage. Use it as an audit instrument: walk your project through each row and confirm the action is present in your actual artifacts, not just your intentions.
| Development stage | Ethical principle | Required action |
|---|---|---|
| Project scoping & requirements | Human agency (autonomy, freedom, dignity) | Write ethical requirements into system specifications alongside technical requirements; identify which decisions users must retain and which freedoms the system must not reduce. |
| Project scoping & requirements | Transparency | Specify clear explanations of AI functionality so users can make informed choices. |
| Data governance & handling | Privacy and data protection | Apply privacy by design: build protections in from the start, not as an afterthought; minimize collection, retention, sharing and use; limit processing to stated purposes. |
| Data governance & handling | Accountability | Assess data's ethical characteristics, e.g. via Datasheets for Datasets. |
| Model design & implementation | Human agency | Design so the system does not deprive people of decisions they should make for themselves; provide user control, opt-out and override paths. |
| Testing & validation | All principles | Treat final ethical-compliance tests as confirmations of safeguards built in from the beginning, not as first encounters with the issues. |
| Deployment & monitoring | Continuous oversight | Verify ethical compliance and performance after launch; adapt to ethical challenges as they emerge; default to privacy-protective settings with accessible controls for reviewing, restricting, exporting and deleting data. |
Because the mapping is methodology-agnostic, the same rows apply whether you run sprints or a waterfall plan — the stages iterate, but the requirement list travels with them.
Avoiding Dark Patterns: Protecting User Autonomy and Privacy
The checklist has an adversarial counterpart: dark patterns. CDT's taxonomy of dark patterns in AI chatbots recommends minimizing data collection, retention, sharing and use, defaulting to privacy-protective settings, and giving "timely notices in simple language to users when data policies change, with a grace period to adjust settings as needed."
Chat interfaces carry a specific hazard: the chat format itself "signals that the conversation is private," while in reality staff across safety, product and research teams may routinely access chat logs. Lex Dinamica's analysis of consent architecture offers a sharp diagnostic question for any designer: "is it as easy to refuse as it is to agree? If the answer is yes, you're on the right path." Consent obtained through manipulative design is not just unethical — it is unlawful processing that exposes the controller to liability.
Actionable Steps for Ethical AI Development
Developers should proactively integrate the Ethics by Design framework into their AI development lifecycle, treating ethical requirements as core technical specifications from the initial stages. The payoff is concrete: when ethics is scoped, designed, tested and monitored like any other requirement, autonomy and privacy protections stop being launch-week scrambles and become properties of the system itself.
You can verify successful integration through the presence of explicit ethical considerations in project requirements, design documents, data governance policies, and continuous monitoring protocols. If those artifacts name human agency, privacy and user control at every stage — and your consent flows pass the "as easy to refuse as to agree" test — the framework is working. If they don't, that is your next backlog item.
Sources
- Ethics by design for artificial intelligence - AI and Ethics — SpringerLink
- EC
- Privacy by Design – AI Ethics Lab — Aiethicslab
- CDT
- Dark patterns and ethical design in data privacy — Lex Dinamica
