Strategies

Define and Apply Ethical Responsibility

Strategy · All strategies
Evidence · 4 claims (3 for, 1 mixed) · 10 studies (6 quant-synthesis, 4 causal), q2–q4 · 4 of 10 report an effect size

Description

This strategy has two halves that must both be present. Defining: making explicit what obligations a domain places on someone acting within it — what a researcher owes participants, a developer owes users, a clinician owes patients, a student owes the people whose work they cite. Applying: putting learners into concrete cases where those obligations conflict with each other or with self-interest, and requiring a decision with reasons. The definition alone produces learners who can recite a code; the application is where the learning is, because the difficulty in practice is almost never ignorance of the principle but failure to notice that it applies.

Design Implications

Rest's four-component model is the most useful frame for design, because it separates what an ethics activity can actually target. Acting ethically requires sensitivity (noticing that a situation has an ethical dimension), judgement (deciding which action is right), motivation (prioritizing the ethical over competing values), and implementation (carrying it through). Most classroom ethics instruction targets judgement, which is the component least often responsible for failure — professionals who behave badly usually did not deliberate wrongly, they did not notice, or noticed and were outweighed. Cases designed so the ethical dimension is announced train judgement; cases where the ethical issue is embedded in an ordinary technical problem train sensitivity, which is the harder and more transferable target.

The applying half works largely through argument. Requiring learners to construct and defend a position, and to engage with a genuinely opposed one, improves reasoning quality Argumentation Improves Reasoning [+M], and structured disagreement formats outperform open discussion for this Some classroom discussion approaches improve text comprehension, but gains are not uniform across approaches and more student talk alone does not produce them [+M]. Perspective-taking on the affected party is the other active ingredient Building Empathy Improves Intergroup Attitudes [+M].

Context

Requirements

Constraints

Implementation Variability

Target Learners

Target Learning Goals

Instructions

  1. Establish the obligations concretely. Work from the actual code, policy, or disciplinary norm, and identify the specific duties it names and to whom they are owed.
  2. Set discussion norms first. Agree how disagreement will work before opening a contested question (Norm Setting, Class Discussion Norms).
  3. Start with an embedded case. Give a task that looks technical and contains an unflagged ethical issue; see who notices, and make noticing the first discussion point.
  4. Require a decision, then the reasons. Have learners commit to an action individually and in writing before any discussion, so the discussion revises a position rather than forms one (Individual Reflection).
  5. Assign opposing positions. Structure the argument so each learner must construct the strongest version of a case they did not choose (Structured Academic Controversy).
  6. Foreground the affected party. Ask explicitly what the person on the other end of the decision experiences (Acting / Role Play).
  7. Move from judgement to implementation. Ask what they would actually say, to whom, and what it would cost them — this is where classroom ethics usually stops and where practice begins.
  8. Return to the code. Close by mapping the decision back onto the stated obligations, including where the code was silent or unhelpful.

Examples

Embedded-dilemma cases in software engineering: Students are given a feature specification to implement; the requirements quietly include collecting data the described use case does not need. Whether anyone raises it before writing the code is the assessed outcome.

Professional code application in clinical education: Trainees take a specific clause from their regulator's code and apply it to three cases where it conflicts with another clause, producing a decision and a justification for each.

Academic integrity as a live ethical question: Rather than a policy briefing, the class works through cases about collaboration boundaries and AI use in their own current assignments, and drafts the class's own working agreement.

Structured controversy on a disciplinary question: Pairs argue an assigned side of a contested question in the field, exchange sides, then attempt a joint statement — the swap being what forces engagement with the opposing case rather than rehearsal of one's own.

Key Sources

Page metadata
Field Value
type strategy
id define_and_apply_ethical_responsibility
title Define and Apply Ethical Responsibility
description Making the ethical obligations of a domain explicit, then having learners apply them to concrete, contested cases rather than affirm them in the abstract.
status review
generated by claude/unspecified on 2026-08-30
trust unverified — no one has confirmed this page's content
sources 3 — bebeau-1999, rest-1986, jagers-2019

Frontmatter is the page's machine-readable record — see the Schema & Guide.