EC-16.1 Public Safety and Professional Responsibility

What this is and why it exists

Engineering ethics is often taught as a list of principles nobody disagrees with, which is exactly why it does not transfer.

The difficulty is never in knowing the principle. It is in recognising the situation, under pressure, when everyone around you is reasonable and the conclusion is still wrong.

This topic is therefore built on cases and on the specific mechanisms by which competent organisations reach unsafe decisions. It is first in the module because the safety, environmental and standards topics that follow are applications of the same duty.

The vocabulary

• Professional code — a published statement of an engineer's obligations.
• Duty to the public — the obligation placed above the client's and the employer's interests.
• Competence — working only within what you are qualified to do, or saying that you are not.
• Normalisation of deviance — gradually accepting an anomaly because nothing bad has happened yet.
• Diffusion of responsibility — everyone assuming somebody else is checking.
• Conflict of interest — a situation where your interests could distort your judgement.

The mental model

Professional codes place public safety above the interests of the client and the employer. That ordering is stated first in nearly every such code, and it is what makes engineering a profession rather than a trade.

It is worth noticing what that ordering costs. It means there are instructions you may not follow, and it means the obligation does not depend on whether following it is convenient. A duty that only applies when it is convenient is not a duty.

Competence is the second obligation and the one most often failed, undramatically. Working outside what you are qualified to do, without saying so, is a professional failure even when nothing goes wrong.

What the obligation actually requires is one of two things: decline, or say clearly that you need review. Both are ordinary and neither ends a career. Silently proceeding is the failure.

Cases teach what principles cannot. Work through a documented case where an engineer's safety concern met a schedule or a cost. Read it slowly enough to notice that the people involved were competent and not villains.

That is the point of the exercise. A story about bad people teaches nothing transferable, because you know you are not one. A story about careful people who reached a wrong conclusion is a story that could include you.

The mechanisms are worth naming because they are recognisable in advance.

Diffusion of responsibility: everyone assumes somebody else is checking, and nobody is. Normalisation of deviance: an anomaly recurs, nothing bad happens, and it stops being an anomaly. Schedule pressure, which does not change any technical fact and changes what people are willing to say. And a burden of proof placed on the person raising the concern, so that a doubt has to be proved rather than resolved.

The last one is the most dangerous, because it inverts the safe default. Being asked to prove that something is unsafe, rather than being asked to show it is safe, is a warning sign in itself.

Raising a concern has a proper form. In writing, factually, through the internal route first, and keeping a record.

The record matters more than it seems. Escalating outside an organisation is a serious step with real consequences, and it is defensible only when the internal route was tried and documented. The record is what protects the person raising the concern, and it is written at the time or not at all.

Finally, conflicts of interest, which are usually misunderstood. Reviewing your own work, or recommending a supplier you have an interest in, is not automatically wrong.

Not declaring it is. The obligation is disclosure, and then somebody else decides whether the conflict matters. Deciding for yourself that it does not is precisely the judgement the rule exists to remove from you.

What you should now be able to explain or do

• State the ordering a professional code places on public safety and say what it costs.
• Recognise working outside your competence and say what the obligation requires.
• Read a case and identify the pressures rather than the villains.
• Name the four mechanisms by which competent organisations reach unsafe conclusions.
• Raise a concern in a form that is factual, internal first, and recorded.
• Declare a conflict of interest rather than judging its significance yourself.

Check yourself