CEIC4000 Chap.6 Moral Reasoning for Engineers
Moral Reasoning for Engineers
Engineering ethics asks what is right or wrong in relation to others, not merely what is technically correct. This chapter separates facts from values, shows why an ought conclusion needs a moral premise, and compares consequential, duty-based and virtue reasoning. It also turns stakeholder lists into causal analysis and matches professional responsibility to the engineer's knowledge, influence and feasible action.
Consequential analysis considers magnitude, likelihood, timing, reversibility and distribution for both action and inaction. Duty reasoning tests obligations such as honesty, competence, consent and protection of public safety, while virtue reasoning examines practical wisdom, integrity, courage and humility. These lenses can support the same action for different reasons or expose a genuine conflict.
People are connected to the decision through concrete pathways of benefit, burden, consent and power rather than placed in a generic list. The final judgement names an actor, action, conditions and limits, then answers the strongest objection. This structure makes the moral bridge inspectable and prevents technical evidence from silently doing the work of a value premise.
What this chapter covers
- 01
Facts and values
- 02
The is-ought problem
- 03
Consequential reasoning
- 04
Duties and professional rules
- 05
Virtue and professional character
- 06
Stakeholders and proportionate action
Worked example · free
Make a hidden moral premise explicit
- 1State the evidence about loading, exposure and affected groups.
- 1State the principle against imposing serious avoidable harm.
- 1Identify the engineer's knowledge and channels for action.
- 1Recommend documentation, redesign and proportionate escalation.
Key terms
- Factual premise
- A testable claim about what is or may be the case.
- Value premise
- A claim about what matters or should be protected.
- Moral judgement
- A conclusion about what an actor ought or ought not do.
- Professional duty
- An obligation arising from a trusted specialised role.
Moral Reasoning for Engineers FAQ
Why can't evidence alone prove what an engineer should do?
Evidence establishes consequences, likelihoods and feasible options, but a duty also depends on a value or principle such as preventing avoidable harm, respecting rights or keeping professional promises. Making that premise visible lets the reader evaluate the logic.
Which ethical framework should I use?
Use the framework that illuminates the reasons relevant to the case, and consider whether another lens exposes a conflict. Consequences, duties and virtues can support the same action differently; the assignment rewards explicit reasoning rather than a prescribed label.
How specific should the ethical conclusion be?
Name the actor, action, conditions and limits. Match the demand to the person's knowledge, authority and feasible influence. A bounded duty to document, advise or escalate is often more defensible than claiming an individual engineer must control a national outcome.
Assessment move
Create two columns for facts and values, then write the ought conclusion beneath them. Test action and inaction, identify stakeholders through concrete effects, and state the strongest counter-reason. Revise until a reader can see why the principle applies to this actor in these circumstances and why the proposed response is proportionate. Begin a case analysis by describing the factual situation without evaluative adjectives.
List the likely consequences, their evidence, uncertainty and distribution, then write the moral premises separately. A statement that harm is possible does not itself establish what anyone should do; connect it to a reason such as avoiding preventable serious harm, respecting rights, honouring a professional promise or cultivating trustworthy judgement.
Test whether the same principle would apply if the preferred technology or institution changed. Use consequential reasoning to compare action and inaction across magnitude, likelihood, timing, reversibility and who bears each outcome. Use duty reasoning to identify obligations that should constrain even beneficial totals, including honesty, consent, competence and public safety.
Use virtue reasoning to ask what practical wisdom, courage, humility or integrity requires of a professional in the circumstances. These lenses need not produce identical answers, and disagreement is useful when it exposes a hidden premise. Map people through causal exposure rather than listing generic stakeholder labels.
For each group, identify the pathway to benefit or burden, their ability to influence the decision and whether effects are voluntary or imposed. Then specify the actor. Knowledge, authority, resources and available channels determine what action is feasible. An individual designer may document, advise or escalate; a manager may allocate resources; a regulator may set requirements.
Form the conclusion with an action, conditions, limits and review trigger. Present the strongest counterargument fairly, especially if it concerns uncertainty, competing duties, cost, mission, or unintended harm. Answer it by refining the principle or narrowing the action rather than dismissing it. Read the final argument as a chain: factual premise, moral premise, role premise, judgement.
If any link could be removed without changing the conclusion, the reasoning may be decorative. Ethical clarity comes from making contestable reasons inspectable, not from attaching an approved framework name after a technical recommendation.
